Summary: | kpowersave blocks updates with dependency on dev-libs/dbus-qt3-old | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aquila <bart.braem> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED INVALID | ||
Severity: | major | CC: | genstef |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aquila
2006-12-21 00:05:29 UTC
Here's an idea - if you unmask something, kindly unmask its dependencies as well... http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3 I'm sorry, but this ebuild did not change and all of a sudden it stopped working. This worked flawlesly and all of a sudden, without ebuild updates or anything like that, it was broken. And yes I do know I have to unmask dependencies, but when they show up afterwards that's quite different, or am I the naive user here? I'm going to reopen in case you would consider my comments or the comments in the forum thread to be valid, but we might be wrong of course... Well, I'm sorry but ~x86 ebuild depending on ~x86 ebuild is NOT a bug. echo ">=dev-libs/dbus-qt3-old-0.70" >> /etc/portage/package.keywords it's a bug when the ebuild dependencies are wrong. 1. kpowersave needs hal 2. kpowersave-0.62 ebuild now needs >=dbus-0.91 3. hal needs =<dbus-0.9 => ebuild is useles, as it can't install without having inconsistent system kpowersave-0.62 was building (and still build, if you edit the ebuild) fine against dbus-0.62 (stable) this would have been so simple to 'fix', if only the ebuild maintainer was to correctly put revisions on his ebuilds versions (we then just use the previous one), esp. when there's only one ebuild in the tree, and that ti was no minor change. the ebuild has even so clearly not been tested after such a modification, that's some basic QA. I know it's testing, but hey, being testing does not mean you can throw anything in just blindly. (In reply to comment #4) > it's a bug when the ebuild dependencies are wrong. Kindly read the output posted in Comment #0. Thanks. CLOSED please when you hit such a bug use all the depends and their childs from ~arch until they get into the stable tree. |