#11826 Untretire EPEL branches for cxxopts
Closed: Fixed with Explanation by humaton. Opened by orion.

  • Describe the issue
    I am the new maintainer for cxxopts and I want to un-retire the epel8 and epel9 branches.

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

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

  • If we cannot complete your request, what is the impact?
    Cannot build updated conda or libmamba for EPEL8/9.


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

Could someone please take a look at this? Thanks.

Sorry about the delays.

The package is now unretired. For missing branches please use $fedpkg request-branch

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

Thanks, though it seems like you reverted back a commit too far on the epel9 branch.

I'm also still getting:

110510475 build (epel9-candidate, /rpms/cxxopts.git:f765579cbcba36125fbf965ad20380678c2833b4): open (buildvm-s390x-22.s390.fedoraproject.org) -> FAILED: BuildError: package cxxopts is blocked for tag epel9-testing-candidate

Metadata Update from @orion:
- Issue status updated to: Open (was: Closed)

do'h, I forgot to unblock it in koji. It is done now.

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

Something is still not right, I get this with fedpkg build:

Could not execute build: Cannot build from stream branch epel8 as it is inactive.
Could not execute build: Cannot build from stream branch epel9 as it is inactive.

Metadata Update from @orion:
- Issue status updated to: Open (was: Closed)

Hmm, it looks like something updated the EOL in PDC again and rendered it inactive.

I updated the PDC EOL date and ran fedpkg build from the latest commit. Let's see if it goes through.

https://koji.fedoraproject.org/koji/taskinfo?taskID=110640023

Ok so what happened was timing, because there were delays between updating PDC and unblocking the package in koji, automation kicked in and retired the package again.

I took the liberty and built it again and it went ok.
https://koji.fedoraproject.org/koji/taskinfo?taskID=110640201

Thank you. Looks like the same treatment is needed for the epel8 branch again:

$ git push
Enumerating objects: 13, done.
Counting objects: 100% (13/13), done.
Delta compression using up to 8 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (8/8), 1.56 KiB | 1.56 MiB/s, done.
Total 8 (delta 1), reused 3 (delta 0), pack-reused 0
fedpremote: Branch refs/heads/epel8 is unsupported. Cannot push to a disabled branch (maybe eol?).
remote: Denied push for ref 'refs/heads/epel8' for user 'orion'
remote: All changes have been rejected
kTo ssh://pkgs.fedoraproject.org/rpms/cxxopts
 ! [remote rejected] epel8 -> epel8 (pre-receive hook declined)
error: failed to push some refs to 'ssh://pkgs.fedoraproject.org/rpms/cxxopts'

ping - can I please get some help here?

Somehow the epel8 branch is marked not active in pdc... so it won't let me adjust the sla/eols, which is causing the push failure. ;(

I am not sure how to make it active, I think we will need to poke around the client...

What I did is the use script from releng repo

releng/scripts/pdc/adjust-eol.py fedora $PDC_TOKEN cxxopts rpm epel8 2024-01-01 -y

that sets all the sla to that date and then koji unblock pkg.

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

Thank you - managed to push and build again.

Metadata