-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wallabag removed while upgrading to 2.5.1~ynh2 #153
Comments
I think I had this issue too, backup is not automatically restored, doing it afterwards works.
You do :) I think the best way to fix this is to execute these commands : wallabag/wallabag#5233 (comment) I can provide assistance about how to do it (in summary : connect to your Wallabag MySQL database (password found in yunohost app settings), execute the command, run the upgrade). |
I was afraid that other people migrating to bulleyes might get stuck with this but I was running the beta so I don't know... Time will tell with the release of YunoHost 11 :)
Well, I went the "lazy way" by using #133 as an intermediate step to fix the DB. It went smoothly 2.3.8~ynh4 (old)=> 2.4.3~ynh1 (fix db) => 2.5.1~ynh2 (current) Thanks for all the people working of the package! @lapineige , you can close this issue if you want, it was a false alert. If someone has to do the same steps:
|
Then we should know pretty soon as it was done :D If it restores well afterwards, that's not a so big deal.
Great, thank you for the feedback, this means it's working ! 🎉
It was not, this is important to document too 😉 |
Describe the bug
2.3.8~ynh4
=>2.5.1~ynh2
)wallabag2-pre-upgrade1.tar
after the failed upgradeContext
Steps to reproduce
Expected behavior
Logs
https://paste.yunohost.org/edoqiliwew.bash
from the log file, it seems that I am affected by #129 and needs to use the #133 to fix the database. Am I correct?
The text was updated successfully, but these errors were encountered: