From: Leon Romanovsky <leon@kernel.org>
To: Honggang Li <honli@redhat.com>
Cc: Itay Aveksis <itayav@nvidia.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Alaa Hleihel <alaa@nvidia.com>, Jason Gunthorpe <jgg@nvidia.com>,
Doug Ledford <dledford@redhat.com>
Subject: Re: rdma-core spec weird behavior on Fedora
Date: Wed, 10 Feb 2021 13:54:42 +0200 [thread overview]
Message-ID: <20210210115442.GB741034@unreal> (raw)
In-Reply-To: <20210207080649.GB4656@unreal>
On Sun, Feb 07, 2021 at 10:06:49AM +0200, Leon Romanovsky wrote:
> Hi Honggang,
>
> Your commit b02de521022a ("redhat: Remove base package dependency from all sub-packages")
> removes protection from rdma-core when user performs "dnf autoremove".
>
> Before your patch, systemd was dependent on libibverbs and latter
> required rdma-core. After your patch, the last link is lost and
> rdma-core marked as orphaned package.
>
> Any attempt to install rdma-core as standalone package will have the
> following errors, due to the library dependency of udevadm.
> [leonro@c rdma-core]$ ldd /sbin/udevadm | grep verbs
> libibverbs.so.1 => not found
ok, the root cause for that was found - broken installation of libpcap.
Thanks
prev parent reply other threads:[~2021-02-10 11:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 8:06 rdma-core spec weird behavior on Fedora Leon Romanovsky
2021-02-08 12:59 ` Jason Gunthorpe
2021-02-08 13:10 ` Leon Romanovsky
2021-02-08 13:15 ` Alaa Hleihel
2021-02-08 13:26 ` Leon Romanovsky
2021-02-08 13:21 ` Jason Gunthorpe
2021-02-08 13:31 ` Leon Romanovsky
2021-02-08 14:08 ` Jason Gunthorpe
2021-02-08 14:31 ` Leon Romanovsky
2021-02-08 15:35 ` Jason Gunthorpe
2021-02-08 15:59 ` Leon Romanovsky
2021-02-08 18:18 ` Jason Gunthorpe
2021-02-10 11:54 ` Leon Romanovsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210210115442.GB741034@unreal \
--to=leon@kernel.org \
--cc=alaa@nvidia.com \
--cc=dledford@redhat.com \
--cc=honli@redhat.com \
--cc=itayav@nvidia.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox