🚀 YunoHost 12.0 (Bookworm) release / Sortie de YunoHost 12.0 (Bookworm)

Thanks for all the work

I migrated but with lot of error.
I share the log and i think i’ll restore my vm

https://paste.yunohost.org/raw/picotahabi
https://paste.yunohost.org/raw/ludimokefi
https://paste.yunohost.org/raw/edekujoyof
https://paste.yunohost.org/raw/elogidadek
https://paste.yunohost.org/raw/urulowimuc
https://paste.yunohost.org/raw/ixagojahah
https://paste.yunohost.org/raw/hapenadozi

The mains problĂšmes seems to be related with:
Python 3.11 and 3.12
An option: “wheel” and --use-pep517
An other : aiohasupervisor==0.1.0

It’s a problùme for the app:
paperless-ngx
homeassistant
libretranslate
searxng

I Hope it will be helpfull


Congrats to the yunohost teams !
I migrated my 3 servers easily, everything runs smooth.
Thank you so much for the work you’ve done there.
I’ll definitly look for a way to help, it’s time for me to contribute.
See you soon !

1 Like

Bravo Ă  tous les contributeurs de cette magnifique distro! J’ai fait la migration ce matin, tout s’est bien passĂ©, Ă  l’exception de Snappymail qui m’affichait un message d’erreur, mĂȘme en forçant la migration. J’ai dĂ©sinstallĂ© l’appli et l’ai reinstallĂ©e, et maintenant elle fonctionne Ă  merveille. Encore bravo, et merci pour cette version qui s’appuie sur Bookworm et que j’attendais avec impatience

2 Likes

Hello Ă  tous !
Hormis une erreur de php7.3-fpm rĂ©solu par la suppression d’un fichier de config d’une ancienne application, tout s’est parfaitement bien dĂ©roulĂ©.
Mon serveur est à présent en version 12.0.6 (stable) et ne rencontre aucun problÚme à cet instant.
Bravo pour le boulot Ă  toute l’équipe !

3 Likes

Hi,

Before upgrading to ynh 12, I am wondering my options.

I don’t have an usual Ynh install: on my RPI 4 I needed a 64bits install in order to use Collabora with Nextcloud. So, I installed a Debian 11 64bits, and then I installed Ynh on it.

Is it safe to update ynh (and thus the Debian it is installed on) by the usual method, or should I use a different path?

Yes it shouldn’t matter that much, as far as I can remember there shouldnt be any specific difference related to this

1 Like

Upgrade went really fine: thanks to all developers, much love!

I have only two little troubles:

  • calibreweb is not reachable. Today I have not time to investigate more, I hope tomorrow;
  • I had to reinstall metronome because, again, I don’t have time to try the “new” prosody. Next days!

I migrated one server today, and it went quite well, many thanks to all involved for that!

I encountered two minor problems:

  1. Prerequisites not met didn’t display any error messages, the migration page refreshed as if nothing had happened. The error was listed in the log, so no big deal.
  2. Due to the new SSO system, and an unusual setup on my side, I couldn’t log in the portal anymore. I used a bogus domain.tld that points to another server, with the main domain on sub.domain.tld. Deleting it solved my problem. Now, every subdomain has its own portal, but I can live with that.

Thanks again for all the hard work! :heart:

1 Like

Thanks for the clarification.

My setup is a little different. The DNS entry for the main domain points to a different server than yunohost.

I have a nextcloud running on example.org which is on a server sitting in my home and yunohost running under yunohost.example.org. But yunohost should handle the mails for example.org as well. With yunohost 11 this worked.
But now if i try to login to yunohost I get always thrown to the IP of example.org.

Setup with yunohost 11: Mail on main domain, yunohost on subdomain

I’m thankful for your thought, if this setup is still possible with yunohost 12.

Best regards!
Samuel

My migration did not complete since I got an error for PHP 7.3 fpm. While trying to re do the migration I had to go and apt autoremove a kernel due to limited space in boot. I got the below error:

