Summary: | dev-python/pygobject-2.16.0 fails to build with libtool-1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | R Bar-On <rb6> |
Component: | [OLD] Development | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amit.prakash.ambasta, gentoo, ivan.diorditsa, kafteji, main.haarp, transacid |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 257399 | ||
Bug Blocks: | |||
Attachments: | build log |
Description
R Bar-On
2009-01-19 19:25:32 UTC
Created attachment 179012 [details]
build log
this is due to libtool-1 + eautoreconf. (In reply to comment #2) > this is due to libtool-1 + eautoreconf. > means what? I have this error too. (In reply to comment #3) > (In reply to comment #2) > > this is due to libtool-1 + eautoreconf. > > > > means what? I have this error too. > echo "sys-devel/libtool ~x86" >> /etc/portage/package.keywords && emerge -av libtool Bad idea. This should be fixed for x86/amd64. No stable package should require unstable anything. Except pygobject-2.16.0 is NOT marked stable. That said, it will be stabilized before libtool-2 in all likelihood, so thanks for the bug report we'll know to avoid this breakage for stable systems by getting it to work with libtool-1 too. Fails here as well.. upgraded to libtool 2.2.6a as resolution *** Bug 256059 has been marked as a duplicate of this bug. *** (In reply to comment #7) > Fails here as well.. upgraded to libtool 2.2.6a as resolution > same thing unless libtool is upgraded So there's is no other solution? Only update the libtool? (In reply to comment #10) > So there's is no other solution? > > Only update the libtool? > You can downgrade dev-python/pygobject to stable version. (In reply to comment #11) > (In reply to comment #10) > > So there's is no other solution? > > > > Only update the libtool? > > > > You can downgrade dev-python/pygobject to stable version. > it wasn't a choice to unmask pygobject you know! it's because of reverse-dependency to other packages like libgweather I can confirm this bug on x86. The ebuild for dev-python/pygobject-2.16.0 should depend on >=sys-devel/libtool-2.0.0 We don't really support mixing arch with ~arch... So if you want to have GNOME-2.24 from ~arch, you get to have libtool-2 from ~arch. That said, as we will probably need to go stable with pygobject-2.16 before libtool-2 does, we will fix this bug by the time pygobject-2.16 is up for stabilization, and it is not a priority before then. (we have more important things to do first, like stabilize gtk+-2.14 and co and fix the bugs that need to be fixed before that) Ok :P no problem then *** Bug 257553 has been marked as a duplicate of this bug. *** + 07 Feb 2009; Gilles Dartiguelongue <eva@gentoo.org> + pygobject-2.16.0.ebuild: + Fix building on libtool-1 systems, bug #255542. + fixed without a bump. Thanks for reporting. |