Bug#884374: systemd: dpkg fails for systemd package when upgrading from jessie to stretch

[Michael Biebl]

Am 14.12.2017 um 17:13 schrieb phil:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: important
>
> Dear Maintainer,
>
>
> I've just done an upgrade from jessie to strech and i'm stuck with the same pb
> that is mentionned in this bug (https://bugs.debian.org/cgi-
> bin/bugreport.cgi?bug=854041): for some reason one package tried to remove
> systemd.
>
>
> As suggested here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854041#65
>
> I've tried :
>
> dpkg -i --force-breaks /var/cache/apt/archives/systemd_232-25+deb9u1_amd64.deb
>
>
> And then i was able to :
>
> apt-get -f install
> apt-get dist-upgrade

Do you get any error messages? If so, please post them.


--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[Michael Biebl]

Am 14.12.2017 um 18:51 schrieb zythox:
> hi, got this :
>
> dpkg: systemd : problème de dépendance, mais suppression comme demandé :
>  systemd-sysv dépend de systemd.
>  libpam-systemd:amd64 dépend de systemd (= 215-17+deb8u7).
>
> (Lecture de la base de données... 65%
> (Lecture de la base de données... 206774 fichiers et répertoires déjà
> installés.)
> Suppression de systemd (215-17+deb8u7) ...
> systemd is the active init system, please switch to another before
> removing systemd.
> dpkg: erreur de traitement du paquet systemd (--remove) :
>  le sous-processus script pre-removal installé a retourné une erreur de
> sortie d'état 1
> Failed to stop lib-init-rw.mount: Unit lib-init-rw.mount not loaded.
> addgroup: Le groupe « systemd-journal » existe déjà en tant que groupe
> système. Fin de la procédure.
> Des erreurs ont été rencontrées pendant l'exécution :
>  systemd
> Log ended: 2017-12-13  19:18:40
Unfortunately I don't speak French and the log is very incomplete.
Do you have a backup of the system so you could rerun the upgrade
process with debugging enabled?
Or do have at least a complete log of the upgrade process, to see which
packages were involved?
Otherwise there is unfortunately not a lot we can do.
It's basically dpkg/apt that decides to remove systemd for some reason.
And the systemd preinst script prevents that (as intended).
Can you check, if you have packages installed, that conflict with systemd?

[Michael Biebl]

Do you have a backup of the system from before the update (basically a
copy of /var/lib/dpkg/status)? If not, there is probably zero chance to
find out why apt decided to remove systemd.