#12713 Stalled EPEL request pyOpenSSL
Closed: Fixed by jnsamyak. Opened by jonathanspw.

  • Describe the issue
    pyOpenSSL is a stalled EPEL request

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2355193

  • When do you need this? (YYYY/MM/DD)
    ASAP to unblock the certbot stack in EPEL10

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

  • If we cannot complete your request, what is the impact?
    certbot likely will not come to EPEL10. This is a very important EPEL package and will block people from upgrading to EL10 and variants.


Sorry I wasn't very clear, I'd like my fas jonathanspw added to EPEL branches. That's what I'm requesting here.

pyOpenSSL is not a stalled EPEL request. The package was already branched for epel10 and the process for stalled EPEL requests is a process for branching, not for updating packages.

pyOpenSSL is not a stalled EPEL request. The package was already branched for epel10 and the process for stalled EPEL requests is a process for branching, not for updating packages.

Is there a more proper procedure for a blocking issue not getting replied to?

I've built the package into Jonathan's side tag, but for what it's worth I'd support them being added for EPEL. I've only got commit on the package, though, so it'd be up to someone from the crypto-team to do that.

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

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

From what i have gathered, jonathanspw is now a collaborator for epel branches for this project.

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

Is there a more proper procedure for a blocking issue not getting replied to?

Provenpackager escalation and/or https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/

There's also a new policy in cooking at FESCo https://pagure.io/fesco/fesco-docs/pull-request/94

Metadata