Summary: | x11-libs/qt-4.2.0_rc1 fails collision test | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markus Rothe (RETIRED) <corsair> |
Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Markus Rothe (RETIRED)
2006-09-07 11:06:25 UTC
yuk. I'm wondering if it's the same dbus? perhaps it's one of their utilities, and it's just being merged poorly. I'll have to investigate. As best as I can tell, qt provides these as addons to the normal dbus package. I'm curious if the qt dbus extensions provided by our normal dbus is what's also providing these causing teh collision. Easiest for me to just make qt not install these files. Are they being provided directly by the dbus package? I've lost the chroot this happened in (disk died) and I'm not able to reproduce this. sys-apps/dbus only provides /usr/bin/dbus-* binaries. As the chroot is gone I cannot check which package the /usr/bin/dbus package belonged to. Marking as INVALID. Please reopen if this is was wrong. s/package belonged to/binary belonged to I just did an emerge and qt didn't create and /usr/bin/dbus* files, just /usr/bin/qdbus, /usr/bin/qdbuscpp2xml, and /usr/bin/qdbusxml2cpp, so it looks like it might have been fixed since _rc1 |