Skip to content

Problema migrating from gogs to gitea #4457

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

Closed
5 tasks
kleper opened this issue Jul 17, 2018 · 1 comment
Closed
5 tasks

Problema migrating from gogs to gitea #4457

kleper opened this issue Jul 17, 2018 · 1 comment
Labels
issue/duplicate The issue has already been reported.

Comments

@kleper
Copy link

kleper commented Jul 17, 2018

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

Description

I recently decided to migrate from GOGS to GITEA. Following the documentation I managed to look at the gogs database to my new server with gitea using version 1 of gitea for migration. Migrate all files as specified by the configuration but I have the following problem:
In the repositories I had in GOGS I can not push, when I try the following error:
emote: *** Project description file has not been set
remote: error: hook declined to update refs / heads / master
To https://code.tupale.co/kleper/milfskleper.git
 ! [remote rejected] master -> master (hook declined)
error: fail push to some refereces to 'https: // ....

In the log I have these types of messages:
= git-upload-pack 401 Unauthorized in 1.566429ms

In the log: log / hooks / pre-receive.log, I have these messages:
GetProtectedBranchBy: http://10.10.10.3:3000/api/internal/branch/30/master

As I saw in other issues update the reference to the hooks using the web interface, also organize several configurations related to the URL and the LOCAL HOST, but I still have this problem.

If I create a new repository I do not have any problems and I can do push and everything works fine.

@lafriks lafriks added the issue/duplicate The issue has already been reported. label Jul 17, 2018
@lafriks
Copy link
Member

lafriks commented Jul 17, 2018

Duplicate of #1794

@lafriks lafriks marked this as a duplicate of #1794 Jul 17, 2018
@kleper kleper closed this as completed Jul 17, 2018
@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
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

2 participants