Current libzstd fails tests when using dpkg-buildpackage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libzstd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When trying to rebuild the current libzstd package on mantic, "dpkg-buildpackage -us -uc -ui -F" fails to pass the tests without error.
Output (excerpt):
[...]
d=6
steps=40
split=100
Save dictionary of size 112640 into file dictionary
make[3]: Leaving directory '/build/
make[2]: *** [Makefile:85: test] Error 2
make[2]: Leaving directory '/build/
rm -fr -- /tmp/user/
dh_auto_test: error: make -j4 test returned exit code 2
make[1]: *** [debian/rules:71: build] Error 255
make[1]: Leaving directory '/build/
make: *** [debian/rules:34: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
To reproduce:
# arch
x86_64
# debootstrap --arch=amd64 mantic ubuntu-mantic-amd64
[...]
# schroot -c ubuntu-mantic-amd64 -u root -d /build/packages -s /bin/bash
[...]
(ubuntu-
deb http://
deb http://
deb http://
deb http://
deb http://
deb-src http://
deb-src http://
deb-src http://
deb-src http://
deb-src http://
(ubuntu-
(ubuntu-
(ubuntu-
(ubuntu-
(ubuntu-
(ubuntu-
(ubuntu-
(ubuntu-
gcc (Ubuntu 13.1.0-8ubuntu1) 13.1.0
(ubuntu-
[...] (see above)
TBH, I find it rather *unnerving* that the tests fail on Mantic given that this package/compressor is used for e.g. compressing all sorts of archives/backups. (Originally, I tried to rebuild this on Focal and Jammy on x86_64/
Shouldn't "dpkg-buildpackage" /always/ work (including passing the enclosed tests) when you rebuild an
officially released package from the main repository in a clean environment when all dependencies are in place?
Of course, I see that (a) the two weeks old build log (from https:/
(The previous package version 1.5.4+dfsg2-5 builds flawlessly in all aforementioned environments.)
description: | updated |