Summary: | gnome-base/gnome-3.2.1 Can't be emerged due to dev-python/pygobject dependency conflicts | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tim Mohlmann <muhlemmer> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tim Mohlmann
2011-11-10 21:51:22 UTC
That tool didn't unmask all that's necessary. The package.mask is for =dev-python/pygobject-2.28.6-r50 You need pygobject-2.28.6-r50 or newer unmasked too - that doesn't install the introspection stuff as pygobject-3 will be doing that, and can co-exist with pygobject-3. err, p.mask is for
>=dev-python/pygobject-2.28.6-r50
I wonder if portage --autounmask option would be able to figure that out based on information in the form of the masking atom in profiles/package.mask
You need to unmask ">=dev-python/pygobject-2.28.6-r50", which would allow you to do "emerge -1 pygobject:2 pygobject:3". The "official" gnome3 unmasking configs are available at http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=tree;f=status/portage-configs There is also a plan to add an ebuild to portage that would install those configs. The gentoo gnome team does not support unmasks generated by app-portage/autounmask, "emerge --autounmask-write=y", or any other automatic tool. They are known to on occasion produce amazingly wrong results. Generally speaking, you should rely on an automatic unmasking tool *only* if you are extremely familiar with its algorithm. Otherwise, you must manually review every line of any configuration file that such a tool generates for sanity and errors. Thanks, that solved it. I am using a seperate test system so I do not really worry about autounmask. It basically unmasked all deps for gnome-3.2.1, but did not figure out the collision between pygobject-3.0.2 and pygobject-2.28.6 with the introspection use-flag enabled, hence it did not unmask pygobject-2.28.6-r50. If I would have found your unmask config files sooner, I would have used those off course. All and all I'm quite happy with the result of autounmask. (I did review all config files). |