Pagure permission denied | Pull Requests

I would like to make a few edits and submit a PR on pagure, but I am running into trouble:

  • I successfully fork the repo on pagure.io using ssh (I did add my keys to my profile), but when I try to clone it to my local machine with git, I encounter the following: ```
    git@pagure.io: Permission denied (publickey).
    fatal: Could not read from remote repository.

  • If I instead use https, I am able to clone the repo locally, stage changes and make commits, but am unable to push:
    fatal: unable to access 'https://pagure.io/forks/fuller/kernel-tests.git/': The requested URL returned error: 403

Anyone know what I’m doing wrong? Do I need to join or be accepted to another Fedora subgroup in order to work on Pagure?

Please make sure you have the correct access rights
and the repository exists.

1 Like

As i understood you have to be a packer to use push. If not you can use a workaround described in the Docs:

Pull Requests :: Fedora Docs

I tested while i was reading the toppic lately:

1 Like

Anyone can works on Pagure if they have a :fedora: account and login into Pagure.

  1. What kind of pagure repo are you going to use to make a PR?.

  2. IF is a normal REPO or TEAM REPO, the procedure is the follow:
    a. Fork the REPO → Forks — pagure documentation.
    b. Make a Commit.
    c. Create a PULL REQUEST against the MAIN REPO → Pull Requests — pagure documentation.
    d. Wait some time until your PR has been reviewed by the TEAM.

  3. IF you’re going to work with RPM source @ilikelinux comment is the best way.

Why this?, this is what you get if you’re part of the TEAM who manage the REPO:

Captura de pantalla de 2021-09-14 19-55-12

If you’re are not a part fo the TEAM who manage the repo you can only get acces via HTTP and not via SSH.

NOTE

However if you’re part of the TEAM who manage the REPO the best Practice is to work in this way/manner.

MORE INFO

https://docs.pagure.org/pagure/usage/

Regards., HTH

2 Likes

No, that’s only for src.fedoraproject.org, not for pagure.io. pagure.io is just a forge that anyone with a Fedora account can use.

Do you have multiple SSH keys by any chance? If you do, you need to update your ~/.ssh/config to note what key should be used for what host. For example, I have this in my config:

HOST *.fedoraproject.org fedorapeople.org *.pagure.io *.fedorainfracloud.org
    # path to SSH key file for use on Fedora services
    IdentityFile ~/.ssh/id_fedora_rsa 
    # My FAS username
    User ankursinha
    AddKeysToAgent yes

Otherwise, it may try your computer’s username and anothe SSH key by default, and if they don’t match, it won’t authenticate.

You may want to check your ssh public key at OpenID transaction in progress
It would have populated that one from the one in the account system at start, but it only updates on logout/login or you manually adding more keys there.

1 Like