-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Migrate 1.13.7 to 1.14.1 failed, need help #15505
Comments
BTW, the diagnostic result of |
Hmm. It would be useful to know if using 1.14.0 first succeed. (This is an unusual step that I would not normally recommend.) I need to know if what you're running on: Windows, Linux or something else and if you're using gogit. There is a release which is referring to an object in your gitea-repositories that is not present - presumably because a tag has been deleted. The solution is to make this migration a bit more tolerant and I will do that but you should try to find out what has happened. |
Same issue here, also with 1.14.0. |
@yusiwen can you confirm that it is fixed by using https://dl.gitea.io/gitea/1.14/ binary? |
@raucao is it solved ☝️ ? |
I'm going to close this as fixed. Please reopen if this is still an issue. |
The error output of
gitea-1.14.1-linux-amd64 doctor --all
is shown below:The output of
gitea-1.14.1-linux-amd64 migrate
is shown below:It seems something in the database is missing, anyone can help? Thanks
The text was updated successfully, but these errors were encountered: