Bugzilla Bug 159996

The following ebuilds are found to have broken autotools handling, as they run
libtoolize directly (they never should, instead they should call eautoreconf in
autotools.eclass, read http://www.gentoo.org/proj/en/qa/autofailure.xml for
more information):

./dev-cpp/libgnomemm/libgnomemm-2.0.1.ebuild:           libtoolize --copy
--force
./dev-cpp/libgnomemm/libgnomemm-2.10.0.ebuild:          libtoolize --copy
--force
./dev-cpp/libgnomemm/libgnomemm-2.12.0.ebuild:          libtoolize --copy
--force
./dev-cpp/libgnomemm/libgnomemm-2.12.2.ebuild:          libtoolize --copy
--force
./dev-cpp/libgnomemm/libgnomemm-2.6.0.ebuild:           libtoolize --copy
--force

Please cleanup the ebuilds by asking for stable marking, removing obsolete
ebuilds with no relevant keywords, or porting the fixes in newer versions (if
presents) to properly handle autotools.

Thanks,
Diego

ppc64 - you are blocking this bug.

No, they aren't the only thing. I have removed all of the old stuff now except
2.0.1. I can't remove that immediately as it lives in an older SLOT. Needs
checking if there are any users of that SLOT. Wanna help there, jakub, with
your magic? :)

(In reply to comment #2)
> I have removed all of the old stuff now except
> 2.0.1. I can't remove that immediately as it lives in an older SLOT. Needs
> checking if there are any users of that SLOT. Wanna help there, jakub, with
> your magic? :)

Would go faster if you CCed me :) No, nothing needs the old slot.

$ pquery --expr
"and(restrict_revdep('<dev-cpp/libgnomemm-2.18.0'),not(restrict_revdep('>=dev-cpp/libgnomemm-2.18.0')))"
$

Done.