github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-06 19:09:28 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

LFS files not deleted with repository #4078

New Issue
Closed
opened 2025-11-02 05:36:51 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 05:36:51 -06:00
Owner
Copy Link

Originally created by @8ctopus on GitHub (Oct 8, 2019).

  • Gitea version (or commit ref): 1.9.3
  • Git version: 2.17.1
  • Operating system: Ubuntu 18.04.3 LTS
  • Database (use [x]):
    • MySQL
  • Can you reproduce the bug at https://try.gitea.io:
    • Not relevant
  • Log gist:

How to reproduce:

  1. Clean installation of gitea 1.9.3 on Ubuntu with git LFS enabled and path set
ROOT = /home/gitea/gitea-repositories
LFS_START_SERVER = true
LFS_CONTENT_PATH = /home/gitea/data/lfs
  1. Create a new repository "repo" in gitea
  2. Clone the repository
git clone https://mydomain/gitea/company/repo.git
  1. Add LFS tracking and add a file to LFS
cd repo
git lfs track "*.zip"
cp ../file.zip .
git add .gitattributes file.zip
git commit -m "added: zip file LFS tracked"
git push origin master
  1. In gitea, delete the repository.
  2. On the server filesystem, the /home/gitea/data/lfs directory is not empty and still contains the zip file.
/home/gitea/data/lfs # ls -alRh
.:
total 12K
drwxr-xr-x 3 gitea gitea 4.0K Oct  8 07:20 .
drwxr-xr-x 3 gitea gitea 4.0K Oct  3 11:30 ..
drwxr-x--- 3 gitea gitea 4.0K Oct  8 07:20 31

./31:
total 12K
drwxr-x--- 3 gitea gitea 4.0K Oct  8 07:20 .
drwxr-xr-x 3 gitea gitea 4.0K Oct  8 07:20 ..
drwxr-x--- 2 gitea gitea 4.0K Oct  8 07:22 7e

./31/7e:
total 7.5M
drwxr-x--- 2 gitea gitea 4.0K Oct  8 07:22 .
drwxr-x--- 3 gitea gitea 4.0K Oct  8 07:20 ..
-rw-r----- 1 gitea gitea 7.5M Oct  8 07:21 ff4325718b51c0fabcd514539af2d1d6db8b8d458a2cc8a724d57d615bd8
Originally created by @8ctopus on GitHub (Oct 8, 2019). - Gitea version (or commit ref): 1.9.3 - Git version: 2.17.1 - Operating system: Ubuntu 18.04.3 LTS - Database (use `[x]`): - [x] MySQL - Can you reproduce the bug at https://try.gitea.io: - [x] Not relevant - Log gist: How to reproduce: 1. Clean installation of gitea 1.9.3 on Ubuntu with git LFS enabled and path set ``` ROOT = /home/gitea/gitea-repositories LFS_START_SERVER = true LFS_CONTENT_PATH = /home/gitea/data/lfs ``` 2. Create a new repository "repo" in gitea 3. Clone the repository ``` git clone https://mydomain/gitea/company/repo.git ``` 4. Add LFS tracking and add a file to LFS ``` cd repo git lfs track "*.zip" cp ../file.zip . git add .gitattributes file.zip git commit -m "added: zip file LFS tracked" git push origin master ``` 5. In gitea, delete the repository. 6. On the server filesystem, the /home/gitea/data/lfs directory is not empty and still contains the zip file. ``` /home/gitea/data/lfs # ls -alRh .: total 12K drwxr-xr-x 3 gitea gitea 4.0K Oct 8 07:20 . drwxr-xr-x 3 gitea gitea 4.0K Oct 3 11:30 .. drwxr-x--- 3 gitea gitea 4.0K Oct 8 07:20 31 ./31: total 12K drwxr-x--- 3 gitea gitea 4.0K Oct 8 07:20 . drwxr-xr-x 3 gitea gitea 4.0K Oct 8 07:20 .. drwxr-x--- 2 gitea gitea 4.0K Oct 8 07:22 7e ./31/7e: total 7.5M drwxr-x--- 2 gitea gitea 4.0K Oct 8 07:22 . drwxr-x--- 3 gitea gitea 4.0K Oct 8 07:20 .. -rw-r----- 1 gitea gitea 7.5M Oct 8 07:21 ff4325718b51c0fabcd514539af2d1d6db8b8d458a2cc8a724d57d615bd8 ```
GiteaMirror added the issue/regression label 2025-11-02 05:36:51 -06:00
GiteaMirror commented 2025-11-02 05:36:52 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 10, 2019):

Hmm this was previously fixed ... This must be a regression.

Is there an error in the logs on repository deletion?

@zeripath commented on GitHub (Oct 10, 2019): Hmm this was previously fixed ... This must be a regression. Is there an error in the logs on repository deletion?
GiteaMirror commented 2025-11-02 05:36:52 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 10, 2019):

Damn I think this is my fault. LFS files need to be deleted relative to the root of the content path.

#8455 should fix this.

@zeripath commented on GitHub (Oct 10, 2019): Damn I think this is my fault. LFS files need to be deleted relative to the root of the content path. #8455 should fix this.
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/regression
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#4078
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?