On 06/28/2016 01:20 PM, Alexander Bokovoy wrote:
On Tue, 28 Jun 2016, Lukas Slebodnik wrote:
On (28/06/16 10:57), Alexander Bokovoy wrote:
On Tue, 28 Jun 2016, Petr Vobornik wrote:
On 06/27/2016 08:11 PM, Lukas Slebodnik wrote:
> On (27/06/16 17:55), Milan Kubík wrote:
> > Hi all,
> >
> > the pki packages that are currently in the COPR repo [1] are broken. There is
> > a conflict between pki-server and pki-base:
> >
> > Error: Transaction check error:
> > file /usr/lib/python2.7/site-packages/pki/server/deployment/pkiparser.pyc from install of pki-server-10.3.3-1.fc24.noarch conflicts with file from package pki-base-10.3.3-1.fc24.noarch > > file /usr/lib/python2.7/site-packages/pki/server/deployment/pkiparser.pyo from install of pki-server-10.3.3-1.fc24.noarch conflicts with file from package pki-base-10.3.3-1.fc24.noarch
> >
> > [1]: https://copr.fedorainfracloud.org/coprs/g/freeipa/freeipa-master/
> >
> I can see the same with pki-core in fedora 24 updates-testing.
> File a fedora bug.
>
> LS
>

Right, even though I can't reproduce, the package in freeipa-master copr should be the same as the one in updates testing. It was built from the
same srpm:
https://kojipkgs.fedoraproject.org//packages/pki-core/10.3.3/1.fc24/src/pki-core-10.3.3-1.fc24.src.rpm
One particular issue could be that you have pki-server installed from
one source and pki-base considered from a different one. For yum and dnf
there is a difference where the package comes from and all subpackages
of the same source package should be coming from the same repository to
avoid conflicts like this because after install the package keeps its
source repo mark.
It is not a "particular issue".
It is a particular issue -- there may be more issues with
multi-repository package delivery but this particular bug of dnf/yum not
allowing upgrades of packages with the same name delivered via different
repositories stands out.

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@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
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@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.

--
Milan Kubik

--
Manage your subscription for the Freeipa-devel mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-devel
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code

Reply via email to