Hello all, I'm running a private OBS 2.7 instance. For one of my projects A I have this in my meta configuration: --- snip --- <repository name="openSUSE_Leap_42.2"> [...] <path project="openSUSE.org:Leap:42.2:Update" repository="standard"/> <path project="openSUSE.org:Leap:42.2" repository="standard"/> <arch>x86_64</arch> </repository> --- snap --- A package B in project A has one BuildRequires, which in turn pulls in another package C (via Requires). Now C has a requires for a standard Leap 42.2 package D but with a version constraint. The required version of D is present in the Leap 42.2 repo. The version in the Leap 42.2 update repo is too high (from /srv/obs/log/scheduler_x86_64.log): --- snip --- 2017-05-10 20:28:59: looking at low prio A/openSUSE_Leap_42.2 (0/0/0/0/42) - A/openSUSE_Leap_42.2 scanning repo A/openSUSE_Leap_42.2... sorting 1 packages - B (spec) unresolvable: nothing provides D < 2.1.3 needed by C --- snap --- If I change the above meta configuration to --- snip --- <repository name="openSUSE_Leap_42.2"> [...] <path project="openSUSE.org:Leap:42.2" repository="standard"/> <arch>x86_64</arch> </repository> --- snap --- package B builds fine. But I'd like to use the RPMs from the update repository. How would I have to configure that? Or how can I track down this dependency issue? Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de Tel. +49 - 40 - 244 2407 - 14 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 Wir sind wieder auf dem BSI IT-Sicherheitskongress 16.-18. Mai 2017 – Bonn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org