Source: gconf Version: 3.2.6-5 Severity: serious Justification: https://release.debian.org/bullseye/rc_policy.txt §6a Tags: patch Forwarded: https://gitlab.gnome.org/Archive/gconf/merge_requests/1
With the recent upload of GLib 2.62 to unstable, gconf's autopkgtest has started failing: https://ci.debian.net/data/autopkgtest/testing/amd64/g/gconf/3045304/log.gz > /usr/include/gconf/2/gconf/gconf-value.h:139:3: error: ‘GTime’ is deprecated: > Use 'GDateTime' instead [-Werror=deprecated-declarations] > 139 | GTime mod_time; /* time of the modification */ > | ^~~~~ > /usr/include/gconf/2/gconf/gconf-value.h:144:1: error: ‘GTime’ is deprecated: > Use 'GDateTime' instead [-Werror=deprecated-declarations] > 144 | GTime gconf_meta_info_mod_time (GConfMetaInfo *gcmi); > | ^~~~~ > /usr/include/gconf/2/gconf/gconf-value.h:153:46: error: ‘GTime’ is > deprecated: Use 'GDateTime' instead [-Werror=deprecated-declarations] > 153 | GTime mod_time); > | ^~~~~ > cc1: all warnings being treated as errors GTime is a gint32 (not a time_t, although it happens to be equivalent on older 32-bit architectures) counting seconds since the beginning of 1970. As such it is not Y2038-safe. The deprecation warnings can be disabled for code that depends on gconf by wrapping a block with the G_GNUC_BEGIN_IGNORE_DEPRECATIONS and G_GNUC_END_IGNORE_DEPRECATIONS macros, as was done in Ubuntu patch 3.2.6-5ubuntu3: https://gitlab.gnome.org/Archive/gconf/merge_requests/1 Regards, smcv
