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

Cannot rename non-empty repositories #7598

New Issue
Closed
opened 2025-11-02 07:30:55 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 07:30:55 -06:00
Owner
Copy Link

Originally created by @arcvetkovic on GitHub (Jul 18, 2021).

  • Gitea version (or commit ref): 1.14.4
  • Git version: 2.31.1
  • Operating system: Windows Server 2019. Using an official download, installed in C:\gitea, run from command prompt (either as an admin or a regular user).
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

Description

I'm able to rename empty repositories. However, I get the following error when I try to rename repositories that contain commits:

2021/07/18 11:32:00 ...ters/repo/setting.go:102:SettingsPost() [E] ChangeRepositoryName: rename repository directory: rename D:\gitea\data\gitea-repositories\arcvetkovic\test.git D:\gitea\data\gitea-repositories\arcvetkovic\test1.git: The process cannot access the file because it is being used by another process.

What I've tried so far:

  • I wasn't able to identify any processes using the file(s) (e.g., by using Process Explorer or similar solutions).
  • After rebooting the server, the error is still there.
  • Also checked that my user has modify/write permission (I'm able to rename directories by hand).
  • Tried moving Gitea data from D: disk to C: as well.
  • Finally, did a clean install, not only on the server but on a laptop with Windows 10 -- getting the same behavior.

Screenshots

Originally created by @arcvetkovic on GitHub (Jul 18, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.14.4 - Git version: 2.31.1 - Operating system: Windows Server 2019. Using an official download, installed in `C:\gitea`, run from command prompt (either as an admin or a regular user). <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. --> I'm able to rename empty repositories. However, I get the following error when I try to rename repositories that contain commits: ``` 2021/07/18 11:32:00 ...ters/repo/setting.go:102:SettingsPost() [E] ChangeRepositoryName: rename repository directory: rename D:\gitea\data\gitea-repositories\arcvetkovic\test.git D:\gitea\data\gitea-repositories\arcvetkovic\test1.git: The process cannot access the file because it is being used by another process. ``` What I've tried so far: - I wasn't able to identify any processes using the file(s) (e.g., by using Process Explorer or similar solutions). - After rebooting the server, the error is still there. - Also checked that my user has modify/write permission (I'm able to rename directories by hand). - Tried moving Gitea data from `D:` disk to `C:` as well. - Finally, did a clean install, not only on the server but on a laptop with Windows 10 -- getting the same behavior. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/duplicate label 2025-11-02 07:30:55 -06:00
GiteaMirror commented 2025-11-02 07:30:56 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 18, 2021):

Can you compile Gitea or try the build mentioned here:

https://github.com/go-gitea/gitea/pull/16439#issuecomment-881457812

@onlygecko for the avoidance of future problems could you please test #16463?

https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16463-windows-4.0-amd64.exe is a windows build of 1.14 with #16463 compiled in. (Once it uploads to my server of course.)

https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16463-windows-4.0-amd64.exe.asc is the gpg signature signed by my key if you want to assert that this from me.

This should be fixed by https://github.com/go-gitea/gitea/pull/16463

@zeripath commented on GitHub (Jul 18, 2021): Can you compile Gitea or try the build mentioned here: https://github.com/go-gitea/gitea/pull/16439#issuecomment-881457812 > @onlygecko for the avoidance of future problems could you please test #16463? > > https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16463-windows-4.0-amd64.exe is a windows build of 1.14 with #16463 compiled in. (Once it uploads to my server of course.) > > https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16463-windows-4.0-amd64.exe.asc is the gpg signature signed by my key if you want to assert that this from me. This should be fixed by https://github.com/go-gitea/gitea/pull/16463
GiteaMirror commented 2025-11-02 07:30:56 -06:00
Author
Owner
Copy Link

@arcvetkovic commented on GitHub (Jul 18, 2021):

I tried https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16463-windows-4.0-amd64.exe, but didn't work (same error message).

@arcvetkovic commented on GitHub (Jul 18, 2021): I tried https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16463-windows-4.0-amd64.exe, but didn't work (same error message).
GiteaMirror commented 2025-11-02 07:30:57 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 18, 2021):

Please try:

https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16481-windows-4.0-amd64.zip

which contains a build of 1.14 with #16481 and it's gpg signature.

@zeripath commented on GitHub (Jul 18, 2021): Please try: https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16481-windows-4.0-amd64.zip which contains a build of 1.14 with #16481 and it's gpg signature.
GiteaMirror commented 2025-11-02 07:30:57 -06:00
Author
Owner
Copy Link

@arcvetkovic commented on GitHub (Jul 19, 2021):

Unfortunately, didn't work.

@arcvetkovic commented on GitHub (Jul 19, 2021): Unfortunately, didn't work.
GiteaMirror commented 2025-11-02 07:30:57 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 19, 2021):

OK let's try:

https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16481-attempt2-windows-4.0-amd64.zip

This just attempts to wait again.

@zeripath commented on GitHub (Jul 19, 2021): OK let's try: https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16481-attempt2-windows-4.0-amd64.zip This just attempts to wait again.
GiteaMirror commented 2025-11-02 07:30:57 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 19, 2021):

@arcvetkovic

@zeripath commented on GitHub (Jul 19, 2021): @arcvetkovic
GiteaMirror commented 2025-11-02 07:30:58 -06:00
Author
Owner
Copy Link

@arcvetkovic commented on GitHub (Jul 19, 2021):

Apologies, stuck at work.

With https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16481-attempt2-windows-4.0-amd64.zip renaming works.

@arcvetkovic commented on GitHub (Jul 19, 2021): Apologies, stuck at work. With https://www.eldritchkitty.com/~andrew/gitea-1.14.5-16481-attempt2-windows-4.0-amd64.zip renaming works.
GiteaMirror commented 2025-11-02 07:30:58 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 19, 2021):

Cool. OK I'll add the necessary bits up.

@zeripath commented on GitHub (Jul 19, 2021): Cool. OK I'll add the necessary bits up.
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/duplicate
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#7598
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?