Pjotr Prins 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 add
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/li
Federico Beffa skribis:
> On Wed, Sep 9, 2015 at 10:53 PM, 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 t
On Wed, Sep 9, 2015 at 10:53 PM, 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/
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
li