Philip Rinn
Philip Rinn
@annejan May I gently ping you on that ... or even propose to release 1.4.0 (Debian freeze is approaching end of this year and I'd love to have a new...
True, one could use the pin version but that would draw it rather useless, as every update of the pin would force the reader of that pin to change the...
From what I see the failure is reproducible - I just triggered a re-test, so we will know soon. As those builds are only done on Debian package upload it's...
Yes, it's reproducible, see https://ci.debian.net/packages/r/rust-zeroize/testing/i386/
I'll try - although, I'm not very fluent in Rust ... In Debian "i386" is the name of the x86 architecture, it now requires a i686 processor - so everything...
Running the test in a i386 chroot gave me this: ``` $ cargo --version cargo 1.56.0 $ RUST_BACKTRACE=full cargo test --all-features [...] ---- zeroize_c_string stdout ---- thread 'zeroize_c_string' panicked at...
Hm, most obvious difference is, I'm testing with `--all-features` and with `rustc` 1.59.0 ... You can reproduce my chroot by this: ``` sudo mmdebstrap --arch=i386 --include=dh-cargo,git sid chroot-i386 sudo systemd-nspawn...
@tarcieri Did you had any chance to reproduce the test failure?
I extracted 8.3.252 from the Android 12 image (Pixel 4a) yesterday and it works fine on GrapheneOS 11 - I guess Aurora Store just picks a wrong variant somehow. Did...
> I just tried installing the same version from APKMirror, and used [SAI](https://github.com/Aefyr/SAI) to install the bundle... > > Got exactly the same issue. Does this mean I have to...