unable to push repo after migrate from gogs #4144

Closed
opened 2025-11-02 05:40:14 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @fangd123 on GitHub (Oct 18, 2019).

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I upgraded from Gogs 0.11.91, after following the document instruction, I can not push or clone my repo with Gitea, and it says:
2019/10/18 17:22:29 [...io/gitea/cmd/serv.go:171 runServ()] [F] Failed to get repository: pq: column "is_bare" does not exist
...

Screenshots

Originally created by @fangd123 on GitHub (Oct 18, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: - Operating system: - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description I upgraded from Gogs 0.11.91, after following the document instruction, I can not push or clone my repo with Gitea, and it says: `2019/10/18 17:22:29 [...io/gitea/cmd/serv.go:171 runServ()] [F] Failed to get repository: pq: column "is_bare" does not exist` ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
Author
Owner

@fangd123 commented on GitHub (Oct 18, 2019):

I have done the migrate command and get nothing wrong, but the problem is still there

@fangd123 commented on GitHub (Oct 18, 2019): I have done the migrate command and get nothing wrong, but the problem is still there
Author
Owner

@lunny commented on GitHub (Oct 18, 2019):

You can try to add a column named is_bare on table repository type is bool.

@lunny commented on GitHub (Oct 18, 2019): You can try to add a column named `is_bare` on table `repository` type is `bool`.
Author
Owner

@fangd123 commented on GitHub (Oct 21, 2019):

You can try to add a column named is_bare on table repository type is bool.

Thanks, the problem is solved. But there is a new problem which says:

routers/repo/http.go:97:HTTP() [E] GetUserByName: user does not exist [uid: 0, name: api, keyid: 0]

@fangd123 commented on GitHub (Oct 21, 2019): > You can try to add a column named `is_bare` on table `repository` type is `bool`. Thanks, the problem is solved. But there is a new problem which says: `routers/repo/http.go:97:HTTP() [E] GetUserByName: user does not exist [uid: 0, name: api, keyid: 0]`
Author
Owner

@jolheiser commented on GitHub (Oct 21, 2019):

That could be a config issue.
Gitea is trying to go to a namespace called api, seemingly instead of calling the actual API.

Can you post more of the log, and perhaps a scrubbed config?

@jolheiser commented on GitHub (Oct 21, 2019): That could be a config issue. Gitea is trying to go to a namespace called api, seemingly instead of calling the actual API. Can you post more of the log, and perhaps a scrubbed config?
Author
Owner

@fangd123 commented on GitHub (Oct 21, 2019):

That could be a config issue.
Gitea is trying to go to a namespace called api, seemingly instead of calling the actual API.

Can you post more of the log, and perhaps a scrubbed config?

Yes, it is a config issue.
After I reset the hooks in the dashboard, it got normal.
Thank you.

@fangd123 commented on GitHub (Oct 21, 2019): > That could be a config issue. > Gitea is trying to go to a namespace called api, seemingly instead of calling the actual API. > > Can you post more of the log, and perhaps a scrubbed config? Yes, it is a config issue. After I reset the hooks in the dashboard, it got normal. Thank you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4144