The following ebuilds/eclasses are using the almost deprecated gnuconfig_update function from gnuconfig.eclass: ./app-cdr/cdrtools/cdrtools-2.01-r1.ebuild: gnuconfig_update ./app-cdr/cdrtools/cdrtools-2.01-r3.ebuild: gnuconfig_update ./app-cdr/cdrtools/cdrtools-2.01.01_alpha10.ebuild: gnuconfig_update ./app-cdr/cdrtools/cdrtools-2.01.01_alpha11.ebuild: gnuconfig_update ./app-cdr/cdrtools/cdrtools-2.01.01_alpha18.ebuild: gnuconfig_update ./app-cdr/cdrtools/cdrtools-2.01.01_alpha20.ebuild: gnuconfig_update This might be due by various reasons, and some of them cannot be worked around at the current time, so please find your case in the following list: * the ebuild does not use econf, but ./configure, because it uses a very old version of autoconf that does not support the parameters we pass; [1] * the software use config.{guess,sub} although not using autotools, thus econf cannot be used; [1] * the ebuild uses ./configure just for fun; [2] * the ebuild uses ../configure or variants thereof to run a different configure script than the one in the current directory; [3] * the ebuild uses an autogen script or some other autotools-rebuilding script that calls ./configure; [4] * the ebuild calls ./configure because it's doing an inline-build of another package. [1] Then see the procedure to handle this bug: [1] You cannot drop gnuconfig_update, so please leave the bug open, but set the status whiteboard to "Waiting autoepatch". [2] Fix the ebuild, use econf! [3] econf accepts a ECONF_SOURCE variable to tell it to run the configure found in another directory; to run ../configure just use ECONF_SOURCE=".." econf. [4] Fix your autotools with http://www.gentoo.org/proj/en/qa/autofailure.xml adnd then use econf. Once you're using econf, it will take care of updating gnuconfig by itself. Thanks from Diego and Mike
I added cdrtools-2.01.01_alpha23 to the tree and took out the gnuconfig.eclass functions. Apparently they are not needed any more. Probably a leftover from an old version. I guess, all other versions should be updated as well?
All we need is mips to mark a newer ebuild as stable and you can get rid of the only ebuild which still needs gnuconfig_update. cdrtools-2.01-r1.ebuild: gnuconfig_update
mips won't mark anything stable, so close this bug.
Please don't close bugs without reading through them. The ebuild using gnuconfig_update is _still_ in the tree, the bug is _still_ open.
Removed ebuild, no stable mips left, they want it anyway to phase out. Sorry, haven't spotted this before, though I checked.
