Bug#1105134: cyme FTBFS with the nocheck build profile
From
Helmut Grohne@21:1/5 to
All on Mon May 12 07:00:01 2025
Source: cyme
Version: 2.2.0+dfsg-1
Severity: serious
Tags: ftbfs
cyme fails to build from source when enabling the nocheck build profile.
A build ends as follows:
dh_auto_configure --buildsystem=rust
/bin/sh: 1: jq: not found
/bin/sh: 1: jq: not found
/usr/share/dh-rust/bin/cargo prepare-debian debian/cargo_registry debian cargo wrapper: options, profiles, parallel, lto: ['nocheck', 'parallel=8'] ['nocheck'] ['-j8'] 0
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into /build/reproducible-path/cyme-2.2.0+dfsg/debian/cargo_registry/
cargo update
error: no matching package named `assert-json-diff` found
location searched: directory source `/build/reproducible-path/cyme-2.2.0+dfsg/debian/cargo_registry` (which is replacing registry `crates-io`)
required by package `cyme v2.2.0 (/build/reproducible-path/cyme-2.2.0+dfsg)` dh_auto_configure: error: cargo update returned exit code 101
make: *** [debian/rules:32: binary] Error 25
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)