Trying to recompile ImageMagick today I found that the tarball of the version in portage (media-gfx/imagemagick-6.1.8.8) is not anymore on the upstream FTP. Instead there are the newer versions 6.1.9-4 and 6.2.0-4, the latter being the official stable version (released today ;) ) There doesn't seem to be a bugreport about this, so here it is. Reproducible: Always Steps to Reproduce: I tried to bump the existing ebuild to 6.1.9.4 and it compiled after removing the lines dealing with the fpx patch and perllocal.pod. Doing the same for 6.2.0.4 also looked fine in an "ebuild compile install" although I didn't merge it. No extensive testing done apart from a couple of "convert" runs, which completed fine. Oh, and I'm on ~x86, last emerge --sync yesterday, all packages up-to-date; let me know if you need any more info.
Graphics people: while you're there, could you update the metadata.xml for this package? It's a bit weird. Thanks.
>>> Downloading ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick-6.2.0-4.tar.bz2 --05:51:44-- ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick-6.2.0-4.tar.bz2 => `/usr/portage/distfiles/ImageMagick-6.2.0-4.tar.bz2' Resolving ftp.imagemagick.org... 66.192.180.107, 216.92.21.77 Connecting to ftp.imagemagick.org[66.192.180.107]:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /pub/ImageMagick ... done. ==> PASV ... done. ==> RETR ImageMagick-6.2.0-4.tar.bz2 ... done. Length: 4,642,489 (unauthoritative) 100%[=============================================>] 4,642,489 55.18K/s ETA 00:00 05:53:09 (54.92 KB/s) - `/usr/portage/distfiles/ImageMagick-6.2.0-4.tar.bz2' saved [4642489] !!! Couldn't download ImageMagick-6.2.0-4.tar.bz2. Aborting. # cat files/digest-imagemagick-6.2.0.4 MD5 682cb65818a5162dadfbb2b9f9a35796 ImageMagick-6.2.0-4.tar.bz2 4642968 # md5sum /usr/portage/distfiles/ImageMagick-6.2.0-4.tar.bz2 46968e700ea16ec06769890b33770453 It seems the tarball has been changed since the ebuild and digest were made - I diffed the latest one against one from the ImageMagick Swedish mirror that matched the current ebuild's digest file md5sum and there was nothing suspicious. I don't think the "!!! Couldn't download...." message is the right behaviour for what looks like it must have been a failed md5sum check though. Is this indicative of a bug in portage or something?
same bug !!! Couldn't download ImageMagick-6.2.0-4.tar.bz2. Aborting.
There is something wrong with imagemagick's mirrors. Changed SRC_URI to gz'ed files instead of bzip2'ed. Please test it.
*** Bug 83925 has been marked as a duplicate of this bug. ***
