Package: pyparted
Version: 3.11.2-6
Followup-For: Bug #922081
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
I think the remaining issue is entirely a bug in the debian/rules
override_dh_auto_test rule. When I dropped this override entirely in
Ubuntu, the package builds fine.
The bug is that this override tries to use 'find | head', and expects that
the result returned is the right directory for use when running the test
suite under python3. But the order in which results are returned from find
is undefined, and likely filesystem-dependent; so on the builders for some
architectures, it returns the python2.7 build instead of the python3 build.
And furthermore, if this override DID work, it would be skipping testing for
the python2 module and only testing the python3 module.
So by deleting the override entirely, the test suite passes for me and does
the right thing of testing all the binaries.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pyparted-3.11.2/debian/rules pyparted-3.11.2/debian/rules
--- pyparted-3.11.2/debian/rules 2019-02-14 13:49:15.000000000 +0100
+++ pyparted-3.11.2/debian/rules 2019-02-18 06:57:48.000000000 +0100
@@ -13,12 +13,6 @@
rm -rf debian/python-parted-dbg/usr/lib/python2.7/dist-packages/parted/
rm -rf debian/python3-parted-dbg/usr/lib/python3*/dist-packages/parted/
-override_dh_auto_test:
-#ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
-# PYTHONPATH=$$(find $$(pwd) -name "*.so" | head -n 1 | xargs
dirname):src/parted:src \
-# python3 -m unittest discover -v
-#endif
-
override_dh_clean:
dh_clean
rm -fr debian/python3-parted-dbg
