Closed axemann closed 1 year ago
I know I can bypass the backup with one of the options listed in README.md, but wouldn't the upgrade be considered 'safer' with at least a code backup prior to the upgrade run? If there's no way to separate the code backup from the data backup without significant work, feel free to close this.
What is the actual version that is installed on your server ?
And can you give me the result of this command yunohost app setting seafile final_path
.
Current version is 9.0.2-ynh1. That command result is empty, but yunohost app setting seafile finalpath
returns /opt/yunohost/seafile
.
@Josue-T, just wanted to give you an update on this issue. I was able to resolve it on my own, although I'm not sure why things were the way they were. My /etc/yunohost/apps/seafile/settings.yml had an incorrect key for the seafile data directory: 'finalpath' instead of 'final_path'. Once I changed it to the correct value, I was able to update to 9.0.2-ynh2 with no issues.
I took a quick look through the history for both the install and upgrade scripts, but didn't see anything that stuck out, so I guess I must've broken it somehow, lol. All good now, though.
Describe the bug
Hi, I attempted to upgrade Seafile to the latest version from both the Yunohost CLI and webUI and received the error in the title.
Context
Steps to reproduce
Expected behavior
Upgrade completes without errors.
Logs
https://paste.yunohost.org/raw/tuvoqipuju