Bug#1015015: unable to upgrade due to elogind vs systemd conflict

Mark Hindley mark at hindley.org.uk
Sat Jul 16 15:39:02 BST 2022


On Sat, Jul 16, 2022 at 03:32:55PM +0200, Adam Borowski wrote:
> The _correct_ way would be to write that dependency as
> 'systemd-tmpfiles | systemd' which is no-op on systemd installs but
> avoids init switch elsewhere.

Thanks. That is a good suggestion.


I know this issue was raised a few days ago in #1014805 and you rejected any
change, but, as they stand, the udev dependencies are causing problems to users
and apt does not readily find the solution which avoids switching init system.

In your rejection of #1014805 you correctly asserted the first alternative in a
dependency should be a real package. So, perhaps

 systemd-standalone-tmpfiles | systemd-tmpfiles

would satisfy the Policy requirements and not produce unexpected behaviour for
users? On systemd systems it would be noop as systemd provides systemd-tmpfiles
and it would avoid trying to install systemd on non-systemd systems which then
causes conflicts with elogind.

What do you think?

Thanks for your consideration.

Best wishes


More information about the Debian-init-diversity mailing list