Re: quirky behaviour of “guix environment”

["Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>]

Hi Ricardo,

On Thu, 22 Feb 2018 14:17:53 +0100
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> wrote:

> Hi Guix,
> 
> for a few days now I have been testing the glibc graft to make
> software work on the cluster running CentOS 6.8 (with a heavily
> patched Linux that has the nominal version 2.6.32).
> 
> The graft seems to work fine (with the exception of a Guile GC
> warning I get when running Guix), except when using “guix environment
> -l”.
> 

[...]

> 2.) How could the *old* glibc end up in the environment?  I expected
> the grafted glibc, which comes with a patch to avoid “FATAL: kernel
> too old”.


I don't know if this is related, but in the last days/weeks I noticed this:

We all know that there are sometimes those collisions:

warning: collision encountered:
/gnu/store/w27inn24x162y9m4hy5d3k7msn6zip47-ld-wrapper-0/bin/ld
/gnu/store/b31l1fzq9xcafhigjm2a11w8y5mzk8n9-binutils-2281/bin/ld
warning: arbitrarily choosing /gnu/store/w27inn24x162y9m4hy5d3k7msn6zip47-ld-wrapper-0/bin/ld

OK, that's fine, they are "normal". When I did a 

guix environment ... (something without the "-l")

I got hundreds of such collisions in the form of

/gnu/store/hash1-package/bin/a-command
/gnu/store/hash2-package/bin/a-command

i.e. only the hash was different. I can't remember the package/commmands nor can I
reproduce it right now. But I also had the idea that there was a graft and its original
version in the environment.

I will have an eye on it and post the details, if I stumple upon it again.

Björn