YunoHost 11.0 (Bullseye) release / Sortie de YunoHost 11.0 (Bullseye)

Yeah … but please forget about apt-get upgrade … This command only does a “partial upgrade” … 99.99% of the time, what you really want to do is apt full-upgrade

Back to the php issues, let’s try to run :

apt install php7.4-common=7.4.32-1+0~20220929.71+debian11~1.gbpe9c007 php7.4-fpm=7.4.32-1+0~20220929.71+debian11~1.gbpe9c007 php7.4-zip=7.4.32-1+0~20220929.71+debian11~1.gbpe9c007 php7.4-ldap php7.4-intl php7.4-mysql php7.4-gd php7.4-curl php-php-gettext php7.4-apcu php7.4-bcmath php7.4-bz2 php7.4-dom php7.4-gmp php7.4-igbinary php7.4-imagick php7.4-imap php7.4-mbstring php7.4-redis php7.4-sqlite3 php7.4-xml --dry-run

thank you for this input as well. I did it + restart through web admin but result is the same. I believe it doesn’t like me :smile:
when I try to enter libreddit URL it lands on " 502 Bad Gateway"
libreddit.service logfile

Thanks for looking at this issue with a beginner…

So with your suggested command I have:

admin@nos:~$ apt install php7.4-common=7.4.32-1+0~20220929.71+debian11~1.gbpe9c007 php7.4-fpm=7.4.32-1+0~20220929.71+debian11~1.gbpe9c007 php7.4-zip=7.4.32-1+0~20220929.71+debian11~1.gbpe9c007 php7.4-ldap php7.4-intl php7.4-mysql php7.4-gd php7.4-curl php-php-gettext php7.4-apcu php7.4-bcmath php7.4-bz2 php7.4-dom php7.4-gmp php7.4-igbinary php7.4-imagick php7.4-imap php7.4-mbstring php7.4-redis php7.4-sqlite3 php7.4-xml --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... Done
Reading state information... Done
Note, selecting 'php7.4-xml' instead of 'php7.4-dom'
E: Version '7.4.32-1+0~20220929.71+debian11~1.gbpe9c007' for 'php7.4-common' was not found
E: Version '7.4.32-1+0~20220929.71+debian11~1.gbpe9c007' for 'php7.4-fpm' was not found
E: Version '7.4.32-1+0~20220929.71+debian11~1.gbpe9c007' for 'php7.4-zip' was not found

Finally, the migration to Yunohost 11 and Debian 11 has been successful :tada:
A huge thanks to @Aleks and @wbk for your patience, advices and the time you spent on my small family Yunohost server.

I am so happy because this small server is working continuously since January 2017 and may continue some more years. It faced already two major migrations from Debian 9 to Debian 10, and now Debian 10 to Debian 11, without breaking any app :fireworks:
I still have all 5 years history on Nextcloud or Matrix for instance, and the reduced number of users of this server have never faced long interruption of services (two or three days only in 5 years). Almost better than AWS and definitively more reliable than Google who closes services regularly.
And with full ownership of data.

Thanks to all people involved in Yunohost, you are doing a fantastic job!

PS: Aleks, can you keep one hour for me when the migration to Debian 12 will be ready in case I face again some php dependencies issues :wink:

5 Likes

I run the migration now and it sadly looks like this:

There are some permission errors, e.g.: redis:

I will take a look tomorrow…

“Failed at NAMESPACE spawning” is typically symptomatic of a container (or LXC maybe ?) running without the security.nesting option set to true

1 Like

Yes, i run my YunoHost instance via Proxmox in a LXC. And yes, nesting was not activated, yet. This was fine with YunoHost v4… Is it now needed for Debian 11?

I will set the feature and reboot YunoHost…

EDIT: Activating “nesting” seems to fix a few problems.

My Python projects are broken. It seems that the “recreating virtualenvs” doesn’t work in my case: The venv is “empty”:

root@YunoHost:/opt/yunohost/pyinventory# ./venv/bin/pip3 freeze
root@YunoHost:/opt/yunohost/pyinventory#

Maybe this is also related to nesting=0 ?

It’s not a big problem for me: I can just fix that, e.g.:

root@YunoHost:/opt/yunohost/pyinventory# ./venv/bin/pip3 install -r requirements.txt 
...
root@YunoHost:/opt/yunohost/pyinventory# systemctl restart pyinventory.service

After this, everything is fine.

A easier way to fix it: Just force update the apps, e.g.:

sudo yunohost app upgrade pyinventory --force
sudo yunohost app upgrade django-fritzconnection --force
sudo yunohost app upgrade django-fmd --force
sudo yunohost app upgrade django-for-runners --force

(Because my upgrade scripts will always delete the venv and recreate it)

