Package: debcargo Version: 2.4.4 Control: affects -1 src:rust-sequoia-openpgp
I'm updating sequoia-openpgp's debcargo.toml to currently contain the following: --- # sequoia always needs at least one crypto backend and nettle is # currently the only crypto-backend available on debian systems. # Since crypto-nettle is included in the default, and in # --all-features we should expect those tests to succeed as well. # See https://bugs.debian.org/985741 for more info. [packages.lib] test_is_broken = true [packages."lib+crypto-nettle"] test_is_broken = false [packages."lib+default"] test_is_broken = false [packages."lib+@"] test_is_broken = false --- I'd expect this to produce a batch of tests where the only tests *not* marked flakey are those tests that include the crypto-nettle feature (see also #985741). However, debcargo 2.4.4 generates a debian/tests/control file that includes this stanza (note that the "flaky" restriction is included): --- Test-Command: /usr/share/cargo/bin/cargo-auto-test sequoia-openpgp 1.1.0 --all-targets --all-features Features: test-name=rust-sequoia-openpgp:@ Depends: dh-cargo (>= 18), librust-quickcheck-0.9-dev, librust-rand-0.7-dev, librust-rpassword-5+default-dev, @ Restrictions: allow-stderr, skip-not-installable, flaky --- I'll try to override this using the *.debcargo.hint mechanism, but i don't understand why the [packages."lib+@"] special section isn't useful for stripping the "flaky" restriction from the --all-features test, as it appears to be documented in the example debcargo.toml. --dkg
signature.asc
Description: PGP signature