From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Knut Omang <knut.omang-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma_core] redhat spec: Avoid conflict due to implicit directory add
Date: Mon, 13 Mar 2017 11:08:29 -0600 [thread overview]
Message-ID: <20170313170829.GD25664@obsidianresearch.com> (raw)
In-Reply-To: <9707bd97229b67fe04d29affcb37f61b80e20dca.1484143751.git-series.knut.omang-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On Wed, Jan 11, 2017 at 03:19:34PM +0100, Knut Omang wrote:
> If *-notation is used to include subdirectories, they
> seem to end as explicit file additions. This causes conflicts
> with other packages that provides the same
> directories, in this case rdma_core-devel conflicts
> with filesystem and kernel-headers.
>
> Using %dir did not seem to help
> avoiding the issue but rather cause duplicate warnings, eg.
>
> warning: File listed twice: /usr/include/infiniband
>
> This should be considered a bug in rpmbuild but
> probably needs to be fixed here anyway:
>
> List each individual directory with wildcards
> to avoid the issue.
>
> Signed-off-by: Knut Omang <knut.omang-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> redhat/rdma-core.spec | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Did this ever get settled?
Jarod? Yes/No?
> diff --git a/redhat/rdma-core.spec b/redhat/rdma-core.spec
> index 4271e7c..72d6f3b 100644
> +++ b/redhat/rdma-core.spec
> @@ -343,7 +343,8 @@ rm -rf %{buildroot}/%{_initrddir}/
>
> %files devel
> %doc %{_docdir}/%{name}-%{version}/MAINTAINERS
> -%{_includedir}/*
> +%{_includedir}/infiniband/*
> +%{_includedir}/rdma/*
> %{_libdir}/lib*.so
> %{_mandir}/man3/ibv_*
> %{_mandir}/man3/rdma*
>
> base-commit: b1c9b6aa22fb91507fb1a63df99566da7720315f
--
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-03-13 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 14:19 [PATCH rdma_core] redhat spec: Avoid conflict due to implicit directory add Knut Omang
[not found] ` <9707bd97229b67fe04d29affcb37f61b80e20dca.1484143751.git-series.knut.omang-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-03-13 17:08 ` Jason Gunthorpe [this message]
[not found] ` <20170313170829.GD25664-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-13 19:23 ` Jarod Wilson
[not found] ` <861182f1-1d2a-2cdc-416f-bc0132201d47-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-14 7:10 ` Knut Omang
2017-03-13 20:11 ` Jarod Wilson
[not found] ` <6e210956-a4e0-242f-a24e-691f87de3ddb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-04-25 19:03 ` Doug Ledford
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=20170313170829.GD25664@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=knut.omang-QHcLZuEGTsvQT0dZR+AlfA@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