unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>, Federico Beffa <beffa@fbengineering.ch>
Subject: Re: Dealing with common collisions in profiles
Date: Fri, 18 Sep 2015 21:11:42 +0200	[thread overview]
Message-ID: <87twqrsftd.fsf@gnu.org> (raw)
In-Reply-To: <20150917142229.GA14689@thebird.nl> (Pjotr Prins's message of "Thu, 17 Sep 2015 16:22:29 +0200")

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

> How do we disable the message?

We don’t, that’s the problem.  :-)

The idea initially was that users may want to know when a collision
happens, because that’s 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/z4pvymzvvk8mlsry6gf04z40ij537aj4-gcc-toolchain-5.1.0/include/linux/if_arp.h /gnu/store/ykdxi4y2caa9v8hi55fr2slpx2kdwpb9-linux-libre-headers-3.3.8/include/linux/if_arp.h 

Could it be that both ‘glibc’ or ‘linux-libre-headers’ and
‘gcc-toolchain’ are present in the profile?

Thanks,
Ludo’.

      reply	other threads:[~2015-09-18 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 20:53 Dealing with common collisions in profiles Ludovic Courtès
2015-09-10 17:53 ` Federico Beffa
2015-09-10 19:24   ` Ludovic Courtès
2015-09-17 14:22 ` Pjotr Prins
2015-09-18 19:11   ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87twqrsftd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=beffa@fbengineering.ch \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).