This is a multi-part MIME message sent by reportbug.


Source: bctoolbox
Version: 5.2.0-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-arm@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

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
bctoolbox 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 bctoolbox
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/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

diff -Nru bctoolbox-5.2.0/debian/changelog bctoolbox-5.2.0/debian/changelog
--- bctoolbox-5.2.0/debian/changelog 2023-07-28 15:22:11.000000000 +0000
+++ bctoolbox-5.2.0/debian/changelog 2024-02-05 05:09:36.000000000 +0000
@@ -1,3 +1,10 @@
+bctoolbox (5.2.0-2.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek <vorlon@debian.org> Mon, 05 Feb 2024 05:09:36 +0000
+
bctoolbox (5.2.0-2) unstable; urgency=medium

* Release to unstable.
diff -Nru bctoolbox-5.2.0/debian/control bctoolbox-5.2.0/debian/control
--- bctoolbox-5.2.0/debian/control 2023-07-28 15:22:11.000000000 +0000
+++ bctoolbox-5.2.0/debian/control 2024-02-05 05:09:35.000000000 +0000
@@ -20,7 +20,7 @@
Section: libdevel
Architecture: any
Multi-Arch: same
-Depends: libbctoolbox1 (= ${binary:Version}),
+Depends: libbctoolbox1t64 (= ${binary:Version}),
${misc:Depends},
Description: Helper code for software by Belledonne Communications (development headers)
The package provides a C/C++ utility library used

X-Debbugs-CC: Steve Langasek <vorlon@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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part MIME message sent by reportbug.


Source: bctoolbox
Dear maintainer,

Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.

Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

diff -Nru bctoolbox-5.2.0/debian/changelog bctoolbox-5.2.0/debian/changelog
--- bctoolbox-5.2.0/debian/changelog 2023-07-28 15:22:11.000000000 +0000
+++ bctoolbox-5.2.0/debian/changelog 2024-03-01 11:44:51.000000000 +0000
@@ -1,3 +1,10 @@
+bctoolbox (5.2.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition. Closes: #1063106
+
+ -- Benjamin Drung <bdrung@debian.org> Fri, 01 Mar 2024 11:44:51 +0000
+
bctoolbox (5.2.0-2) unstable; urgency=medium

* Release to unstable.
diff -Nru bctoolbox-5.2.0/debian/control bctoolbox-5.2.0/debian/control
--- bctoolbox-5.2.0/debian/control 2023-07-28 15:22:11.000000000 +0000
+++ bctoolbox-5.2.0/debian/control 2024-03-01 11:44:51.000000000 +0000
@@ -3,7 +3,7 @@
Maintainer: Debian VoIP Team <pkg-voip-maintainers@lists.alioth.debian.org>
Uploaders: Bernhard Schmidt <berni@debian.org>
Rules-Requires-Root: no
-Build-Depends: cmake,
+Build-Depends: dpkg-dev (>= 1.22.5), cmake,
debhelper-compat (= 13),
libdecaf-dev,
libm

This is a multi-part message in MIME format...

Your message dated Fri, 01 Mar 2024 12:04:13 +0000
with message-id <E1rg1cb-00G8na-2e@fasolo.debian.org>
and subject line Bug#1063106: fixed in bctoolbox 5.2.0-2.1
has caused the Debian Bug report #1063106,
regarding bctoolbox: 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.)


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

Received: (at submit) by bugs.debian.org; 5 Feb 2024 05:10:38 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-110.1 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FOURLA,FROMDEVELOPER,
HEADER_FROM_DIFFERENT_DOMAINS,SPF_HELO_NONE,SPF_NONE,
T_SCC_BODY_TEXT_LINE,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,
XMAILER_REPORTBUG autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 25; hammy, 150; neutral, 262; spammy,
0. spammytokens: hammytokens:0.000-+--sk:taint_o, 0.000-+--sk:TAINT_O,
0.000-+--trixie, 0.000-+--langasek, 0.000-+--Langasek
Return-path: <vorlon@homer.dodds.net>
Received: from becquer.dodds.net ([207.224.24.209]:59579)
by buxtehude.