sudo apt autoremove --purge
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  linux-image-5.10.0-32-amd64*
0 upgraded, 0 newly installed, 1 to remove and 5 not upgraded.
1 not fully installed or removed.
After this operation, 318 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 114889 files and directories currently installed.)
Removing linux-image-5.10.0-32-amd64 (5.10.223-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.10.0-32-amd64
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.0-26-amd64
Found initrd image: /boot/initrd.img-6.1.0-26-amd64
Found linux image: /boot/vmlinuz-5.10.0-33-amd64
Found initrd image: /boot/initrd.img-5.10.0-33-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
Setting up php7.3-fpm (7.3.33-21+0~20240927.121+debian12~1.gbp15d8b1) ...
Job for php7.3-fpm.service failed because the control process exited with error code.
See "systemctl status php7.3-fpm.service" and "journalctl -xeu php7.3-fpm.service" for details.
invoke-rc.d: initscript php7.3-fpm, action "restart" failed.
● php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
     Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; disabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Sun 2024-11-03 23:42:24 EET; 25ms ago
       Docs: man:php-fpm7.3(8)
    Process: 2043102 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exited, status=78)
    Process: 2043103 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.3/fpm/pool.d/www.conf 73 (code=exited, status=0/SUCCESS)
   Main PID: 2043102 (code=exited, status=78)
        CPU: 59ms
dpkg: error processing package php7.3-fpm (--configure):
 installed php7.3-fpm package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 php7.3-fpm
E: Sub-process /usr/bin/dpkg returned an error code (1)

After migrating to 12 i can’t change the app domain without setting a folder.
Like tld.com instead of tld.com/folder.
Is that normal or a bug?

The users settings can not be changed. There is a bug. I can not edit any users permissions. Should I create a topic for it or here is fine?

PS: Thanks for all the hardwork

We do not read crystal balls. If you “can’t” then explain what happens exactly : what happens when you try, share error messages if any

1 Like

Yeah, I thought it would be clear, my bad. But it’s really as I said. When I click on the users edit permission page. Page is just stuck. You can not just enter that page where you edit users permissions.

More simply:

Yunohost settings page>Users>Edit permissions

The page is just stuck

Bonjour, je reviens tardivement pour vous féliciter pour la mise à jour !

AprĂšs le contretemps dĂ» Ă  l’erreur de clĂ© GPG que j’ai dĂ©jĂ  signalĂ©e la mise Ă  jour s’est bien dĂ©roulĂ©e et a permis de rendre fonctionnels Vaultwarden et LibreTranslate !

À noter que l’adresse IPv6 de mon serveur a changĂ©, je ne sais pas pourquoi, ça a causĂ© quelques difficultĂ©s avec mon VPN jusqu’à ce que je m’en rende compte et mette Ă  jour mes DNS.

J’ai eu quelques galĂšres qui m’ont pris une partie de la nuit mais qui sont dĂ»es Ă  mes bricolages personnels et non Ă  YunoHost lui-mĂȘme, et que j’ai fini par rĂ©soudre.

DĂ©tails

Comme j’utilise ejabberd installĂ© en .deb comme serveur XMPP j’ai vite constatĂ© qu’il ne fonctionnait plus correctement. J’ai compris que mariadb avait Ă©tĂ© dĂ©sinstallĂ© et ai donc dĂ» la rĂ©installer manuellement. J’ai ensuite compris qu’il y avait un problĂšme avec l’authentification LDAP vu que la permission XMPP avait Ă©tĂ© supprimĂ©e; j’ai fini par trouver qu’il fallait supprimer la ligne ldap_filters de la conf d’ejabberd

J’envoie donc un grand merci à tous les contributeurs :heart:

Hello everyone. It’s incredible. I migrated to yunohost 12.0.6 yesterday and everything works great. Yunohost is installed in Proxmox LXC. I am very grateful to everyone involved in the project for their work.

2 Likes


I cannot change the url of an app without a subfolder, right now its forumsons[.]com/forumsons and i can’t change to forumsons[.]com.
When i click save button nothing happens

2 Likes

I also checked, I have this issue also. The URL extension can not be empty and saved.

1 Like

I also encountered this problem, but already installed applications work properly.

I wonder if anyone else is also having issue with manage user permissions page. Please let me know :slight_smile: