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

[1.9.0+rc2] Migrate from Github private repo fails #7644

Closed
2 of 7 tasks
behnoodk opened this issue Jul 27, 2019 · 6 comments · Fixed by #7917
Closed
2 of 7 tasks

[1.9.0+rc2] Migrate from Github private repo fails #7644

behnoodk opened this issue Jul 27, 2019 · 6 comments · Fixed by #7917
Labels
Milestone

Comments

@behnoodk
Copy link

  • Gitea version (or commit ref): 1.9.0+rc2-14-g650fdceb5
  • Git version: 2.17.1
  • Operating system: Ubuntu 18.04
  • 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

When trying to migrate a private Github repo, migration tool fails with following error:

Authentication failed: Clone: exit status 128 - fatal: could not read Username for 'https://github.com': No such device or address

I have tried following senarios:

  1. Disable my two factor authentication and enter my username and password
  2. Enter a Personal Access Token with full access on my account

As long as my repo is private the migrate tool fails. Finally if I make my repo public, migrate tool works as it should.

P.S. Gitea is awesome! Thank you :)

@dustalov
Copy link

dustalov commented Aug 3, 2019

I have the very same issue with the version 1.10.0+dev-129-g6c0c5c531 of Gitea. As a workaround, I specified the following clone URL, and it worked like a charm: https://username:token@github.com/username/repo.git.

@lunny
Copy link
Member

lunny commented Aug 20, 2019

could you confirm that #7917 fixed this issue?

@dustalov
Copy link

Sorry, my installation is running in a container on ARM64. Currently, I cannot build and test it.

@behnoodk
Copy link
Author

I cannot upgrade my own instance right now. but if the pull request is merged and deployed on try.gitea.io which right now says 1.10.0+dev-190-g852876a98, I just created an account and tried to migrate my private repo and it failed again with the error:
Authentication failed: Clone: exit status 128 - fatal: could not read Username for 'https://github.com': No such device or address

what I did was, I created a Personal Access Token with full permissions and provided that as my password in the migrate page and selected all the migration items : Wiki, Milestones, Labels, Issues, Pull Requests, Releases.

@wsand02
Copy link

wsand02 commented Aug 29, 2019

I'm running 1.9.2 which supposedly fixed this issue, yet I still have it.

Edit: I did some research and found out it wasn't in 1.9.2

@lrecknagel
Copy link

If anyone running into this and needs a "solution" in some way:
https://gist.github.com/lrecknagel/cdb5f85f150f5f15d882651b6119157e

@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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants