From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Federico Beffa <beffa@fbengineering.ch>
Subject: Re: Dealing with common collisions in profiles
Date: Thu, 17 Sep 2015 16:22:29 +0200 [thread overview]
Message-ID: <20150917142229.GA14689@thebird.nl> (raw)
In-Reply-To: <87egi7qppi.fsf@gnu.org>
How do we disable the message? 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
On Wed, Sep 09, 2015 at 10:53:45PM +0200, Ludovic Courtès wrote:
> Hello!
>
> You’ve probably noticed that as soon as there’s a non-negligible number
> of packages in a profile, there are collisions. It’s really harmless,
> but seriously annoying. Here’s a collection of those I get:
>
> share/glib-2.0/schemas/gschemas.compiled
> share/icons/hicolor/icon-theme.cache
> lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
> lib/perl5/5.16.1/x86_64-linux/perllocal.pod
>
> Federico, I know ‘glib-or-gtk-build-system’ builds the first 3 items on
> purpose, but what do you think can be done about them? At worst we
> could always change (guix build profiles) to not report collisions for
> those.
>
> The .pod files are used by ‘perldoc’ IIUC. What can be done about them?
>
> Thanks,
> Ludo’.
>
--
next prev parent reply other threads:[~2015-09-17 14:24 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 [this message]
2015-09-18 19:11 ` Ludovic Courtès
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=20150917142229.GA14689@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=beffa@fbengineering.ch \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.