When I attempted to emerge -e world my system I received the following error... * You need to build dev-scheme/guile with USE='deprecated discouraged threads' * * ERROR: sys-devel/autogen-5.9.2 failed. * Call stack: * ebuild.sh, line 1711: Called dyn_setup * ebuild.sh, line 762: Called qa_call 'pkg_setup' * ebuild.sh, line 44: Called pkg_setup * autogen-5.9.2.ebuild, line 24: Called die * The specific snippet of code: * die "re-emerge dev-scheme/guile with USE='deprecated discouraged threads'" * The die message: * re-emerge dev-scheme/guile with USE='deprecated discouraged threads' I didn't include the discouraged USE variable when I recompiled guile because equery claims that it is implied by deprecated... $ equery uses dev-scheme/guile [ Searching for packages matching dev-scheme/guile... ] [ Colour Code : set unset ] [ Legend : Left column (U) - USE flags from make.conf ] [ : Right column (I) - USE flags packages was installed with ] [ Found these USE variables for dev-scheme/guile-1.8.3-r1 ] U I - - debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml . - - debug-freelist : include garbage collector freelist debugging code - - debug-malloc : include malloc debugging code + + deprecated : enable deprecated features - - discouraged : (implied by deprecated) enable merely discouraged features ... Please update the autogen-5.9.2 ebuild to not specifically look for the "discouraged" USE variable on the guile package, or the description needs to be adjusted to reflect that it is not implied by "deprecated". Reproducible: Always
fixed in cvs
I believe it was the dependency on the "discouraged" use flag which should have been removed, rather than the dependency on "deprecated". autogen will only build for me if guile was built with deprecated in use, and I'm not the only one, see this forum thread for details; forums.gentoo.org/viewtopic-p-4472198.html
Correct...your forum note swaps the names though. Also I'm not sure if by "in CVS" it means that we'll see it after a sync or not (might need to wait until a new revision is created...not sure if that is separate). I'll attempt to verify the fix in a second though.
Hopeless - you're right...they messed up on the fix. Reopening bug...
dont cc me
