From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Dealing with common collisions in profiles
Date: Fri, 18 Sep 2015 21:11:42 +0200
Message-ID: <87twqrsftd.fsf@gnu.org>
References: <87egi7qppi.fsf@gnu.org> <20150917142229.GA14689@thebird.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49816)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1Zd14a-0003jq-0P
	for guix-devel@gnu.org; Fri, 18 Sep 2015 15:11:52 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1Zd14Z-0003Br-70
	for guix-devel@gnu.org; Fri, 18 Sep 2015 15:11:51 -0400
In-Reply-To: <20150917142229.GA14689@thebird.nl> (Pjotr Prins's message of
	"Thu, 17 Sep 2015 16:22:29 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>, Federico Beffa <beffa@fbengineering.ch>

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> How do we disable the message?

We don=E2=80=99t, that=E2=80=99s the problem.  :-)

The idea initially was that users may want to know when a collision
happens, because that=E2=80=99s usually a bad sign.

Nowadays, we indeed get way too many of them.  The point of my message
was that we should address those that are genuine packaging issues
rather than try to hide the messages.

> I get pages and pages of collisions by now.
>
> warning: arbitrarily choosing /gnu/store/z4pvymzvvk8mlsry6gf04z40ij537aj4=
-gcc-toolchain-5.1.0/include/linux/ipv6.h
> warning: collision encountered: /gnu/store/z4pvymzvvk8mlsry6gf04z40ij537a=
j4-gcc-toolchain-5.1.0/include/linux/if_arp.h /gnu/store/ykdxi4y2caa9v8hi55=
fr2slpx2kdwpb9-linux-libre-headers-3.3.8/include/linux/if_arp.h=20

Could it be that both =E2=80=98glibc=E2=80=99 or =E2=80=98linux-libre-heade=
rs=E2=80=99 and
=E2=80=98gcc-toolchain=E2=80=99 are present in the profile?

Thanks,
Ludo=E2=80=99.