Public bug reported:
In python3-setuptools/73.0.1-1, the usage of setup.py to run tests is
not supported anymore (it has been deprecated for a while).
protobuf/3.21.12-9 still uses setup.py to run tests (snippet from
debian/rules):
set -e; \
export LD_LIBRARY_PATH=$(CURDIR)/src/.libs; \
cd python3 && for PYTHON in $(shell py3versions -r); do \
$$PYTHON setup.py test --cpp_implementation; \
done
protobuf is not FTBFSing and blocking the ruby 3.3 transition. I tried
to migrate this to use pybuild (as suggested on IRC by tumbleweed) but
it is not straightforward, actually, it is complex because of the custom
system implemented in protobuf to run the tests.
To unblock the transition, the python tests will be disabled for now,
and in the future they should be enabled again.
FWIW upstream already re-wrote the whole build/test system, not easy to
cherry-pick anything from there. The best option is to move to a newer
upstream version.
** Affects: protobuf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078265
Title:
python3-setuptools does not support setup.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/2078265/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
