Re: systemd being pulled in during dist-upgrade
On 2/20/22 20:32, Stan Johnson wrote:
>> That's an or-condition, i.e. cron or anacron or cron-daemon or systemd-sysv,
>> see also the debian/control file of the logrotate package [1].
>
> I do have cron, anacron and cron-daemon installed, so the OR condition
> should have been met. So perhaps a dependency is broken somewhere, but I
> don't know how to determine where the problem is.
Try uninstalling logrotate and systemd-sysv, then try installing the logrotate
package and see whether the systemd-sysv package is going to be pulled in.
>> FWIW, this discussion isn't specific to PowerPC, so it should be moved to
>> debian-user or preferably, debian-devel.
>
> I also use Debian SID on x86 and x64 systems. Only on PowerPC do I run
> into the issue of "apt-get dist-upgrade" occasionally wanting to pull in
> systemd, but I have no objection to moving the discussion to debian-user
> or debian-devel (I didn't do that originally because I thought since
> powerpc is not a supported architecture they would not be able to help).
There is no specific behavior on systemd on PowerPC, so it's just coincidence.
>> In any case, you should just make sure that either of the three cron packages
>> is installed, then you can uninstall the systemd-sysv package again.
>
> No, it appears to be more complicated than that.
Did you try uninstalling systemd-sysv? If that doesn't work, what is the error
message?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: