-
Notifications
You must be signed in to change notification settings - Fork 500
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
The tokio-tar
dependency seems unmaintained, and it is broken on PowerPC
#3423
Comments
Thanks for raising this issue. I’m working on packaging |
Seems reasonable to switch to a maintained repository. cc @BurntSushi who has more context on auditing Rust packages than me. |
For the record, I've gotten an initial response on the |
I’m trying to build a Fedora package
…and on
At a glance, the allocation on |
It looks like the I think a reasonable conclusion here is that |
I tested |
It turns out that flaky test failures, particularly
This failed on iteration 82. When I tried |
Could you perhaps also try |
We can't really use |
I haven’t attempted to build an RPM package for |
The current version of
uv
depends on the tokio-tar crate:uv/Cargo.toml
Line 132 in 8e86cd0
However, the upstream repository has not seen any activity for 10 months now, and the project seems dead. It is currently broken on PowerPC, and I've filed a pull request to fix it. However, I don't hold my hopes high and in general, the repository has a feeling of a fork of async-tar that wasn't really meant to be maintained (note that it doesn't even have a bug tracker).
That said, krata-tokio-tar seems to be a fork of the fork that has had some recent activity, so I've filed my pull request there as well.
Perhaps a better option would be not to rely on
tokio-tar
(orasync-tar
) at all.The text was updated successfully, but these errors were encountered: