Package: rust-urlshortener
Version: 3.0.2-1
Severity: grave
Justification for severity: Policy violation
During a rebuild of Debian testing, we ran into this test failing during an
sbuild controlled build on a VM with limit network connectivity (only
configured APT repositories usable). See log excerpt below.
This network access is a violation of policy section 4.9:
For packages in the main archive, required targets must not attempt network
access, except, via loopback interface, to services on the build host that
have been started by the build.
Inspection of the source reveals that this test indeed tries to reach
targets in the internet.
---- client::tests::providers stdout ----
IsGd -> Connection
VGd -> Connection
BamBz -> Connection
TinyPh -> Connection
FifoCc -> Connection
SCoop -> Connection
Bmeo -> Connection
UrlShortenerIo -> Connection
HmmRs -> Connection
TnyIm -> Connection
SirBz -> Connection
Rlu -> Connection
HecSu -> Connection
Abv8 -> Connection
TinyUrl -> Connection
PsbeCo -> Connection
NowLinks -> Connection
thread 'client::tests::providers' panicked at 'There are no valid providers
to use.', src/client.rs:158:9
stack backtrace:
0: std::panicking::begin_panic
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:610:12
1: urlshortener::client::tests::providers
at
/usr/share/cargo/registry/urlshortener-3.0.2/src/client.rs:158:9
2: urlshortener::client::tests::providers::{{closure}}
at
/usr/share/cargo/registry/urlshortener-3.0.2/src/client.rs:144:20
3: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
