Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2010417 - F36FailsToInstall: pki-base-java
Summary: F36FailsToInstall: pki-base-java
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: pki-core
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Harmsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F36FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2021-10-04 15:49 UTC by Miro Hrončok
Modified: 2022-01-14 23:27 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-14 23:27:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Miro Hrončok 2021-10-04 15:49:48 UTC 
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!
Comment 1 Endi Sukma Dewata 2021-10-04 16:12:21 UTC 
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.
Comment 2 Miro Hrončok 2021-10-04 16:20:55 UTC 
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).
Comment 3 Miro Hrončok 2021-10-04 16:22:57 UTC 
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).
Comment 4 Endi Sukma Dewata 2021-10-04 16:49:55 UTC 
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
Comment 5 Endi Sukma Dewata 2021-10-04 17:00:54 UTC 
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.
Comment 6 Miro Hrončok 2021-10-04 18:48:49 UTC 
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
Comment 7 Endi Sukma Dewata 2021-10-04 19:20:07 UTC 
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!
Comment 8 Miro Hrončok 2021-10-04 19:35:14 UTC 
I suggest just retiring it today to make things nice and consistent.
Comment 9 Endi Sukma Dewata 2021-10-04 19:39:57 UTC 
I wish I could, but we might not have resources to test and provide karma before the deadline.
Comment 10 Miro Hrončok 2021-10-04 19:51:06 UTC 
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?
Comment 11 Endi Sukma Dewata 2021-10-04 21:16:38 UTC 
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.
Comment 12 Miro Hrončok 2021-10-04 21:28:45 UTC 
Thanks!
Comment 13 Miro Hrončok 2022-01-14 23:27:55 UTC 
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!
Note You need to log in before you can comment on or make changes to this bug.