All releases lost upon upgrading from Gogs to Gitea-1.3.2

[strk]

• Gitea version (or commit ref):1.3.2
• Git version: 1.7.10
• Operating system: GNU/Linux
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant (cannot test an upgrade there)

Description

Gogs used to show every tag in the Releases page, upon upgrade all those entries in Releases are gone. I've tried that removing all remote tags and re-pushing them is effective as a work-around, but it is crazy to do this for each and every repository we host.

@lafriks mentioned this synchronization should have happened at migration time but evidently it did not. How to fix now ? I think there should be an admin task to resynchronize those releases or we're stuck forever with this problem.

The problem may or may not be related to git version being < 1.8 - see #1133 (from #1133 (comment))

[lafriks]

API method could be added as I don't see where could it be added in admin interface

[strk]

I'm doing an ./gitea admin repo-sync-releases-with-tags command. Want to help with that ? I dont' see how am I supposed to get the engine from model, although admin calls models.SetEngine() I don't see any models.GetEngine() function..

[lunny]

That command should be help and seems it's easy to implementation.

[lunny]

@strk which version was your Gogs? Maybe you lost some migrations?

[lafriks]

You need to call models function that does not require engine or create one

[strk]

Gogs-0.9.99.0903, with database at version 14. The "release" table, present, was empty. Model functions are not what the migration (v39.go) calls. The migration does make use of `x` (the engine) to get the list of repositories to scan/sync.

[strk]

Actually, I went looking logs and found the probable cause of loosing all those releases:

2017/10/18 13:27:11 [I] Migration: add tags to releases and sync existing repositories 2017/10/18 13:27:12 [W] SyncReleasesWithTags: GetTags: exit status 128 - fatal: Not a git repository (or any of the parent directories): .git ... 2017/10/18 13:27:12 [W] SyncReleasesWithTags: GetTags: exit status 128 - fatal: Not a git repository (or any of the parent directories): .git 2017/10/18 13:27:12 [I] Migration: remove duplicate unit types

There seem to be some problem with the repository paths.

[strk]

Working more on the PR adding an admin command to re-sync I found more problems: the function used by the migration supposed to synchronize repo tags with releases does not really work. Do you remember who changed the way releases were handled ?

[ethantkoenig]

@strk I believe it was @lafriks: #2459