tokio-xmpp: Fix build on insecure-tcp

Emmanuel Gil Peyrot created 11 months ago

insecure-tcp requires the io-util feature of tokio, so let’s enable it
there.

Fixes this error:
5   | use tokio::{io::BufStream, net::TcpStream};
    |             ^^^^^^^^^^^^^ no `BufStream` in `io`

Change summary

tokio-xmpp/Cargo.toml | 2 +-
tokio-xmpp/ChangeLog  | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)

Detailed changes

tokio-xmpp/Cargo.toml

@@ -52,7 +52,7 @@ tls-rust-webpki-roots = ["tls-rust", "webpki-roots"]
 tls-native = ["tokio-native-tls", "native-tls"]
 starttls-native = ["starttls", "tls-native"]
 starttls-rust = ["starttls", "tls-rust"]
-insecure-tcp = []
+insecure-tcp = ["tokio/io-util"]
 syntax-highlighting = ["syntect"]
 # Enable serde support in jid crate
 serde = [ "xmpp-parsers/serde" ]

tokio-xmpp/ChangeLog

@@ -33,6 +33,7 @@ XXXX-YY-ZZ RELEASER <[e-mail]>
         actual encryption and decryption to the kernel, which in turn can
         delegate it to a hardware implementations if available.  This depends
         on the `tls-rust-ktls` feature. (!458, !490)
+      - Building with insecure-tcp and no other feature got fixed.
 
 Version 4.0.0:
 2024-07-26 Maxime “pep” Buquet <[e-mail]>