Retex migration Buster → Bullseye sur mon serveur principal.

  • Migration faite via la webmin comme conseillé (555 warnings + quelques dizaines dans la suivante).
    – App LSTU cassée : Error 502 → Réinstallation
    – App Calibreweb cassée : Error 502 → Réparée avec une MaJ forcée : yunohost app upgrade calibreweb -F ( [Calibre-web] Manage your ebooks - #109 by Mamie )

Tous le reste semble OK, bon boulot les gars :+1:

1 Like

Nouvelle mise à jour (d’un gros serveur) OK ! Super boulot, la team Yuno ! On a du juste supprimer Galene qu’il faut réinstaller si besoin…
liste des apps:

id: coturn
dokuwiki
dolibarr   
etherpad_mypads
gitea
grav
istmonk
matomo
my_webapp
nodered
osticket
phpldapadmin
phpmyadmin
phpservermon
redirect
roundcube
sogo
wordpress
zabbix

just want to inform that after recent update my instance shows two messages at <yunohost/admin/#/update>
it’s already 11.0.10.1 (stable) for quite a long time, and I felt like it worth sharing
it seems to cause no problems though

There are some pending migrations waiting to be run. Please go to Tools > Migrations to run them.

A major YunoHost upgrade is available. It is heavily recommended to carefully read the release note(s) on the forum before upgrading : Browse the release notes on the forum

2 Likes

You have to restart yunohost-api :slight_smile:

1 Like

Whaou !

Alors là “Un grand bravo à toute l’équipe et toutes les personnes contributrices à ce merveilleux projet Yunohost!!!”

Mise à part un petit problème relatif à la place attribuée (confère le post Migration to V11: failed because of /boot/ has less than 70MB available ) , tout s’est réroulé comme une fleur sur ma pi 3!

Troooop Super cool !

Merciiiiii ! :pray:

1 Like

Petit retour d’expérience d’une migration en cours, juste pour garder une trace:

  • Mailman2 n’étant plus supporté (mais c’était très bien indiqué), j’ai:
  1. installé mailman3 (avec quelques soucis - voir Installlation doesn't work · Issue #34 · YunoHost-Apps/mailman3_ynh · GitHub)
  2. migré les listes via le script prévu sur Migrating from Mailman 2.1 to Mailman 3 — Mailman Suite 3.3 documentation, ce qui donne (en root) sudo -u list /usr/lib/mailman3/bin/mailman import21 nom-de-la-liste@domaine.tld /var/lib/mailman/lists/nom-de-la-liste/config.pck text
  3. Désinstallé mailman2
  • Z-push bloquait la migration parce que “des paquets suivants contiennent des dépendances non satisfaites : z-push-ynh-deps : Dépend: php7.3-memcached”
    N’utilisant plus ce paquets depuis des années, je l’ai simplement supprimé et ça a débloqué la situation.

Tout le reste s’est passé comme un charme. C’est impressionnant.
Merci à tout le monde pour l’immense travail derrière ce poussage de bouton sans accroc.

Hello à tous!
De mon côté une migration vers Bullseye comme du papier à musique, et l’autre qui semble avoir cassé LDAP qui n’est plus accessible (dans quasiment les mêmes conditions, mêmes rpi4 et mêmes apps installées :thinking:).
Dans tous les cas un grand merci pour le boulot!

edit: après un reboot je me retrouve plutôt dans un cas similaire à Mise a niveau qui sepasse mal - #17 by olitask
sans services nginx ni firewall ni hciuart

I I hit update, and I get the notification that YNH is now version Powered by YunoHost 11.1.0 (testing

There is a yellow flag saying go to tools/migrations to migrate. when I do that however I get:


[GET] /migrations?pending
YunoHost encountered an internal error
Really sorry about that.
You should look for help on the forum or the chat to fix the situation, or report the bug on the bugtracker.
The following information might be useful for the person helping you:
Error: "500"

Action: "GET" /yunohost/api/migrations?pending&locale=en

Error message:
Could not load migration 0025_global_settings_to_configpanel: cannot import name 'translate_legacy_settings_to_configpanel_settings' from 'yunohost.utils.legacy' (/usr/lib/python3/dist-packages/yunohost/utils/legacy.py)

Check for

maybe relatedly: I can no longer install applications (nothing appears) (fixed with a restart)

edit: the restart fixed this too. looks like the only issue is that the YunoHost banner (usually in tip left of webadmin) is missing. minor issue!

I just did the upgrade to YunoHost 11.1.0 and it is awesome to finally be able to log in in the admin interface with a normal user.

Thanks a lot for this big evolution !

1 Like

Je suis allé la fleur au fusil mettre à jour mon yunohost pour appliquer une mise à jour des paquets… et je me suis retrouvé à mettre à jour la majeure :sweat_smile:

A part mon blog pelican que je dois remettre d’équerre (python 2 → 3), toutes les applis sont up :tada:

Grand merci à toute l’équipe Yunohost, you are the best :heart: :heart: :heart:

1 Like

Wonderful work and thank you to the team and testers!

Migration done successfully on VPS OVH with applications Nextcloud and Roundcube.

From:

:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

:~$ sudo yunohost --version
yunohost: 
  repo: stable
  version: 4.4.2.14
yunohost-admin: 
  repo: stable
  version: 4.4.1
moulinette: 
  repo: stable
  version: 4.4.1
ssowat: 
  repo: stable
  version: 4.4.1

to:

:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye
:~$ sudo yunohost --version
yunohost: 
  repo: stable
  version: 11.0.10.2
yunohost-admin: 
  repo: stable
  version: 11.0.11
moulinette: 
  repo: stable
  version: 11.0.9
ssowat: 
  repo: stable
  version: 11.0.9

Some warnings were raised during the process.
Some were requested by the migration script.
Others seem not to have an impact on the well being of the server.
More info: hastebin

Thank you again!

Hi YunoHost!
As always thank you so much for the work! I migrated on a RPi 4 which went rather well except for a weird issue I have since then: port 993 is unreachable, and dovecot cannot be started. I’ve checked my router, the firewall but all is fine here. I presume dovecot cannot start because 993 is not found, but could this be the other way around?
Any idea? I may have some lag in my response time, because well… my port 993 is dead :crazy_face:

Port 993 is reported to be unreachable because dovecot cant start (as far as I know there’s no way to test that a port really is open without actually trying to establish a communication with it - hence why when a service is down, the corresponding ports are reported as unreachable)

Anyway, can you please share the log of Dovecot, to be found in Services > Dovecot > green button ‘Share logs with yunopaste’

1 Like