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

  • Bug#1108412: libgstreamer1.0-dev: Multi-Arch: same but differs across a

    From =?UTF-8?Q?Jeremy_B=C3=ADcha?=@21:1/5 to All on Fri Jun 27 23:40:01 2025
    Package: libgstreamer1.0-dev
    Version: 1.26.0-1
    Severity: serious
    Justification: violates Debian policy section 9.1.1
    X-Debbugs-CC: [email protected], [email protected]

    libgstreamer1.0-dev has set Multi-Arch: same, but beginning with
    gstreamer 1.26, Gst-1.0.gir varies across architectures. See https://launchpad.net/bugs/2115325 where this issue was originally
    reported for more details.

    As I noted in the Launchpad bug, I was unable to co-install
    libgstreamer1.0-dev on older Ubuntu releases. Perhaps the
    installability issue was fixed with the various gobject-introspection improvements that were done for trixie (#1029957 etc.).

    Based on https://bugs.debian.org/1029957 , I am filing this as serious
    because architecture-dependent files should not be installed to
    /usr/share/

    Based on my reading of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023591#28 , I guess
    we could try to move Gst-1.0.gir to
    /usr/lib/${DEB_HOST_MULTIARCH}/gir-1.0 for trixie.

    Thank you,
    Jeremy Bícha

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Simon McVittie@21:1/5 to All on Sat Jun 28 12:10:01 2025
    On Fri, 27 Jun 2025 at 17:30:05 -0400, Jeremy B�cha wrote:
    libgstreamer1.0-dev has set Multi-Arch: same, but beginning with
    gstreamer 1.26, Gst-1.0.gir varies across architectures. See >https://launchpad.net/bugs/2115325 where this issue was originally
    reported for more details.

    As I noted in the Launchpad bug, I was unable to co-install >libgstreamer1.0-dev on older Ubuntu releases. Perhaps the
    installability issue was fixed with the various gobject-introspection >improvements that were done for trixie (#1029957 etc.).

    Yes, that probably hid the issue by making it practically impossible to co-install libgstreamer1.0-dev on dissimilar architectures until
    recently.

    Based on my reading of >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023591#28 , I guess
    we could try to move Gst-1.0.gir to
    /usr/lib/${DEB_HOST_MULTIARCH}/gir-1.0 for trixie.

    That comes with a risk of breaking code-generation by tools that have
    not yet been updated to search /usr/lib/${DEB_HOST_MULTIARCH}/gir-1.0,
    which might be an unacceptable risk at this point in the freeze process.

    In *forky*, I think the GStreamer team should move Gst-1.0.gir and GstAudio-1.0.gir to /usr/lib/${DEB_HOST_MULTIARCH}/gir-1.0 (and those
    binding generators will just have to be fixed); but in trixie, I think
    it would be a safer solution to remove Multi-Arch: same from libgstreamer1.0-dev, similar to libgstreamer-plugins-base1.0-dev.

    smcv

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Jeremy_B=C3=ADcha?=@21:1/5 to [email protected] on Sat Jun 28 16:10:01 2025
    On Sat, Jun 28, 2025 at 6:05 AM Simon McVittie <[email protected]> wrote:
    In *forky*, I think the GStreamer team should move Gst-1.0.gir and GstAudio-1.0.gir to /usr/lib/${DEB_HOST_MULTIARCH}/gir-1.0 (and those
    binding generators will just have to be fixed); but in trixie, I think
    it would be a safer solution to remove Multi-Arch: same from libgstreamer1.0-dev, similar to libgstreamer-plugins-base1.0-dev.

    Ok, I filed https://bugs.debian.org/1108432 as a pre-approval unblock
    to remove Multi-Arch: same

    Thank you,
    Jeremy Bícha

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

    Your message dated Mon, 30 Jun 2025 19:34:03 +0000
    with message-id <[email protected]>
    and subject line Bug#1108412: fixed in gstreamer1.0 1.26.2-2
    has caused the Debian Bug report #1108412,
    regarding libgstreamer1.0-dev: Multi-Arch: same but differs across architectures
    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.)


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

    Received: (at submit) by bugs.debian.org; 27 Jun 2025 21:30:47 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
    (2024-03-25) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-15.1 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,HAS_PACKAGE,RCVD_IN_DNSWL_MED,
    RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,RCVD_IN_VALIDITY_RPBL_BLOCKED,
    RCVD_IN_VALIDITY_SAFE_BLOCKED,SPF_HELO_NONE,SPF_PASS autolearn=ham
    autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 19; hammy, 150; neutral, 47; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie,
    0.000-+--H*F:D*canonical.com, 0.000-+--H*rp:D*canonical.com,
    0.000-+--U*smcv, [email protected]
    Return-path: <[email protected]>
    Received: from smtp-r
  • From Debian Bug Tracking System@1:229/2 to All on Mon Jun 30 21:40:02 2025
    From: [email protected]

    This is a multi-part message in MIME format...

    Your message dated Mon, 30 Jun 2025 19:34:16 +0000
    with message-id <[email protected]>
    and subject line Bug#1108412: fixed in gstreamer1.0 1.26.3-2
    has caused the Debian Bug report #1108412,
    regarding libgstreamer1.0-dev: Multi-Arch: same but differs across architectures
    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.)


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

    Received: (at submit) by bugs.debian.org; 27 Jun 2025 21:30:47 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
    (2024-03-25) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-15.1 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,HAS_PACKAGE,RCVD_IN_DNSWL_MED,
    RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,RCVD_IN_VALIDITY_RPBL_BLOCKED,
    RCVD_IN_VALIDITY_SAFE_BLOCKED,SPF_HELO_NONE,SPF_PASS autolearn=ham
    autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 19; hammy, 150; neutral, 47; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie,
    0.000-+--H*F:D*canonical.com, 0.000-+--H*rp:D*canonical.com,
    0.000-+--U*smcv, [email protected]
    Return-path: <[email protected]>
    Received: from smtp-r