https://bugzilla.redhat.com/show_bug.cgi?id=2299712 --- Comment #16 from Ben Beasley <code@xxxxxxxxxxxxxxxxxx> --- (In reply to Ben Beasley from comment #15) > I filed https://github.com/Majored/rs-async-zip/issues/146, and async_zip > upstream removed the problematic document in > https://github.com/Majored/rs-async-zip/commit/ > 2d841d600c6d509cb4ecc611001ec339876ca6c9. I’m working on a solution for > rust-async_zip. For the fork https://github.com/charliermarsh/rs-async-zip, > I’m going to have to resort to email or something, since the fork has no > issue tracker and pull requests are limited to collaborators. I have added a script to filter the snapshot bundled in uv to avoid uploading the problematic SPECIFICATION.md to the lookaside cache or including it in source RPMs. Since I filed https://github.com/astral-sh/uv/issues/5556 upstream asking uv to update their async_zip fork, and upstream tends to be very responsive, I expect this will not be necessary for long and we will be able to go back to just using a snapshot archive directly in a near-future release. In fact, I wouldn’t be surprised if this is handled upstream before I finish preparing a new submission for review. I am fixing the rust-async_zip package via https://src.fedoraproject.org/rpms/rust-async_zip/pull-request/1, and I will backport the same fix to the compat package https://src.fedoraproject.org/rpms/rust-async_zip0.0.15 . These are not used for uv, but the fix is still important. ----- I reviewed the archives for the bundled pubsub and reqwest-retry/reqwest-middleware crates and didn’t find anything new, problematic, or notable. I think %{cargo_license_summary} should already be handling their licenses, but I added explicit spec-file comments documenting them anyway. ----- I am currently tracking upstream release 0.2.30, with no significant packaging or dependency changes from the original submission. ----- I still need to audit and document possibly-bundled sources in the main uv archive before uploading a new submission. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2299712 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202299712%23c16 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
