Bug#1063106: bctoolbox: NMU diff for 64-bit time_t transition

[Dennis Filder]

X-Debbugs-CC: Steve Langasek <vorlon at debian.org>

The packages bctoolbox, belle-sip and linphone have been marked as
affected by the 64-bit time_t transition.  However, all these packages
currently have new versions staged in experimental because their
library packages had soname bumps unrelated to the 64-bit time_t
transition (which you already noticed for belle-sip).  As long as
these staged versions actually make it into testing before the Trixie
freeze there should be no need for these NMU diffs, correct?

> 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.

I presume the need for "close together in time" is to prevent
interoperability issues from cropping up in unstable between shared
library versions on different sides of the time_t transition.  How
timely would our staged versions need to be uploaded to unstable to
obviate the need for the NMUs?  I ask because it is very difficult to
say with a useful degree of certainty when these staged versions will
actually reach testing.  Experience has shown that linphone stack
transitions are prone to being afflicted by (sometimes multi-month)
delays due to being blocked by other transitions, and I see no open
bugreport for linphone on the release.debian.org pseudopackage, so
Berni (who will do these uploads) apparently has not yet applied for a
new transition slot.

Regards.