I find Michel Lind’s script fedrq-cratedeps-verbose.sh quite useful, too. It takes a crate name (or a compat name, like foo0.4), and it shows the actual version bounds from the reverse dependencies. It’s “just” a thin wrapper around fedrq, but I find it helpful and reliable.
https://git.sr.ht/~michel-slm/fedora-packaging-scripts/tree/main/item/fedrq-...
There’s also a similar fedrq-pydeps-verbose.sh, which is an even thinner wrapper around fedrq. Still, it provides a useful formula for getting versioned reverse dependency information for a PyPI canonical name.
On 4/14/25 9:42 AM, the Mulhern via Rust wrote:
I ran into much the same problem for much the same reason recently, i.e., I didn't believe that there were any other dependents on a package.
fedrq will help a bit with that if you know the magic way to invoke it.
This is an example:
fedrq whatrequires-src 'rust-libcryptsetup-rs*' -b
fido-device-onboard-0.5.4-1.fc43.src rust-libcryptsetup-rs-0.12.0-1.fc42.src rust-libcryptsetup-rs+default-devel-0.12.0-1.fc42.noarch rust-libcryptsetup-rs+mutex-devel-0.12.0-1.fc42.noarch rust-libcryptsetup-rs-devel-0.12.0-1.fc42.noarch rust-libcryptsetup-rs-sys+default-devel-0.4.0-3.fc42.noarch rust-libcryptsetup-rs0.11-0.11.2-1.fc43.src rust-libcryptsetup-rs0.11+default-devel-0.11.2-1.fc43.noarch rust-libcryptsetup-rs0.11+mutex-devel-0.11.2-1.fc43.noarch rust-libcryptsetup-rs0.11-devel-0.11.2-1.fc43.noarch stratisd-3.8.0-1.fc43.src
fedrq's underlying model continues to perplex me, but it works better than anything else I know for finding out this info.
There are significant man pages, with examples, and that certainly helps.
- mulhern
On Mon, Apr 14, 2025 at 4:34 AM Gris Ge fge@redhat.com wrote:
On Sun, Apr 13, 2025 at 03:27:16PM +0200, Fabio Valentini wrote:
This update has since also been built and pushed to Fedora 41, but the additional compat package for netlink-packet-route wasn't included in it. I have now submitted the missing build to Fedora 41 too, and made a buildroot override for it too to fix FTBFS / FTI issues caused by the incomplete F41 update.
In the future, please check dependent packages when pushing "breaking" updates for Rust crates like this one, and coordinate with maintainers of dependent packages. The fact that this was pushed to Fedora 41 as-is even though this was already pointed out to have been a problem on Rawhide and Fedora 42 isn't great, either.
Fabio
Hi Fabio,
Thanks for fix!
I was expecting nisport and nmstate the only user of `rust-netlink-packet-route`. Will work with dependent package maintainer(s) for breaking changes in the future.
-- Gris Ge
-- On all the line a sudden vengeance waits, And frequent hearses shall besiege your gates. -- Alexander Pope, To the Memory of an Unfortunate Lady.