sometimes i'll make changes to the current version of a package and test it out ... then when i move it cvs, i'll want to rev bump it since it installs differently ... however, in the process, i'll touch up something in src_unpack() ... when i try to unpack the new version, portage gets mad because it cant find the ebuild in $PORTDIR or $PORTDIR_OVERLAY so, to recap, portage should work off the ebuild specified instead of trying to scan for one in $PORTDIR or $PORTDIR_OVERLAY test case: cd /to/your/portage/tree/app-editors/nano cp nano-1.3.3.ebuild nano-1.3.3-r1234.ebuild ebuild nano-1.3.3-r1234.ebuild digest clean unpack (OH GOD THIS FAILS BAD) cp nano-1.3.3-r1234.ebuild /usr/portage/app-editors/nano/ ebuild nano-1.3.3-r1234.ebuild digest clean unpack (well it works now, but wtf)
more explanation (for people like ferringb): i have three portage trees rsync: /usr/portage local: /usr/local/portage cvs: /usr/local/gentoo-x86 PORTDIR=/usr/portage PORTDIR_OVERLAY=/usr/local/portage now, if i go into the cvs tree and create a new version of a package that doesnt exist in $PORTDIR or $PORTDIR_OVERLAY and then try to run `emerge` or `ebuild` operations on it, they generally fail horribly
Created attachment 37253 [details, diff] emerge patch to use varttree for querying. I've corrected this InCVS a bit earlier prior to noticing this bug; so... here's the patch :)
Comment on attachment 37253 [details, diff] emerge patch to use varttree for querying. Aww Damn. Wrong freaking Bug :-/
Mike, add the actual error being thrown please...
blah root@vapier 0 quake1 # portageq envvar PORTDIR /usr/portage root@vapier 0 quake1 # portageq envvar PORTDIR_OVERLAY /usr/local/portage root@vapier 0 quake1 # pwd /usr/local/gentoo-x86/games-fps/quake1 root@vapier 0 quake1 # ls /usr/portage/games-fps/quake1 ChangeLog Manifest files metadata.xml quake1-2.40.ebuild root@vapier 0 quake1 # ls /usr/local/portage/games-fps/quake1 ls: /usr/local/portage/games-fps/quake1: No such file or directory root@vapier 0 quake1 # ls CVS ChangeLog Manifest files metadata.xml quake1-2.40.ebuild root@vapier 0 quake1 # mv quake1-2.40.ebuild quake1-2.40-r1.ebuild root@vapier 0 quake1 # ebuild quake1-2.40-r1.ebuild digest !!! aux_get(): ebuild for 'games-fps/quake1-2.40-r1' does not exist at: !!! None !!! aux_get(): ebuild for 'games-fps/quake1-2.40-r1' does not exist at: !!! None doebuild(): aux_get() error; aborting. root@vapier 0 quake1 # cp quake1-2.40-r1.ebuild /usr/portage/games-fps/quake1/ root@vapier 0 quake1 # ebuild quake1-2.40-r1.ebuild digest >>> Generating digest file... <<< q1source.zip >>> Generating manifest file... <<< ChangeLog <<< metadata.xml <<< quake1-2.40-r1.ebuild <<< files/digest-quake1-2.40 <<< files/fix-sys_printf.patch <<< files/makefile-gcc2-cflags.patch <<< files/makefile-gcc3-cflags.patch <<< files/makefile-path-fixes.patch <<< files/makefile-sedable.patch <<< files/digest-quake1-2.40-r1 --- Warning: digests are not yet added into CVS. >>> Computed message digests.
*** Bug 64941 has been marked as a duplicate of this bug. ***
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
I assume repoman automagic deals with this.
