Nextcloud upgrade from 32.0.6~ynh1 to 33.0.2~ynh1 fails

[BluishHumility]

I did read that issue, but I am not sure how to benefit from the script they referenced.

@dazu

So, a closer look into the upgrade script revealed, that my situation (having ldap config without prefix used to be normal) had already been contemplated by alexAubin, thus modifying the setting ldap_config_prefix from ldap_config_prefix: s02 to ldap_config_prefix: '' was sufficient to take advantage of the upgrade logic and smoothly transition to 32.0.6!

# Before NCv32, Yunohost was not using any prefix for the LDAP config.
# This is now mandatory so we need to create a new config with a prefix.
if [ "$ldap_config_prefix" = "" ]
then
    ldap_config_prefix=$(exec_occ ldap:create-empty-config --only-print-prefix)
    ynh_app_setting_set --key=ldap_config_prefix --value="$ldap_config_prefix"
fi

That appears to be a change that was merged back in December: fix(ldap): Explicitly test created config by artonge · Pull Request #837 · YunoHost-Apps/nextcloud_ynh · GitHub

I guess I would think if that was the fix, I would already have it.

Edit

I didn’t see the edit to your post, hang on one sec while I try that.

Edit 2

@rodinux

try a shell in nextcloud

yunohost app shell nextcloud

and then then copy-paste this bloc

if [ "$ldap_config_prefix" = "" ]
then
    ldap_config_prefix=$(exec_occ ldap:create-empty-config --only-print-prefix)
    ynh_app_setting_set --k

There is no output when I run this, but unfortunately the update still fails afterward. https://paste.yunohost.org/raw/jilogenuxu