View previous topic :: View next topic |
Author |
Message |
audiodef Watchman


Joined: 06 Jul 2005 Posts: 6656 Location: The soundosphere
|
Posted: Sat Aug 20, 2005 7:53 pm Post subject: Cannot find $EPATCH_SOURCE [SOLVED] |
|
|
While merging Gnome, I ran into this problem during the merging of gtk:
Code: |
*Applying gtk+-2.2.1-disable_icons_smooth_alpha.patch
*Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/distfiles/gtk+-2.6-smoothscroll-r5.patch
* ( gtk+-2.6-smoothscrool-r5.patch )
|
My USE flag is "-kde -qt gnome gtk hal howl X".
I haven't found anything useful googling for this issue, and only a few results for this exact error are returned by Google. Any insight would be appreciated!
Last edited by audiodef on Sun Aug 21, 2005 12:11 am; edited 1 time in total |
|
Back to top |
|
 |
Lokheed Veteran


Joined: 12 Jul 2004 Posts: 1295 Location: /usr/src/linux
|
Posted: Sat Aug 20, 2005 9:06 pm Post subject: |
|
|
There are two ways to fix this. The easiest one would be to go into /usr/portage/distfiles and unpack the gtk+-2.6-smoothscroll-r5 tarball in distfiles. This will show portage there is a patch there. File a bug as this problem follows all GTK releases, including 2.6.10.
The other way would be to copy over the GTK directory to your portage overlay and edit the ebuild, removing the path to distfiles and replacing it with the files directory. Unpack the gtk+-2.6-smoothscroll-r5 tarball to the files directory, run a digest and it will install. I did this option before I thought about the easier one provided previously... _________________ You're not afraid of the dark are you? |
|
Back to top |
|
 |
audiodef Watchman


Joined: 06 Jul 2005 Posts: 6656 Location: The soundosphere
|
Posted: Sun Aug 21, 2005 12:11 am Post subject: |
|
|
I took your first suggestion, Lokheed, and it of course worked perfectly.
Thanks! |
|
Back to top |
|
 |
eleanor l33t


Joined: 01 Nov 2004 Posts: 666
|
Posted: Fri Jun 30, 2006 6:42 pm Post subject: |
|
|
I have similar problem:
Quote: | Downloading http://distfiles.gentoo.org/distfiles/tiff-3.8.2.tar.gz
--20:45:01-- http://distfiles.gentoo.org/distfiles/tiff-3.8.2.tar.gz
=> `/usr/portage/distfiles/tiff-3.8.2.tar.gz'
Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195, 64.50.236.52, ...
Connecting to distfiles.gentoo.org|216.165.129.135|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1,336,295 (1.3M) [application/x-gzip]
100%[====================================>] 1,336,295 89.99K/s ETA 00:00
20:45:17 (84.96 KB/s) - `/usr/portage/distfiles/tiff-3.8.2.tar.gz' saved [1336295/1336295]
>>> checking ebuild checksums
>>> checking auxfile checksums
>>> checking miscfile checksums
>>> checking tiff-3.8.2.tar.gz
>>> Unpacking source...
>>> Unpacking tiff-3.8.2.tar.gz to /var/tmp/portage/tiff-3.8.2-r1/work
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /var/tmp/portage/tiff-3.8.2-r1/distdir/tiff-3.8.2-tiff2pdf.patch.bz2
* ( tiff-3.8.2-tiff2pdf.patch.bz2 )
!!! ERROR: media-libs/tiff-3.8.2-r1 failed.
Call stack:
ebuild.sh, line 1545: Called dyn_unpack
ebuild.sh, line 711: Called src_unpack
tiff-3.8.2-r1.ebuild, line 23: Called epatch '/var/tmp/portage/tiff-3.8.2-r1/distdir/tiff-3.8.2-tiff2pdf.patch.bz2'
eutils.eclass, line 192: Called die
!!! Cannot find $EPATCH_SOURCE!
!!! If you need support, post the topmost build error, and the call stack if relevant.
localhost eleanor # |
How rto fix it.
As far I did this:
Code: | rm /usr/portage/distfiles/tiff* | but the same problem.
Need help!! |
|
Back to top |
|
 |
themaze75 n00b

Joined: 14 Mar 2006 Posts: 22
|
Posted: Thu Jul 20, 2006 5:52 am Post subject: |
|
|
I had a similar problem with another package. I only had to synchronize again ("emerge --sync") and emerge the package.
It went through no sweat. _________________ Eric Maziade
In the Maze |
|
Back to top |
|
 |
DMan8686 n00b

Joined: 25 Oct 2010 Posts: 2 Location: Pennsylvania, United States
|
Posted: Mon Oct 25, 2010 11:10 pm Post subject: I agree with themaze75... |
|
|
I know this is an OLD thread but for anyone viewing this now I have found out the themaze75 was right. If you have this problem just type emerge --sync and that should fix the problem. If not then Lokheed's answer should work. |
|
Back to top |
|
 |
|