[W] SyncReleasesWithTags: GetTags: exit status 128 - fatal: Not a git repository (or any of the parent directories): .git #1374

New Issue

GiteaMirror · 2025-11-02T03:58:19-06:00

GiteaMirror commented

2025-11-02 03:58:19 -06:00

Originally created by @strk on GitHub (Dec 17, 2017).

Upon upgrading from Gogs-0.9-something to Gitea-1.3.2-dev I found a few of these messages in the logs:

2017/12/17 03:24:04 [W] SyncReleasesWithTags: GetTags: exit status 128 - fatal: Not a git repository (or any of the parent directories): .git

This ticket is to request to make the message more interesting by adding the repository name.
Would also be nice to know how to fix the problem, if problem needs be fixed...

Originally created by @strk on GitHub (Dec 17, 2017). Upon upgrading from Gogs-0.9-something to Gitea-1.3.2-dev I found a few of these messages in the logs: > 2017/12/17 03:24:04 [W] SyncReleasesWithTags: GetTags: exit status 128 - fatal: Not a git repository (or any of the parent directories): .git This ticket is to request to make the message more interesting by adding the repository name. Would also be nice to know how to fix the problem, if problem needs be fixed...

GiteaMirror added the issue/stale type/bug labels 2025-11-02 03:58:19 -06:00

GiteaMirror closed this issue

2025-11-02 03:58:19 -06:00

GiteaMirror commented

2025-11-02 03:58:20 -06:00

@amit-handa commented on GitHub (Aug 22, 2018):

@strk
I am facing the same problem while migrating from gogs (0.11.34) to gitea (1.5.0 ). were you able to resolve the issue ? Thanks.

@amit-handa commented on GitHub (Aug 22, 2018): @strk I am facing the same problem while migrating from gogs (0.11.34) to gitea (1.5.0 ). were you able to resolve the issue ? Thanks.

GiteaMirror commented

2025-11-02 03:58:20 -06:00

@lafriks commented on GitHub (Aug 23, 2018):

Check that your repositories directory is specified correctly in app.ini

@lafriks commented on GitHub (Aug 23, 2018): Check that your repositories directory is specified correctly in app.ini

GiteaMirror commented

2025-11-02 03:58:20 -06:00

@amit-handa commented on GitHub (Aug 23, 2018):

yes, thanks @lafriks . I was running in docker on k8s. for some reason, even though file ownerships and docker process uids matched, it still had an issue reading the bare repos.
I somehow solved it via hit and trial.

@amit-handa commented on GitHub (Aug 23, 2018): yes, thanks @lafriks . I was running in docker on k8s. for some reason, even though file ownerships and docker process uids matched, it still had an issue reading the bare repos. I somehow solved it via hit and trial.

GiteaMirror commented

2025-11-02 03:58:20 -06:00

@stale[bot] commented on GitHub (Jan 12, 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 12, 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 03:58:20 -06:00

@stale[bot] commented on GitHub (Feb 20, 2019):

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

@stale[bot] commented on GitHub (Feb 20, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#1374