Your message dated Tue, 7 Jan 2020 22:02:52 +0000
with message-id <[email protected]>
and subject line re: freedv ftbfs with libcodec2-0.9
has caused the Debian Bug report #947620,
regarding freedv ftbfs with libcodec2-0.9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
947620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947620
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: freedv
Version: 1.3.1-4
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye
Dear maintainer,
Your package is part of the libcodec2-0.9 transition. I tried to binNMU
your package but it fails to build from source. Please have a look.
Paul
https://buildd.debian.org/status/package.php?p=freedv
Tail of log for freedv on amd64:
make[3]: *** [src/CMakeFiles/freedv.dir/build.make:79:
src/CMakeFiles/freedv.dir/dlg_filter.cpp.o] Error 1
In file included from /<<PKGBUILDDIR>>/src/dlg_ptt.h:25,
from /<<PKGBUILDDIR>>/src/dlg_ptt.cpp:22:
/<<PKGBUILDDIR>>/src/fdmdv2_main.h:74:10: fatal error: codec2.h: No such
file or directory
74 | #include "codec2.h"
| ^~~~~~~~~~
compilation terminated.
make[3]: *** [src/CMakeFiles/freedv.dir/build.make:105:
src/CMakeFiles/freedv.dir/dlg_ptt.cpp.o] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/Build'
make[2]: *** [CMakeFiles/Makefile2:98: src/CMakeFiles/freedv.dir/all]
Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/Build'
make[1]: *** [Makefile:133: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/Build'
dh_auto_build: cd Build && make -j4 returned exit code 2
make: *** [debian/rules:6: build-arch] Error 255
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
version: 1.4-1
This issue seems to have been fixed in version 1.4-1 (1.4-1 failed to build on
most architectures for an unrelated reason, 1.4-1.1 successfully built on all
release architectures).
--- End Message ---
