[opensuse-buildservice] Re: Handling BuildRequires: Package = 1.2.3

For build.opensuse.org, in the case of dependent items which have API changes (ie, it will break), those packages are put in different projects? That seems like a large increase in administrative overhead if you are using OBS as your main source of locally built software for an organization. Ie, now I have to keep track of all of the repositories that need to be put on a machine in order to be able to satisfy version requirements. Where would one go about modifying the code to change this behavior? -Matt On Tue, 2013-11-19 at 10:04 +0100, Andreas Schwab wrote:

Matthew Drobnak writes:

...

Why does OBS behave like this for BuildRequires? Why does it stop on first match?

There is only one match. The repository where the packages are fetched from (see osc ls -b <project>) doesn't distinguish between different versions of the same package, it will carry the version that was built last. If you want to use different versions of the same package you need to either create separate projects or build in separate repositories for each version.

Andreas.

N�����r��y隊Z)z{.���Wlz��qﮞ˛���m�)z{.��+�:�{Zr�az�'z��j)h���Ǜ�)]���Ǿ� ޮ�^�ˬz��