Does any rust dev or package maintainer has found a viable approach to downstream patch management? E.g. Arch, Fedora, Alpine and probably most others use diff patches along with the "package recipe", as this allows maintaining everything in one place.

E.g. rust package foo depending on crate bar: If there is a patch for foo, diffs work fine. But what if I need to patch bar? Note that patching in a `[patch.crates-io]` entry is manageable, having that point to a repo is not.

#rustlang #distro

@maribu 🤔 how many crates in pure Rust would require patches?

@michalfita I cannot really answer that. In Alpine there are currently 661 APKBUILDs that contain the word `cargo`, 221 of those contain `.patch` and in total there are 1017 matches of `.patch` in those 221 packages. Due to the crude method this will be an overestimation, but it strongly suggests that downstream patches for rust packages is not a one-off.

For the problem at hand the issue is in rust source: https://github.com/hoodie/notify-rust/issues/253

panic when closing manually dismissed notification on zbus · Issue #253 · hoodie/notify-rust

According to the docs, a call to CloseNotification returns a dbus error if the notification no longer exists. The dbus implementation just ignores this error notify-rust/src/xdg/dbus_rs.rs Line 97 ...

GitHub