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 repo from GitLab fails if Wiki is checked #19545

Closed
fnetX opened this issue Apr 28, 2022 · 4 comments · Fixed by #19563
Closed

Migrating repo from GitLab fails if Wiki is checked #19545

fnetX opened this issue Apr 28, 2022 · 4 comments · Fixed by #19563
Assignees
Labels

Comments

@fnetX
Copy link
Contributor

fnetX commented Apr 28, 2022

Description

Migrating repos from GitLab fails if the user ticks the "wiki" option in Gitea, tested from https://gitlab.com/interpeer/caprock which was reported on https://Codeberg.org

It works fine if the "wiki" checkbox is left unticked. Probably a check is missing that the wiki exists // what is the branch.

log excerpt (seems relevant):

2022/04/28 22:06:21 ...s/repository/repo.go:102:MigrateRepositoryGitData() [W] Clone wiki: exit status 128 - fatal: Remote branch master not found in upstream origin
	
2022/04/28 22:06:23 ...ervices/task/task.go:56:handle() [E] Run task failed: unable to write commit-graph for '/data/git/gitea-repositories/interpeer/liberate.wiki.git' : chdir /data/git/gitea-repositories/interpeer/liberate.wiki.git: no such file or directory

Gitea Version

1.17.0+dev-491-g8eb1cd926

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Codeberg deployment + try.gitea.io

Database

No response

@fnetX fnetX added the type/bug label Apr 28, 2022
@6543 6543 self-assigned this Apr 29, 2022
@6543
Copy link
Member

6543 commented Apr 30, 2022

Migrate repository from https://gitlab.com/interpeer/caprock failed: unable to write commit-graph for '/data/git/gitea-repositories/6543/caprock2.wiki.git' : chdir /data/git/gitea-repositories/6543/caprock2.wiki.git: no such file or directory

-> this is is happening because the "wiki" is activated in gitlab but it's an empty git issue if you like to clone it

6543 added a commit to 6543-forks/gitea that referenced this issue Apr 30, 2022
@fnetX
Copy link
Contributor Author

fnetX commented Apr 30, 2022

https://gitlab.com/interpeer/caprock/-/wikis/home it still looks empty, so probably can be checked via API? I'm just wondering if another error could occur on cloning an existing wiki and would not be detected with your change.

@6543
Copy link
Member

6543 commented Apr 30, 2022

@fnetX blame gitlab, yes you can check via API - but it wont tell you anything about the state (if initialized or empty)

@6543
Copy link
Member

6543 commented Apr 30, 2022

my pull #19563 does fix by the way ...

lunny pushed a commit that referenced this issue Apr 30, 2022
6543 added a commit to 6543-forks/gitea that referenced this issue Apr 30, 2022
Gusted pushed a commit to Gusted/gitea that referenced this issue Apr 30, 2022
zjjhot added a commit to zjjhot/gitea that referenced this issue May 1, 2022
* giteaofficial/main:
  Avoid MoreThanOne Error (go-gitea#19557)
  [skip ci] Updated licenses and gitignores
  Simplify loops to copy (go-gitea#19569)
  Use middleware to open gitRepo (go-gitea#19559)
  Added X-Mailer header to outgoing emails (go-gitea#19562)
  fix go-gitea#19545 (go-gitea#19563)
  [skip ci] Updated translations via Crowdin
  Respect DefaultUserIsRestricted system default when creating new user (go-gitea#19310)
  Mute link in diff header (go-gitea#19556)
  Add API to query collaborators permission for a repository (go-gitea#18761)
  Permalink files In PR diff (go-gitea#19534)
  Fix Pull Request comment filename word breaks (go-gitea#19535)
  Don't error when branch's commit doesn't exist (go-gitea#19547)
AbdulrhmnGhanem pushed a commit to kitspace/gitea that referenced this issue Aug 24, 2022
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants