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

Hi there,
I’ve just performed the migration to Bookworm.
Thank you to all the dev, testers, translators, for the fantastic work you did, and I can say that this migration was easier to me than the previous ones. Thanks a lot, so happy!
On my side, it’s not all over yet, and I’m encountering a few problems:

  • first of all, to share my experience, I’m using Yunohost on a RPi 3B+, I encountered the problem of free space on /boot, the famous 70MB limit (I only had 18MB free), I had trouble finding the message that explains how to work around : Migration Yunohost 11.3.0.2 towards 12 / lacking space in /boot/ - #2 by Aleks so I started with a manual migration to Debian12 (and I think I overwritten some conf files…), the installation failed, I then modified the Yunohost install file to get around the 70MB limit and everything went fine (it took about 2 hours).
  • the main problem I encounter is that MySQL is dead:
    I tryed:
    sudo systemctl status mysql.service
    Warning: The unit file, source configuration file or drop-ins of mysql.service changed on disk. Run 'systemctl daemon-reload' to reload units.
    â—‹ mysql.service
    Loaded: error (Reason: Unit mysql.service failed to load properly, please adjust/correct and reload service manager: File exists)
    Active: inactive (dead)
    Then:
    systemctl daemon-reload
    and then:
    sudo yunohost service restart mysql
    Failed to restart mysql.service: Unit mysql.service failed to load properly, please adjust/correct and reload service manager: File exists
    See system logs and 'systemctl status mysql.service' for details.
    Warning: Could not execute the command 'systemctl restart mysql'
    Error: Could not restart the service 'mysql'
    Recent service logs:-- No entries --
    “File exists”? what that, what file?
    Does it speak to you?