I tried to create a few forks to create a coordinated update between six packages, and it looks like they're broken again.
They were created today via the "Fork" button, but it looks like the git repos in the backend were actually not deleted when I last deleted those forks a while ago (they don't have the last few commits from the upstream master branch, so they're definitely not "fresh").
What do you prefer, having the read-only flag removed or delete the project?
Wow, that was fast response time! If you could delete them so I can create "fresh" working forks, that would be perfect. :)
okidoke
Metadata Update from @pingou: - Issue assigned to pingou
Done
I went with a bunch of pagure-admin commands, here is the last one:
# pagure-admin delete-project rpms/jackson-jaxrs-providers --user decathorpe pingou Using configuration file `/etc/pagure/pagure.cfg` Are you sure you want to delete: forks/decathorpe/rpms/jackson-jaxrs-providers? This cannot be undone! Do you want to continue? [y/N]y Project deleted
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Can confirm, all good now. Thank you!
It happened again (or, rather, I found another victim of the original issue):
https://src.fedoraproject.org/fork/decathorpe/rpms/maven
Could you please delete that fork?
Metadata Update from @decathorpe: - Issue status updated to: Open (was: Closed)
Done.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.