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

Migrating from 1.14 to 1.15.6 #17708

Closed
ndelpuppo opened this issue Nov 18, 2021 · 3 comments
Closed

Migrating from 1.14 to 1.15.6 #17708

ndelpuppo opened this issue Nov 18, 2021 · 3 comments

Comments

@ndelpuppo
Copy link

Gitea Version

gitea-1.15.6

Git Version

git-2.29.3

Operating System

centos7

How are you running Gitea?

I am using the binary release downloaded from https://dl.gitea.io/gitea

Database

PostgreSQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

Hi All,
I am facing issues while trying to upgrade Gitea from release 1.14 to 1.15.6.
Looking at the logs, it seems a db migration-related problem:

ORM engine initialization attempt #5/10 failed. Error: migrate: do migrate: pq: column "message" of relation "task" already exists

I would like to avoid wiping the database, is there anything I could do to fix this issue?

PLease see attached the log file.
giteamigration.txt

Screenshots

No response

@wxiaoguang
Copy link
Contributor

Please do not re-install on an installed database.

You should use your old app.ini.

To bypass this error, you may either:

  1. Use your 1.14 backup database and use your old app.ini to do the upgrade again.
  2. Drop the duplicated column and use the old app.ini to continue to migrate.

The old app.ini is a must.

@wxiaoguang
Copy link
Contributor

Duplicate of #17328

@wxiaoguang wxiaoguang marked this as a duplicate of #17328 Nov 18, 2021
@ndelpuppo
Copy link
Author

Please do not re-install on an installed database.

You should use your old app.ini.

To bypass this error, you may either:

  1. Use your 1.14 backup database and use your old app.ini to do the upgrade again.
  2. Drop the duplicated column and use the old app.ini to continue to migrate.

The old app.ini is a must.

Thank you very much for your quick answer, I went for solution (2) and it worked!
Just for information, I was already using the original app.ini file, I simply replaced the gitea executable with the new one.

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

No branches or pull requests

2 participants