When I upgrade my Debian 10 to 11, the SeaHub service does not start anymore. Has anyone encountered the same problem or is there a known solution here? Unfortunately, I cannot find any clues in the log files.
Thanks,
Stev
try to enable “DEBUG = True” in seahub_settings.py
It was not a seafile problem.
5.1.6. MariaDB package names no longer include version numbers Unlike bullseye that had the MariaDB version in package names (e.g. mariadb-server-10.5 and mariadb-client-10.5), in bookworm the equivalent MariaDB 10.11 package names are fully versionless (e.g. mariadb-server or mariadb-client). The MariaDB version is still visible in the package version metadata. There is at least one known upgrade scenario (Bug #1035949) where the transition to versionless package names fails: running apt-get install default-mysql-server may fail when mariadb-client-10.5 and the file /usr/bin/mariadb-admin in it is removed before the MariaDB server SysV init service has issued a shutdown, which uses mariadb-admin. The workaround is to run apt upgrade before running apt full-upgrade
I had to reinstall the dependencies after the “apt full-upgrade”
sudo apt-get update sudo apt-get install -y python3 python3-setuptools python3-pip libmysqlclient-dev sudo apt-get install -y memcached libmemcached-dev # replace for libmysqlclient-dev sudo apt-get install -y libmariadb-dev sudo pip3 install --timeout=3600 django==3.2.* future==0.18.* mysqlclient==2.1.* \ pymysql pillow==9.3.* pylibmc captcha==0.4 markupsafe==2.0.1 jinja2 sqlalchemy==1.4.3 \ psd-tools django-pylibmc django_simple_captcha==0.5.* djangosaml2==1.5.* pysaml2==7.2.* pycryptodome==3.16.* cffi==1.15.1 lxml