FTBFS: zfp has test failures on Lunar (most architectures)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
h5z-zfp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
numcodecs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
zfp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
zfp 1.0.0-5 currently fails to build on Ubuntu Lunar on most architectures.
For some reason the package has built successfully on Debian Sid, and I have not been able to reproduce the issue there myself either. So whatever is causing it seems to be Ubuntu specific.
The error message is:
[100%] Linking C shared module ../bin/
cd /<<PKGBUILDDIR>
/usr/bin/cc -fPIC -g -O2 -ffile-
make[3]: Leaving directory '/<<PKGBUILDDIR
[100%] Built target testzfp
make[3]: Leaving directory '/<<PKGBUILDDIR
[100%] Built target zfpy
make[2]: Leaving directory '/<<PKGBUILDDIR
make[1]: *** [Makefile:149: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR
dh_auto_build: error: cd .pybuild/
E: pybuild pybuild:379: build: plugin cmake failed with: exit code=25: dh_auto_build --buildsystem=cmake --builddirector
dh_auto_build: error: pybuild --build -i python{version} -p "3.11 3.10" returned exit code 13
make: *** [debian/rules:20: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
(taken from the amd64 build log https:/
At first I thought the linking failed, but upon further inspection it looks like the actual problem occur right after the linking has finished...
Changed in zfp (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in numcodecs (Ubuntu): | |
status: | Fix Committed → Fix Released |
This in turn cause dependency wait failures for numcodecs and h5z-zfp which are waiting for python3-zfpy and libzfp-dev, respectively.