Migration to 11 won’t start : “libc6-dev : Breaks: libgcc-8-dev”

Mon serveur YunoHost

**Matériel: Raspberry Pi 4
Version de YunoHost: 4.4.3
J’ai accès à mon serveur : En SSH + Par la webadmin
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : oui
Si oui, expliquer: Migration vers Bullseye

Bonjour à tous,

Comme certains dans ce forum (Migration to 11 won't start : "libc6-dev : Breaks: libgcc-8-dev"), je n’arrive pas à faire la migration vers bullseye (oui, j’ai trainé :smiley: )

Voici la log complète de mon erreur : https://paste.yunohost.org/raw/ininujewey

J’ai essayé d’appliquer les conseils déjà prodigués sur le forum, sans grand succès :

dpkg -s $(dpkg --list | grep ynh-deps | awk ‘{print $2}’) | grep ‘Package:|Depends:’ | grep ‘build|gcc|g++’ -B1

Retourne :

Package: jellyfin-ynh-deps
Depends: libass9, libbluray2, libc6, libdrm2, libfontconfig1, libfreetype6, libfribidi0, libgcc1, libgmp10, libgnutls30, libllvm11, libmp3lame0, libopus0, libstdc++6, libtheora0, libvdpau1, libvorbis0a, libvorbisenc2, libwebp6, libwebpmux3, libx11-6, libxcb-randr0, libzvbi0, zlib1g, libvpx5, libx264-155, libx265-165, at, libsqlite3-0, libssl1.1, jellyfin-web (= 10.8.5-1), jellyfin-ffmpeg5 (= 5.1.1-2-buster), jellyfin-server (= 10.8.5-1)

apt policy libgcc-8-dev

Retourne :

libgcc-8-dev:
  Installed: 8.3.0-6+rpi1
  Candidate: 8.4.0-7+rpi1
  Version table:
     8.4.0-7+rpi1 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
 *** 8.3.0-6+rpi1 100
        100 /var/lib/dpkg/status

apt policy gcc-8-base

Retourne :

gcc-8-base:
  Installed: 8.3.0-6+rpi1
  Candidate: 8.4.0-7+rpi1
  Version table:
     8.4.0-7+rpi1 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
 *** 8.3.0-6+rpi1 100
        100 /var/lib/dpkg/status

Et LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none sudo apt install --quiet -o=Dpkg::Use-Pty=0 --fix-broken --assume-yes gcc-8- libgcc-8-dev- debhelper dh-autoreconf

Retourne :

Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 dh-autoreconf : Depends: libtool (>= 2.4.2) but it is not going to be installed
 guacamole-ynh-deps : Depends: libjpeg62-turbo-dev but it is not going to be installed
                      Depends: libpng-dev but it is not going to be installed
                      Depends: libtool-bin but it is not going to be installed
                      Depends: libpango1.0-dev but it is not going to be installed
                      Depends: libssh2-1-dev but it is not going to be installed
                      Depends: libvncserver-dev but it is not going to be installed
                      Depends: libwebsockets-dev but it is not going to be installed
                      Depends: libpulse-dev but it is not going to be installed
 homeassistant-ynh-deps : Depends: python3-dev but it is not going to be installed
                          Depends: libjpeg-dev
                          Depends: zlib1g-dev but it is not going to be installed
                          Depends: libmariadb-dev but it is not going to be installed
                          Depends: libmariadb-dev-compat but it is not going to be installed
                          Depends: rustc
 jupyterlab-ynh-deps : Depends: python3-dev but it is not going to be installed
                       Depends: libzmq3-dev but it is not going to be installed
 libgirepository-1.0-1 : Breaks: python3-gi (< 3.34.0-4~) but 3.30.4-1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Merci d’avance pour votre aide, et j’en profite pour vous remercie pour Yunohost, que j’utilise avec beaucoup de plaisir depuis quelques années !

C’est sans doute python3-gi et libgi-truc qui posent problème

Regardons ce que raconte apt remove python3-gi --dry-run

Salut,

Pour apt remove python3-gi --dry-run

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  python3-gi
0 upgraded, 0 newly installed, 1 to remove and 1147 not upgraded.
Remv python3-gi [3.30.4-1]

Il n’a pas l’air de râler pour le moment, on dirait ?

En revanche pour

apt remove libgirepository-1.0-1 --dry-run

NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 guacamole-ynh-deps : Depends: libjpeg62-turbo-dev but it is not going to be installed
                      Depends: libpng-dev but it is not going to be installed
                      Depends: libtool-bin but it is not going to be installed
                      Depends: libpango1.0-dev but it is not going to be installed
                      Depends: libssh2-1-dev but it is not going to be installed
                      Depends: libvncserver-dev but it is not going to be installed
                      Depends: libwebsockets-dev but it is not going to be installed
                      Depends: libpulse-dev but it is not going to be installed
 homeassistant-ynh-deps : Depends: python3-dev but it is not going to be installed
                          Depends: libjpeg-dev
                          Depends: zlib1g-dev but it is not going to be installed
                          Depends: libmariadb-dev but it is not going to be installed
                          Depends: libmariadb-dev-compat but it is not going to be installed
                          Depends: rustc
 jupyterlab-ynh-deps : Depends: python3-dev but it is not going to be installed
                       Depends: libzmq3-dev but it is not going to be installed
 yunohost : Depends: equivs but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Et autre bizarrerie, dans mon sources.list, j’ai les repo bulleye, on dirait que l’outil de migration n’a pas revert lorsqu’il a rencontré ses erreurs

deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi

Oui c’est le comportement attendu

Yes donc allons-y :

apt remove python3-gi

puis ensuite tu peux retenter la migration

La suppression de python3-gi est ok :

sudo apt remove python3-gi

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  python3-gi
0 upgraded, 0 newly installed, 1 to remove and 1147 not upgraded.
After this operation, 895 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 102200 files and directories currently installed.)
Removing python3-gi (3.30.4-1) ...

En revanche, une migration depuis l’interface coince toujours :

https://paste.yunohost.org/raw/redunixibe

2023-08-30 11:55:22,233: INFO - +  libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed

Mokay alors essayons de forcer la main un peu à apt (ou alors en tout cas on devrait obtenir plus de détails sur ce qui bloque vraiment) avec :

LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none apt install --quiet -o=Dpkg::Use-Pty=0 --fix-broken --assume-yes gcc-8- libgcc-8-dev- guacamole-ynh-deps jupyterlab-ynh-deps homeassistant-ynh-deps dh-autoreconf libtool python3-dev libpng-dev zlib1g-dev libmariadb-dev libzmq3-dev

Cette fois ci j’ai ça :

Reading package lists...
Building dependency tree...
Reading state information...
guacamole-ynh-deps is already the newest version (1.4.0~ynh1).
homeassistant-ynh-deps is already the newest version (2022.5.4~ynh1).
jupyterlab-ynh-deps is already the newest version (3.4.2~ynh1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 moulinette : Depends: python3-yaml but it is not going to be installed
              Depends: python3-gevent-websocket but it is not going to be installed
 yunohost : Depends: python3-lexicon but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Mouai donc continuons de creuser … (apt est super chiant, des fois y’a pas de probleme, mais il faut lui demander explicitement pleins de truc pour qu’il finisse par le faire)

LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none apt install --quiet -o=Dpkg::Use-Pty=0 --fix-broken --assume-yes gcc-8- libgcc-8-dev- guacamole-ynh-deps jupyterlab-ynh-deps homeassistant-ynh-deps dh-autoreconf libtool python3-dev libpng-dev zlib1g-dev libmariadb-dev libzmq3-dev python3-yaml python3-gevent-websocket python3-lexicon

Il y’a du mieux !

En exécutant ta commande (qui a mouliné un bon petit moment) :

sudo LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none apt install --quiet -o=Dpkg::Use-Pty=0 --fix-broken --assume-yes gcc-8- libgcc-8-dev- guacamole-ynh-deps jupyterlab-ynh-deps homeassistant-ynh-deps dh-autoreconf libtool python3-dev libpng-dev zlib1g-dev libmariadb-dev libzmq3-dev python3-yaml python3-gevent-websocket python3-lexicon smbclient

(j’ai ajouté smbclient car nextcloud râlait un peu de la même façon que depuis le début avec cette fois ci smb client)

J’obtient :

systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-241.so: cannot open shared object file: No such file or directory
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error exit status 127
Setting up gfortran (4:10.2.1-1+rpi1) ...
Setting up python3-dev (3.9.2-3) ...
Setting up libsmbclient:armhf (2:4.13.13+dfsg-1~deb11u5) ...
Setting up smbclient (2:4.13.13+dfsg-1~deb11u5) ...
dpkg: dependency problems prevent configuration of libpam-systemd:armhf:
 libpam-systemd:armhf depends on systemd (= 247.3-7+rpi1+deb11u2); however:
  Package systemd is not configured yet.

dpkg: error processing package libpam-systemd:armhf (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-systemd:armhf:
 libnss-systemd:armhf depends on systemd (= 247.3-7+rpi1+deb11u2); however:
  Package systemd is not configured yet.

dpkg: error processing package libnss-systemd:armhf (--configure):
 dependency problems - leaving unconfigured
Processing triggers for dbus (1.12.24-0+deb10u1) ...
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ...
Processing triggers for man-db (2.8.5-2) ...
Errors were encountered while processing:
 systemd
 libpam-systemd:armhf
 libnss-systemd:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)

Et en lançant via l’outil de migration depuis l’interface web :
https://paste.yunohost.org/raw/bomiferuxe (mariadb est accusé, j’imagine à tort, ça semble plus lié à systemd ?)

Mokay alors commencons par résoudre les warnings dans les logs a propos du composant “ui” qui n’existe pas / plus :

grep -nr ui /etc/apt/sources.list*

devrait lister les lignes problématiques

Il faut ouvrir le fichier avec nano <chemin_complet_du_fichier>, enlever le mot clef “ui” de la ligne, sauvegarder/quitter avec Ctrl+X, puis Y, puis Entrée

grep -nr ui /etc/apt/sources.list*

retourne

/etc/apt/sources.list.d/raspi.list:1:deb http://archive.raspberrypi.org/debian/ bullseye main ui
/etc/apt/sources.list.d/raspi.list:3:#deb-src http://archive.raspberrypi.org/debian/ bullseye main ui

J’ai modifié ces deux lignes dans /etc/apt/sources/list.d/raspi.list

En relancant la migration depuis l’interface web, j’obtiens à vue de nez la même erreur:
https://paste.yunohost.org/raw/ovugehitic

Et en relançant

sudo LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none apt install --quiet -o=Dpkg::Use-Pty=0 --fix-broken --assume-yes gcc-8- libgcc-8-dev- guacamole-ynh-deps jupyterlab-ynh-deps homeassistant-ynh-deps dh-autoreconf libtool python3-dev libpng-dev zlib1g-dev libmariadb-dev libzmq3-dev python3-yaml python3-gevent-websocket python3-lexicon smbclient

Même chose :

Reading package lists...
Building dependency tree...
Reading state information...
Package 'gcc-8' is not installed, so not removed
Package 'libgcc-8-dev' is not installed, so not removed
dh-autoreconf is already the newest version (20).
libmariadb-dev is already the newest version (1:10.5.19-0+deb11u2).
libpng-dev is already the newest version (1.6.37-3).
libtool is already the newest version (2.4.6-15).
libzmq3-dev is already the newest version (4.3.4-1).
python3-dev is already the newest version (3.9.2-3).
python3-gevent-websocket is already the newest version (0.10.1-4).
python3-yaml is already the newest version (5.3.1-5).
smbclient is already the newest version (2:4.13.13+dfsg-1~deb11u5).
zlib1g-dev is already the newest version (1:1.2.11.dfsg-2+deb11u2).
python3-lexicon is already the newest version (3.11.2+ynh11-1).
guacamole-ynh-deps is already the newest version (1.4.0~ynh1).
homeassistant-ynh-deps is already the newest version (2022.5.4~ynh1).
jupyterlab-ynh-deps is already the newest version (3.4.2~ynh1).
The following packages were automatically installed and are no longer required:
  cpp-8 dh-python libasan5 libpython2-stdlib libpython3.7-dev libtasn1-doc python2 python2-minimal python2.7 python2.7-minimal python3-msgpack python3.7-minimal rpi.gpio-common
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 1032 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up systemd (247.3-7+rpi1+deb11u2) ...
systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-241.so: cannot open shared object file: No such file or directory
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error exit status 127
dpkg: dependency problems prevent configuration of libpam-systemd:armhf:
 libpam-systemd:armhf depends on systemd (= 247.3-7+rpi1+deb11u2); however:
  Package systemd is not configured yet.

dpkg: error processing package libpam-systemd:armhf (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-systemd:armhf:
 libnss-systemd:armhf depends on systemd (= 247.3-7+rpi1+deb11u2); however:
  Package systemd is not configured yet.

dpkg: error processing package libnss-systemd:armhf (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 systemd
 libpam-systemd:armhf
 libnss-systemd:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)

Essayons ça même si pas sur à 100% que ça résolve le problème:

sudo cp /usr/lib/systemd/libsystemd-shared-247.so /usr/lib/
sudo apt --fix-broken install systemd-sysv
sudo apt-get --reinstall install systemd

(si l’une des deux dernières commandes renvoie des erreurs, inutile de relancer la migration pour le moment)

Tu es certain pour libsystemd-shared-247.so ? (la log parle de libsystemd-shared-241.so)

Ah oui effectivement il faut remplacer 247 par 241

C’est un peu la mé-merde :smiley:

Sur sudo apt --fix-broken install systemd-sysv

J’ai :

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cpp-8 dh-python libasan5 libpython2-stdlib libpython3.7-dev libtasn1-doc python2 python2-minimal python2.7 python2.7-minimal python3-msgpack python3.7-minimal rpi.gpio-common
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  systemd-sysv
1 upgraded, 0 newly installed, 0 to remove and 1031 not upgraded.
3 not fully installed or removed.
Need to get 114 kB of archives.
After this operation, 15.4 kB of additional disk space will be used.
Get:1 http://mirrors.ircam.fr/pub/raspbian/raspbian bullseye/main armhf systemd-sysv armhf 247.3-7+rpi1+deb11u2 [114 kB]
Fetched 114 kB in 0s (429 kB/s)
Reading changelogs... Done
Setting up systemd (247.3-7+rpi1+deb11u2) ...
[/usr/lib/tmpfiles.d/fail2ban-tmpfiles.conf:1] Line references path below legacy directory /var/run/, updating /var/run/fail2ban → /run/fail2ban; please update the tmpfiles.d/ drop-in file accordingly.

Et surtout un crash violent !

J’ai rédémarré le pi, il ne ping plus. Il faut que je le branche sur un écran pour voir s’il est parti en mode rescue.

(Et je crois que je vais sortir mes backups :smiley: )

Bon, au boot je tombe au bout de 3 secondes sur le message :

end kernel panic not syncing attempted to kill init exit code=0x000000100

ça vaut le coup d’investiguer plus ou je pars sur une install fresh avec restauration de backups ? (la question bonus : j’imagine que si j’installe directement la version 11, je ne pourrais pas restaurer mes backups faits sur 4.4.3, si ?)

Petit retour d’expérience :

J’ai en effet dû repartir d’une fresh install en Bulleyes, la bonne nouvelle, c’est qu’en globalité, mes backups faits en version 4.x étaient fonctionnels !

Merci pour le support apporté, dans tous les cas :slight_smile:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.