Bug#758111: [Pkg-utopia-maintainers] installation-reports: Please consider dbus for the core files
Am 20.08.2014 14:50, schrieb Michael Biebl: Am 20.08.2014 13:27, schrieb Ansgar Burchardt: On 08/20/2014 10:12, Simon McVittie wrote: On Thu, 14 Aug 2014 at 13:24:34 +0200, Michael Biebl wrote: Two possible outcomes then 1/ Make systemd recommend/depend on dbus (recommend would probably be sufficient) According to the initial bug report, the base system is installed without Recommends, so no, Recommends is not sufficient unless we arrange for d-i to install dbus some other way. systemd already indirectly Recommends dbus, for instance: Then we could also just make sure dbus is included in the base installation, i.e. increase its priority to either standard or important. Since systemd already depends on libdbus-1-3, I'd bump libdbus-1-3 to important and dbus to standard. Does that sound ok? Just a quick followup: Since systemd v209 and later no longer uses libdbus-1-3 and we plan to update systemd to v215 for jessie, I guess there is no longer a need to bump the priority of libdbus-1-3. Bumping dbus to standard still makes sense though. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#758111: [Pkg-utopia-maintainers] installation-reports: Please consider dbus for the core files
On Thu, 14 Aug 2014 at 13:24:34 +0200, Michael Biebl wrote: Two possible outcomes then 1/ Make systemd recommend/depend on dbus (recommend would probably be sufficient) According to the initial bug report, the base system is installed without Recommends, so no, Recommends is not sufficient unless we arrange for d-i to install dbus some other way. systemd already indirectly Recommends dbus, for instance: systemd --R- libpam-systemd --D- dbus systemd --P-D- libdbus-1-3 --R- dbus 2/ Make logind talk via a private dbus socket to systemd (not sure if that is feasible / doable). Just to complete the options: 3/ Waste a small amount of memory by pre-running getty@tty2 to getty@tty6, like sysvinit would: /etc/systemd/system% ls -l getty.target.wants total 24 lrwxrwxrwx 1 root root 34 Aug 6 12:41 getty@tty1.service - /lib/systemd/system/getty@.service lrwxrwxrwx 1 root root 34 Apr 27 11:43 getty@tty2.service - /lib/systemd/system/getty@.service lrwxrwxrwx 1 root root 34 Apr 27 11:43 getty@tty3.service - /lib/systemd/system/getty@.service lrwxrwxrwx 1 root root 34 Apr 27 11:43 getty@tty4.service - /lib/systemd/system/getty@.service lrwxrwxrwx 1 root root 34 Apr 27 11:43 getty@tty5.service - /lib/systemd/system/getty@.service lrwxrwxrwx 1 root root 34 Apr 27 11:43 getty@tty6.service - /lib/systemd/system/getty@.service (The symlink for tty1 is currently shipped with systemd; the others are a local change on my laptop.) S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758111: [Pkg-utopia-maintainers] installation-reports: Please consider dbus for the core files
On 08/20/2014 10:12, Simon McVittie wrote: On Thu, 14 Aug 2014 at 13:24:34 +0200, Michael Biebl wrote: Two possible outcomes then 1/ Make systemd recommend/depend on dbus (recommend would probably be sufficient) According to the initial bug report, the base system is installed without Recommends, so no, Recommends is not sufficient unless we arrange for d-i to install dbus some other way. systemd already indirectly Recommends dbus, for instance: Then we could also just make sure dbus is included in the base installation, i.e. increase its priority to either standard or important. Maybe also for libpam-systemd? systemd should still Recommend: dbus to get it installed on upgrades from wheezy. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758111: [Pkg-utopia-maintainers] installation-reports: Please consider dbus for the core files
Am 20.08.2014 13:27, schrieb Ansgar Burchardt: On 08/20/2014 10:12, Simon McVittie wrote: On Thu, 14 Aug 2014 at 13:24:34 +0200, Michael Biebl wrote: Two possible outcomes then 1/ Make systemd recommend/depend on dbus (recommend would probably be sufficient) According to the initial bug report, the base system is installed without Recommends, so no, Recommends is not sufficient unless we arrange for d-i to install dbus some other way. systemd already indirectly Recommends dbus, for instance: Then we could also just make sure dbus is included in the base installation, i.e. increase its priority to either standard or important. Since systemd already depends on libdbus-1-3, I'd bump libdbus-1-3 to important and dbus to standard. Does that sound ok? Maybe also for libpam-systemd? Not quite sure about that one. On one hand, libpam-systemd is mostly interesting for desktop environments and multi-user systems (and the desktop meta packages usually already pull in libpam-systemd), so keeping the base system as small as possible seems desirable. On the other hand, even stuff like remote access via SSH might need libpam-systemd, e.g. if you run screen sessions which should persist when you log out. I *think* this requires a proper logind session to not be killed on logout, but this would need further investigation. systemd should still Recommend: dbus to get it installed on upgrades from wheezy. As Simon already mentioned, libdbus-1-3 already recommends dbus, but I guess an explicit Recommends in systemd wouldn't hurt. Also, the user might already have libdbus-1-3- installed in wheezy and deselected the dbus recommends. Adding it to systemd would pull it in anew afaics. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
