On Wed, Mar 13, 2019 at 12:49 PM Florian Weimer <fweimer(a)redhat.com> wrote:
* Mikolaj Izdebski:
>> As far as I understand it, under the Koji model, one of the tags wins,
>> and which one determines whether you get the Python 2 subpackage or the
>> Python 3 subpackage. You cannot get both. You will need two or more
>> buildroots for that.
>
> That used to be the case, but for some time Koji supports
> "repo_include_all" option [1] that has the exact effect you describe -
> when set it makes build repos include all tagged RPMs, even if they
> come from different SRPMs that happen to have the same name.
>
> [1]
https://pagure.io/koji/issue/588
*Very* interesting.
Could this be used to address this issue, too?
<
https://pagure.io/koji/issue/273>
(Including select i686 packages in the x86_64 buildroot.)
No, not by itself. repo_include_all won't lead to inclusion of RPMs
with non-matching arches.
--
Mikolaj Izdebski