github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

git clone/pull stuck after enabling lfs support #826

New Issue
Closed
opened 2025-11-02 03:37:57 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 03:37:57 -06:00
Owner
Copy Link

Originally created by @ufosaga on GitHub (Jun 20, 2017).

  • Gitea version (or commit ref):
    1.1.2
  • Git version:
    1.9.1
  • Operating system:
Linux LC-SVR-dev 3.13.0-119-generic #166-Ubuntu SMP Wed May 3 12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty

  • Database (use [x]):

    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite

  • Can you reproduce the bug at https://try.gitea.io:

  • Log gist:
    Nothing unusual

Description

The repo and config are migrated from gogs v0.11.rc.

  1. Enable lfs support in app.ini:
    LFS_START_SERVER = true
    LFS_CONTENT_PATH = /home/git/data/lfs-data
    LFS_JWT_SECRET = LqI8JDMWKGseM1WvKyg7FoOlj8Q7RGVYO9g963so0Lw

  2. restart gitea:
    sudo service gitea restart

  3. Then git clone/pull will stuck:
    $ git clone git@mydomain.tech:thomas/lfs-test.git
    Cloning into 'lfs-test'...
    ^C
    $ git pull
    ^C

...

Originally created by @ufosaga on GitHub (Jun 20, 2017). - Gitea version (or commit ref): 1.1.2 - Git version: 1.9.1 - Operating system: ``` Linux LC-SVR-dev 3.13.0-119-generic #166-Ubuntu SMP Wed May 3 12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty ``` - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No, https://try.gitea.io does not enable lfs support - [ ] Not relevant - Log gist: Nothing unusual ## Description The repo and config are migrated from gogs v0.11.rc. 1. Enable lfs support in app.ini: LFS_START_SERVER = true LFS_CONTENT_PATH = /home/git/data/lfs-data LFS_JWT_SECRET = LqI8JDMWKGseM1WvKyg7FoOlj8Q7RGVYO9g963so0Lw 2. restart gitea: sudo service gitea restart 3. Then git clone/pull will stuck: $ git clone git@mydomain.tech:thomas/lfs-test.git Cloning into 'lfs-test'... ^C $ git pull ^C ...
GiteaMirror added the issue/staletype/bug labels 2025-11-02 03:37:57 -06:00
GiteaMirror commented 2025-11-02 03:37:58 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Jul 2, 2017):

Were the hooks updated after the migration (and turning on LFS)?

@bkcsoft commented on GitHub (Jul 2, 2017): Were the hooks updated after the migration (and turning on LFS)?
GiteaMirror commented 2025-11-02 03:37:59 -06:00
Author
Owner
Copy Link

@ufosaga commented on GitHub (Jul 10, 2017):

Yes, I did Resync pre-receive, update and post-receive hooks of all repositories. in the admin panel after enabled the LFS and restarted server.

@ufosaga commented on GitHub (Jul 10, 2017): Yes, I did `Resync pre-receive, update and post-receive hooks of all repositories.` in the admin panel after enabled the LFS and restarted server.
GiteaMirror commented 2025-11-02 03:37:59 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 4, 2018):

Same problem for me but gitea 1.4.0
Linux sxyz 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
CentOS Linux release 7.4.1708 (Core)

Edit : Resolved using https://packages.endpoint.com/ to obtain a more recent git : 2.8.4

@ghost commented on GitHub (Apr 4, 2018): Same problem for me but **gitea 1.4.0** Linux sxyz 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.4.1708 (Core) **Edit : Resolved using https://packages.endpoint.com/ to obtain a more recent git : 2.8.4**
GiteaMirror commented 2025-11-02 03:37:59 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Apr 28, 2018):

@colundrum Are you sure 2.8.4 fixed it? The documentation for git-lfs states 1.8.2 should be fine 🤔 https://github.com/git-lfs/git-lfs/wiki/Installation#requirements

@bkcsoft commented on GitHub (Apr 28, 2018): @colundrum Are you sure 2.8.4 fixed it? The documentation for `git-lfs` states 1.8.2 should be fine :thinking: https://github.com/git-lfs/git-lfs/wiki/Installation#requirements
GiteaMirror commented 2025-11-02 03:37:59 -06:00
Author
Owner
Copy Link

@dani commented on GitHub (Nov 26, 2018):

I have the same issue (git clone hangs if LFS is enabled on Gitea). On CentOS 7 too, but using git 2.12.2 from SCL repo. I'll try to get some more info. Gitea version is 1.6.0

@dani commented on GitHub (Nov 26, 2018): I have the same issue (git clone hangs if LFS is enabled on Gitea). On CentOS 7 too, but using git 2.12.2 from SCL repo. I'll try to get some more info. Gitea version is 1.6.0
GiteaMirror commented 2025-11-02 03:37:59 -06:00
Author
Owner
Copy Link

@dani commented on GitHub (Nov 26, 2018):

Forget about my previous comment. Gitea daemon was indeed started using the 2.12.2 GIT version, but SSH sessions were not (and so, was using the default 1.8.3 version). Just added a /etc/profile.d/ snippet enabling the SCL version by default. Working now

@dani commented on GitHub (Nov 26, 2018): Forget about my previous comment. Gitea daemon was indeed started using the 2.12.2 GIT version, but SSH sessions were not (and so, was using the default 1.8.3 version). Just added a /etc/profile.d/ snippet enabling the SCL version by default. Working now
GiteaMirror commented 2025-11-02 03:37:59 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 31, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 31, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/stale type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#826
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?