• Bug#1109070: rust-sequoia-octopus-librnp FTBFS with the nocheck build p

    From Helmut Grohne@21:1/5 to All on Thu Jul 10 21:30:01 2025
    Package: rust-sequoia-octopus-librnp
    Version: 1.11.1-1
    Severity: serious
    Tags: ftbfs

    Hi,

    rust-sequoia-octopus-librnp fails to build from source when enabling the nocheck build profile.

    | /usr/share/cargo/bin/cargo build --release
    | debian cargo wrapper: options = ['parallel=8', 'nocheck'], profiles = ['nocheck'], parallel = ['-j8'], lto =
    | debian cargo wrapper: rust_type = x86_64-unknown-linux-gnu, gnu_type = x86_64-linux-gnu
    | debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j8', '--target', 'x86_64-unknown-linux-gnu', '--release'],) {}
    | error: no matching package named `anyhow` found
    | location searched: directory source `/<<PKGBUILDDIR>>/registry` (which is replacing registry `crates-io`)
    | required by package `sequoia-octopus-librnp v1.11.1 (/<<PKGBUILDDIR>>)`
    | make[1]: *** [debian/rules:26: override_dh_auto_build] Error 101
    | make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    | make: *** [debian/rules:16: binary] Error 2
    | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

    The easy way here is to delete <!nocheck> annotations from debian/control and that is likely what should be done for trixie. Revisit them for forky.

    Helmut

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)