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

  • Bug#1102278: coinstallation failure of various llvm-toolchain-20 packag

    From Helmut Grohne@21:1/5 to All on Mon Apr 7 09:50:01 2025
    Package: libc++-20-dev,libc++1-20,libc++abi-20-dev,libc++abi1-20,libclang-rt-20-dev,libmlir-20,libmlir-20-dev,liboffload-20,libomp5-20,libpolly-20-dev,libunwind-20,libunwind-20-dev
    Version: 1:20.1.1-1~exp1
    Severity: serious
    User: [email protected]
    Usertags: fileconflict

    The named packages fail to coinstall despite explicitly declaring that capability via Multi-Arch: same. Most of them install
    architecture-dependent files to architecture-independent filenames below /usr/lib/llvm-20/lib. Please either move those files to multiarch
    locations or remove the Multi-Arch: same annotations.

    Helmut

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

    tags -1 + patch
    Bug #1102278 [libc++-20-dev,libc++1-20,libc++abi-20-dev,libc++abi1-20,libclang-rt-20-dev,libmlir-20,libmlir-20-dev,liboffload-20,libomp5-20,libpolly-20-dev,libunwind-20,libunwind-20-dev] coinstallation failure of various llvm-toolchain-20 packages
    Added tag(s) patch.

    --
    1102278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102278
    Debian Bug Tracking System
    Contact [email protected] with problems

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

    Your message dated Sat, 03 May 2025 15:42:08 +0000
    with message-id <[email protected]>
    and subject line Bug#1102278: fixed in llvm-toolchain-20 1:20.1.4-1~exp1
    has caused the Debian Bug report #1102278,
    regarding coinstallation failure of various llvm-toolchain-20 packages
    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 [email protected]
    immediately.)


    --
    1102278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102278
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 7 Apr 2025 07:45:19 +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,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, 18; hammy, 92; neutral, 33; spammy, 0.
    spammytokens: hammytokens:0.000-+--exp1, 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: <[email protected]>
    Received: from isilmar-4.linta.de ([136.243.71.142]:40230)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
    (Exim 4.94.2)