#10808 Cannot request epel8 branch for uptimed using fedpkg
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by ttorcz.

  • Describe the issue
    I'm trying to create an EPEL8 (and EPEL9 later) branch for package uptimed.
sources/fedora/uptimed% fedpkg request-branch epel8   
Could not execute request_branch: The following error occurred while creating a new issue in Pagure: Invalid or expired token. Please visit https://src.fedoraproject.org/settings#nav-api-tab to get or renew your API token.
For invalid or expired tokens please set a new token in your user configuration with:

        fedpkg set-pagure-token <token>

I went to the page shown, created a token (fedpkg message did not specify which ACL are important, I've enabled all - see attached screenshot).

sources/fedora/uptimed% fedpkg set-pagure-token JFVA<redacted>
updating config '/home/zdzichu/.config/rpkg/fedpkg.conf'

sources/fedora/uptimed% fedpkg request-branch epel8                                                             
Could not execute request_branch: The following error occurred while creating a new issue in Pagure: Invalid or expired token. Please visit https://pagure.io/settings#nav-api-tab to get or renew your API token.
For invalid or expired tokens please set a new token in your user configuration with:

        fedpkg set-pagure-token <token>

So the command does not work.

  • When do you need this? (YYYY/MM/DD)

Sometime.

  • When is this no longer needed or useful? (YYYY/MM/DD)

Cannot specify.

  • If we cannot complete your request, what is the impact?

There will be no uptimed in EPEL8+.

Screenshot_from_2022-05-26_18-45-23.png


That message is wrong. ;(

See:

fedpkg request-repo --help

Request a new dist-git repository

Before the operation, you need to generate a pagure.io API token at:
    https://pagure.io/settings/token/new

    ACL required:
        "Create a new ticket"

Update your token with the following command:
    fedpkg set-pagure-token <api_key_here>

Command saves token to fedpkg config file:
    ~/.config/rpkg/fedpkg.conf

For example:
    [fedpkg.pagure]
    token = <api_key_here>

Below is a basic example of the command to request a dist-git repository for
the package foo:

    fedpkg request-repo foo 1234

Another example to request a module foo:

    fedpkg request-repo --namespace modules foo

ie, you need a token for pagure.io (because you will be opening a ticket there which we process).

Try getting one of those and see if that fixes it?

Metadata Update from @phsmoura:
- Issue tagged with: low-gain, low-trouble, ops

2 years ago

Metadata Update from @humaton:
- Issue assigned to humaton

2 years ago

hi @ttorcz, any luck with getting fedpkg running? If nirik's advice worked we can update the error message so it reflects reality.

Hi, sorry for not providing feedback. Yes, nirik's advice worked.
Error message certainly needs updating (and extending - user have to select ACLs when creating token, it would be nice to know which is relevant for fedpkg).

Can someone file a issue on fedpkg to get this updated? :)

Glad it's working now.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog
Attachments 1