Hi

BuildRequires: A >= 1.2 works without any problem but I do require A = 1.2.

We support several versions of some tools and have this requirement.

Sébastien

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@unil.ch mailto:sebastien.moretti@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@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys

-- Sébastien Moretti

Both A-1.2 and A-1.5 are available in my build repos.

If A-1.2 was not in build repos, the error message would be different I guess.

Sébastien

Do you have A-1.2 available in your build repos? Usually that error arises when you do not have the specified version available. You may have to build A-1.2 first.

On Tue, Oct 27, 2015 at 10:52 AM, Sebastien Moretti

Hi

BuildRequires:   A >= 1.2  works without any problem
but I do require A = 1.2.


We support several versions of some tools and have this requirement.

Sébastien

    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@unil.ch <mailto:sebastien.moretti@unil.ch>
    <mailto:sebastien.moretti@unil.ch
    <mailto:sebastien.moretti@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@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys

-- Sébastien Moretti

...

Both A-1.2 and A-1.5 are available in my build repos.

If A-1.2 was not in build repos, the error message would be different I guess.

This is not a Koji issue.

If you look at your build log, you will see that Koji runs some commands in a mock chroot, one of which tries to install the dependencies.

It is going to be something like "yum-builddep" or "dnf builddep", depending on which depsolver you are using.

Yum/DNF is responsible for installing the dependencies inside the buildroot, so you need to figure out what works and what doesn't with Yum/DNF.

We use yum-builddep --skip-broken (skip packages with depsolving problems) looks too dangerous, and will certainly skip packages in cascade.

Is --obsoletes (enable obsoletes processing during updates) the right option - if there is one - to enable use of older package versions? The help message is a bit ambiguous.

-- Mathieu

-- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys

-- Sébastien Moretti

On Wednesday, October 28, 2015 02:51:45 PM Sebastien Moretti 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.

koji repos can contain only single build of a package, that's by design

Dan

But if I try yum info A it will return A-1.5

If I try yum info A-1.2 it will return A-1.2

So both should be in the repos, right?

no koji only has the last tagged version of a package in its repos. if you need multiple versions of something you will need to manage that in the packaging. having a12 a15 etc packages

Dennis

Dennis