I was on +1 last week. Due to some ISP issues on Friday, my report is
delayed and there are a few loose ends in this report.
## hfst dep-wait on libfst-dev
This package needs libfst-dev (>= 1.7.9) from src:openfst, which is
not able to autosync from Debian because of Ubuntu delta. However,
this delta was just to fix the build with python3. The openfst in
Debian no longer needs python for the build, so we synced the Debian
version. One follow-on change was needed to avoid excessive memory
usage and FTBFS during openfst's dh_auto_test
(https://pad.lv/1984137).
Thanks to William for reviewing and sponsoring this patch.
## ghdl FTBFS with LLVM 14 (https://pad.lv/1983908)
The package explicitly adds a line for each LLVM version in it's
configure script, hence the history of existing patches to allow newer
LLVM versions. After fixing the build with LLVM 14.0, I hit FTBFS on
armhf (https://pad.lv/1984138). After trying a while to fix or work
around the single test, I opted to disable to tests on armhf and
opened an upstream bug (https://github.com/ghdl/ghdl/issues/2170).
Thanks to William for reviewing and sponsoring this patch.
## libxsmm FTBFS (https://pad.lv/1984111)
This FTBFS with an undefined reference to pthread_yield. Upstream
already has fixes for this, so I cherry-picked those.
I am still looking for a sponsor for this patch.
## node-grunt-timer FTBFS (https://pad.lv/1983866)
This fails because of a missing node-functional.js dependency. This
package was removed from Ubuntu because of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014605, i.e. it
never built from source in Debian or Ubuntu. Steve was happy to remove
node-grunt-timer from the archive.
## python-duniterpy breaks silkaj autopkgtest (https://pad.lv/1984122)
The immediate cause is the BlockUID type being changed to BlockID, but
the upstream commit that resolves this does not apply cleanly to
v0.9.0. The best resolution here is probably to wait for v0.10.0 to be
packaged in Debian unstable (currently in experimental).
## generate-ninja FTBFS (https://pad.lv/1984224)
The gn binary is DWARFv5, but dh_dwz is not fully compatible with
DWARFv5. Setting the -gdwarf-4 build flag forces DWARFv4 and makes
dh_dwz happy.
Thanks to William for reviewing and sponsoring this patch.
## libtree FTBFS on some arches (https://pad.lv/1984008)
The immediate cause of this is that one of the test cases
unconditionally compiles binaries with -m32 and -m64 flags, which do
not exist on all arches. Upstream has an open issue tracking this, and
due to the complexity it seems better to let it be sorted out there.
Opened an update-excuse bug with this info.
## bpftrace FTBFS (https://pad.lv/1985648)
The bpftrace-aotrt binary is built conditionally, but debian/rules
always attempts to strip it. This can be fixed by stripping the binary
only if the file exists. However, if my patch is applied this package
will still FTBFS on armhf and s390x due to libbpfcc-dev dep-wait.
I am still looking for a sponsor for this patch.
## dtfabric autopkgtest regression on s390x (https://pad.lv/1860568)
The failing test is not big-endian proof. I opened an upstream bug
(https://github.com/libyal/dtfabric/issues/29), and will propose
skipping the problematic test on big endian arches for now.
## deepin-album FTBFS with LTO enabled (https://pad.lv/1984124)
Disabling LTO fixes the build.
Thanks to William for reviewing and sponsoring this patch.
## faketime FTBFS (https://pad.lv/1984446)
This package had a test snippet that used a format specifier for
time_t that was not portable to 32 bit arches. I fixed the print
statement and the patch was merged upstream. The Debian maintainer
cherry-picked my upstream patch, and the new Debian version has since
autosynced to Ubuntu.
Thanks,
Nick
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
