On Tue, Nov 22, 2022 at 2:47 AM the Mulhern <amulhern(a)redhat.com> wrote:
Hi all,
I'm investigating upgrading rust-libudev[1] to 0.3.0.
There are a bunch of considerations and one that l, alas, can not
manage for myself.
I know that two of my packages, stratisd[2], and rust-devicemapper[3]
depend on rust-libudev. I know certainly that they will not update
cleanly.
What I would like to know is how to find out any other packages that
depend on rust-libudev. I would like to investigate, what, if
anything, would be required to update these packages, if they exist.
In a previous email to this list[4], directions were given to use a
script[5] to find this out. Unfortunately, I don't know in what
context to use this script, or what it does, exactly
In another email[5] a new tool, rust-update-set, was introduced. I've
tried that tool out, but it doesn't seem to do what I need, that is
just tell me what packages depend on the package I want to update, in
a particular Fedora release.
What should I do now?
You can use a script like this one:
https://github.com/decathorpe/miscripts/blob/master/cratedeps
It only works for rawhide, but adapting it for stable branches should
be as easy as
- replacing "--repo rawhide --repo rawhide-source" with "--repo fedora
--repo fedora-source --repo updates --repo updates-source"
- replacing "--releasever rawhide" with "--releasever 37" (or 36)
As I've had multiple people asking me about this, would it make sense
to polish up this script and ship it with rust2rpm?
Fabio