Bug 255601 - multilib dbus breaks
multilib dbus breaks
Product: Fedora
Classification: Fedora
Component: dbus (Show other bugs)
All All
medium Severity low
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-26 19:51 EDT by Dave Airlie
Modified: 2013-03-05 22:51 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-08 23:51:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
split dbus into dbus and dbus-libs (2.34 KB, patch)
2007-08-27 17:26 EDT, drago01
no flags Details | Diff

  None (edit)
Description Dave Airlie 2007-08-26 19:51:00 EDT
Description of problem:

So with rawhide, on x86_64 I wanted to install 32-bit skype which depends on qt4
which depends on dbus, now dbus has daemons and client libs in one package, so
it also references lib64 in /etc/dbus-1/system.conf so I get conflicts

Can we split dbus into multiple packages please?
Comment 1 David Zeuthen 2007-08-27 10:33:03 EDT
> So with rawhide, on x86_64 I wanted to install 32-bit skype which depends on qt4
> which depends on dbus, now dbus has daemons and client libs in one package, so
> it also references lib64 in /etc/dbus-1/system.conf so I get conflicts

Conflicts as in... RPM complaining because the files /etc/dbus-1/system.conf
from dbus.i386 and dbus.x86_64 differ?
Comment 2 drago01 2007-08-27 17:26:37 EDT
Created attachment 174581 [details]
split dbus into dbus and dbus-libs
Comment 3 Bug Zapper 2008-04-04 09:40:57 EDT
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Comment 4 Bug Zapper 2008-11-26 02:42:56 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-01-08 23:51:33 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.