• Bug#1061341: cyrus-common: identified for time_t transition but no ABI

    From Steve Langasek@21:1/5 to All on Mon Jan 22 21:50:01 2024
    Package: cyrus-common
    Version: 3.8.1-1
    Severity: serious
    User: debian-arm@lists.debian.org
    Usertags: time-t

    Dear maintainers,

    Analysis of the archive for the 64-bit time_t transition[0][1] identifies cyrus-common as an affected package, on the basis that the headers could not
    be compiled and analyzed out of the box using abi-compliance-checker[2], so
    we have to assume it's affected.

    However, cyrus-commons's shlibs file declares a dependency on a library
    package name that contains no ABI information:

    $ cat DEBIAN/shlibs
    libcyrus 0 cyrus-common (>= 3.8.1)
    libcyrus_imap 0 cyrus-common (>= 3.8.1)
    libcyrus_min 0 cyrus-common (>= 3.8.1)
    libcyrus_sieve 0 cyrus-common (>= 3.8.1)
    $

    It is therefore not obvious that we should rename the package to 'cyrus-common-t64' as part of this transition.

    Looking at the archive, there are packages that depend on these libraries, cyrus-admin and cyrus-clients. Despite being built from the same source package, they do not have a strict versioned dependency on cyrus-common but instead use the shlibs.

    Since there is no self-evident thing to do with the library package name
    here, we will not be handling this package as part of the mass NMUs.
    Instead I am filing a serious bug because partial upgrades from bookworm to trixie on 32-bit architectures (upgrading cyrus-common without also
    upgrading cyrus-{admin,clients}) will result in ABI skew and may result in broken behavior.

    Thanks,
    --
    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

    [0] https://wiki.debian.org/ReleaseGoals/64bit-time
    [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
    [2] https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/cyrus-dev/base/log.txt

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmWu010ACgkQVo0w8yGy Ez0VrA/+JuNBJX8sff4DEIFuwIoM0XF+rEpWymIHa+VtUZgF5sOpCOg3GV05IBHI rrnV4JK3ZjVMGKwdwSvjpnaEf7DcZ0BBy2ZtB6rNAF1NYnEmMmh8quhwbw3XBdNs HAg81nH+ieKzoqenDK/IHat/uaVOU77+mSbm1SvrIqdTXtaKvMGsF+uUGuNS+x9I d9Anllfo2bOiKUaZZe2O8m27NfkB2oD3i2H4pJSy+Ojizt8c+yd/cd8kwsy55NVS /tkOX6LPZbh5PJpTP5FhDx/L+Y8kjKNi8Ewi6I58GRf14AAVm0XjzwoCZjPgODM+ fNJKjNu29EVgHFzNQ2xL2okbSci8MiCJ3xU+iQHRTDbPDYySz2XxEaigL/ZIreRi
    y6gVlTwf/ucQd
  • From Debian Bug Tracking System@21:1/5 to All on Tue Jan 23 05:40:01 2024
    Processing control commands:

    tags -1 + moreinfo
    Bug #1061341 [cyrus-common] cyrus-common: identified for time_t transition but no ABI in shlibs
    Added tag(s) moreinfo.

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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steve Langasek@21:1/5 to Yadd on Sun Jan 28 17:40:01 2024
    On Tue, Jan 23, 2024 at 08:32:18AM +0400, Yadd wrote:
    Control: tags -1 + moreinfo

    On 1/23/24 00:43, Steve Langasek wrote:
    Package: cyrus-common
    Version: 3.8.1-1
    Severity: serious
    User: debian-arm@lists.debian.org
    Usertags: time-t

    Dear maintainers,

    Analysis of the archive for the 64-bit time_t transition[0][1] identifies cyrus-common as an affected package, on the basis that the headers could not
    be compiled and analyzed out of the box using abi-compliance-checker[2], so we have to assume it's affected.

    However, cyrus-commons's shlibs file declares a dependency on a library package name that contains no ABI information:

    according to https://adrien.dcln.fr/misc/armhf-time_t/2024-01-17/logs/cyrus-dev/base/log.txt
    , this issue looks like a false-positive: test failed because of C error,
    not bad report

    Am I right here ?

    We do not *know* that it's a false positive; we only know that we were
    unable to analyze the header files under a-c-c to prove that the ABI is not affected.

    Patches to the check-armhf-time_t script at https://salsa.debian.org/vorlon/armhf-time_t/-/blob/main/check-armhf-time_t?ref_type=heads
    to quirk this package and allow its headers to be analyzed, or changes to
    the source package to not ship uncompilable headers ("apt-file search lib/strarray.h" returns no results), would both be welcome.

    Thanks,
    --
    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

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmW2fvoACgkQVo0w8yGy Ez2cLxAAgTmcovvLq2Mh5qNO5uY9gbr2yaGt1iwLEBcvgikCJUK1AaBYcdUS6loj C5ksQMHKgCQgFU47+XL5pK+uOttfcmk9BIShMZVy7AWc4tYDQE9y3vyQRZWh9oeS fki1+CAlIelVNhL4BWzNBoYTkQeUlKyzX+eUb+9FME0E00Utx/iUMJfvCVVdztsl FTxMQ930+5ihj1SRQRI9TdF7BrFtK818L/Y7pSX0CQRrMWZndml15LjnXqo7PDLI l64WXUjyEYaylmUZlbaUUdajru7GekGtSQAB/YdchA8kk04TEko9V1y/oXgWKQOJ Gl4tRYVYA1cbUSzF7wk4p1Kpz2QvBH3oLidikk2BXUl4+yWRYJYThXYQHt51wWzs /qIBQMx3LoJtruN4f/YFN6TccrlXafsP03diwbZt0nULSpV0IEZYRBC8qJE8boP1 Lumbw9EOxGts3bz+sWpjA954AZw43fI4jypffmoyzFhQHGG6uaU/J8+mzZa6NvgA QMXfKLnwnJ2O+t2ASfIaFLSfyZ5I2Rc7lr+5tZaUsJL4D79JXxPbL4SHd+wwRsTn ZlhQtbXN874VK0BhSDjl
  • From Debian Bug Tracking System@21:1/5 to All on Thu Feb 15 11:00:02 2024
    This is a multi-part message in MIME format...

    Your message dated Thu, 15 Feb 2024 09:50:07 +0000
    with message-id <E1raYNb-009Gk9-Rd@fasolo.debian.org>
    and subject line Bug#1061341: fixed in cyrus-imapd 3.10.0~beta1-2
    has caused the Debian Bug report #1061341,
    regarding cyrus-common: identified for time_t transition but no ABI in shlibs 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.)


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

    Received: (at submit) by bugs.debian.org; 22 Jan 2024 20:43:25 +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=-120.5 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,PGPSIGNATURE,
    SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,USER_IN_DKIM_WELCOMELIST,
    USER_IN_DKIM_WHITELIST autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 21; hammy, 150; neutral, 98; spammy,
    0. spammytokens: hammytokens:0.000-+--bookworm, 0.000-+--trixie,
    0.000-+--langasek, 0.000-+--Langasek, 0.000-+--H*ct:application Return-path: <vorlon@debian.org>
    Received: from becquer.dodds.net ([207.224.24.209]:60755)
    by buxte
  • From Debian Bug Tracking System@21:1/5 to All on Thu Feb 15 11:10:01 2024
    This is a multi-part message in MIME format...

    Your message dated Thu, 15 Feb 2024 10:05:23 +0000
    with message-id <E1raYcN-009Jbk-Ch@fasolo.debian.org>
    and subject line Bug#1061341: fixed in cyrus-imapd 3.8.1-2
    has caused the Debian Bug report #1061341,
    regarding cyrus-common: identified for time_t transition but no ABI in shlibs 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.)


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

    Received: (at submit) by bugs.debian.org; 22 Jan 2024 20:43:25 +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=-120.5 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,PGPSIGNATURE,
    SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,USER_IN_DKIM_WELCOMELIST,
    USER_IN_DKIM_WHITELIST autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 21; hammy, 150; neutral, 98; spammy,
    0. spammytokens: hammytokens:0.000-+--bookworm, 0.000-+--trixie,
    0.000-+--langasek, 0.000-+--Langasek, 0.000-+--H*ct:application Return-path: <vorlon@debian.org>
    Received: from becquer.dodds.net ([207.224.24.209]:60755)
    by buxte