Opened 14 years ago
Closed 13 years ago
#28547 closed defect (fixed)
libiconv: checksum error because mirrorservice.org distfile is corrupted
Reported by: | gnormington@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | ||
Port: | libiconv |
Description (last modified by mf2k (Frank Schima))
I have upgraded to macports 1.9.2 by downloading a dmg. I am using svn rather than rsynch so selfupdate does not update macports itself, but otherwise seems to work. However, I cannot install libiconv:
# port install -d libiconv ---> Computing dependencies for libiconv ---> Verifying checksum(s) for libiconv Error: Checksum (md5) mismatch for libiconv-1.13.1.tar.gz Error: Checksum (sha1) mismatch for libiconv-1.13.1.tar.gz Error: Checksum (rmd160) mismatch for libiconv-1.13.1.tar.gz Error: Target org.macports.checksum returned: Unable to verify file checksums Log for libiconv is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_textproc_libiconv/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets>
I have tried:
#port clean --all libiconv
and it didn't help.
Attachments (1)
Change History (12)
Changed 14 years ago by gnormington@…
comment:1 Changed 14 years ago by gnormington@…
I have attached main.log which was produced after cleaning libiconv so the download server shows up there.
comment:2 Changed 14 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to ryandesign@… |
Port: | libiconv added |
comment:3 follow-up: 4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Status: | new → assigned |
---|---|
Summary: | Checksum errors installing libiconv → libiconv: checksum error because mirrorservice.org distfile is corrupted |
Confirmed, the file being offered by http://www.mirrorservice.org/ is corrupted. At nine different places in the file, it is all zeroes:
- starting at 0x008000: 2560 bytes
- starting at 0x008E00: 512 bytes
- starting at 0x00B600: 512 bytes
- starting at 0x00C000: 1024 bytes
- starting at 0x00C600: 1536 bytes
- starting at 0x00CE00: 512 bytes
- starting at 0x00D200: 512 bytes
- starting at 0x10C000: 512 KB
- starting at 0x20C000: 512 KB
I will remove this mirror from the mirror list for this port, and will inform the administrators of this mirror. In the meantime, you can fetch the correct distfile from our main mirror http://distfiles.macports.org/libiconv/ and place it in /opt/local/var/macports/distfiles/libiconv/.
comment:4 follow-up: 7 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to ryandesign@…:
I will remove this mirror from the mirror list for this port
Actually it's coming from the gnu fetchgroup common to many ports. I removed it from there in r76498. Hopefully the administrators of this mirror will resolve the issue quickly and we can reinstate the mirror then.
comment:5 follow-up: 6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to gnormington@…:
I am using svn rather than rsynch so selfupdate does not update macports itself
FYI, using svn instead of rsync for your ports tree has no effect whatsoever on MacPorts' ability to selfupdate itself. selfupdate continues to use rsync. If your reason for using svn instead of rsync for the ports tree is that your network blocks rsync traffic, then that would explain an inability to use selfupdate, and using the dmg instead is a fine alternative.
comment:6 Changed 14 years ago by gnormington@…
Replying to ryandesign@…:
Replying to gnormington@…:
I am using svn rather than rsynch so selfupdate does not update macports itself
FYI, using svn instead of rsync for your ports tree has no effect whatsoever on MacPorts' ability to selfupdate itself. selfupdate continues to use rsync. If your reason for using svn instead of rsync for the ports tree is that your network blocks rsync traffic, then that would explain an inability to use selfupdate, and using the dmg instead is a fine alternative.
A new network policy at work is indeed the reason I used a dmg.
comment:7 Changed 14 years ago by gnormington@…
Replying to ryandesign@…:
Replying to ryandesign@…:
I will remove this mirror from the mirror list for this port
Actually it's coming from the gnu fetchgroup common to many ports. I removed it from there in r76498. Hopefully the administrators of this mirror will resolve the issue quickly and we can reinstate the mirror then.
Still no dice I'm afraid. Do I have to do something other than clean and retry? (If selfupdate is necessary, I'll need a dmg.)
comment:8 follow-up: 9 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
You need to update your ports tree using "sudo port sync" or whatever method you usually use to do so. (The dmg contains MacPorts base only, not the ports tree.)
comment:9 Changed 14 years ago by gnormington@…
Replying to ryandesign@…:
You need to update your ports tree using "sudo port sync" or whatever method you usually use to do so. (The dmg contains MacPorts base only, not the ports tree.)
That worked a treat. The ticket can be closed from my perspective. Thanks.
comment:10 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
comment:11 Changed 13 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
log file