Checksum error for libgnomeui-2.24.1

[jean_seb@…]

Again while trying to install gimp (see Ticket #20163), I'm getting a checksum error for libgnomeui:

[...]
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/python25
DEBUG: Searching for dependency: python25
DEBUG: Found Dependency: receipt exists for python25
DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig
DEBUG: Searching for dependency: pkgconfig
DEBUG: Found Dependency: receipt exists for pkgconfig
DEBUG: Executing org.macports.main (libgnomeui)
DEBUG: Skipping completed org.macports.fetch (libgnomeui)
--->  Verifying checksum(s) for libgnomeui
DEBUG: Executing org.macports.checksum (libgnomeui)
--->  Checksumming libgnomeui-2.24.1.tar.bz2
Error: Checksum (md5) mismatch for libgnomeui-2.24.1.tar.bz2
Portfile checksum: libgnomeui-2.24.1.tar.bz2 md5 8e7d36dd1decfcf5cc4d5cb93bc4d217
Distfile checksum: libgnomeui-2.24.1.tar.bz2 md5 15efcbaa884f821635b7d6eeee2966d6
Error: Checksum (sha1) mismatch for libgnomeui-2.24.1.tar.bz2
Portfile checksum: libgnomeui-2.24.1.tar.bz2 sha1 b95cd3da3908896bd09b129bcbe3a6eba7d37dd5
Distfile checksum: libgnomeui-2.24.1.tar.bz2 sha1 68706c6b1f61fb03eb41dd1a0e99bf0e80f63c2b
Error: Checksum (rmd160) mismatch for libgnomeui-2.24.1.tar.bz2
Portfile checksum: libgnomeui-2.24.1.tar.bz2 rmd160 b8c57e6cf2ba1667f7926b135121ef34e8c4167d
Distfile checksum: libgnomeui-2.24.1.tar.bz2 rmd160 6befb82e3e2e542a01e0ef3c7c1854847fc53c36
The correct checksum line may be:
checksums           md5     15efcbaa884f821635b7d6eeee2966d6 \
                    sha1    68706c6b1f61fb03eb41dd1a0e99bf0e80f63c2b \
                    rmd160  6befb82e3e2e542a01e0ef3c7c1854847fc53c36
Error: Target org.macports.checksum returned: Unable to verify file checksums
Warning: the following items did not execute (for libgnomeui): org.macports.activate org.macports.extract org.macports.checksum org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install
Error: The following dependencies failed to build: gimp-app gimp2 libgnomeui libmng lcms libwmf poppler openjpeg poppler-data py25-gtk py25-cairo py25-numpy fftw-3 py25-nose py25-setuptools py25-gobject gimp-jp2 gimp-lqr-plugin liblqr gtk-nodoka-engine coreutils gmp gutenprint icns-gimp macclipboard-gimp macfile-gimp ufraw exiv2 gtkimageview xsane sane-backends libusb
Error: Status 1 encountered during processing.

I tried doing a selfupdate to see if this was something that would have been fixed in the mean time, but re-running 'sudo port -d install gimp' still gives the same result.

[jean_seb@…]

Rerunning 'sudo port -d install libgnomeui' after a 'sudo port clean --all libgnomeui' now results in the package installing properly. I was able to go on installing gimp (which is compiling now, all its dependencies have been installed).

Not sure if someone fixed something on the servers, but I had done a clean --all a few times before and it had had no effect, so I'm not sure what was different this time. In any case, this ticket can be closed. Next time I'll try multiple times before opening a ticket.

[blb@…]

libgnomeui, like most gnome ports, tries to fetch from the gnome master_sites, which is a list of various servers. If you happen to know which server gave the bad file, we may be able to track down the issue and/or remove that server so others don't use it. Unfortunately, unless you used -d when port fetched the bad file, it won't say from which server it fetched.

[jean_seb@…]

Hi, yes I used -d but I've since closed the Terminal. Does port log these things to a log file somewhere? If so I'll be able to post the info, but otherwise we're out of luck and we'll have to wait for someone else to have the same problem... But I'll know for next time.

[blb@…]

Replying to jean_seb@…:

Hi, yes I used -d but I've since closed the Terminal. Does port log these things to a log file somewhere? If so I'll be able to post the info, but otherwise we're out of luck and we'll have to wait for someone else to have the same problem... But I'll know for next time.

It doesn't currently keep a log (that's being worked on as part of this year's Google summer of code). If you do hit a checksum issue again, the originating server would definitely be a good bit of info to see if another can reproduce the bad file; other than that, see the FAQ entry about checksums.

[jean_seb@…]

Yes I saw that FAQ. I also saw some mailing list posts about manually changing some checksums in ports so that something might install.

Thanks for the tip, if I ever get that problem I'll be sure to post the server it came from (which also means I'll be running with -d all the time from now on...).