We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
This is a follow-up to #2329
There was a bug in the NetBSD implementation for getmntinfo in the libc crate which has been fixed and a new version of libc is released. This bug broke deleting files on file systems except /, since trash-rs didn't properly recognize that it was not on the same file system, and trashing to a different file system is not supported.
/
Please run cargo upgrade so libc 0.2.170 is pulled in.
cargo upgrade
Thank you!
The text was updated successfully, but these errors were encountered:
Hey @0-wiz-0, I noticed that you did not correctly follow the issue template. Please ensure that:
yazi --debug
Issues with needs info will be marked ready once edited with the proper content, or closed after 2 days of inactivity.
needs info
Sorry, something went wrong.
I checked and Cargo.lock currently requires 0.2.169
trash
libc
Thank you for your follow-up update @0-wiz-0!
I've updated libc and trash to the latest in #2388
Thank you for fixing this so quickly!
Successfully merging a pull request may close this issue.
This is a follow-up to #2329
There was a bug in the NetBSD implementation for getmntinfo in the libc crate which has been fixed and a new version of libc is released. This bug broke deleting files on file systems except
/
, since trash-rs didn't properly recognize that it was not on the same file system, and trashing to a different file system is not supported.Please run
cargo upgrade
so libc 0.2.170 is pulled in.Thank you!
The text was updated successfully, but these errors were encountered: