-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Closed
Labels
type/questionIssue needs no code to be fixed, only a description on how to fix it yourself.Issue needs no code to be fixed, only a description on how to fix it yourself.
Description
- Gitea version (or commit ref): v1.9.0+dev-314-g8eba27c79 (Docker)
- Git version: 2.20.1
- Operating system: Linux
- Database (use
[x]
):- PostgreSQLMySQLMSSQLSQLiteTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)NoNot relevantTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
- Log gist: https://gist.github.com/lgrahl/3e9992345ad6b83650492af4b2bbba61
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.
Metadata
Metadata
Assignees
Labels
type/questionIssue needs no code to be fixed, only a description on how to fix it yourself.Issue needs no code to be fixed, only a description on how to fix it yourself.
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
lafriks commentedon Jun 2, 2019
Have you tried upgrading directly to 1.8.2?
lgrahl commentedon 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 commentedon Jun 2, 2019
I've solved the mystery. My repository path changed and I misinterpreted the above error. Works fine for me now. 👍