Source: rust-dolby-vision
Version: 3.4.0-1
Severity: serious
Tags: ftbfs

rust-dolby-vision fails to build from source when enabling the nocheck
build profile:

|    debian/rules execute_after_dh_auto_build
| make[1]: Entering directory '/build/reproducible-path/rust-dolby-vision-3.4.0'
| 
CARGO_HOME="/build/reproducible-path/rust-dolby-vision-3.4.0/debian/cargo_home" 
\
|         /usr/share/cargo/bin/cargo cbuild --release --destdir=debian/tmp 
--prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --offline
| 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', 'cbuild', '--verbose', '--verbose', 
'--release', '--destdir=debian/tmp', '--prefix=/usr', 
'--libdir=/usr/lib/x86_64-linux-gnu', '--offline'],) {}
| Error: CliError { error: Some(no matching package named `anyhow` found
| location searched: directory source 
`/build/reproducible-path/rust-dolby-vision-3.4.0/debian/cargo_registry` (which 
is replacing registry `crates-io`)
| required by package `dolby_vision v3.4.0 
(/build/reproducible-path/rust-dolby-vision-3.4.0)`
| note: offline mode (via `--offline`) can sometimes cause surprising 
resolution failures
| help: if this error is too confusing you may wish to retry without `--offline`
| 
| Stack backtrace:
|    0: <unknown>
|    1: <unknown>
|    2: <unknown>
|    3: <unknown>
|    4: <unknown>
|    5: <unknown>
|    6: <unknown>
|    7: <unknown>
|    8: <unknown>
|    9: <unknown>
|   10: <unknown>
|   11: <unknown>
|   12: <unknown>
|   13: <unknown>
|   14: __libc_start_main
|   15: <unknown>), exit_code: 101 }
| make[1]: *** [debian/rules:24: execute_after_dh_auto_build] Error 1
| make[1]: Leaving directory '/build/reproducible-path/rust-dolby-vision-3.4.0'
| make: *** [debian/rules:21: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2

Consider reducing <!nocheck> annotations.

Helmut

Reply via email to