[Freeipa-devel] Broken pki 10.3.3-1 packages in freeipa-master COPR

[Lukas Slebodnik]

On (28/06/16 14:50), Alexander Bokovoy wrote:
>On Tue, 28 Jun 2016, Milan Kubík wrote:
>> > > It's real packaging bug and have to be fixed.
>> > Right.
>> > 
>> > > The same files are owned by two packages even though one depens
>> > > on other.
>> > > Milan, please fiel a fedora bug.
>> > > 
>> > > [root at 5946ca9bf02b /]# rpm -q pki-server pki-base
>> > > pki-server-10.3.3-1.fc24.noarch
>> > > pki-base-10.3.3-1.fc24.noarch
>> > > 
>> > > [root at 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 at 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
>> > This is not a real bug:
>> > https://fedoraproject.org/wiki/Packaging:Guidelines#File_and_Directory_Ownership
>> > 
>> > ------------------------------------------------------------------------
>> > In most cases, it should not be necessary for multiple packages to
>> > contain identical copies of the same file. However, if it is necessary,
>> > multiple packages may contain identical copies of the same file, as long
>> > as the following requirements are met:
>> > 
>> >   The packages sharing ownership of the identical files are built from
>> > a single SRPM.
>> > OR
>> > 
>> >   The packages sharing ownership of the identical files are not in a
>> > dependency chain (e.g. if package A requires package B, they should not
>> > both contain identical files, either A or B must own the common files,
>> > but not both.) --------------------------------------------------------------------------
>> > 
>> > The bug here is that they come from different repositories and thus from
>> > the dnf/yum point of view are built from different source packages.
>> > 
>> > > 
>> > > [root at 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
>> > > 
>> > > LS
>> > 
>> The bug is exactly the violation of the second clause. pki-server
>> requires pki-base while both own the files.
>Right -- what I wanted to point is that the conflict you get from dnf is
>not due to violating this policy, it is due to the files ownership
>coming from subpackages built from different source packages. Package
>policy violations are not always (not in this case) enforced by
>dnf/yum/rpm.
If there was not a violation of packaging guidelines then it would not be a
problem if pki-base is from one repository and pki-server from other.

It has to work because they are built from the same source.

LS