Bug#1086231: libchamplain: FTBFS on 32-bit with 64-bit time_t: passing argument 1 of ‘gmtime’ from incompatible pointer type

[Arnd Bergmann]

On Thu, Jan 23, 2025, at 16:01, Jeremy Bícha wrote:
> I have filed an armel/armhf removal bug [1] for libchamplain. If
> libchamplain is removed on those architectures, we will demote this
> bug to important.
>
> Upstream prefers [2] that apps that use gtk3+libchamplain switch to
> gtk4+libshumate.
>
> Because of this issue, I have disabled the maps plugin for eog and the
> maps plugin for evolution on the non-x86 32-bit architectures. We are
> also removing fotoxx on those architectures. The only other affected
> app in Debian is qreator which is arch: all.
>
> [1] https://gitlab.gnome.org/GNOME/libchamplain/-/issues/61
> [2] https://gitlab.gnome.org/GNOME/libchamplain/-/issues/61

According to codesearch, there are 262 packages that reference
GTimeVal, though looking at a couple of packages I have installed
locally this is often only a changelog entry mentioning that the
deprecated type has been change. The ones that do use it are
likely to be incompatible with a 64-bit time_t on all 32-bit
architectures:
https://codesearch.debian.net/search?q=GTimeVal

In most cases this will not show up as a build failure or
runtime error today, but will turn into a runtime error in
2038.

I found an older blog post that describes how to fix packages
using GTimeVal:
https://tecnocode.co.uk/2019/08/24/gtimeval-deprecation-in-glib-2-61-2/

It would be good to identify all packages that still use
GTimeVal on 32-bit targets and do the same as here: either fix
them or mark them as broken.

    Arnd