#6376 Error: Repo already exists: Cannot fork dist-git repo a second time after deleting first forked repo
Closed: Fixed 6 years ago Opened 6 years ago by lorbus.

On src.fp.o, I am getting the following error on my second try to fork a repo, after forking successfully the first time and then later deleting the dist-git repo:

Repo "forks/lorbus/colm" already exists

I am not in the packagers group, so I could only add changes through the web ui anyway, but this still seems like an issue to me.


The main issue has been fixed upstream at: https://pagure.io/pagure/pull-request/2596 but the infrastructure is currently in freeze for the beta release of Fedora 27 and thus the patch has not yet been applied.

Edit: Point to the correct PR

Metadata Update from @pingou:
- Issue assigned to pingou
- Issue tagged with: src.fp.o, unfreeze

6 years ago

Thanks for the info :)

Just tested 3.8 in staging and it works :)

yes, but when it will work on src.fp.o? :)

After freeze, once we can upgrade pagure :)

So part of this is resolved, pagure does it job correctly.

However, if you fork a project and delete it while the backend job updating the ACLs is still running, gitolite will re-create the repo and re-forking will fail with the error above.

Since we now have a banner explaining that access may not work while we refresh the ACLs in the back, I hope that this lower this scenario. However, there isn't really anything clean we can do to fix this atm, it's sort of a weird race-condition.

Metadata Update from @pingou:
- Issue untagged with: unfreeze
- Issue close_status updated to: Fixed

6 years ago

Hmm, the issue persits for me and I still can't fork the colm repo again..is there anyone who could manually delete it for me?

Login to comment on this ticket.

Metadata