Permission denied error when trying to push new branch to giit

j3s commented

2021-09-18 07:41:33 +00:00

Owner

Check out ~forest/capsul-flask
Create a fork, as ~threewordchant/capsul-flask
Add a remote for the fork, called fork
Create a new branch locally, and add commits
Run git push fork

Sometimes this works, often I get an error like this:

Enumerating objects: 31, done.
Counting objects: 100% (31/31), done.
Delta compression using up to 4 threads
Compressing objects: 100% (23/23), done.
Writing objects: 100% (24/24), 4.79 KiB | 350.00 KiB/s, done.
Total 24 (delta 14), reused 1 (delta 0), pack-reused 0
error: unable to write file ./objects/78/86c8a217ecda3c0dce911c02fe68d3b97a8adf: Permission denied
To giit.cyberia.club:~threewordchant/capsul-flask
 ! [remote rejected] tests -> tests (unable to migrate objects to permanent storage)
error: failed to push some refs to 'giit.cyberia.club:~threewordchant/capsul-flask'

1. Check out ~forest/capsul-flask 2. Create a fork, as ~threewordchant/capsul-flask 3. Add a remote for the fork, called `fork` 4. Create a new branch locally, and add commits 5. Run `git push fork` Sometimes this works, often I get an error like this: ``` Enumerating objects: 31, done. Counting objects: 100% (31/31), done. Delta compression using up to 4 threads Compressing objects: 100% (23/23), done. Writing objects: 100% (24/24), 4.79 KiB | 350.00 KiB/s, done. Total 24 (delta 14), reused 1 (delta 0), pack-reused 0 error: unable to write file ./objects/78/86c8a217ecda3c0dce911c02fe68d3b97a8adf: Permission denied To giit.cyberia.club:~threewordchant/capsul-flask ! [remote rejected] tests -> tests (unable to migrate objects to permanent storage) error: failed to push some refs to 'giit.cyberia.club:~threewordchant/capsul-flask' ```

j3s commented

2021-09-18 07:41:43 +00:00

Author

Owner

~threewordchant referenced this from #822 months ago
~threewordchant2 months ago · edit
Strangely, it just worked pushing up a new publicapi branch:

b8d149e862

Could there be some kind of clash with the tests branch?

~threewordchant2 months ago · edit
Update: also failed for a branch called publicapi-tests:

$ git push mine
Enumerating objects: 61, done.
Counting objects: 100% (59/59), done.
Delta compression using up to 4 threads
Compressing objects: 100% (48/48), done.
Writing objects: 100% (49/49), 8.93 KiB | 457.00 KiB/s, done.
Total 49 (delta 33), reused 1 (delta 0), pack-reused 0
error: unable to write file ./objects/15/c49b35069bdf751762b3e845aaa98a65149070: Permission denied
error: unable to write file ./objects/3a/676697681815573697ec66fe9ab460016f5194: Permission denied
error: unable to write file ./objects/78/86c8a217ecda3c0dce911c02fe68d3b97a8adf: Permission denied
~threewordchant referenced this from #842 months ago
~foresta month ago · edit
Dang, this is weird. I have seen authentication issues with sr.ht before (because redis crashed) but when that happens, it means you can't authenticate at all.

In the past we also saw a problem where a stale key got stuck in redis and was never updated or expired for a long time, I don't remember exactly what the error messages for that looked like, but I don't think it was exactly like what you are seeing.

~foresta month ago · edit
I hesitate to try to fix this right now because we're currently shopping for ways to replace sr.ht.

If this is blocking us from collaborating, we can temporarily use my gitea server git.sequentialread.com or yours https://git.autonomic.zone .

~threewordchanta month ago · edit
It's a dice-roll each branch I upload, I guess I could try renaming and reuploading until it works, but yes I think a gitea could be easier for the time being, no preference on which 👌

~threewordchanta month ago · edit
I notice that it's trying to write to objects/78/... in both failed pushes – I wonder if it's to do with file permissions in the repo directory?

~threewordchant referenced this from #822 months ago ~threewordchant2 months ago · edit Strangely, it just worked pushing up a new publicapi branch: https://giit.cyberia.club/~threewordchant/capsul-flask/commit/b8d149e8625b33fef4cee25748f63ba662833e7c Could there be some kind of clash with the tests branch? ~threewordchant2 months ago · edit Update: also failed for a branch called publicapi-tests: $ git push mine Enumerating objects: 61, done. Counting objects: 100% (59/59), done. Delta compression using up to 4 threads Compressing objects: 100% (48/48), done. Writing objects: 100% (49/49), 8.93 KiB | 457.00 KiB/s, done. Total 49 (delta 33), reused 1 (delta 0), pack-reused 0 error: unable to write file ./objects/15/c49b35069bdf751762b3e845aaa98a65149070: Permission denied error: unable to write file ./objects/3a/676697681815573697ec66fe9ab460016f5194: Permission denied error: unable to write file ./objects/78/86c8a217ecda3c0dce911c02fe68d3b97a8adf: Permission denied ~threewordchant referenced this from #842 months ago ~foresta month ago · edit Dang, this is weird. I have seen authentication issues with sr.ht before (because redis crashed) but when that happens, it means you can't authenticate at all. In the past we also saw a problem where a stale key got stuck in redis and was never updated or expired for a long time, I don't remember exactly what the error messages for that looked like, but I don't think it was exactly like what you are seeing. ~foresta month ago · edit I hesitate to try to fix this right now because we're currently shopping for ways to replace sr.ht. If this is blocking us from collaborating, we can temporarily use my gitea server git.sequentialread.com or yours https://git.autonomic.zone . ~threewordchanta month ago · edit It's a dice-roll each branch I upload, I guess I could try renaming and reuploading until it works, but yes I think a gitea could be easier for the time being, no preference on which 👌 ~threewordchanta month ago · edit I notice that it's trying to write to objects/78/... in both failed pushes – I wonder if it's to do with file permissions in the repo directory?

forest commented

2021-09-19 17:41:06 +00:00

Owner

This should be resolved now that we moved to gitea 👍

forest closed this issue

2021-09-19 17:41:06 +00:00

Permission denied error when trying to push new branch to giit #14