Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1184534

Bug#1061954: frog: NMU diff for 64-bit time_t transition

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi Lukas,

On Tue Jan 30, 2024 at 2:31 PM CET, Lukas Märdian wrote:
> 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
> frog 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 frog
> 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.

Thanks for your patch. I am currently in the progress of upgrading these
packages to the new upstream sources after a long hiatus. This would
involve a library transition anyway (libfrog2 -> libfrog3). Is it
sufficient if I include  'Provides: ${t64:Provides}' for the new
libfrog3 package to accomodate this transition? I just did this in
commit 2bbda8d92d40b96a216e8d8db972a9589f8df02f:
  
  https://salsa.debian.org/science-team/frog/-/commit/2bbda8d92d40b96a216e8d8db972a9589f8df02f

Perhaps that also removes the need for the oddly named frog2t64 package?
If not, I'll apply your patch and rebase my changes on top of it.

Regards,

-- 

Maarten van Gompel (proycon)

web: https://proycon.anaproy.nl
gpg: 0x39FE11201A31555C

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#1061954: frog: NMU diff for 64-bit time_t transition "Maarten van Gompel" <proycon@anaproy.nl> - 2024-02-01 18:50 +0100
  Bug#1061954: frog: NMU diff for 64-bit time_t transition Joost van Baal-Ilić <joostvb-debian@mdcc.cx> - 2024-02-02 13:10 +0100
    Bug#1061954: frog: NMU diff for 64-bit time_t transition Joost van Baal-Ilić <joostvb-debian@mdcc.cx> - 2024-02-02 15:10 +0100

csiph-web