Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 81665 - mythfrontend 0.17 ebuild fails to compile due to invalid work dir
Summary: mythfrontend 0.17 ebuild fails to compile due to invalid work dir
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Television related Applications in Gentoo's Portage
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-11 14:09 UTC by Brian Zushi
Modified: 2005-02-12 09:12 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Zushi 2005-02-11 14:09:46 UTC
The (masked) mythfrontend-0.17 build fails to compile due to an apparent invalid work directory. See details below:

>>> Unpacking mythtv-0.17.tar.bz2 to /var/tmp/portage/mythfrontend-0.17/work
/usr/lib/portage/bin/ebuild.sh: line 21: cd: /var/tmp/portage/mythfrontend-0.17/work/mythfrontend-0.17: No such file or directory
sed: can't read settings.pro: No such file or directory

Reproducible: Always
Steps to Reproduce:
1. Take steps to emerge the masked package
2. "emerge mythfrontend"
3. Despair

Actual Results:  
Failure to compile.

Expected Results:  
Compilation and installion. :)

Note: The actual subdir under work/ is mythtv-0.l7, as opposed to the expected
mythfrontend-0.17
Comment 1 Jesse Adelman 2005-02-11 14:13:21 UTC
I believe this is due to a missing line, present in the 0.16 ebuild:

/usr/portage/media-tv/mythfrontend/mythfrontend-0.16.ebuild:
---
S="${WORKDIR}/mythtv-${PV}"
---

While I don't use this ebuild, this would solve the single issue presented here. The rest of the ebuild may have problems, too, but that's for another bug report ;).
Comment 2 Sloan Poe 2005-02-12 08:17:04 UTC
Yes.  I added this line, and it worked just fine on my system.
Comment 3 Doug Goldstein (RETIRED) gentoo-dev 2005-02-12 09:12:15 UTC
sometimes you just have to use "emerge --sync". ;) It's been fixed.