On Fri, Mar 01, 2024 at 12:03:26PM +0100, José Luis Blanco-Claraco wrote: > Hi Steve, > As package and upstream's maintainer, what should I do to ensure the > library is change safe?
> Would it help to totally remove references to time_t in all public headers? I don't understand what you mean by "change safe". The API is the API, and we have uploaded it to pick up the new 64-bit time_t ABI. > El dom, 18 feb 2024, 9:00, Steve Langasek <vor...@debian.org> escribió: > > > Source: mrpt > > Version: 1:2.11.9+ds-1 > > Severity: important > > Tags: patch pending sid trixie > > User: debian-...@lists.debian.org > > Usertags: time-t > > > > NOTICE: these changes must not be uploaded to unstable yet! > > > > Dear maintainer, > > > > As part of the 64-bit time_t transition required to support 32-bit > > architectures in 2038 and beyond > > (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified > > mrpt as a source package shipping runtime libraries whose ABI > > either is affected by the change in size of time_t, or could not be > > analyzed via abi-compliance-checker (and therefore to be on the safe > > side we assume is affected). > > > > To ensure that inconsistent combinations of libraries with their > > reverse-dependencies are never installed together, it is necessary to > > have a library transition, which is most easily done by renaming the > > runtime library package. > > > > Since turning on 64-bit time_t is being handled centrally through a change > > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is > > important that libraries affected by this ABI change all be uploaded close > > together in time. Therefore I have prepared a 0-day NMU for mrpt > > which will initially be uploaded to experimental if possible, then to > > unstable after packages have cleared binary NEW. > > > > Please find the patch for this NMU attached. > > > > If you have any concerns about this patch, please reach out ASAP. Although > > this package will be uploaded to experimental immediately, there will be a > > period of several days before we begin uploads to unstable; so if > > information > > becomes available that your package should not be included in the > > transition, > > there is time for us to amend the planned uploads. > > > > > > > > -- System Information: > > Debian Release: trixie/sid > > APT prefers unstable > > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, > > 'experimental') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT) > > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE > > Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
