Fedora Account System
Red Hat Associate
Red Hat Customer
Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). Your package (pki-core) Fails To Install in Fedora 36: can't install pki-base-java: - nothing provides resteasy-jaxb-provider >= 3.0.17-1 needed by pki-base-java-11.0.0-0.2.alpha1.fc35.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
The pki-core package has been replaced by dogtag-pki. The latest dogtag-pki build can be installed without issues. We plan to orphan/retire pki-core package as soon as the dogtag-pki build reaches stable repository.
If the build is dogtag-pki-11.0.0-1.fc36, go ahead and retire pki-core. The action of retirement cannot technically remove the dogtag-pki component from the repos before this update is included https://bodhi.fedoraproject.org/updates/FEDORA-2021-015adf5602 (because this update will be included in the next successful compose).
BTW if you intend to do this in Fedora 35 as well, you need to get https://bodhi.fedoraproject.org/updates/FEDORA-2021-2c86bcd3f3 in stable before the final freeze starts tomorrow (or request a freeze exception).
If we can't get it into stable before the final freeze, can we update the packages (and retire pki-core) after F35 GA? In case we need to request an exception, is this the procedure? https://fedoraproject.org/wiki/Final_Freeze_Policy#Exceptions
Actually I think we already have Dogtag PKI 11.0.0 Beta in stable: https://koji.fedoraproject.org/koji/buildinfo?buildID=1827994 The Bodhi update above is basically for Dogtag PKI 11.0.0 GA release, which is not too different from beta1, so it's probably OK if it goes to stable after F35 GA.
It is not technically possible to retire packages after GA. They will be forever available in the "fedora" repos. https://fedoraproject.org/wiki/Final_Freeze_Policy#Exceptions hasn't been updated in 10 years, not sure why that page exists. The procedure is https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process#Proposing_freeze_exception_bugs
To my understanding pki-core doesn't really need to be retired from F35 since it's been made obsolete by dogtag-pki, but we'll request an exception if necessary. Thanks!
I suggest just retiring it today to make things nice and consistent.
I wish I could, but we might not have resources to test and provide karma before the deadline.
Oh, I understood Dogtag PKI 11.0.0 Beta already replaces pki-core: $ repoquery --repo=fedora --releasever 35 --whatobsoletes pki-base-java dogtag-pki-base-java-0:11.0.0-0.4.beta1.fc35.noarch $ repoquery --repo=fedora --releasever 35 --obsoletes dogtag-pki-base-java pki-base-java < 11.0.0-0.4.beta1.fc35 $ repoquery --repo=fedora --releasever 35 --obsoletes dogtag-pki-base pki-base < 11.0.0-0.4.beta1.fc35 And so on... So pki-core can be retired already. Or is that not the case?
Ah yes, I've retired pki-core and idm-console-framework now: https://src.fedoraproject.org/rpms/pki-core/tree/f35 https://src.fedoraproject.org/rpms/pki-core/tree/main https://src.fedoraproject.org/rpms/idm-console-framework/tree/f35 https://src.fedoraproject.org/rpms/idm-console-framework/tree/main If we can get the exception we would be able to drop the JAXB packages that have FTBFS issues as well.
Thanks!
Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). All subpackages of a package against which this bug was filled are now installable or removed from Fedora 36. Thanks for taking care of it!