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: rdma-core spec weird behavior on Fedora
Date: Sun, 7 Feb 2021 10:06:49 +0200 [thread overview]
Message-ID: <20210207080649.GB4656@unreal> (raw)
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
[leonro@c rdma-core]$ sudo dnf install /tmp/rdma-core/RPMS/x86_64/rdma-core-34.0-1.fc32.x86_64.rpm
Last metadata expiration check: 1:29:40 ago on Sun 07 Feb 2021 07:29:13 AM IST.
Dependencies resolved.
======================================================================================================================
Package Architecture Version Repository Size
======================================================================================================================
Installing:
rdma-core x86_64 34.0-1.fc32 @commandline 54 k
Transaction Summary
======================================================================================================================
Install 1 Package
Total size: 54 k
Installed size: 121 k
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : rdma-core-34.0-1.fc32.x86_64 1/1
Running scriptlet: rdma-core-34.0-1.fc32.x86_64 1/1
/sbin/udevadm: error while loading shared libraries: libibverbs.so.1: cannot open shared object file: No such file or directory
/sbin/udevadm: error while loading shared libraries: libibverbs.so.1: cannot open shared object file: No such file or directory
/sbin/udevadm: error while loading shared libraries: libibverbs.so.1: cannot open shared object file: No such file or directory
/usr/bin/udevadm: error while loading shared libraries: libibverbs.so.1: cannot open shared object file: No such file or directory
/usr/bin/systemctl: error while loading shared libraries: libibverbs.so.1: cannot open shared object file: No such file or directory
warning: %triggerin(systemd-245.8-2.fc32.x86_64) scriptlet failed, exit status 127
Error in <unknown> scriptlet in rpm package rdma-core
Verifying : rdma-core-34.0-1.fc32.x86_64 1/1
Installed:
rdma-core-34.0-1.fc32.x86_64
Complete!
--------------------------------------------------------------------------------------
I think that the right solution is to make rdma-core meta-package as we
wanted it from the beginning when created rdma-core repo.
Thanks
next reply other threads:[~2021-02-07 8:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 8:06 Leon Romanovsky [this message]
2021-02-08 12:59 ` rdma-core spec weird behavior on Fedora 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
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=20210207080649.GB4656@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