From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core 1/6] debian: Let libibverbs1 16 break ibverbs-providers 15
Date: Tue, 14 Nov 2017 13:39:39 -0700 [thread overview]
Message-ID: <20171114203939.GT4263@ziepe.ca> (raw)
In-Reply-To: <20171114200247.25890-2-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
On Tue, Nov 14, 2017 at 09:02:42PM +0100, Benjamin Drung wrote:
> ibverbs-providers uses the private symbols of libibverbs1. Thus
> libibverbs1 will not work with an old version version of
> ibverbs-providers if the private symbol version is bumped.
>
> Bump the ibverbs-providers version that libibverbs1 breaks which was
> forgotten on the symbol version bump. See also commit
> 611b7cc3b8e0d79aa986f042f486fccc95d73679. Append a tilde to support
> the lower version numbers (e.g. 16~201711132208) in the PPA builds.
This seems strange to me, we don't really need Breaks semantics here.
Shouldn't we do something like:
Package: ibverbs-providers
Depends: [..], libibverbs1 (= ${binary:Version}),
?
We really do not want to encourage mixing and matching versions.
IIRC the existing breaks is only because of how the new packages
interact with the legacy ones??
--
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-11-14 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 20:02 [PATCH rdma-core 0/6] More Debian packaging cleanup Benjamin Drung
[not found] ` <20171114200247.25890-1-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 20:02 ` [PATCH rdma-core 1/6] debian: Let libibverbs1 16 break ibverbs-providers 15 Benjamin Drung
[not found] ` <20171114200247.25890-2-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 20:39 ` Jason Gunthorpe [this message]
[not found] ` <20171114203939.GT4263-uk2M96/98Pc@public.gmane.org>
2017-11-15 9:20 ` Benjamin Drung
2017-11-14 20:02 ` [PATCH rdma-core 2/6] debian: Replace priority extra by optional Benjamin Drung
2017-11-14 20:02 ` [PATCH rdma-core 3/6] debian: Relax dh-systemd build dependency Benjamin Drung
2017-11-14 20:02 ` [PATCH rdma-core 4/6] debian: Bump Standards-Version to 4.1.1 Benjamin Drung
2017-11-14 20:02 ` [PATCH rdma-core 5/6] debian: Drop lintian overrides for false positives Benjamin Drung
2017-11-14 20:02 ` [PATCH rdma-core 6/6] debian: Run wrap-and-sort Benjamin Drung
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=20171114203939.GT4263@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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