[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1062170: glw: NMU diff for 64-bit time_t transition



On Wed, 31 Jan 2024 14:54:08 +0000 =?utf-8?q?Lukas_M=C3=A4rdian?= <slyon@debian.org> wrote:
> Source: glw
> Version: 8.0.0-1.1
> Severity: serious
> Tags: patch pending
> Justification: library ABI skew on upgrade
> User: debian-arm@lists.debian.org
> Usertags: time-t
>
> 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
> glw 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 glw
> 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.

I don't think this patch was effective. There is no package rename and the build log from experimental contains the following warning:

> dpkg-gencontrol: warning: Provides field of package libglw1-mesa: substitution variable ${t64:Provides} used, but is not defined



--
Michael R. Crusoe

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


Reply to: