Bug#964679: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below

[Lucas Nussbaum]

Source: gtk+3.0
Version: 3.24.20-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_makeshlibs -plibgtk-3-0 --add-udeb=libgtk-3-0-udeb -Xusr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 -- -c4
> dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
> dpkg-gensymbols: warning: debian/libgtk-3-0/DEBIAN/symbols doesn't match completely debian/libgtk-3-0.symbols
> --- debian/libgtk-3-0.symbols (libgtk-3-0_3.24.20-1_amd64)
> +++ dpkg-gensymbolseXFnOd	2020-07-09 00:50:15.027590197 +0000
> @@ -1,5 +1,8 @@
>  libgdk-3.so.0 libgtk-3-0 #MINVER#
>  * Build-Depends-Package: libgtk-3-dev
> + _gdk_get_resource at Base 3.24.20-1
> + _gdk_register_resource at Base 3.24.20-1
> + _gdk_unregister_resource at Base 3.24.20-1
>   gdk__private__ at Base 3.16.2
>   gdk_add_option_entries_libgtk_only at Base 3.0.0
>   gdk_anchor_hints_get_type at Base 3.21.5
> @@ -758,6 +761,9 @@
>   gdk_x11_xatom_to_atom at Base 3.0.0
>   gdk_x11_xatom_to_atom_for_display at Base 3.0.0
>  libgtk-3.so.0 libgtk-3-0 #MINVER#
> + _gtk_get_resource at Base 3.24.20-1
> + _gtk_register_resource at Base 3.24.20-1
> + _gtk_unregister_resource at Base 3.24.20-1
>   gtk_about_dialog_add_credit_section at Base 3.3.16
>   gtk_about_dialog_get_artists at Base 3.0.0
>   gtk_about_dialog_get_authors at Base 3.0.0
> dh_makeshlibs: error: failing due to earlier errors
> make[1]: *** [debian/rules:240: override_dh_makeshlibs] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/gtk+3.0_3.24.20-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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.