Source: cubeb
Version: 0.0~git20220110.9edd150+ds-1
severity: important
tags: patch
Hello, looks like in Ubuntu cubeb is FTBFS due to an extra symbol now removed.
I think this will become an issue in Debian too once new gcc defaults.
The best fix to me is to just mark the c++ vtable symbol as optional
--- debian/libcubeb0.symbols
(libcubeb0_0.0~git20220110.9edd150+ds-1build1_amd64)
+++ dpkg-gensymbolsPCFvbW 2022-03-07 11:13:45.893845307 +0000
@@ -26,4 +26,4 @@
cubeb_strings_destroy@Base 0.0~git20210801.6ce9596
cubeb_strings_init@Base 0.0~git20210801.6ce9596
cubeb_strings_intern@Base 0.0~git20210801.6ce9596
- (c++)"vtable for
std::thread::_State_impl<std::thread::_Invoker<std::tuple<cubeb_async_logger::run()::{lambda()#1}>
> >@Base" 0.0~git20210801.6ce9596
+#MISSING: 0.0~git20220110.9edd150+ds-1build1# (c++)"vtable for
std::thread::_State_impl<std::thread::_Invoker<std::tuple<cubeb_async_logger::run()::{lambda()#1}>
> >@Base" 0.0~git20210801.6ce9596
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
see e.g.
https://launchpad.net/ubuntu/+source/cubeb/0.0~git20220110.9edd150+ds-1ubuntu1
and this patch:
--- cubeb-0.0~git20220110.9edd150+ds/debian/libcubeb0.symbols 2022-01-12
18:16:20.000000000 +0000
+++ cubeb-0.0~git20220110.9edd150+ds/debian/libcubeb0.symbols 2022-03-07
11:14:51.000000000 +0000
@@ -1,6 +1,6 @@
libcubeb.so.0 libcubeb0 #MINVER#
* Build-Depends-Package: libcubeb-dev
- (c++)"vtable for
std::thread::_State_impl<std::thread::_Invoker<std::tuple<cubeb_async_logger::run()::{lambda()#1}>
> >@Base" 0.0~git20210801.6ce9596
+ (c++|optional)"vtable for
std::thread::_State_impl<std::thread::_Invoker<std::tuple<cubeb_async_logger::run()::{lambda()#1}>
> >@Base" 0.0~git20210801.6ce9596
cubeb_destroy@Base 0.0~git20210801.6ce9596
cubeb_device_collection_destroy@Base 0.0~git20210801.6ce9596
cubeb_enumerate_devices@Base 0.0~git20210801.6ce9596
