#13035 Unblock CGSI-gSOAP (epel10.1 and epel10.2)
Closed: Fixed 19 days ago by jnsamyak. Opened 19 days ago by ellert.

  • Describe the issue

This is a follow-up on #13024
After unretiring the package in epel10 and epel10.0, the package is still blocked in epel10.1 and epel10.2.
Building packages for epel10.1 - which is a new branch requested after the package was unretired in epel10 and epel10.0 - does not work.
Building packages for epel10 - which was unretired and unblocked - does not work, because building for epel10 builds for epel10.2-candidate which inherits from epel10.2 where the package is blocked.

I tried reopening the previous ticket, but there was no reply for 3 days.

$ koji list-pkgs --show-blocked --package CGSI-gSOAP | grep epel10 | sort
CGSI-gSOAP              epel10.0                                 ellert         
CGSI-gSOAP              epel10.1                                 ellert          [BLOCKED]
CGSI-gSOAP              epel10.2                                 ellert          [BLOCKED]
CGSI-gSOAP              epel10                                   ellert         
  • When do you need this? (YYYY/MM/DD)

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

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


Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

19 days ago

Metadata Update from @jnsamyak:
- Issue tagged with: low-gain, low-trouble, ops, sprint-3

19 days ago
Branches that you need it to be unretired for?
epel10 epel10.0

Oh, I see you got a blocked package, and I unblocked it for ya:

CGSI-gSOAP              epel10.1                                 ellert         
CGSI-gSOAP              epel10.2                                 ellert  

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

19 days ago

Log in to comment on this ticket.

Metadata
Boards 2
Ops Status: Backlog
sprint-3 Status: Done