linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-core] rpm: BR: python for libmlx5
Date: Wed, 22 Mar 2017 21:47:28 -0600	[thread overview]
Message-ID: <20170323034728.GA24582@obsidianresearch.com> (raw)
In-Reply-To: <20170323021246.35786-1-jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Wed, Mar 22, 2017 at 10:12:46PM -0400, Jarod Wilson wrote:
> The relpath python script added in commit 07764bc805ba requires python to
> run, thus we must BuildRequires: python in the rpm spec files, or the
> build will fail in minimal environments (such as mock).
> 
> Fixes: 07764bc805ba ("mlx5: Export mlx5 direct verbs interface")
> CC: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> Signed-off-by: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>  rdma-core.spec        | 1 +
>  redhat/rdma-core.spec | 1 +
>  2 files changed, 2 insertions(+)

I suspect we need to add python to debian/control as well, for the
same reasons.

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

  parent reply	other threads:[~2017-03-23  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  2:12 [PATCH rdma-core] rpm: BR: python for libmlx5 Jarod Wilson
     [not found] ` <20170323021246.35786-1-jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-23  3:47   ` Jason Gunthorpe [this message]
2017-03-23 16:58   ` 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=20170323034728.GA24582@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=leonro-VPRAkNaXOzVWk0Htik3J/w@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;
as well as URLs for NNTP newsgroup(s).