gitea: checking out repo with LFS fails - keeps on trying to use http authentication

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

I was able to clone non-LFS repo, push some files, even with GIT-LFS and then cloning it fails.

$ git clone ssh://git@git.domain:2222/avd/test.git test1 Cloning into ‘test1’… The authenticity of host ‘[git.domain]:2222 ([10.61.2.112]:2222)’ can’t be established. RSA key fingerprint is SHA256:8x9uZXuGSs4cATzr21c/iU2lhHliale/E94rqCNzsXk. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added ‘[git.domain]:2222,[10.61.2.112]:2222’ (RSA) to the list of known hosts. remote: Counting objects: 4, done. remote: Compressing objects: 100% (3/3), done. remote: Total 4 (delta 0), reused 0 (delta 0) Receiving objects: 100% (4/4), done. Checking connectivity… done. Downloading a.bin (4 B) Username for ‘http://git.domain’: Password for ‘http://git.domain’: Username for ‘http://git.domain’: Password for ‘http://git.domain’: warning: Clone succeeded, but checkout failed. You can inspect what was checked out with ‘git status’ and retry the checkout with ‘git checkout -f HEAD’

$ git lfs env git-lfs/2.0.1 (GitHub; linux amd64; go 1.8; git 678cdbd4) git version 2.7.4 Endpoint=https://git.domain/avd/test.git/info/lfs (auth=basic) SSH=git@git.domain:avd/test.git LocalWorkingDir=/home/nfs/avd/kuba/test1 LocalGitDir=/home/nfs/avd/kuba/test1/.git

Thanks

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 21 (21 by maintainers)

Most upvoted comments

how are you planning on keeping track of all the repositories that have given file and ensure that it stays there until the last repository deletes it?

The data structure is already there since each object is saved together with its repository id. It already works with forks and deletions of repositories.

looking at the xorm spec it’s not clear to me that the index (and therefore uniqueness) is composite.

Have a look at the column definiton manual