Package: src:fssync
Version: 1.6-1
Severity: important
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
--------------------------------------------------------------------------------
[...]
debian/rules build-indep
dh build-indep
dh_testdir -i
dh_update_autotools_config -i
dh_autoreconf -i
dh_auto_configure -i
dh_auto_build -i
make -j1
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rst2man README.rst fssync.1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test -i
make -j1 test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
./test
.missing b'b/c' on destination side
missing b'b' on destination side
... create new inode for b'a'
b'a/c': missing
F
======================================================================
FAIL: test2 (__main__.Test)
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test", line 371, in test2
self.assertListEqual([b'a', b'a/c'], list(self.fssync.check(b'')))
AssertionError: Lists differ: [b'a', b'a/c'] != [b'a/c']
First differing element 0:
b'a'
b'a/c'
First list contains 1 additional elements.
First extra element 1:
b'a/c'
- [b'a', b'a/c']
+ [b'a/c']
----------------------------------------------------------------------
Ran 2 tests in 0.382s
FAILED (failures=1)
Makefile:21: recipe for target 'test' failed
make[1]: *** [test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:17: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------
This is just how the build ends, not necessarily the relevant part.
I've put several build logs here:
https://people.debian.org/~sanvila/build-logs/fssync/
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the page for this package.
The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough times (as the failure happens randomly).
Thanks.
