1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1102357: nng: FTBFS: The following tests FAILED: 36 - nng.sp.transp

    From Santiago Vila@21:1/5 to All on Tue Apr 8 09:40:02 2025
    Package: src:nng
    Version: 1.10.1-1
    Severity: serious
    Tags: ftbfs trixie sid

    Dear maintainer:

    During a rebuild of all packages in unstable, your package failed to build:

    Note: This is an "always" failure, and I think it's triggered by some build-dependency which changed behavior recently.

    --------------------------------------------------------------------------------
    [...]
    The following tests FAILED:
    36 - nng.sp.transport.tls.tls_tran_test (Timeout)
    Errors while running CTest
    make[2]: *** [Makefile:94: test] Error 8
    make[2]: Leaving directory '/<<PKGBUILDDIR>>/build-static'
    dh_auto_test: error: cd build-static && make -j2 test ARGS\+=--verbose ARGS\+=-j2 returned exit code 2
    make[1]: *** [debian/rules:25: override_dh_auto_test] Error 25
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    make: *** [debian/rules:39: binary] Error 2
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------

    The above is just how the build ends and not necessarily the most relevant part.
    If required, the full build log is available here:

    https://people.debian.org/~sanvila/build-logs/202504/

    About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages.

    If you could not reproduce the bug please contact me privately, as I
    am willing to provide ssh access to a virtual machine where the bug is
    fully reproducible.

    If this is really a bug in one of the build-depends, please use
    reassign and add an affects on src:nng, so that this is still
    visible in the BTS web page for this package.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aurelien Jarno@21:1/5 to All on Sun Apr 20 20:10:01 2025
    Hi László,

    On 2025-04-20 18:53, László Böszörményi (GCS) wrote:
    Hi Aurelien,

    On Sun, Apr 20, 2025 at 1:13 PM Aurelien Jarno <aurel32@debian.org> wrote:
    The problem is easily reproducible and is caused by mbedtls 3.6.3-1, ad it builds fine with mbedtls 3.6.2-3.
    Yes, this is known.

    WARNING: NNG-TLS-HANDSHAKE: TLS handshake failed: SSL - Attempt to verify a certificate without an expected hostname. This is usually insecure. In TLS clients, when a client authenticates a server through its certificate, the client normally
    checks three WARNING: NNG-CONN-FAIL: Failed connecting socket<2> to tls+tcp://127.0.0.1:42757: Cryptographic error

    My guess is that this is linked to the CVE-2025-27809 fix.
    Just found, it is [1]. I will do other tests if I can fix it without upstream involvement.

    It seems to be already fixed upstream. The first hunk of this commit
    (the second applies to code added on versions following the one in
    debian) fixes the issue here:

    https://github.com/nanomsg/nng/commit/55925438bc8b8fd243ab995c48c8996ac49a6652

    Regards
    Aurelien

    --
    Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://aurel32.net

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sun Apr 20 22:40:02 2025
    This is a multi-part message in MIME format...

    Your message dated Sun, 20 Apr 2025 20:35:46 +0000
    with message-id <E1u6bOE-00HCx5-Sn@fasolo.debian.org>
    and subject line Bug#1102357: fixed in nng 1.10.1-2
    has caused the Debian Bug report #1102357,
    regarding nng: FTBFS: The following tests FAILED: 36 - nng.sp.transport.tls.tls_tran_test (Timeout)
    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.)


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

    Received: (at submit) by bugs.debian.org; 8 Apr 2025 07:36:39 +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=-122.0 required=4.0 tests=ALL_TRUSTED,BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FROMDEVELOPER,HAS_PACKAGE,
    SPF_HELO_PASS,SPF_NONE,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,
    X_DEBBUGS_CC autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 15; hammy, 150; neutral, 83; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--H*F:U*sanvila, 0.000-+--H*rp:U*sanvila Return-path: <sanvila@debian.org>
    Received: from mailly.debian.org ([2001:41b8:202:deb:6564:a62