• Bug#1062752: linphone: NMU diff for 64-bit time_t transition

    From Steve Langasek@21:1/5 to All on Sat Feb 3 00:20:02 2024
    This is a multi-part MIME message sent by reportbug.


    Source: linphone
    Version: 5.2.0-4.1
    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
    linphone 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 linphone
    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'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
    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 linphone-5.2.0/debian/changelog linphone-5.2.0/debian/changelog
    --- linphone-5.2.0/debian/changelog 2023-12-17 16:31:05.000000000 +0000
    +++ linphone-5.2.0/debian/changelog 2024-02-02 20:31:04.000000000 +0000
    @@ -1,3 +1,10 @@
    +linphone (5.2.0-4.2) experimental; urgency=medium
    +
    + * Non-maintainer upload.
    + * Rename libraries for 64-bit time_t transition.
    +
    + -- Steve Langasek <vorlon@debian.org> Fri, 02 Feb 2024 20:31:04 +0000
    +
    linphone (5.2.0-4.1) unstable; urgency=medium

    * Non-maintainer upload.
    diff -Nru linphone-5.2.0/debian/control linphone-5.2.0/debian/control
    --- linphone-5.2.0/debian/control 2023-12-17 16:28:42.000000000 +0000
    +++ linphone-5.2.0/debian/control 2024-02-02 20:31:04.000000000 +0000
    @@ -41,8 +41,8 @@

    Package: liblinphone-dev
    Section: libdevel
    -Depends: liblinphone11 (= ${binary:Version}),
    - liblinphone++11 (= ${binary:Version}),
    +Depends: liblinphone11t64 (= ${binary:Version}),
    + liblinphone++11t64 (= ${binary:Version}),
    libbelcard-dev (>= 5.2.0~),
    libbellesip-dev (>= 5.2.0~),
  • From Debian Bug Tracking System@21:1/5 to All on Fri Mar 1 08:10:01 2024
    This is a multi-part message in MIME format...

    Your message dated Fri, 01 Mar 2024 07:04:52 +0000
    with message-id <E1rfwwu-00Ex3G-Ps@fasolo.debian.org>
    and subject line Bug#1062752: fixed in linphone 5.2.0-4.3
    has caused the Debian Bug report #1062752,
    regarding linphone: 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.)


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

    Received: (at submit) by bugs.debian.org; 2 Feb 2024 23:14:28 +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=-112.4 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
    DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,
    FROMDEVELOPER,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, 41; hammy, 150; neutral, 289; 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@debian.org>
    Received: from becquer.dodds.net ([207.224.24.209]:44251)
    by buxtehude.debian.org with esmtps