Summary: | kde-misc/kdnssd-avahi-0.1.2 (is blocking kde-base/kdelibs-3.5.6-r7) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alejandro Wainzinger <aikawarazuni> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jakub, kde |
Priority: | High | Keywords: | InVCS, REGRESSION |
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 179036 | ||
Bug Blocks: | 155723, 172589 | ||
Attachments: | handle this case where the blocker can be avoided |
Description
Alejandro Wainzinger
2007-05-02 06:20:27 UTC
Anything avahi related in package.use? Can reproduce it here, Marius. Both with stable and testing Portage. It's really only the kdelibs ebuild, Portage is choking on. Only things in package.use just have avahi enabled, or are setting USE flags for avahi, not disabled, i.e. net-dns/avahi gdbm mono media-sound/rhythmbox avahi The problem is that the build planner doesn't recognize that the blocker is invalidated when the avahi flag changes state. Workaround: emerge --oneshot --nodeps kdelibs && emerge --oneshot --noreplace kdelibs Created attachment 118026 [details, diff]
handle this case where the blocker can be avoided
This is fixed in svn r6472:6474.
This has been released in 2.1.2.6. |