Commit/push error #5655

New Issue

GiteaMirror · 2025-11-02T06:32:06-06:00

GiteaMirror commented

2025-11-02 06:32:06 -06:00

Originally created by @obi1 on GitHub (Jun 28, 2020).

Gitea version (or commit ref): 1.11.6
Git version: 2.26.2
Operating system: Gentoo Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

I haven't been using Gitea for anything but pulls since may, when I had versions <1.11.5. Everything worked fine. In this time I've updated to 1.11.5 and most recently to 1.11.6. Today I wanted to make a push to the server and I was greeted with
remote: fatal: not a git repository: '.' After that I've tried to create a new test file directly in the web interface and get the following error: Failed to update/create file 'test' with error: Clone: exit status 128 - Cloning into bare repository '/var/lib/gitea/data/tmp/local-repo/upload.git927228562'... fatal: unable to access '/var/lib/gitea/data/tmp/local-repo/upload.git927228562/config': Permission denied exit status 128 - Cloning into bare repository '/var/lib/gitea/data/tmp/local-repo/upload.git927228562'... fatal: unable to access '/var/lib/gitea/data/tmp/local-repo/upload.git927228562/config': Permission denied.
The permissions seem to be in order and even if I set them to 777 I still get the same error.

Originally created by @obi1 on GitHub (Jun 28, 2020). - Gitea version (or commit ref): 1.11.6 - Git version: 2.26.2 - Operating system: Gentoo Linux - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description I haven't been using Gitea for anything but pulls since may, when I had versions <1.11.5. Everything worked fine. In this time I've updated to 1.11.5 and most recently to 1.11.6. Today I wanted to make a push to the server and I was greeted with `remote: fatal: not a git repository: '.'` After that I've tried to create a new test file directly in the web interface and get the following error: `Failed to update/create file 'test' with error: Clone: exit status 128 - Cloning into bare repository '/var/lib/gitea/data/tmp/local-repo/upload.git927228562'... fatal: unable to access '/var/lib/gitea/data/tmp/local-repo/upload.git927228562/config': Permission denied exit status 128 - Cloning into bare repository '/var/lib/gitea/data/tmp/local-repo/upload.git927228562'... fatal: unable to access '/var/lib/gitea/data/tmp/local-repo/upload.git927228562/config': Permission denied`. The permissions seem to be in order and even if I set them to 777 I still get the same error.

GiteaMirror added the issue/stale label 2025-11-02 06:32:06 -06:00

GiteaMirror closed this issue

2025-11-02 06:32:06 -06:00

GiteaMirror commented

2025-11-02 06:32:07 -06:00

@obi1 commented on GitHub (Jun 29, 2020):

I figured out it's because apparently the new version is forcing me to enable xattr which I had disabled in the kernel. It works if I recompile the kernel with xattr support for my file system. Maybe this could be an optional setting at compile time?

@obi1 commented on GitHub (Jun 29, 2020): I figured out it's because apparently the new version is forcing me to enable xattr which I had disabled in the kernel. It works if I recompile the kernel with xattr support for my file system. Maybe this could be an optional setting at compile time?

GiteaMirror commented

2025-11-02 06:32:07 -06:00

@lunny commented on GitHub (Jul 7, 2020):

Maybe it's a problem of Golang v1.14?

@lunny commented on GitHub (Jul 7, 2020): Maybe it's a problem of Golang v1.14?

GiteaMirror commented

2025-11-02 06:32:07 -06:00

@stale[bot] commented on GitHub (Sep 5, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 5, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:32:08 -06:00

@stale[bot] commented on GitHub (Sep 20, 2020):

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

@stale[bot] commented on GitHub (Sep 20, 2020): 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#5655