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


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

Bug#1036884: transition: time64_t

From Steve Langasek <vorlon@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.devel.release
Subject Bug#1036884: transition: time64_t
Date 2023-05-28 18:50 +0200
Message-ID <GArKF-c2RS-3@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


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

Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: transition
Severity: normal

Dear Release Team,

I had started a thread on debian-devel[1] about the need to migrate 32-bit
architectures to 64-bit time_t in preparation for 2038, an ABI-breaking
change.

As the discussion on debian-devel has died down, I think it's time to
formally put this request on debian-release's radar.

I believe the last time we had an archive ABI change was before the Release
Team's current policy on transitions was put into place.  As mentioned in
that thread, there are probably more than 400 libraries whose ABIs/package
names are affected (380 identified to date); a list of these is attached. 
I've provided a mock ben config below; a real one could be synthesized once
the analysis is finished, though I'm not sure how useful it would be.

Also mentioned in the thread[2], it would be quite cumbersome to start this
transition in experimental (since it's toolchain-driven rather than
source-driven) but getting all of the binary packages through NEW in
experimental (with the wrong ABI) may help with timing.  I'm open to
guidance here.

Due to the broad and disruptive nature of this change, I am writing to
request a slot for the transition, preferably the first in the upcoming
trixie cycle.

I have not build-tested the reverse-build-dependencies.  There are at least
5000 source packages in unstable that need rebuilt as part of this
transition.  Some of them will likely show they have regressed in
buildability, including some that are currently in testing; hopefully a very
small number since we are about to release.  There is discussion of whether
we should enable -Werror=implicit-function-declaration as part of the ABI
transition.  If so, that will increase the number of build failures, though
also hopefully only a bit.  I do not expect build failures as a direct
result of the ABI transition.  If you do want build tests before upload to
unstable, guidance is welcome.

Ben file:

title = "time64_t";
is_affected = .depends ~ "old=/^.*$/" | .depends ~ "new=/^.*64t$/";
is_good = .depends ~ "new=/^.*64t$/";
is_bad = .depends ~ "old=/^.*$/";

-- 
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/
slangasek@ubuntu.com                                     vorlon@debian.org

[1] https://lists.debian.org/debian-devel/2023/05/msg00168.html
[2] https://lists.debian.org/debian-devel/2023/05/msg00260.html

Back to linux.debian.bugs.dist | Previous | Next | Find similar


Thread

Bug#1036884: transition: time64_t Steve Langasek <vorlon@debian.org> - 2023-05-28 18:50 +0200

csiph-web