-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update insecure dependencies #22
Comments
I gave this a try myself, and it got hairy rather quickly :D The bump in I did not want to do a PATH lookup, so I tried calling |
Oh yeah, right. I probably postponed updating
Uh oh, that sounds like my mistake when I was writing the
I guess just calling
Yeah, unfortunately those tests are pretty flaky (#1). Perhaps the new wayland-rs will eventually allow making them more robust; I haven't looked into it yet. |
It was the latter. I managed to make it work with
No, distributions vary rather wildly in their locations for binaries. Hardcoding absolute paths should be avoided. |
This crate currently depends on
nix
0.18 and transitively onnix
0.17. Apparently, those are potentially insecure: nix-rust/nix#1541 https://rustsec.org/advisories/RUSTSEC-2021-0119 . According to the advisory, this can be fixed by simply updating the affected dependencies.The text was updated successfully, but these errors were encountered: