Control: notfound -1 rustc/1.82.0+dfsg1-2 Control: found -1 libgit2/1.8.4+ds-2 Control: reassign -1 libgit2/1.8.4+ds-2 Control: severity -1 grave Control: merge -1 1088281 Control: affects 1088281 rustc
On Tue, Nov 26, 2024, at 6:29 PM, Justus Winter wrote: > Package: cargo > Version: 1.82.0+dfsg1-2 > Severity: normal > > Dear Maintainer, > > cargo from Debian fails to clone git repositories from github.com, for > example: > > % cargo --version > cargo 1.82.0 (8f40fc59f 2024-08-21) > % cargo install --git https://github.com/meta-rust/rust-hello-world > Updating git repository > `https://github.com/meta-rust/rust-hello-world` > error: failed to clone into: > /home/teythoon/.cargo/git/db/rust-hello-world-1fbd72c4e19584b8 > > Caused by: > network failure seems to have happened > if a proxy or similar is necessary `net.git-fetch-with-cli` may help here > https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli > > Caused by: > SSL error: 0xffff8880 - SSL - A fatal alert message was received from > our peer; class=Ssl (16) > > In contrast, cargo 1.82 from rustup works just fine. This, in > combination with the error message, makes me think that the TLS > handshake failed, perhaps because client and server couldn't agree on > a cipher suite, and that the difference to rustup's cargo is a build > option. Hi! Thanks for your report. This seems to actually be a regression in libgit2 (as packaged in Debian) - downgrading to http://snapshot.debian.org/package/libgit2/1.8.2~rc1%2Bds2-1/#libgit2-1.8_1.8.2:7e:rc1:2b:ds2-1 makes the problem go away for me. Merging with the already filed bug on the libgit2 side accordingly - I'll see about adding autopkgtests to rustc/cargo to catch such issues faster in the future! Fabian