Hi, Am 14.06.21 um 20:49 schrieb Michael Ströder:
HI!
Why are some Python packages failing to build on Leap? Is special project config needed? I tried to copy the config from devel:languages:python in the web UI but this does not work.
Example:
https://build.opensuse.org/package/show/home:stroeder:iam/python-pyasn1
[ 37s] find: '//home/abuild/rpmbuild/BUILDROOT/python-pyasn1-0.4.8-lp153.98.1.x86_64/usr/share/polkit-1/actions/': No such file or directory [ 37s] find: '//home/abuild/rpmbuild/BUILDROOT/python-pyasn1-0.4.8-lp153.98.1.x86_64/usr/share/mime/': No such file or directory [ 37s] find: '//home/abuild/rpmbuild/BUILDROOT/python-pyasn1-0.4.8-lp153.98.1.x86_64/usr/share/metainfo/': No such file or directory [ 37s] find: '//home/abuild/rpmbuild/BUILDROOT/python-pyasn1-0.4.8-lp153.98.1.x86_64/usr/share/appdata/': No such file or directory
That's not the failure message. The error is a few lines below that: [ 37s] + %pyunittest discover -v [ 37s] /var/tmp/rpm-tmp.1RJB1Y: line 28: fg: no job control [ 37s] error: Bad exit status from /var/tmp/rpm-tmp.1RJB1Y (%check) Plain Leap 15.3 lacks the pyunittest macro from an up to date python-rpm-macros: [ 12s] [4/175] cumulate python-rpm-macros-20200207.5feb6c1-3.11.1 devel:languages:python uses d:l:p:backports for its build targets, which is not part of the released Leap 15.3 distribution. If you must update a package in SLE or Leap which must go into the distribution, replace the %pyunittest macro with %{python_expand # export PYTHONPATH=%{builddir}%{$python_sitelib} $python -m unittest discover -v } The above retains compatibility with Tumbleweed. If you don't need that, in most cases you can also just do python3 -m unittest discover -v - Ben