On 2/20/19 1:55 PM, Steve Langasek wrote: > 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 problem is reproducible-builds. Did you see the log? The tests have a random problem. > > 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. I copy and paste from Makefile the 'find | head'. Please, see this CI log: https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pyparted/1918396/log.gz But it is true that it tries to use _ped.so from Python 2. The random behavior can be from find. I put an find for each version. And got one more assertGreater error. ====================================================================== FAIL: runTest (tests.test__ped_ped.DeviceGetNextTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/pyparted-3.11.2/tests/test__ped_ped.py", line 210, in runTest self.assertGreater(len(lst), 0) AssertionError: 0 not greater than 0 ---------------------------------------------------------------------- Only remove the override does not work. I tried now. I also tried a build for one Python version with an override with a find for it only. ./.pybuild/cpython2_2.7_parted/ AssertionError version 3.11.2-3 has only the patch you sent. I did not work for everybody. You can check upstream Makefile. Regards, Herbert
