#8669 Cannot create EPEL 8 branch for wine
Closed: Invalid 4 years ago by mooninite. Opened 4 years ago by mooninite.

  • Describe the issue
    The wine package did not receive an epel8 branch automatically. Trying to create one results in a failure:

$ git push origin
Total 0 (delta 0), reused 0 (delta 0)
remote: Unspecified ref refs/heads/epel8 is blocked
remote: Denied push for ref 'refs/heads/epel8' for user 'mooninite'
remote: All changes have been rejected
To ssh://pkgs.fedoraproject.org/rpms/wine
! [remote rejected] epel8 -> epel8 (pre-receive hook declined)
error: failed to push some refs to 'ssh://mooninite@pkgs.fedoraproject.org/rpms/wine'

I'm only an 'admin' and not 'main admin', but I am a provenpackager. The hook to prevent branch creation is NOT active. Anyway, I'd like to make sure the branch is there so I can push a build.


EPEL branches do get branched automatically but need a fedpkg branch-request done to make this done. That puts the ticket in the correct place for the branching to occur.

I cannot perform a request-branch. I have a fresh pagure token.

$ cat ~/.config/rpkg/fedpkg.conf
[fedpkg.pagure]
token = <redacted>
$ 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#api-keys to get or renew your API token.
For invalid or expired token refer to "fedpkg request-repo -h" to set a token in your user configuration.

@mooninite What is the fedpkg version you are using and can you verify if the token you are using is not an expired token?

@mooninite The only thing that I can think of it might be missing the Create New Ticket ACL, can you create a new token and try with it?

The issue was the Pagure platform I was creating the token in. I had a brain fart. SCM request is now created.

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

4 years ago

Login to comment on this ticket.

Metadata
Attachments 1
Attached 4 years ago View Comment