Source: rust-nodrop-union
Version: 0.1.9-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> export RUSTC_BOOTSTRAP=1; \
> dh_auto_test
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling nodrop-union v0.1.9 (/<>)
> Running `CARGO_PKG_VERSION_PRE=
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_VERSION_MINOR=1 CARGO=/usr/bin/cargo CARGO_PKG_HOMEPAGE=
> CARGO_PKG_REPOSITORY='https://github.com/bluss/arrayvec'
> CARGO_PKG_NAME=nodrop-union CARGO_PKG_AUTHORS=bluss
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_VERSION=0.1.9
> CARGO_PKG_DESCRIPTION='A wrapper type to inhibit drop (destructor).
> Implementation crate for nodrop, the untagged unions implementation (which is
> unstable / requires nightly) as of this writing.' CARGO_PKG_VERSION_PATCH=9
> CARGO_PKG_VERSION_MAJOR=0 rustc --crate-name nodrop_union src/lib.rs --color
> never --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
> metadata=572ee23bdbbb16ca -C extra-filename=-572ee23bdbbb16ca --out-dir
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target
> x86_64-unknown-linux-gnu -C
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
> -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
> dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn
> -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix
> /<>=/usr/share/cargo/registry/nodrop-union-0.1.9`
> warning: unknown lint: `unions_with_drop_fields`
> --> src/lib.rs:29:9
>|
> 29 | #[allow(unions_with_drop_fields)]
>| ^^^
>|
>= note: `#[warn(unknown_lints)]` on by default
>
> error[E0740]: unions may not contain fields that need dropping
> --> src/lib.rs:32:5
>|
> 32 | value: T,
>|
>|
> note: `std::mem::ManuallyDrop` can be used to wrap the type
> --> src/lib.rs:32:5
>|
> 32 | value: T,
>|
>
> error: aborting due to previous error
>
> For more information about this error, try `rustc --explain E0740`.
> error: could not compile `nodrop-union`.
>
> Caused by:
> process didn't exit successfully: `CARGO_PKG_VERSION_PRE=
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_VERSION_MINOR=1 CARGO=/usr/bin/cargo CARGO_PKG_HOMEPAGE=
> CARGO_PKG_REPOSITORY='https://github.com/bluss/arrayvec'
> CARGO_PKG_NAME=nodrop-union CARGO_PKG_AUTHORS=bluss
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_VERSION=0.1.9
> CARGO_PKG_DESCRIPTION='A wrapper type to inhibit drop (destructor).
> Implementation crate for nodrop, the untagged unions implementation (which is
> unstable / requires nightly) as of this writing.' CARGO_PKG_VERSION_PATCH=9
> CARGO_PKG_VERSION_MAJOR=0 rustc --crate-name nodrop_union src/lib.rs --color
> never --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
> metadata=572ee23bdbbb16ca -C extra-filename=-572ee23bdbbb16ca --out-dir
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target
> x86_64-unknown-linux-gnu -C
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
> -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L
> dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn
> -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix
> /<>=/usr/share/cargo/registry/nodrop-union-0.1.9` (exit code: 1)
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/rust-nodrop-union_0.1.9-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
