On Fri, 2017-07-07 at 17:03 +0200, jan matejek wrote:
On 5.7.2017 12:31, Scott Bahling wrote:
What was the outcome of this? Is there something
we can do within the
Backports projects to fix the issue? Currently the multi version build
is blocking us from submitting packages that require the python3
packages, but we conflict with the python2 versions in SLE.
i wrote a proof-of-concept patch for python-rpm-macros that allows building only python3
blacklisted packages from SLE, without modifying the packages in question. See it at 
Cool! We could add this to the Backports projects. We currently have a
bot that updates the Backports rpmlint blacklist as new packages are
added to SLE 12. We could piggy back off that to update the blacklist in
the python-rpm-macros package.
However, there is still a problem: there are conflicts
with the src.rpm, because, for instance,
python-six.src.rpm already exists in SLE.
I don't have a very good idea what to do about this. Is it possible to somehow
change name of the
src.rpm package? If not, you can fork the package under a different name, but it's
going to be a
fork, so at that point you can modify the spec in any case.
Alternately, could the multibuild magic somehow fix this?
Maybe we can adjust the checks in the Backports projects to ignore src
packages. I need to discuss that idea with others to identify any risks
of doing so. I gut feeling is that we can do it.