Overview

Request 561345 accepted

- Fix build failure when using more than one python version:
swig wrapper files were only generated the first time and
and then kept for subsequent builds.

=> Note that the replacement package will be called python3-pivy!

Loading...

Atri Bhattacharya's avatar

Would it be useful to add Provides: python-pivy for the python3-pivy flavour of the package, to help with the transition from python- to python3-?


Lorenz Hüdepohl's avatar

That would be nice, but I am not sure how to do that with all the RPM macro magic going on there. Do you have an example on how to add a Provides: tag to just one of the two python-version-packages?


Atri Bhattacharya's avatar

@lorenz, According to [1], possibly this

%if %{have_python3}
Provides: python-pivy
%endif

[1] https://github.com/openSUSE/python-rpm-macros


Lorenz Hüdepohl's avatar

It does not like it when I do that:

[ 687s] ERROR: /.build.packages/RPMS/x86_64/python2-pivy-0.6.2-0.x86_64.rpm [ 687s] has an unversioned self-provide. [ 687s] Remove it, self-provides are done automatically. [ 687s] If you don't understand this error message, contact dmueller@suse.de [ 687s] [ 687s] [ 687s] ERROR: /.build.packages/RPMS/x86_64/python3-pivy-0.6.2-0.x86_64.rpm [ 687s] has an unversioned self-provide. [ 687s] Remove it, self-provides are done automatically. [ 687s] If you don't understand this error message, contact dmueller@suse.de


Lorenz Hüdepohl's avatar

No idea how to properly format comments, there seems to be no (easily found) documentation for this...


Request History
Lorenz Hüdepohl's avatar

lorenz created request

- Fix build failure when using more than one python version:
swig wrapper files were only generated the first time and
and then kept for subsequent builds.

=> Note that the replacement package will be called python3-pivy!


Atri Bhattacharya's avatar

badshah400 accepted request

OK, seems like python3- provides the python- package (if I am understanding this right).

openSUSE Build Service is sponsored by