6 days ago(June 10th) I created a Pagure repo for fiddling with Ansible playbooks. During the setup I tried to be clever with the branch names(bad idea I guess) and ended up making a branch name that was not allowed, but somehow Pagure let it through. I think I put spaces in or something. Pagure tried to create the repo anyways, but ended up with no branches. That somehow tricked Pagure into thinking the repo was still being set up in the backend.
The permissions on this repository are being updated. This may take a while. During this time, you or some of the project's contributors may not be able to push to this repository.
The repo is https://pagure.io/Grayson-Ansible-Playground
It's been saying that for 6 days. Because it's still setting up, it blocks access to the settings, meaning I can't delete and create the repo with a better branch.
Short term, this repo should be killed, but long term maybe this should be filed against Pagure itself. Thanks!
I have deleted it.
Metadata Update from @nb: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@nb note that using pagure-admin on the host machine you can toggle the read-only flag of a project (which solves that issue).