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

Unable to migrate from 1.7.6 to 1.8.0 and beyond #7105

Closed
2 of 7 tasks
lgrahl opened this issue Jun 2, 2019 · 3 comments
Closed
2 of 7 tasks

Unable to migrate from 1.7.6 to 1.8.0 and beyond #7105

lgrahl opened this issue Jun 2, 2019 · 3 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@lgrahl
Copy link

lgrahl commented Jun 2, 2019

Description

First of all, many thanks for maintaining this awesome project! 👍

I'm trying to migrate from a 1.4.x database version to 1.8.0. I've been able to slowly migrate my database from 1.4.x to 1.7.6 but as soon as I try 1.8.0, I always run into an error for the following migration routine: Migration[82]: hot fix for wrong release sha1 on release table. This eventually fails with the cryptic error ORM engine initialization failed: migrate: do migrate: no such file or directory. I tried running the latest Docker tag to see if #6387 fixes it but that fails with the same error.

See the Gist linked above for a full log.

@lafriks
Copy link
Member

lafriks commented Jun 2, 2019

Have you tried upgrading directly to 1.8.2?

@lafriks lafriks added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Jun 2, 2019
@lgrahl
Copy link
Author

lgrahl commented Jun 2, 2019

Initially, yes. But I had a backup of the database and then tried incrementally upgrading to 1.7.6. The result was the same.

@lgrahl
Copy link
Author

lgrahl commented Jun 2, 2019

I've solved the mystery. My repository path changed and I misinterpreted the above error. Works fine for me now. 👍

@lgrahl lgrahl closed this as completed Jun 2, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

2 participants