I still have the issue 
(Iâll use the manual way)
hello Yuno, bonjour @Aleks
jâai tentĂ© la migration Ă partir de ma sauvegarde en 4.4.2 dâhier, le passage en 4.4.2.3 se passe bien, au lancement de la migration vers 11, ça bloque comme si je nâavais pas appliquĂ© les mesures que tu as dĂ©crites ici:
je nâapplique pas les mesures manuellement pour pousser le test jusquâau bout 
(pour mĂ©moire je suis sur un PI400, et tu mâas aidĂ© ici)
1 Like
Tu veux dire que lorsque tu reboot il nây a pas de rĂ©seau ? Est-ce que tu peux regarder si le contenu du fichier /etc/systemd/system/dhcpcd.service.d/wait.conf est le bon ?
Okay, Iâm stuck. âŠ
I removed Mobilizon Application and tried to do the migration, but obviously removing the database failed and because of this the migrations still fails. 
There are some other applications failing (searx, synapse, lufi, moodle), but I think this is mostly because of postgresql or php7.3.
So Iâll have to wait and fix it later.
Quâest-ce que tu veux dire par âla migration ne se fait pasâ ? Quelle migration ? Est-ce que tu peux partager le log complet ?
pour tester les derniĂšres mises au point, je suis repartie dâune sauvegarde en 4.4.2
Elle est bien passĂ©e en 4.4.2.3, puis jâai lancĂ© la migration qui Ă©choue. voici le log
câest exactement ce qui ce passait avant cette Ă©tape
1 Like
Donc câest le probleme de libc6 et non pas le probleme de dhcpcd ⊠Jâessaye de patcher la migration dĂšs que jâai 2 minutes de tranquilles pour coder âŠ
3 Likes
Courage
(et merci pour le travail de support qui déchire 
)
3 Likes
arf, jâai mis Ă jour le lien vers le bon post dans mon premier message, du coup je ne tâai pas aiguillĂ© sur le bon pb⊠
encore merci pour tout (le boulot, lâassistance, la prĂ©sence, ⊠)
je le laisse online pour le moment
I definitely feel sorry for poor @Aleks. I think we need to collect vitamins for his brain for him
Der arme @Aleks tut mir eindeutig leid. Ich glaube, wir mĂŒssen fĂŒr ihn sammeln Vitaminstoffe fĂŒr sein Gehirn 
1 Like
I did (and un-did) it before already, but here is what it actually says (short: nothing changed):
# apt install postgresql-postgis
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package postgresql-postgis is a virtual package provided by:
postgresql-11-postgis-2.5 2.5.1+dfsg-1
postgresql-13-postgis-3 3.1.1+dfsg-1
You should explicitly select one to install.
E: Package 'postgresql-postgis' has no installation candidate
Okay, then letâs name it explicitly:
# apt install postgresql-11-postgis-2.5 postgresql-13-postgis-3
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
postgresql-11-postgis-2.5 is already the newest version (2.5.1+dfsg-1).
postgresql-11-postgis-2.5 set to manually installed.
The following NEW packages will be installed:
postgresql-13-postgis-3 postgresql-13-postgis-3-scripts
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,452 kB of archives.
After this operation, 37.1 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 postgresql-13-postgis-3-scripts all 3.1.1+dfsg-1 [1,085 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 postgresql-13-postgis-3 amd64 3.1.1+dfsg-1 [3,366 kB]
Fetched 4,452 kB in 0s (44.1 MB/s)
Selecting previously unselected package postgresql-13-postgis-3-scripts.
(Reading database ... 79058 files and directories currently installed.)
Preparing to unpack .../postgresql-13-postgis-3-scripts_3.1.1+dfsg-1_all.deb ...
Unpacking postgresql-13-postgis-3-scripts (3.1.1+dfsg-1) ...
Selecting previously unselected package postgresql-13-postgis-3.
Preparing to unpack .../postgresql-13-postgis-3_3.1.1+dfsg-1_amd64.deb ...
Unpacking postgresql-13-postgis-3 (3.1.1+dfsg-1) ...
Setting up postgresql-13-postgis-3-scripts (3.1.1+dfsg-1) ...
update-alternatives: using /usr/share/postgresql/13/extension/postgis-3.control to provide /usr/share/postgresql/13/extension/postgis.control (postgresql-13-postgis.control) in auto mode
Setting up postgresql-13-postgis-3 (3.1.1+dfsg-1) ...
Processing triggers for postgresql-common (225) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
Updating coolwsd systemplate
and now try to migrate again:
# LC_ALL=C pg_upgradecluster -m upgrade 11 main
Restarting old cluster with restricted connections...
Notice: extra pg_ctl/postgres options given, bypassing systemctl for start operation
Stopping old cluster...
Creating new PostgreSQL cluster 13/main ...
/usr/lib/postgresql/13/bin/initdb -D /var/lib/postgresql/13/main --auth-local peer --auth-host md5 --encoding UTF8 --lc-collate en_US.UTF-8 --lc-ctype en_US.UTF-8
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.UTF-8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /var/lib/postgresql/13/main ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Europe/Berlin
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
Success. You can now start the database server using:
pg_ctlcluster 13 main start
Ver Cluster Port Status Owner Data directory Log file
13 main 5433 down postgres /var/lib/postgresql/13/main /var/log/postgresql/postgresql-13-main.log
/usr/lib/postgresql/13/bin/pg_upgrade -b /usr/lib/postgresql/11/bin -B /usr/lib/postgresql/13/bin -p 5432 -P 5433 -d /etc/postgresql/11/main -D /etc/postgresql/13/main
Finding the real data directory for the source cluster ok
Finding the real data directory for the target cluster ok
Performing Consistency Checks
-----------------------------
Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for system-defined composite types in user tables ok
Checking for reg* data types in user tables ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for tables WITH OIDS ok
Checking for invalid "sql_identifier" user columns ok
Creating dump of global objects ok
Creating dump of database schemas
ok
Checking for presence of required libraries fatal
Your installation references loadable libraries that are missing from the
new installation. You can add these libraries to the new installation,
or remove the functions using them from the old installation. A list of
problem libraries is in the file:
loadable_libraries.txt
Failure, exiting
Error: pg_upgrade run failed. Logfiles are in /var/log/postgresql/pg_upgradecluster-11-13-main.1dey
Error during cluster dumping, removing new cluster
Cluster is not running.
Error: could not stop old cluster, please do that manually
and finaly:
# cat /var/log/postgresql/pg_upgradecluster-11-13-main.1dey/loadable_libraries.txt
could not load library "$libdir/postgis-2.5": ERROR: could not access file "$libdir/postgis-2.5": No such file or directory
In database: mobilizon
could not load library "$libdir/rtpostgis-2.5": ERROR: could not access file "$libdir/rtpostgis-2.5": No such file or directory
In database: mobilizon
1 Like
Bonjour,
Migration rĂ©alisĂ©e sans problĂšme aujourdâhui.
Bravo et merci Ă tous les contributeurs.
Juste quelques messages dâerreur apparaissent sur ma page dâaccueil PIWIGO :
Deprecated: Invalid characters passed for attempted conversion, these have been ignored in /var/www/piwigo/include/template.class.php on line 215
Deprecated: Invalid characters passed for attempted conversion, these have been ignored in /var/www/piwigo/include/template.class.php on line 1024
Deprecated: Invalid characters passed for attempted conversion, these have been ignored in /var/www/piwigo/include/template.class.php on line 1024
Deprecated: Invalid characters passed for attempted conversion, these have been ignored in /var/www/piwigo/include/template.class.php on line 1899
@beelu : Version 4.4.2.4 should have a better detection and auto-patching for the libc6 / libgcc-8-dev hell. Though if you already ran the migration once, your sources.list now points to bullseye so youâll need to manually tweak them to get backup to buster, then apt install yunohost=4.4.2.4, then retry the migration
1 Like
@Aleks jâai âmerdĂ©â en cours de route donc reparti Ă zĂ©ro 
dâune 4.3.6.3 jâsuis passĂ© sur en 4.4.2.5.
La migration de 4.x.x vers 11.x ne passe pas, voici le log ,semble toujours venir de libc6
@beelu : 
Si jamais tâes dispo sur le chat et que ton instance est âjetableâ ce serait cool de se faire un tmux ou un screen pour regarder le truc ensemble en interactif plutĂŽt que de galĂ©rer Ă se synchro sur le forum. Jâai quelques idĂ©es supplĂ©mentaires que jâaimerais tester mais câest galĂšre sans avoir accĂšs directement Ă un RPi sous Buster
1 Like
Hello,
en ce qui me concerne, cette mise Ă jour, appliquĂ©e sur une installation fraiche et un Raspberry 4 8Go, nâa plus gĂ©nĂ©rĂ©e dâerreurs bloquantes ou la disparition du rĂ©seau au redĂ©marrage.
Par contre, la migration de lâapplication searx nâa pas Ă©tĂ© fonctionnelle (mĂȘme avec yunohost app upgrade -F searx) et a nĂ©cessitĂ© une dĂ©sinstallation puis une rĂ©installation.