I built this package 4 weeks ago and was able to build other packages that depended on it:
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-814a130fdc
I just received a request to build this package for EPEL-10 (https://bugzilla.redhat.com/show_bug.cgi?id=2319286) and sure enough, the package is no longer available in the repos.
What happened, and how should it be fixed?
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
Okay not sure what happened exactly, but presently I can see that it is blocked in koji for epel10.0 tag, and I think that is the reason it's not available anymore, I'll unblock it from koji now, so you can check and build it again to see if the push is going through in bodhi or not?
perl-Crypt-PBKDF2 epel10.0 pghmcfc [BLOCKED]
After unblocking;
perl-Crypt-PBKDF2 epel10.0 pghmcfc
Let me know, if you face any issues, after getting built and stable by bodhi it should be available once the next compose is out!
Let's see what happens: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ec31000573 Don't suppose there's any way of finding out why or when it got blocked?
Tue Sep 17 17:34:33 2024 perl-Crypt-PBKDF2-0.161520-21.eln140 untagged from eln by oscar Tue Sep 17 20:27:11 2024 package owner changed for perl-Crypt-PBKDF2 in epel10.0 by patrikp Tue Sep 17 20:27:11 2024 package list entry for perl-Crypt-PBKDF2 in epel10.0 updated by patrikp blocked: False -> True Mon Sep 23 17:29:29 2024 perl-Crypt-PBKDF2-0.161520-21.eln140 tagged into trashcan by oscar [still active] Thu Oct 17 12:09:52 2024 package owner changed for perl-Crypt-PBKDF2 in epel10.0 by jnsamyak [still active] Thu Oct 17 12:09:52 2024 package list entry for perl-Crypt-PBKDF2 in epel10.0 updated by jnsamyak [still active] blocked: True -> False Thu Oct 17 12:45:41 2024 perl-Crypt-PBKDF2-0.161520-19.el10_0 tagged into epel10.0-testing-candidate by pghmcfc Thu Oct 17 12:46:37 2024 perl-Crypt-PBKDF2-0.161520-19.el10_0 tagged into epel10.0-signing-pending by bodhi Thu Oct 17 12:47:40 2024 perl-Crypt-PBKDF2-0.161520-19.el10_0 untagged from epel10.0-signing-pending by autosign/autosign02.iad2.fedoraproject.org Thu Oct 17 12:47:40 2024 perl-Crypt-PBKDF2-0.161520-19.el10_0 tagged into epel10.0-testing-pending by autosign/autosign02.iad2.fedoraproject.org Thu Oct 17 12:49:05 2024 perl-Crypt-PBKDF2-0.161520-19.el10_0 untagged from epel10.0-testing-pending by bodhi Thu Oct 17 12:49:06 2024 perl-Crypt-PBKDF2-0.161520-19.el10_0 untagged from epel10.0-testing-candidate by bodhi Thu Oct 17 12:49:45 2024 perl-Crypt-PBKDF2-0.161520-19.el10_0 tagged into epel10.0 by bodhi [still active]
Not sure why but @patrikp may have blocked it because of some request that might have came in for blocking? But I see it got tagged into epel10.0 by bodhi now
Hmm, so the blocking happened on 17th September, the day after the original build was done: https://koji.fedoraproject.org/koji/buildinfo?buildID=2546706 Curious.
If I blocked it manually it was very likely part of a request to block certain packages that failed to get blocked automatically by the script/toddler that does automatic retirements. Apologies for the inconvenience.
@pghmcfc, so can you verify if it's there in epel10.0 now, and close the ticket once it's done?
Metadata Update from @jnsamyak: - Issue tagged with: low-gain, medium-trouble, ops
It's available in the buildroot now; I'll close the ticket after there's been a compose and I can see it again here: https://dl.fedoraproject.org/pub/epel/10/Everything/x86_64/Packages/p/
Metadata Update from @pghmcfc: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)