Skip to content
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

Failed Migration from Gogs 0.9.97.0901 to Gitea master #871

Closed
2 of 6 tasks
fettlaus opened this issue Feb 8, 2017 · 3 comments · Fixed by #929
Closed
2 of 6 tasks

Failed Migration from Gogs 0.9.97.0901 to Gitea master #871

fettlaus opened this issue Feb 8, 2017 · 3 comments · Fixed by #929
Labels
Milestone

Comments

@fettlaus
Copy link

fettlaus commented Feb 8, 2017

Description

When doing a direct upgrade from Gogs 0.9.97.0901 to Gitea master, the migration failed with the attached errorlog. This doesn't happen when migrating from Gogs to Gitea 1.0.1 and then upgrading to Gitea master.

@lunny lunny added this to the 1.1.0 milestone Feb 8, 2017
@lunny lunny added the type/bug label Feb 8, 2017
@lunny
Copy link
Member

lunny commented Feb 8, 2017

That maybe a migration method bug, both Gitea and Gogs. But I think you can upgrade v1.0.1 and then to master, It will smooth.

Because when you migrate from v7 to v12, but on v9 column external_tracker_url should be created by x.Sync2(), but that not in migrations list.

So I think we have to ask all database schemas changes should add a migration even if x.Sync2 could do that.

@lunny
Copy link
Member

lunny commented Feb 14, 2017

@fettlaus please confirm #929 fix this.

@fettlaus
Copy link
Author

Sorry, I am unable to confirm this. I don't have the gogs backup anymore and thus can't revert to the old installation.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants