The SRC_URI tarball doesn't exist on 184.108.40.206. it exists as a symlink only.It does point to something.
version 220.127.116.11 does exist though.
Really? It points to good file for me. What shows you emerge, add some output. Please reopen this bug if problem still exists.
There is no problem as such just upstream has 6.1.6-0 and 6.1.6-1 exactly the same.
Version bump is the same ebuild.
ls -la ftp://ftp.imagemagick.org/pub/ImageMagick
lrwxrwxrwx 1 ftpuser ftpusers 26 Dec 7 13:36 ImageMagick-6.1.6-0.tar.gz -> ImageMagick-6.1.6-1.tar.gz
-rw-r--r-- 1 ftpuser ftpusers 4558135 Dec 7 15:32 ImageMagick-6.1.6-1.tar.bz2
-rw-r--r-- 1 ftpuser ftpusers 5579540 Dec 7 15:32 ImageMagick-6.1.6-1.tar.gz
Also worth noting is the the SRC_URI on perlmagic has differences between its 6.1.6-0 and 6.1.6-1 bz2 tarball. From the changelog I think they did a rapid version bump.
As per changlog:
# diff ImageMagick-6.1.6-0.bz2/ChangeLog ImageMagick-6.1.6-1.bz2/ChangeLog
> 2004-12-06 Chris Madison <madisonblu@hotma...>
> * CompareImages() now sets the black channel when comparing CMYK images.
Suggested course of action: copy media-gfx/imagemagick/imagemagick-18.104.22.168.ebuild to media-gfx/imagemagick/imagemagick-22.214.171.124.ebuild without the ususal drop in keywords (same tarball contents). Bump dev-perl/perlmagick-126.96.36.199.ebuild to dev-perl/perlmagick-188.8.131.52.ebuild (tarball contents change).
Also as imagemagick and perlmagick use the same tarball contents should they use the same tarball? They are fetched from different locations however they are essentually the same except for the odd anomaly when they symlink versions together.
Could they just be combined into one ebuild?
I'm really thinking about adding perl USE flag to imagemagick and remove perlmagick's ebuild. I think, I'll do you it in next week, so be patient.
sorry if I seemed to be rushing you. This wasn't my intent.
no problem, i've planned this for few weeks ;)
Neither 184.108.40.206, nor 220.127.116.11 is in portage any more, closing a pointless bug.