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

Package:
src:libchamplain
Source:
src:libchamplain
Submitter:
Simon McVittie
Date:
2025-11-18 10:03:02 UTC
Severity:
normal
Tags:
#1086231#5
Date:
2024-10-29 09:35:09 UTC
From:
To:
Source: libchamplain
Version: 0.12.21-1
Severity: serious
Tags: ftbfs trixie sid upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-arm@lists.debian.org
User: debian-arm@lists.debian.org
Usertags: armel armhf
Forwarded: https://gitlab.gnome.org/GNOME/libchamplain/-/issues/61

https://buildd.debian.org/status/fetch.php?pkg=libchamplain&arch=armhf&ver=0.12.21-1%2Bb2&stamp=1730190463&file=log

This looks like delayed fallout from the 64-bit time_t transition. 'time'
is a GTimeVal, which has a fixed ABI ({ long tv_sec, long tv_usec }) which
is neither Y2038-compatible nor a match for the new ABI of struct timeval.
I've sent some bug reports upstream.

The armel build hasn't been tried yet, but I'm 99% confident that it will
fail in the same way.

In -ports world, x32 has the same build failure, and other 32-bit ports
like powerpc and sh4 probably will too.

    smcv

#1086231#12
Date:
2025-01-23 15:01:24 UTC
From:
To:
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

Thank you,
Jeremy Bícha

#1086231#17
Date:
2025-01-23 20:41:18 UTC
From:
To:
Control: block -1 with 1093857

I guess in [1] you meant https://bugs.debian.org/1093857

Thanks for filing that and taking care of the rdeps. Sounds like we can lower
this bug to important once the removal is processed.

Cheers,
Emilio

#1086231#26
Date:
2025-01-26 22:01:14 UTC
From:
To:
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

#1086231#31
Date:
2025-11-18 10:00:08 UTC
From:
To:
Dear submitter,

as the package libchamplain has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1118065

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)