Describe the issue I submitted this update: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c2ac13a0fc But now python39-pyasn1-epel-0.4.8-1.el8 not tagged: https://koji.fedoraproject.org/koji/buildinfo?buildID=2085995
When do you need this? ASAP
If we cannot complete your request, what is the impact?
Error: Problem: conflicting requests - nothing provides python3.9dist(pyasn1) >= 0.3.7 needed by python39-ldap-3.4.3-1.el8.x86_64 - nothing provides python3.9dist(pyasn1-modules) >= 0.1.5 needed by python39-ldap-3.4.3-1.el8.x86_64 - nothing provides python39-pyasn1 >= 0.3.7 needed by python39-ldap-3.4.3-1.el8.x86_64 - nothing provides python39-pyasn1-modules >= 0.1.5 needed by python39-ldap-3.4.3-1.el8.x86_64
Metadata Update from @humaton: - Issue tagged with: low-gain, medium-trouble, ops
Seems like some automation untagged the build.
$ koji list-history --build=python39-pyasn1-epel-0.4.8-1.el8 Tue Nov 8 22:54:21 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-testing-candidate by orion Tue Nov 8 22:57:19 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-signing-pending by bodhi Tue Nov 8 22:57:22 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-override by bodhi Tue Nov 8 22:57:24 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-signing-pending by autopen Tue Nov 8 22:57:24 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-testing-pending by autopen Wed Nov 9 12:56:34 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-testing-candidate by bodhi Wed Nov 9 12:56:34 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-testing by bodhi Wed Nov 9 12:56:49 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-testing-pending by bodhi Mon Nov 14 01:35:42 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-override by bodhi Wed Nov 16 13:02:43 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-pending by bodhi Thu Nov 17 03:55:04 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-testing by bodhi Thu Nov 17 03:55:04 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8 by bodhi Thu Nov 17 03:55:21 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-pending by bodhi Thu Nov 17 16:50:49 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8 by releng
Hmm, it was also blocked for epel8. Everything should work as expected now.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Looks good. Thank you.
Looks like it got untagged again. What's going on?
Metadata Update from @orion: - Issue status updated to: Open (was: Closed)
Hey @orion,
Did it happen recently? Because koji list-history says it was untagged from epel8 long back
koji list-history --build=python39-pyasn1-epel-0.4.8-1.el8 Wed Nov 9 03:24:21 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-testing-candidate by orion Wed Nov 9 03:27:19 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-signing-pending by bodhi Wed Nov 9 03:27:22 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-override by bodhi Wed Nov 9 03:27:24 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-signing-pending by autopen Wed Nov 9 03:27:24 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-testing-pending by autopen Wed Nov 9 17:26:34 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-testing-candidate by bodhi Wed Nov 9 17:26:34 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-testing by bodhi Wed Nov 9 17:26:49 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-testing-pending by bodhi Mon Nov 14 06:05:42 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-override by bodhi Wed Nov 16 17:32:43 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8-pending by bodhi Thu Nov 17 08:25:04 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-testing by bodhi Thu Nov 17 08:25:04 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8 by bodhi Thu Nov 17 08:25:21 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8-pending by bodhi Thu Nov 17 21:20:49 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8 by releng Mon Dec 12 17:58:32 2022 python39-pyasn1-epel-0.4.8-1.el8 tagged into epel8 by humaton Tue Dec 13 11:16:39 2022 python39-pyasn1-epel-0.4.8-1.el8 untagged from epel8 by releng
On digging deeper, I see the package it orphaned in dist-git: https://src.fedoraproject.org/rpms/python39-pyasn1-epel
Seems epel8 branch is active but is blocked in koji and PDC eol is also set to older date
Koji:
koji list-pkgs --show-blocked --package=python39-pyasn1-epel Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python39-pyasn1-epel module-package-list orion python39-pyasn1-epel epel8-build orion python39-pyasn1-epel epel8 orion [BLOCKED] python39-pyasn1-epel epel8-testing orion python39-pyasn1-epel epel8-pending orion python39-pyasn1-epel f38 orphan [BLOCKED] python39-pyasn1-epel f39 orphan [BLOCKED] python39-pyasn1-epel f38-Beta orphan [BLOCKED]
PDC: https://pdc.fedoraproject.org/rest_api/v1/component-branch-slas/?branch=epel8&global_component=python39-pyasn1-epel
No idea when it happened, just noticed it now. No idea why it was orphaned. It should only have been retired in Fedora, not EPEL.
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
So I'm gonna try to unretire it for epel8, and we will see if it kicks back again, what say?
Worth a shot, thanks.
I unblocked it from Koji and gave you the project permissions, check now.
Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python39-pyasn1-epel module-package-list orion python39-pyasn1-epel epel8-build orion python39-pyasn1-epel epel8 orphan
Can you check now?
I've created an update - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-e59c2d98a0 So far so good.
Awesome, seems like the update is in testing!
Hi @orion, do you see any issues? If not, we can close this otherwise, let's see what more to resolve :D
Yeah, closing. Thanks.
Metadata Update from @orion: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.