Robles Rodolphe

It is strange because between 31.0.4~ynh1 and 31.0.4~ynh2 there is not really such differences between the scripts...

Perhaps you can try edit the file `/etc/systemd/system/nextcloud-notify-push.service` below `[Unit]` ``` [Unit] Description=Push daemon for Nextcloud clients After=php8.3-fpm.service mysql.service redis.service ``` To prevent the service start before this services... Or...

really ? You may have a file `/etc/system/sytemd/nextcloud-notify-push.service`, the scripts here sure create it and also a file `/etc/systemd/system/nextcloud-notify-watcher-.service`. For the logs upgrade ,it seems you have a problem with...

I forget look all logs... in the restore log it stop does it stop here ? ``` 2025-04-18 20:27:54,551: DEBUG - ++ mysql -B nextcloud 2025-04-18 20:27:54,551: DEBUG - ++...

Perhaps you haven't wait enough for the restore... You can try again and wait ? I did not see failed message on the log, so it wasn't finish ? Or...

> On webadmin, update says this : But nextcloud is actually 30.0.13. I think we should wait the maj upgrade to 31.* to avoid this mistake and just be aware...

Thanks to keep for now this branch since the bugs found in v28 are not really resolved...

Strange, an error with the regex of the sources ? ` in key resources > sources '23', '24', '25', '26' do not match any of the regexes: '^[a-z][a-z0-9_-]*$'` ?? Then...

!testme

Or just create a PR like this one `Oldstable | 28.0.x` and a branch `oldstable-28` ?? for now on the last commit for 28.0.6 `e9f82ab78eae3ae20d969151ab4f8b95bfe6942c`