Re: Bug#1108298: FTBFS with symbol mismatch
On Wed, Jul 02, 2025 at 06:33:04PM +0200, Sven Mueller wrote:
> I shall probably add that the rebuild happened in testing, not unstable.
>
> However, I reproduced it now without the +b1 of a binNMU in testing,
> so this isn't purely because of the binNMU, it also happens in plain
> Trixie.
I've just tried to repro this, and can report that building gensio
in both unstable and testing shows the same symbol file issues, but
the build continues for me. (On aarch64.)
The diff is:
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below
dpkg-gensymbols: warning: debian/libgensio6t64/DEBIAN/symbols doesn't match completely debian/libgensio6t64.symbols
--- debian/libgensio6t64.symbols (libgensio6t64_2.8.13-7_arm64)
+++ dpkg-gensymbolsLuugWc 2025-07-02 16:40:31.199554297 +0000
@@ -456,7 +456,7 @@
_ZNSt12_Vector_baseIhSaIhEED1Ev@Base 2.8.6
_ZNSt12_Vector_baseIhSaIhEED2Ev@Base 2.8.6
_ZNSt6vectorIhSaIhEE17_M_default_appendEj@Base 2.8.13-7
-#MISSING: 2.8.13-7# _ZNSt6vectorIhSaIhEE17_M_default_appendEm@Base 2.8.13
+ _ZNSt6vectorIhSaIhEE17_M_default_appendEm@Base 2.8.13-7
_ZTIN7gensios12gensio_errorE@Base 2.8.6
_ZTIN7gensios13Serial_GensioE@Base 2.8.6
_ZTIN7gensios14Serial_Op_DoneE@Base 2.8.6
@@ -816,7 +816,7 @@
_ZNK7gensios4Addr13to_string_allB5cxx11Ev@Base 2.8.6
_ZNK7gensios4Addr9to_stringB5cxx11Ev@Base 2.8.6
_ZNSt6vectorIhSaIhEE17_M_default_appendEj@Base 2.8.13-7
-#MISSING: 2.8.13-7# _ZNSt6vectorIhSaIhEE17_M_default_appendEm@Base 2.8.13
+ _ZNSt6vectorIhSaIhEE17_M_default_appendEm@Base 2.8.13-7
_ZTIN7gensios12gensio_errorE@Base 2.8.6
_ZTIN7gensios4AddrE@Base 2.8.6
_ZTIN7gensios8Os_FuncsE@Base 2.8.6
There's only one r-dep in Debian, ser2net. Maybe this is fine for ser2net or
maybe not. CC'ing release for awareness.
Chris
Reply to: