Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 124580 - tetex 2.0.2-r8 fails to find patch file
Summary: tetex 2.0.2-r8 fails to find patch file
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Text-Markup Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
: 124609 124629 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-03-01 16:25 UTC by Timothy Bergeron
Modified: 2006-03-02 05:50 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Bergeron 2006-03-01 16:25:41 UTC 
I installed tetex-2.0.2-r8 last week and it installed fine. Today, I am trying to reinstall it and I get the following error:


 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 * 
 *   /usr/portage/app-text/tetex/files/tetex-2.0.2-flex-compile.patch
 *   ( tetex-2.0.2-flex-compile.patch )


!!! ERROR: app-text/tetex-2.0.2-r8 failed.
!!! Function epatch, Line 207, Exitcode 0
!!! Cannot find $EPATCH_SOURCE!
!!! If you need support, post the topmost build error, NOT this status message.

One of my systems that I haven't synced for a bit has a tetex-2.0.2-r8.ebuild that doesn't try to apply the above patch (which is missing from my portage tree).

Since tetex-2.0.2-r8 is a stable ebuild, this needs to get fixed quickly. I came across the problem because tetex is a dependency of t1lib which is in turn a dependency of kpdf. t1lib depends upon tetex when using the doc USE flag.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-03-02 01:20:35 UTC 
*** Bug 124609 has been marked as a duplicate of this bug. ***
Comment 2 Martin Ehmsen (RETIRED) gentoo-dev 2006-03-02 01:54:50 UTC 
Fixed in CVS. Thanks for reporting.
Comment 3 Carsten Lohrke (RETIRED) gentoo-dev 2006-03-02 05:50:18 UTC 
*** Bug 124629 has been marked as a duplicate of this bug. ***