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?
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org