[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-devel
Subject:    Re: Bug#1036884: 64-bit time_t: updated archive analysis, proposed transition plan with timeline
From:       Sune Vuorela <nospam () vuorela ! dk>
Date:       2024-01-08 7:58:00
Message-ID: ung9u8$f35$1 () ciao ! gmane ! io
[Download RAW message or body]

On 2024-01-05, Sebastian Ramacher <sramacher@debian.org> wrote:
>> libpoppler-cpp0v5
>> libpoppler-glib8
>> libpoppler-qt5-1
>> libpoppler-qt6-3
>> libpoppler126

Poppler core (126ish) changes SONAME by release and is in general not
supposed to be used by well-behaving applications.

the frontentds (cpp,glib,Qt*) is supposedly stable.

But I can confirm that all of them uses time-related types in their
api's. (time_t specifically)

For added fun, the cpp frontend does it like this on all architectures:
typedef unsigned int /* time_t */ time_type;

in deprecated api, replaced with time_t in non-deprecated methods. That
might require extra investigations.

(The commit deprecating and replacing api specifically mentions y2k38)

/Sune


[prev in list] [next in list] [prev in thread] [next in thread]