Compilation of media-gfx/imagemagick-6.3.4 fails due to imagemagick-6.3.4-docs.patch not being in the portage tree (despite several resyncs over the last couple of hours.) # emerge -uD --newuse world Calculating world dependencies ..... ..... ..... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) media-gfx/imagemagick-6.3.4 to / * ImageMagick-6.3.4-4.tar.bz2 RMD160 ;-) ... [ ok ] * ImageMagick-6.3.4-4.tar.bz2 SHA1 ;-) ... [ ok ] * ImageMagick-6.3.4-4.tar.bz2 SHA256 ;-) ... [ ok ] * ImageMagick-6.3.4-4.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking ImageMagick-6.3.4-4.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking ImageMagick-6.3.4-4.tar.bz2 to /var/tmp/portage/media-gfx/imagemagick-6.3.4/work * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /usr/portage/media-gfx/imagemagick/files/imagemagick-6.3.4-docs.patch * ( imagemagick-6.3.4-docs.patch ) !!! ERROR: media-gfx/imagemagick-6.3.4 failed. Call stack: ebuild.sh, line 1615: Called dyn_unpack ebuild.sh, line 752: Called qa_call 'src_unpack' ebuild.sh, line 44: Called src_unpack imagemagick-6.3.4.ebuild, line 54: Called epatch '/usr/portage/media-gfx/imagemagick/files/imagemagick-6.3.4-docs.patch' eutils.eclass, line 198: Called die !!! Cannot find $EPATCH_SOURCE! !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/media-gfx/imagemagick-6.3.4/temp/build.log'.
I got it to build by copying the patch from '...-6.3.3-...' to '...-6.3.4-...'. I had noticed that the. I noticed that the ebuild makes reference only to a file "${PN}-${PV}-docs.patch", which explains why there is a 6.3.3 patch but not a 6.3.4. It may be, though, that the patch is not necessary at all anymore.
The patch can be found here http://bugs.gentoo.org/show_bug.cgi?id=179943 if people need it before it gets into the tree properly.
Bryan, hope you don't mind, I've fixed the patch naming so that the old version is applied instead.
*** Bug 180218 has been marked as a duplicate of this bug. ***
