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

  • Bug#1104982: rust-graphene-sys FTBFS with the nocheck build profile

    From Helmut Grohne@21:1/5 to All on Fri May 9 14:10:01 2025
    Source: rust-graphene-sys
    Version: 0.20.7-1
    Severity: serious
    Tags: ftbfs

    rust-graphene-sys fails to build from source when enabling the nocheck
    build profile. A build ends as follows:

    debian/rules execute_before_dh_auto_build
    make[1]: Entering directory '/build/reproducible-path/rust-graphene-sys-0.20.7' cp /usr/share/gir-1.0/GObject-2.0.gir /build/reproducible-path/rust-graphene-sys-0.20.7
    cp /usr/share/gir-1.0/GLib-2.0.gir /build/reproducible-path/rust-graphene-sys-0.20.7
    cp /usr/share/gir-1.0/Graphene-1.0.gir /build/reproducible-path/rust-graphene-sys-0.20.7
    cp: cannot stat '/usr/share/gir-1.0/Graphene-1.0.gir': No such file or directory
    make[1]: *** [debian/rules:10: execute_before_dh_auto_build] Error 1
    make[1]: Leaving directory '/build/reproducible-path/rust-graphene-sys-0.20.7' make: *** [debian/rules:3: binary] Error 2
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

    Consider reviewing <!nocheck> annotations in Build-Depends.

    Helmut

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

    Your message dated Sat, 10 May 2025 13:35:02 +0000
    with message-id <E1uDkM2-00Cqva-4E@fasolo.debian.org>
    and subject line Bug#1104982: fixed in rust-graphene-sys 0.20.7-2
    has caused the Debian Bug report #1104982,
    regarding rust-graphene-sys FTBFS with the nocheck build profile
    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.)


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

    Received: (at submit) by bugs.debian.org; 9 May 2025 12:08:00 +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=-2.6 required=4.0 tests=BAYES_00,DATE_IN_PAST_03_06,
    DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,
    RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,RCVD_IN_VALIDITY_RPBL_BLOCKED,
    SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 12; hammy, 112; neutral, 23; spammy,
    0. spammytokens: hammytokens: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, 0.000-+--H*rp:D*subdivi.de
    Return-path: <helmut@subdivi.de>
    Received: from isilmar-4.linta.de ([136.243.71.142]:40208)
    by buxtehude.debian.org with esmtps (TLS1.3:EC