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

Repo shows up as bare after migrating from svn #2276

New Issue
Closed
opened 2025-11-02 04:30:44 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2025-11-02 04:30:44 -06:00
Owner
Copy Link

Originally created by @kolaente on GitHub (Aug 31, 2018).

  • Gitea version (or commit ref): b9ae16d
  • Git version: 2.1.4
  • Operating system: Debian 8
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

After migrating an old svn repo following the guide here, the repo still shows up as bare in the ui, meaning it only shows instructions on how to initialize it instead of showing the code. The code is in the repo, when I clone the repo manually I get all the code.
When I commit & push a test file manually after this, the UI acts normal.

Originally created by @kolaente on GitHub (Aug 31, 2018). - Gitea version (or commit ref): b9ae16d - Git version: 2.1.4 - Operating system: Debian 8 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant ## Description After migrating an old svn repo following the guide [here](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git), the repo still shows up as bare in the ui, meaning it only shows instructions on how to initialize it instead of showing the code. The code is in the repo, when I clone the repo manually I get all the code. When I commit & push a test file manually after this, the UI acts normal.
GiteaMirror added the issue/stale label 2025-11-02 04:30:44 -06:00
GiteaMirror commented 2025-11-02 04:30:45 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 12, 2018):

Did you see any errors in gitea.log?

@lafriks commented on GitHub (Sep 12, 2018): Did you see any errors in gitea.log?
GiteaMirror commented 2025-11-02 04:30:46 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 10, 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 10, 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.
GiteaMirror commented 2025-11-02 04:30:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 11, 2019):

I think this maybe unrelated with gitea if svn to git is not right. @kolaente

@lunny commented on GitHub (Jan 11, 2019): I think this maybe unrelated with gitea if svn to git is not right. @kolaente
GiteaMirror commented 2025-11-02 04:30:47 -06:00
Author
Owner
Copy Link

@rkCSD commented on GitHub (Jan 16, 2019):

@lafriks @kolaente
Here are some errors which may be related to the issue:

http.log

2018/08/31 21:41:33 [...routers/repo/http.go:391 serviceRPC()] [E] fail to serve RPC(upload-pack): exit status 141 - {[101 114 114 111 114 58 32 103 105 116 45 117 112 108 111 97 100 45 112 97 99 107 32

serv.log

2018/08/31 10:04:41 [...io/gitea/cmd/serv.go:181 runServ()] [F] Repository does not exist: rkcsd/tex
2018/08/31 10:04:42 [...io/gitea/cmd/serv.go:181 runServ()] [F] Repository does not exist: rkcsd/tex
2018/08/31 13:18:32 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git
2018/08/31 13:18:33 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git
2018/08/31 13:18:34 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git
2018/08/31 13:18:35 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git
2018/08/31 13:18:36 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git
2018/08/31 13:18:37 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git
2018/08/31 13:18:38 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git

(@kolaente asked me to scan the log files for it, cause the instance we're talking about, here, is running on a server managed by me; @kolaente has no access to the log files)

@rkCSD commented on GitHub (Jan 16, 2019): @lafriks @kolaente Here are some errors which may be related to the issue: ### http.log `2018/08/31 21:41:33 [...routers/repo/http.go:391 serviceRPC()] [E] fail to serve RPC(upload-pack): exit status 141 - {[101 114 114 111 114 58 32 103 105 116 45 117 112 108 111 97 100 45 112 97 99 107 32 ` ### serv.log ``` 2018/08/31 10:04:41 [...io/gitea/cmd/serv.go:181 runServ()] [F] Repository does not exist: rkcsd/tex 2018/08/31 10:04:42 [...io/gitea/cmd/serv.go:181 runServ()] [F] Repository does not exist: rkcsd/tex 2018/08/31 13:18:32 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git 2018/08/31 13:18:33 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git 2018/08/31 13:18:34 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git 2018/08/31 13:18:35 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git 2018/08/31 13:18:36 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git 2018/08/31 13:18:37 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git 2018/08/31 13:18:38 [...io/gitea/cmd/serv.go:263 runServ()] [F] User konrad does not have level write access to repository rkcsd/flyspray.git ``` (@kolaente asked me to scan the log files for it, cause the instance we're talking about, here, is running on a server managed by me; @kolaente has no access to the log files)
GiteaMirror commented 2025-11-02 04:30:47 -06:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 16, 2019):

I think it should not even show me the repo when I don't have access. But it'd be interesting to know where these Repository does not exist: rkcsd/tex errors come from.

@kolaente commented on GitHub (Jan 16, 2019): I think it should not even show me the repo when I don't have access. But it'd be interesting to know where these `Repository does not exist: rkcsd/tex` errors come from.
GiteaMirror commented 2025-11-02 04:30:47 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 17, 2019):

Have I missed something? It seems @rkCSD is not related?

@lunny commented on GitHub (Jan 17, 2019): Have I missed something? It seems @rkCSD is not related?
GiteaMirror commented 2025-11-02 04:30:48 -06:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 17, 2019):

@lunny He is the admin of the instance where the issue occurred, which is why he has access to the logs and I don't.

@kolaente commented on GitHub (Jan 17, 2019): @lunny He is the admin of the instance where the issue occurred, which is why he has access to the logs and I don't.
GiteaMirror commented 2025-11-02 04:30:48 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 25, 2019):

Maybe it's your username is rkCSD on gitea but you clone via rkcsd?

@lunny commented on GitHub (Jan 25, 2019): Maybe it's your username is `rkCSD` on gitea but you clone via `rkcsd`?
GiteaMirror commented 2025-11-02 04:30:48 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 26, 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 (Mar 26, 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.
GiteaMirror commented 2025-11-02 04:30:49 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Apr 9, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Apr 9, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
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
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#2276
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?