Red Hat Bugzilla – Bug 623456
dbus packaging is odd
Last modified: 2014-03-16 23:24:34 EDT
Description of problem:
Something should own the directory, and it's likely dbus.target should move to the dbus package too.
Version-Release number of selected component (if applicable):
I think it makes sense to keep dbus.target in systemd. While this is not really important for systemd itself I'd like to keep this similar to how syslog is handled:
The generic syslog.target unit you find in systemd yourself, while the various available implementations then install syslog.service/syslog.socket as they see fit, with different contents and even different names.
While we (currently?) only have a single D-Bus implementation I think it is the path of least surprise if we follow the same scheme of dbus and syslog here.
The directory ownership should indeed be fixed.
I'm not sure planning for ever having a separate dbus implementation is useful. CC'ing Colin in any case, as the packaging changes may affect dbus.
So, this is just a dbus packaging bug, right ?
It needs to own /lib/systemd/system/dbus.target.wants
Should we move this bug to dbus ?
systemd-10-1.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14 has been submitted as an update for Fedora 14.
systemd-10-1.fc14, initscripts-9.20-1.fc14, sysvinit-2.87-5.dsf.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update systemd initscripts sysvinit'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/systemd-10-1.fc14,initscripts-9.20-1.fc14,sysvinit-2.87-5.dsf.fc14
initscripts-9.20-1.fc14, sysvinit-2.87-5.dsf.fc14, systemd-10-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.