On 07/31/2017 03:49 PM, John Paul Adrian Glaubitz wrote:

So, I have obviously the problem that OBS is enabling the devel:languages:python repository for the build which it shouldn't. Is there a way to tell OBS which repositories it's allowed to use during build and which not? In the OBS webinterface go to the project -> Repositories and then you can edit the repositories and change the used package repository paths.

Sebastian -- python programming - mail server - photo - video - https://sebix.at cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers

On lundi, 31 juillet 2017 15.49:28 h CEST John Paul Adrian Glaubitz wrote:

Hi!

I am currently working on updating the Microsoft Azure SDK for Python for SLE12SP2. All of these Python packages use setuptools upstream which causes some problems on SLE12SP2 because they use a feature not present in the old version of setuptools in SLE12P2, namely the "~=" operator which is used to denote compatible versions in Python. To resolve this problem, I simply patched the setup.py to replace "~=" with ">" and made sure the proper version dependencies are noted in the spec file.

This worked all fine and without problems until I worked on a package (python-azure-sdk) that I branched from the devel:languages:python project. Although the package uses the aforementioned operator in setup.py, the package still builds fine in a SLE12SP2 environment without the necessary patch.

After digging some time, I noticed that the chroot for the package branched from devel:languages:python was using a current version of setuptools, namely version 36.2.2 while my other packages were using the setuptools version present in SLE12SP2 which is 1.10.x.

So, I have obviously the problem that OBS is enabling the devel:languages:python repository for the build which it shouldn't. Is there a way to tell OBS which repositories it's allowed to use during build and which not?

Or do I have to branch the package into a specific project to avoid the inclusion of these particular repositories?

Thanks, Adrian

osc branch create the branch repository with heritage of all attributes (Mean if you don't delete your branches, it will not get new configurations :-) You can use osc linkpac to only pick the package but not the repository meta attribute. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Jul 31 2017, John Paul Adrian Glaubitz wrote:

Or do I have to branch the package into a specific project to avoid the inclusion of these particular repositories?

If you branch a package to a new project then this project is set up to add the repositories from the project you branch from to the repository path. If the branched package is created in an existing project then the repository paths remain untouched. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Hi, Took a look at your project and it looks like you resolved the problem, anyway.... On 07/31/2017 09:49 AM, John Paul Adrian Glaubitz wrote:

Hi!

<snip>

So, I have obviously the problem that OBS is enabling the devel:languages:python

Which should make sense. If a package is branched from a project it should build against that project to make sure when it gets merged back the target project still builds.

repository for the build which it shouldn't. Is there a way to tell OBS which repositories it's allowed to use during build and which not?

Yes, that's where the Meta data comes into play, which in your project [1] has been adjusted to consider the SLE 12 repo as a source rather than the SLE 12 build target in d:l:p

Or do I have to branch the package into a specific project to avoid the inclusion of these particular repositories?

Nope, you have to adjust the meta data. Later, Robert [1] https://build.opensuse.org/project/show/home:glaubitz:branches:devel:languag... -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Architect LINUX Team Lead Public Cloud rjschwei@suse.com IRC: robjo