Wondering about the current state of this transition. Is there a tracker of any kind for this? Or would someone be willing to post an email here periodically? Weekly maybe?
I looked at the release goals wiki and at the "brain dump" page but failed to
find anything dated more precisely than "***The t64 transition is ongoing
(March 2024) in Debian***".
There are five milestones listed on the release goal page. I would hazard that
the first three are done but I'm not sure whether the last two are complete?
The Milestones are:
1. Make a complete list of libraries with changed public ABI changes that must
transition together.
2. Change gcc-* to emit -D_FILE_OFFSET_BITS=64 and -D_TIME_BITS=64 by default.
3. Change dpkg-buildflags to emit -D_FILE_OFFSET_BITS=64 and -D_TIME_BITS=64 on
all 32-bit arches except i386 and hurd-i386 (filter this out for 100-odd
packages which are sensitive to LFS but not time_t).
4. NMU all libraries with binaries renamed from libfoo to libfoot64, removing
old suffixes (c102, c2, ldbl, g…) if present, and emit a Provides/Replaces/
Breaks libfoo on 64-bit arches + i386 and hurd-i386.
5. Do unchanged source rebuilds (binNMUs on all architectures) of 5000-6000
packages which depend on those. By the magic of transitions this just works.
I'm guessing that we're somewhere in the midst of Milestone 5?
In looking at packages I maintain, I find things like "blocked by ${pkg}". But
when I go to the blocker, there's often no upload for 2-3 weeks and no other
visible sign of progress. What's holding things up? Are we waiting for folks
to identify the 5-6k packages that need binNMU?
Can we help? I tried filing a binNmu bug for a package, but then found out the
package was nmu'd later -- without closing my bug. So clearly someone is
looking at things. Where are we in the process?
Appreciate all the good work going into this. Just wondering whether there's
something constructive I could pitch in on? If there is nothing for me but to
wait, that is useful information, too.
Thanks,
-Steve
signature.asc
Description: This is a digitally signed message part.
