#12607 BuildError: package python-robotframework not in list for tag epel10.1-testing-candidate
Closed: Fixed by fedepell. Opened by fedepell.

  • Describe the issue
    Branched epel10 for this package and pushed correctly, but seems I cannot build it.

  • When do you need this? (YYYY/MM/DD)
    No rush, when possible.

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

  • If we cannot complete your request, what is the impact?
    Sadness! :)

Thanks!


I don't see a request for it in the fedora-scm-requests issue tracker. That likely means you pushed the branch directly in git. The documented process is to run fedpkg request-branch epel10, which will create the branch and add the package to the build tag allow list. If you run that command now, it will report a failure to create the branch because it already exists, but it should trigger the second step an unblock you from building. Please try that and report back here if it still doesn't work.

Metadata Update from @carlwgeorge:
- Issue assigned to carlwgeorge
- Issue tagged with: low-gain, low-trouble

Indeed sorry I likely just pushed without prior request :-/

I've tried it now and as you said it errored since it already exists:

Requested branch "epel10" already exists. Skipping the operation.

I anyway tried the build, but the error persists

BuildError: package python-robotframework not in list for tag epel10.1-testing-candidate

Note that you can pass '--no-git-branch' in this case to have it just add the package and not error...

@kevin Oh yeah I forgot about that flag. I was hoping even with the "already exists" failure it would still kick off the owner-sync-pagure process, but I guess not. I've added it manually now, so builds should now be allowed now.

 koji list-pkgs --package python-robotframework | grep epel10
python-robotframework   epel10.1                                 fedepel

@fedepell Can you try the build again?

All good now! Thanks a lot for immediate help and sorry for creating the problem at first!

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

Metadata