On Wed, 28 Oct 2015 19:16:35 +0100
Till Maas <opensource(a)till.name> wrote:
On Wed, Oct 28, 2015 at 10:06:53AM -0600, Kevin Fenzi wrote:
> koji operates on package names. It will only get rpms from a
> package in one place, it won't mix them at all.
>
> So, if RHEL has python-foo and EPEL creates a package named
> python-foo, it will cause koji to completely and utterly ignore the
> RHEL python-foo and all rpms it makes.
In which case does it not mix packages? It is allowed for limited arch
packages to use the same package name as RHEL:
https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
Koji doesn't mix those.
When thats done the entire package is taken from EPEL.
So, if you buildrequire foo and it's in both epel and rhel it will use
the epel version. koji will not use the rhel version for anything at
all.
The reason that policy has:
"Change the release of the package to have a leading 0. EXAMPLE: RHEL
has foobar-1.0-1, you change it to foobar-1.0-0.1 for EPEL."
Is not for koji, but for end users. That makes the EPEL version lower
E-N-V-R than the rhel one for arches that rhel ships it, so people get
the rhel version.
kevin