Fixed.

[root@pkgs01 ~][PROD-IAD2]# pagure-admin read-only --ro false --user fxzxmicah rpms/gnome-shell
Using configuration file /etc/pagure/pagure.cfg
The read-only flag of the project forks/fxzxmicah/rpms/gnome-shell has been set to False

Apologies for contacting both ways as I wasn't sure if you got the email or if I was contacting the right person.

For this issue, I'm guessing it might be a bug because it happened that my login expired when I forked the repository.

https://src.fedoraproject.org/fork/fxzxmicah/rpms/gnome-shell

It failed again.

I did again what @kevin did.

[root@pkgs01 ~][PROD-IAD2]# pagure-admin read-only --ro false --user fxzxmicah rpms/gnome-shell
Using configuration file `/etc/pagure/pagure.cfg`
The read-only flag of the project forks/fxzxmicah/rpms/gnome-shell has been set to False

It seems that the project isn't read-only anymore. What did you do when it failed again?

my login expired

Like I said above, both times I was asked to log in again right after I forked.

Your task failed: Did not manage to rebase this pull-request

This time I saw an error message — it doesn’t seem to be related to my login status, but rather to the repository itself.

And it failed again. Looks like I won’t be able to fork this repository until the bug is fixed.

Hm, I see the error pop up again on the repository. Something else is probably wrong with it :-/

Did you get the login invalidated when trying to do rebase?

Here's what I just did:
1. Deleted the previous empty fork
2. Forked the original repository again

The error message Your task failed: Did not manage to rebase this pull-request appeared right after I clicked the fork button on the original repository in step 2.

That is probably correct, if you opened the PR from the fork you deleted it doesn't know how to rebase it.

But that the fork is created read-only is strange. Either there is something wrong in the fork metadata or there is something strange with your user (the prompt for login after fork is not normal).

I changed the flag again. Please don't delete the fork again to prevent the issue. Feel free to report the problem upstream on https://pagure.io/pagure/issues

That is probably correct, if you opened the PR from the fork you deleted it doesn't know how to rebase it.

I haven’t opened any PRs for this upstream repository. I can't even fork the repository successfully — I'm far from being able to open a PR.

the prompt for login after fork is not normal

That’s not the reason — it was probably just that my login session happened to expire at the time. Because it doesn’t ask me to log in again every time I fork.

Please don't delete the fork again to prevent the issue.

So does that mean I won’t be able to submit code to the upstream repository from the fork until the issue is fixed?

Now I see that the error you get was not related to any PR. I got misguided by the error message.

In that case there is probably some metadata that are left after deleting the repository. Let me check the permissions on the folder.

In fact, my first attempt to fork this upstream repository failed.

I do see what is wrong, you are not in packager group, so you don't actually have permissions to write to newly created fork. You don't even signed the FPCLA on your account.

I'm surprised that it did even show you the fork button.

https://src.fedoraproject.org/user/fxzxmicah/forks

But I have other successful forks, don’t I? Not only that, I even created a few PRs.

I do see what is wrong, you are not in packager group

You don't even signed the FPCLA on your account.

I don’t even know what those are.

Hm, on the other forks the permissions are the same, so there must be something wrong with the repo.

FPCLA is Fedora Contributor License Agreement. It should be accepted by every Fedora contributor, you can do that on https://accounts.fedoraproject.org

The permission is not an issue as everything is actually done by pagure user. Could you delete the fork now and I will check if there are any leftovers in database and on server?

FPCLA is Fedora Contributor License Agreement. It should be accepted by every Fedora contributor, you can do that on https://accounts.fedoraproject.org

Could you delete the fork now and I will check if there are any leftovers in database and on server?

Done.

The directory itself on the server is gone and the fork is gone from database, so there shouldn't be any metadata left.

So I'm not sure what is causing the fork to be read only.

So can I try forking it again now?

Try it, I will look in the db at the newly created fork and see if there is something odd on it.

Failed again....

The only difference in comparison to your mutter fork is that this one is set read-only, but why does that happen I don't have a clue.

At least I was able to find the error in journal:

Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]: 2025-04-17 13:03:17,709 [ERROR] celery.app.trace: Task pagure.lib.tasks.fork[e0c3820e-ff9a-453f-b741-8811505d8024] raised unexpected: PagureException('Did not manage to rebase>
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]: Traceback (most recent call last):
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib/python3.6/site-packages/pagure/lib/repo.py", line 35, in run_command
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     command, stderr=subprocess.STDOUT, cwd=cwd
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     **kwargs).stdout
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib64/python3.6/subprocess.py", line 438, in run
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     output=stdout, stderr=stderr)
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]: subprocess.CalledProcessError: Command '['git', 'clone', '/srv/git/repositories/rpms/gnome-shell.git', '/tmp/pagure-fork-jvecunim']' returned non-zero exit status 128.
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]: During handling of the above exception, another exception occurred:
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]: Traceback (most recent call last):
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib/python3.6/site-packages/celery/app/trace.py", line 385, in trace_task
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     R = retval = fun(*args, **kwargs)
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib/python3.6/site-packages/celery/app/trace.py", line 648, in __protected_call__
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     return self.run(*args, **kwargs)
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib/python3.6/site-packages/pagure/lib/tasks_utils.py", line 36, in decorated_function
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     return function(self, session, *args, **kwargs)
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib/python3.6/site-packages/pagure/lib/tasks.py", line 501, in fork
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     repo_from, "main", "fork"
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib/python3.6/site-packages/pagure/lib/git.py", line 1028, in __enter__
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     PagureRepo.clone(self._origpath, self.repopath)
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib/python3.6/site-packages/pagure/lib/repo.py", line 78, in clone
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     run_command(cmd)
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:   File "/usr/lib/python3.6/site-packages/pagure/lib/repo.py", line 47, in run_command
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]:     "Did not manage to rebase this pull-request"
Apr 17 13:03:17 pkgs01.iad2.fedoraproject.org celery[1252]: pagure.exceptions.PagureException: Did not manage to rebase this pull-request

When trying to clone the repo manually I got:

$ sudo -u pagure git clone /srv/git/repositories/rpms/gnome-shell.git /tmp/pagure-fork-jvecunim
Cloning into '/tmp/pagure-fork-jvecunim'...
warning: error opening directory '/srv/git/repositories/rpms/gnome-shell.git/objects/tmp_objdir-incoming-YTneP7/': Permission denied
fatal: failed to iterate over '/srv/git/repositories/rpms/gnome-shell.git/objects/'

And the mentioned folder in the error has really strange permissions. I fixed the permissions on that folder. @fxzxmicah could you try to recreate the fork again?

Please help me fix the current fork first, otherwise I won’t be able to delete it.

Should be fixed now, forgot about that.

Succeed!

Finally :tada:

Let me close the ticket as this is now solved.

There might need to be a mechanism to prevent this from happening again.

That would be probably good issue for https://pagure.io/pagure