• Bug#1103592: faust: FTBFS on mips64el: dwz: Unknown debugging section .

    From Chris Hofstaedtler@21:1/5 to All on Sat Apr 19 14:10:01 2025
    Source: faust
    Version: 2.79.3+ds-1
    Severity: serious
    Tags: ftbfs
    Justification: ftbfs

    Your package FTBFS on mips64el because of the dwz bug #1016936. While
    its likely dwz's fault, your package is affected by it, and the dwz bug
    has not moved since November 2024. It seems necessary to apply a
    workaround in your package.

    Note that the ftbfs prevents testing migration.

    https://buildd.debian.org/status/fetch.php?pkg=faust&arch=mips64el&ver=2.79.3%2Bds-1&stamp=1744805443&raw=0

    make[1]: Leaving directory '/build/reproducible-path/faust-2.79.3+ds'
    dh_fixperms -a
    dh_missing -a
    dh_dwz -a
    dwz: debian/faust/usr/bin/faust: Unknown debugging section .debug_addr
    dwz: debian/faust/usr/bin/faust: Unknown debugging section .debug_addr
    dh_dwz: error: dwz -mdebian/faust/usr/lib/debug/.dwz/mips64el-linux-gnuabi64/faust.debug -M/usr/lib/debug/.dwz/mips64el-linux-gnuabi64/faust.debug -- debian/faust/usr/bin/faust debian/faust/usr/bin/sound2faust debian/faust/usr/bin/sound2file returned
    exit code 1
    dwz: debian/libfaust2t64/usr/lib/mips64el-linux-gnuabi64/libfaust.so.2.79.3: Unknown debugging section .debug_addr
    dwz: debian/libfaust2t64/usr/lib/mips64el-linux-gnuabi64/libfaust.so.2.79.3: Unknown debugging section .debug_addr
    dh_dwz: error: dwz -mdebian/libfaust2t64/usr/lib/debug/.dwz/mips64el-linux-gnuabi64/libfaust2t64.debug -M/usr/lib/debug/.dwz/mips64el-linux-gnuabi64/libfaust2t64.debug -- debian/libfaust2t64/usr/lib/mips64el-linux-gnuabi64/libHTTPDFaust.so.0.7.1 debian/
    libfaust2t64/usr/lib/mips64el-linux-gnuabi64/libOSCFaust.so.1.2.2 debian/libfaust2t64/usr/lib/mips64el-linux-gnuabi64/libfaust.so.2.79.3 debian/libfaust2t64/usr/lib/mips64el-linux-gnuabi64/libfaustmachine.so.1.0.0 returned exit code 1
    dh_dwz: error: Aborting due to earlier error
    make: *** [debian/rules:37: binary-arch] Error 25
    dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?B?SU9oYW5uZXMgem3DtmxuaWc=?@21:1/5 to All on Tue Apr 22 12:10:02 2025
    Control: tag -1 pending

    Hello,

    Bug #1103592 in faust reported by you has been fixed in the
    Git repository and is awaiting an upload. You can see the commit
    message below and you can check the diff of the fix at:

    https://salsa.debian.org/multimedia-team/faust/-/commit/818c10e2cba5ee2d9349c6e33185d476e5221001

    ------------------------------------------------------------------------ Disable dh_dwz on all archs

    Closes: #1103592 ------------------------------------------------------------------------

    (this message was generated automatically)
    --
    Greetings

    https://bugs.debian.org/1103592

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Tue Apr 22 12:10:02 2025
    Processing control commands:

    tag -1 pending
    Bug #1103592 [src:faust] faust: FTBFS on mips64el: dwz: Unknown debugging section .debug_addr causes some builds to fail
    Added tag(s) pending.

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

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

    Your message dated Tue, 22 Apr 2025 10:19:47 +0000
    with message-id <E1u7AjD-007P7d-Cx@fasolo.debian.org>
    and subject line Bug#1103592: fixed in faust 2.79.3+ds-2
    has caused the Debian Bug report #1103592,
    regarding faust: FTBFS on mips64el: dwz: Unknown debugging section .debug_addr causes some builds to fail
    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.)


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

    Received: (at submit) by bugs.debian.org; 19 Apr 2025 12:07:59 +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=-10.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
    SPF_HELO_NONE,SPF_NONE,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, 35; hammy, 149; neutral, 33; spammy,
    1. spammytokens:0.944-+--H*r:bugs.debian.org
    hammytokens:0.000-+--sk:buildd., 0.000-+--UD:buildd.debian.org,
    0.000-+--buildddebianorg, 0.000-+--buildd.debian.org,
    0.000-+--H*x:12.0.0
    Return-path: <zeha@debian.org>
    Received: from per.namespace.at ([2a01:4f9:6b:302c::2]:58900)
    by buxtehude.debian.org with esmtp (Exim 4.94.2)
    (envelope-from <zeha@debian.org>)
    id 1u66zG-00B8gn-QO
    for submit@bu