Koji and spec file with not the most up-to-date version of a package

Anthony Boccia anthony.atomictech at gmail.com
Tue Oct 27 14:47:11 UTC 2015


Hi Sébastien,

Give this a try,

BuildRequires:   A >= 1.2

This will pull in whatever version of A is available so long as it is not
less than 1.2.

On Tue, Oct 27, 2015 at 10:36 AM, Sebastien Moretti <
sebastien.moretti at unil.ch> wrote:

> Hi
>
> We use Koji and have an issue with some packages (let say B) requiring a
> particular version of another package (A = 1.2 ) which has a more
> up-to-date version (A = 1.2 & A = 1.5).
> e.g.
> Name:            B
> BuildRequires:   A = 1.2
>
> In that case, Koji builds fail:
> DEBUG util.py:388:  Error: Package: B-3.4.2-4.el6.x86_64 (build)
> DEBUG util.py:388:             Requires: A = 1.2
> DEBUG util.py:388:             Available: A = 1.5-1.x86_64 (build)
> DEBUG util.py:388:                 A = 1.5
>
>
>
> Is there a way to avoid that behavior?
> When no version is specified, use the most up-to-date, when a particular
> version is required, use that one.
>
>
> Regards
>
>
> Mock Version: 1.2.7
>
> --
> Sébastien Moretti
>
> --
> buildsys mailing list
> buildsys at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/buildsys
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/buildsys/attachments/20151027/1dc9f254/attachment.html>


More information about the buildsys mailing list