Bug#1008398: libgee-0.8: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below

[Lucas Nussbaum]

Source: libgee-0.8
Version: 0.20.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> find debian -name '*.la' -print -delete
> debian/tmp/usr/lib/x86_64-linux-gnu/libgee-0.8.la
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_install
>    dh_installdocs
>    dh_installchangelogs
>    dh_gnome
>    dh_perl
>    dh_link
>    dh_strip_nondeterminism
>    dh_compress
>    dh_fixperms
>    dh_missing
>    dh_dwz -a
>    dh_strip -a
>    dh_makeshlibs -a
> dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
> dpkg-gensymbols: warning: debian/libgee-0.8-2/DEBIAN/symbols doesn't match completely debian/libgee-0.8-2.symbols
> --- debian/libgee-0.8-2.symbols (libgee-0.8-2_0.20.5-1_amd64)
> +++ dpkg-gensymbolsG6A0XB	2022-03-26 19:39:59.278268649 +0000
> @@ -170,6 +170,7 @@
>   gee_functions_get_compare_func_for at Base 0.8.3
>   gee_functions_get_equal_func_for at Base 0.8.3
>   gee_functions_get_hash_func_for at Base 0.8.3
> + gee_future_error_get_type at Base 0.20.5-1
>   gee_future_error_quark at Base 0.14.0
>   gee_future_flat_map at Base 0.14.0
>   gee_future_get_exception at Base 0.14.0
> dh_makeshlibs: error: failing due to earlier errors
> make: *** [debian/rules:8: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/libgee-0.8_0.20.5-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.