From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Ram Amrani <ram.amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
Adit Ranadive <aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
RDMA mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: qedr and vmw_pvrdma are not packaged in rdma-core
Date: Thu, 2 Feb 2017 09:38:31 -0700 [thread overview]
Message-ID: <20170202163831.GA10782@obsidianresearch.com> (raw)
In-Reply-To: <20170202062628.GZ6005-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
On Thu, Feb 02, 2017 at 08:26:28AM +0200, Leon Romanovsky wrote:
> Hi Ram and Adit,
>
> I want to bring to your attention that qedr and vmw_pvrdma drivers are
> missing from various package files available in rdma-core.
It is handled automatically, can't be missing:
$ buildlib/cbuild pkg jessie
$ dpkg-deb -c ../ibverbs-providers_13-1_amd64.deb
-rw-r--r-- root/root 35024 2017-02-02 09:31 ./usr/lib/x86_64-linux-gnu/libibverbs/libqedr-rdmav2.so
-rw-r--r-- root/root 18600 2017-02-02 09:31 ./usr/lib/x86_64-linux-gnu/libibverbs/libvmw_pvrdma-rdmav2.so
$ buildlib/cbuild pkg fc25
$ rpm -q -l -p ../libibverbs-13-1.fc25.x86_64.rpm
/usr/lib64/libibverbs/libqedr-rdmav2.so
/usr/lib64/libibverbs/libvmw_pvrdma-rdmav2.so
> RedHat has different scheme with explicit declaration, from redhat/rdma-core.spec
> 98 Provides: librxe = %{version}-%{release}
> 99 Obsoletes: librxe < %{version}-%{release}
This is only for things that were previously packaged in redhat, qedr
and vmw_pvrdma have not been, so they should not include those
stanzas. It is similar to the obsoletes/replaces in debian/control.
> But it is not installation only. for example debian/copyright
> doesn't have information about providers/vmw_pvrdma.
Yes, this needs to be fixed..
This is why I was hoping for an automatic script to maintain this file :)
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-02 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 6:26 qedr and vmw_pvrdma are not packaged in rdma-core Leon Romanovsky
[not found] ` <20170202062628.GZ6005-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-02-02 8:13 ` Christoph Hellwig
[not found] ` <20170202081311.GA10429-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-02-02 9:17 ` Benjamin Drung
[not found] ` <1486027076.4257.30.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-02-02 9:39 ` Leon Romanovsky
2017-02-02 16:38 ` Jason Gunthorpe [this message]
[not found] ` <20170202163831.GA10782-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-02-02 17:44 ` Leon Romanovsky
[not found] ` <20170202174415.GC6005-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-02-02 17:49 ` Jason Gunthorpe
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=20170202163831.GA10782@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=aditr-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ram.amrani-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.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