Two of the pki packages own the same files
[root@5946ca9bf02b /]# rpm -q pki-server pki-base pki-server-10.3.3-1.fc24.noarch pki-base-10.3.3-1.fc24.noarch [root@5946ca9bf02b /]# rpm -ql pki-base | grep pkiparser.py /usr/lib/python2.7/site-packages/pki/server/deployment/pkiparser.py /usr/lib/python2.7/site-packages/pki/server/deployment/pkiparser.pyc /usr/lib/python2.7/site-packages/pki/server/deployment/pkiparser.pyo [root@5946ca9bf02b /]# rpm -ql pki-server | grep pkiparser.py /usr/lib/python2.7/site-packages/pki/server/deployment/pkiparser.py /usr/lib/python2.7/site-packages/pki/server/deployment/pkiparser.pyc /usr/lib/python2.7/site-packages/pki/server/deployment/pkiparser.pyo [root@5946ca9bf02b /]# rpm -q --requires pki-server | grep pki pki-base = 10.3.3-1.fc24 pki-base-java = 10.3.3-1.fc24 pki-tools = 10.3.3-1.fc24
I verified this on a recent build.
I suspect that there is stuff in these files that are required by clients?
While it makes sense that since 'pki-server' requires 'pki-base', and 'pki-base' is required by both clients and servers, these files could probably be removed from 'pki-server'.
The strange part about doing this, however, is that:
Per PKI Bug Council of 07/14/2016: 10.3.5
Sorry, this was my fault. I didn't exclude the server files when I changed the spec file. The old spec file simply included pki/*.py. With Python 3 support and the new pki.cli package, the old rule didn't work any more.
$ git diff diff --git a/specs/pki-core.spec b/specs/pki-core.spec index 7c54974..9faaf14 100644 --- a/specs/pki-core.spec +++ b/specs/pki-core.spec @@ -991,6 +991,7 @@ systemctl daemon-reload %{_datadir}/pki/key/templates %dir %{_sysconfdir}/pki %config(noreplace) %{_sysconfdir}/pki/pki.conf +%exclude %{python2_sitelib}/pki/server %{python2_sitelib}/pki %dir %{_localstatedir}/log/pki %{_sbindir}/pki-upgrade @@ -1011,6 +1012,7 @@ systemctl daemon-reload %files -n pki-base-python3 %defattr(-,root,root,-) %doc base/common/LICENSE +%exclude %{python3_sitelib}/pki/server %{python3_sitelib}/pki %endif # with_python3 %endif
commit a8f34a868258a2f5ccdfa57b33b12e5d3e019880 Author: Matthew Harmsen mharmsen@redhat.com Date: Thu Jul 14 14:37:55 2016 -0600
Fix conflict in file ownership in pki-base and pki-server - PKI TRAC Ticket #2402 - Conflict in file ownership in pki-base and pki-server (cheimes)
Metadata Update from @mkubik: - Issue assigned to cheimes - Issue set to the milestone: 10.3.5
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2522
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.