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

  • Bug#1100920: libspfft-dev fails coinstallation

    From Helmut Grohne@21:1/5 to All on Thu Mar 20 15:00:01 2025
    Package: libspfft-dev
    Version: 1.1.1-2
    Severity: serious
    User: debian-qa@lists.debian.org
    Usertags: fileconflict

    libspfft-dev fails to coinstall for amd64 and i386 (but likely also any
    other combination).

    mmdebstrap --verbose --variant=apt '' /dev/null "deb http://deb.debian.org/debian unstable main" --architectures=amd64,i386 --include=libspfft-dev,libspfft-dev:i386

    Unpacking libspfft-dev:amd64 (1.1.1-2) ...
    dpkg: error processing archive /tmp/apt-dpkg-install-IXZ43Y/61-libspfft-dev_1.1.1-2_amd64.deb (--unpack):
    trying to overwrite shared '/usr/include/spfft/config.h', which is different from other instances of package libspfft-dev:amd64
    Errors were encountered while processing:
    /tmp/apt-dpkg-install-IXZ43Y/61-libspfft-dev_1.1.1-2_amd64.deb

    The simplest solution here is to remove "Multi-Arch: same" from the
    relevant binary package section and that certainly is a valid approach.

    Another option would be moving the affected file to an
    architecture-dependent path such as /usr/include/${DEB_HOST_MULTIARCH}/spfft/config.h hoping that it still
    will be found.

    A third option is to investigate the architecture-differences and trying
    to remove them.

    I don't think coinstallation is important for this package and given the
    freeze timing recommend dropping Multi-Arch: same at least for trixie.

    Helmut

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Thu Mar 20 17:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Thu, 20 Mar 2025 15:55:24 +0000
    with message-id <E1tvIEu-00DyWW-Dv@fasolo.debian.org>
    and subject line Bug#1100920: fixed in spfft 1.1.1-3
    has caused the Debian Bug report #1100920,
    regarding libspfft-dev fails coinstallation
    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.)


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

    Received: (at submit) by bugs.debian.org; 20 Mar 2025 13:52:41 +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=-15.2 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,
    DKIM_VALID_EF,FVGT_m_MULTI_ODD,HAS_PACKAGE,SPF_HELO_NONE,SPF_NONE
    autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 16; hammy, 147; neutral, 40; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--H*F:U*helmut,
    0.000-+--H*F:D*subdivi.de, 0.000-+--H*RU:sk:helmut@,
    0.000-+--H*rp:U*helmut
    Return-path: <helmut@subdivi.de>
    Received: from isilmar-4.linta.de ([136.243.71.142]:33268)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_G