On Tue, Nov 22, 2022 at 3:23 PM Fabio Valentini <decathorpe(a)gmail.com> wrote:
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
I just noticed that I forgot to paste the actual results:
$ cratedeps libudev
rust-devicemapper-0:0.32.2-1.fc38.src
rust-libudev+default-devel-0:0.2.0-14.fc37.noarch
stratisd-0:3.3.0-1.fc38.src
So rust-devicemapper and stratisd are indeed the only two packages
that depend on rust-libudev (at least on rawhide).
Fabio