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

2022-07-16 Thread Thorsten Glaser
On Sun, 17 Jul 2022, Craig Sanders wrote: > > You most likely want some pinning. > > I've never found pinning to be of much use. When I did have an actual use for […] No, not that. You need it to get apt to not even consider systemd installable. > wanted. Far more work than it was worth - I ende

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

2022-07-16 Thread Craig Sanders
On Sun, Jul 17, 2022 at 04:01:38AM +0200, Thorsten Glaser wrote: > On Sun, 17 Jul 2022, Craig Sanders wrote: > > > and, of course: > > > > apt-mark hold sysvinit-core > > > > To prevent systemd from being auto-installed in some future upgrade. > > You most likely want some pinning. I've never

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

2022-07-16 Thread Thorsten Glaser
On Sun, 17 Jul 2022, Craig Sanders wrote: > and, of course: > > apt-mark hold sysvinit-core > > To prevent systemd from being auto-installed in some future upgrade. You most likely want some pinning. Just held in dpkg or even marked as XB-Important: yes often brings apt to tears in sid, i.e

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

2022-07-16 Thread Craig Sanders
On Sat, Jul 16, 2022 at 02:35:33PM +0100, Mark Hindley wrote: > On Sat, Jul 16, 2022 at 11:07:47PM +1000, Craig Sanders wrote: > > A little more investigation reveals that it's udev. > > > > udev 2.51.3-1 (Wed, 13 Jul 2022 23:05:40 +0200) now depends on 'systemd | > > systemd-tmpfiles'. > > Great.

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

2022-07-16 Thread Mark Hindley
Adam, 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. Michael, I know this issue was r

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

2022-07-16 Thread Mark Hindley
Craig, Thanks. On Sat, Jul 16, 2022 at 11:07:47PM +1000, Craig Sanders wrote: > A little more investigation reveals that it's udev. > > udev 2.51.3-1 (Wed, 13 Jul 2022 23:05:40 +0200) now depends on 'systemd | > systemd-tmpfiles'. Great. systemd-tmpfiles is a virtual package that is also provi

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

2022-07-16 Thread Adam Borowski
On Sat, Jul 16, 2022 at 11:07:47PM +1000, Craig Sanders wrote: > The machine is running sid, so this was just a routine dist-upgrade. > > > I can't immediately see the package that might be causing the conflict here. > A little more investigation reveals that it's udev. > > udev 2.51.3-1 (Wed, 13

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

2022-07-16 Thread Craig Sanders
On Sat, Jul 16, 2022 at 10:00:27AM +0100, Mark Hindley wrote: > What release are you upgrading from an to? Version of what? There's no new version of elogind. That's kind of what my bug report is asking for. The machine is running sid, so this was just a routine dist-upgrade. > On Sat, Jul 16,

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

2022-07-16 Thread Mark Hindley
Craig, Thanks for this. What release are you upgrading from an to? On Sat, Jul 16, 2022 at 06:34:35PM +1000, Craig Sanders wrote: > Package: elogind > Version: 246.9.1-1+debian1 > > I don't know if a newer version of elogind would help here, but it > probably wouldn't hurt. elogind in debian ha

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

2022-07-16 Thread Craig Sanders
Package: elogind Version: 246.9.1-1+debian1 I don't know if a newer version of elogind would help here, but it probably wouldn't hurt. elogind in debian hasn't been updated since Dec 23. # apt -u dist-upgade [...] The following packages will be REMOVED: alsa-firmware-loaders bluez brasero fwupd