Source: rust-wl-nl80211
Version: 0.2.0-1
Severity: serious
X-Debbugs-Cc: Reinhard Tartler <siret...@tauware.de>

https://tracker.debian.org/pkg/rust-wl-nl80211

Issues preventing migration:
∙ ∙ autopkgtest for rust-wl-nl80211/0.2.0-1: amd64: Regression or new test ♻, 
arm64: Regression or new test ♻, armel: Regression or new test ♻, armhf: 
Regression or new test ♻, i386: Regression or new test ♻, ppc64el: Regression 
or new test ♻, riscv64: Regression or new test ♻, s390x: Regression or new test 
♻


...
186s error[E0425]: cannot find function `new_connection` in crate `wl_nl80211`
186s   --> examples/dump_nl80211_wiphy.rs:14:47
186s    |
186s 14 |     let (connection, handle, _) = 
wl_nl80211::new_connection().unwrap();
186s    |                                               ^^^^^^^^^^^^^^ not 
found in `wl_nl80211`
186s    |
186s note: found an item that was configured out
186s   --> /usr/share/cargo/registry/wl-nl80211-0.2.0/src/lib.rs:28:27
186s note: the item is gated behind the `tokio_socket` feature
186s   --> /usr/share/cargo/registry/wl-nl80211-0.2.0/src/lib.rs:27:7
186s 
186s error[E0425]: cannot find function `new_connection` in crate `wl_nl80211`
186s   --> examples/dump_nl80211_station.rs:29:47
186s    |
186s 29 |     let (connection, handle, _) = 
wl_nl80211::new_connection().unwrap();
186s    |                                               ^^^^^^^^^^^^^^ not 
found in `wl_nl80211`
186s    |
186s note: found an item that was configured out
186s   --> /usr/share/cargo/registry/wl-nl80211-0.2.0/src/lib.rs:28:27
186s note: the item is gated behind the `tokio_socket` feature
186s   --> /usr/share/cargo/registry/wl-nl80211-0.2.0/src/lib.rs:27:7
186s 
186s error[E0425]: cannot find function `new_connection` in crate `wl_nl80211`
186s   --> examples/dump_nl80211_iface.rs:14:47
186s    |
186s 14 |     let (connection, handle, _) = 
wl_nl80211::new_connection().unwrap();
186s    |                                               ^^^^^^^^^^^^^^ not 
found in `wl_nl80211`
186s    |
186s note: found an item that was configured out
186s   --> /usr/share/cargo/registry/wl-nl80211-0.2.0/src/lib.rs:28:27
186s note: the item is gated behind the `tokio_socket` feature
186s   --> /usr/share/cargo/registry/wl-nl80211-0.2.0/src/lib.rs:27:7
186s 
186s error[E0599]: no method named `enable_io` found for struct 
`tokio::runtime::Builder` in the current scope
186s  --> examples/dump_nl80211_wiphy.rs:7:10
186s   |
186s 6 |       let rt = tokio::runtime::Builder::new_current_thread()
186s   |  ______________-
186s 7 | |         .enable_io()
186s   | |         -^^^^^^^^^ private field, not a method
186s   | |_________|
186s   |
186s   |
186s help: there is a method `enable_time` with a similar name
186s   |
186s 7 |         .enable_time()
186s   |          ~~~~~~~~~~~
186s 
186s error[E0599]: no method named `enable_io` found for struct 
`tokio::runtime::Builder` in the current scope
186s  --> examples/dump_nl80211_iface.rs:7:10
186s   |
186s 6 |       let rt = tokio::runtime::Builder::new_current_thread()
186s   |  ______________-
186s 7 | |         .enable_io()
186s   | |         -^^^^^^^^^ private field, not a method
186s   | |_________|
186s   |
186s   |
186s help: there is a method `enable_time` with a similar name
186s   |
186s 7 |         .enable_time()
186s   |          ~~~~~~~~~~~
186s 
186s error[E0599]: no method named `enable_io` found for struct 
`tokio::runtime::Builder` in the current scope
186s   --> examples/dump_nl80211_station.rs:20:10
186s    |
186s 19 |       let rt = tokio::runtime::Builder::new_current_thread()
186s    |  ______________-
186s 20 | |         .enable_io()
186s    | |         -^^^^^^^^^ private field, not a method
186s    | |_________|
186s    |
186s    |
186s help: there is a method `enable_time` with a similar name
186s    |
186s 20 |         .enable_time()
186s    |          ~~~~~~~~~~~
186s 
186s Some errors have detailed explanations: E0425, E0599.
186s For more information about an error, try `rustc --explain E0425`.
186s error: could not compile `wl-nl80211` (example "dump_nl80211_wiphy" test) 
due to 2 previous errors
...

Reply via email to