All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Honggang Li <honli@redhat.com>, Itay Aveksis <itayav@nvidia.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>,
	Alaa Hleihel <alaa@nvidia.com>,
	Doug Ledford <dledford@redhat.com>
Subject: Re: rdma-core spec weird behavior on Fedora
Date: Mon, 8 Feb 2021 08:59:00 -0400	[thread overview]
Message-ID: <20210208125900.GX4247@nvidia.com> (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

well that makes no sense, since when is udevadm connected to
libibverbs?

$ ldd `which udevadm`
	linux-vdso.so.1 (0x00007ffcc09ef000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f394bec3000)
	libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x00007f394bea8000)
	libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x00007f394be9d000)
	libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f394be46000)
	libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f394be1b000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f394bdf8000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f394c1b6000)
	liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f394bdcd000)
	libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f394baf7000)
	libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007f394ba67000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f394ba61000)

Jason

  reply	other threads:[~2021-02-08 13:00 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 [this message]
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=20210208125900.GX4247@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alaa@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=honli@redhat.com \
    --cc=itayav@nvidia.com \
    --cc=leon@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.