Summary: | qt-gui-4.5.1* USE=+dbus but qt-gui-4.5.2* no automatic dbus ---> blocking packages | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas Fink <finkandreas> |
Component: | New packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andreas Fink
2009-07-22 15:20:31 UTC
This was posted by a Gentoo dev on planet.gentoo.org: http://www.linuxized.com/2009/07/gentoo-testing-clean-install-qt-kde-4-blockers-help/ It clearly describes your problem. @qt herd: Still assigning this to you, I'm sure you have a duplicate bug somewhere but I'm not seeing it. Not a qt bug IMHO. We (the qt herd) have decided to drop IUSE defaults for flags which are already enabled by the desktop or base profiles, and we are not going to change that again. As wired explained in his blog post: "Portage first checks qt-gui-4.5.2, which doesn’t have dbus enabled by default. No go. But wait, qt-gui-4.5.1 has it enabled and portage falls back to it. So now portage tries to mix all the other qt-*-4.5.2 packages with qt-gui-4.5.1 (and its 4.5.1 dependencies) [...]" => blockers! So IMHO this should be considered a portage bug (or rather, a limitation of its dep resolver), if anything. *** Bug 278701 has been marked as a duplicate of this bug. *** If you are on the desktop profile, dbus is enabled by default. If you are not, then we now respect your choice and you get to enable dbus yourself if you need it anyway. Most Qt users will want the desktop profile and should not have any problem. For the non-desktop profile users I'm sorry that this transition is bumpy, but we do end up with a clearer situation in the end, which is why we decided to do this. |