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

Groups > linux.debian.bugs.rc > #355147 > unrolled thread

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

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1061954: frog: NMU diff for 64-bit time_t transition Lukas Märdian <slyon@debian.org> - 2024-01-30 14:40 +0100
    Bug#1061954: frog: NMU diff for 64-bit time_t transition "Maarten van Gompel" <proycon@anaproy.nl> - 2024-02-02 14:30 +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
    Bug#1061954: marked as done (frog: NMU diff for 64-bit time_t  transition) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-03-02 09:50 +0100

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

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

Source: frog
Version: 0.20-2
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
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.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-14-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

[toc] | [next] | [standalone]

#355524

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

Hi Joost, Lukas, 

On second thought, I read https://wiki.debian.org/ReleaseGoals/64bit-time and checked the updated Frog sources, there is no time_t
exposed at all anymore in the new version I'm packaging. So if I understand things correctly, the new
libfrog3 library does not need the t64 transition and I can revert
https://salsa.debian.org/science-team/frog/-/commit/2bbda8d92d40b96a216e8d8db972a9589f8df02f ?

> Afaik the plan is to keep the binary packages named lib<foo>t64 (reading
> https://wiki.debian.org/ReleaseGoals/64bit-time ); this helps executing the
> transition.

I'll rebase so the libfrog2t64 patch is included, but it'll be
immediately superseded by libfrog3.

Regards,

-- 

Maarten van Gompel (proycon)

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

[toc] | [prev] | [next] | [standalone]

#355525

Hi,

[sorry for yet another one, i clicked sent too early...]

On Fri, Feb 02, 2024 at 03:01:04PM +0100, Joost van Baal-Ilić wrote:
> On Fri, Feb 02, 2024 at 02:22:20PM +0100, Maarten van Gompel wrote:
> > 
> > On second thought, I read https://wiki.debian.org/ReleaseGoals/64bit-time and
> > checked the updated Frog sources, there is no time_t exposed at all anymore
> > in the new version I'm packaging.
> 
> That's nice.
> 
> > So if I understand things correctly, the new
> > libfrog3 library does not need the t64 transition and I can revert
> > https://salsa.debian.org/science-team/frog/-/commit/2bbda8d92d40b96a216e8d8db972a9589f8df02f ?
> 
> 
> > > Afaik the plan is to keep the binary packages named lib<foo>t64 (reading
> > > https://wiki.debian.org/ReleaseGoals/64bit-time ); this helps executing the
> > > transition.
> > 
> > I'll rebase so the libfrog2t64 patch is included, but it'll be
> > immediately superseded by libfrog3.
> 
> Upcoming stable release could likely ship both frog2 and frog3.  E.g. if
> testing around release-time ships binaries build-depending upon frog2, this
> will happen.

Wow, having just read Message-Id: <CYUMSR5QIVHF.1TRNK0G75U8VQ@anaproy.nl> to
debian-science, we might indeed succeed in shipping upcoming Debian stable
without frog2.

Bye,

Joost

[toc] | [prev] | [next] | [standalone]

#357726 — Bug#1061954: marked as done (frog: NMU diff for 64-bit time_t transition)

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

Your message dated Sat, 02 Mar 2024 08:43:00 +0000
with message-id <E1rgKxQ-003Czr-NH@fasolo.debian.org>
and subject line Bug#1061954: fixed in frog 0.20-2.1
has caused the Debian Bug report #1061954,
regarding frog: NMU diff for 64-bit time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1061954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061954
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web