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

  • Bug#1103020: nfs-ganesha: wrong use of Multi-Arch

    From Helmut Grohne@21:1/5 to All on Sun Apr 13 21:00:02 2025
    Source: nfs-ganesha
    Version: 6.5-3+b1
    Severity: serious
    Justification: may cause an unpack error from dpkg

    Hi,

    the use of Multi-Arch in nfs-ganesha is wrong on multiple accounts.

    Multi-Arch: foreign says that the interface provided to other packages
    is architecture-independent. However, nfs-ganesha is able to load
    plugins packages in nfs-ganesha-* as shared libraries via dlopen. This
    is an architecture-dependent interface. nfs-ganesha must not be marked Multi-Arch: foreign. It is a prime example where Multi-Arch: allowed is appropriate.

    The actual plugins also wrongly use Multi-Arch. The generation of manual
    pages is not reproducible across architectures. Therefore the manual
    page is architecture-dependent. As it also uses an architecture-indepent
    path, this may cause an unpack error from dpkg when attempting to
    coinstall plugins. Such an installation failure is a release-critical
    bug.

    nfs-ganesha-gluster
    * /usr/share/man/man8/ganesha-gluster-config.8.gz
    nfs-ganesha-gpfs
    * /usr/share/man/man8/ganesha-gpfs-config.8.gz
    nfs-ganesha-proxy-v4
    * /usr/share/man/man8/ganesha-proxy-v4-config.8.gz
    nfs-ganesha-rgw
    * /usr/share/man/man8/ganesha-rgw-config.8.gz
    nfs-ganesha-vfs
    * /usr/share/man/man8/ganesha-vfs-config.8.gz

    Since they are to be loaded into nfs-ganesha and there can only be one nfs-ganesha at a time, Multi-Arch: same does not support any practical
    use case. Rather than improving the generation of manual pages, I
    recommand dropping Multi-Arch from these packages.

    For nfs-ganesha itself, I think the safe answer for trixie is to also
    drop Multi-Arch. Multi-Arch: allowed is also ok, but may not be the best solution, because the only architecture-dependent use of nfs-ganesha may
    be internal via its plugins. An alternative here (not for trixie) would
    be to create an alibi package nfs-ganesha-plugin-abi that happens to be Arch:any + M-A:no such that nfs-ganesha and all plugins depend on. Doing
    so ensures that they're all installed for the same architecture. Then nfs-ganesha itself may become M-A:foreign again arguing that use of the
    plugin interface requires a dependency on nfs-ganesha-plugin-abi.

    TL;DR: Please drop all Multi-Arch headers except for nfs-ganesha-doc.

    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 15 00:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Mon, 14 Apr 2025 21:51:15 +0000
    with message-id <E1u4Rhz-005221-4A@fasolo.debian.org>
    and subject line Bug#1103020: fixed in nfs-ganesha 6.5-4
    has caused the Debian Bug report #1103020,
    regarding nfs-ganesha: wrong use of Multi-Arch
    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.)


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

    Received: (at submit) by bugs.debian.org; 13 Apr 2025 18:55:37 +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=-4.2 required=4.0 tests=BAYES_00,DKIM_SIGNED,
    DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,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, 21; hammy, 145; neutral, 55; 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]:58156)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
    (Exim 4.94.2)
    (envelope-from <helmut@subdiv