From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54350@debbugs.gnu.org
Subject: bug#54350: Profile collisions are ignored, installing multiple versions of the same package is silently broken
Date: Tue, 15 Mar 2022 14:50:32 +0100 [thread overview]
Message-ID: <87zglrjpef.fsf@gnu.org> (raw)
In-Reply-To: <afde4231155f7fe32e709dc0d3a4c12d71ea8011.camel@telenet.be> (Maxime Devos's message of "Sat, 12 Mar 2022 10:45:46 +0100")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> $ guix shell --pure bash pango@1.42 pango@1.48
> $ ~/.guix-profile/bin/ls -l $GUIX_ENVIRONMENT/lib/libpango*.so
>
> Result:
> [...]/lib/libpango-1.0.so -> [...]-pango-1.42.4/lib/libpango-1.0.so
> [...]/lib/libpangocairo-1.0.so -> [...]-pango-1.42.4/lib/libpangocairo-1.0.so
> [...]/lib/libpangoft2-1.0.so -> [...]-1.42.4/lib/libpangoft2-1.0.so
> [...]/lib/libpangoxft-1.0.so -> [...]-pango-1.42.4/lib/libpangoxft-1.0.so
>
> Question: how does this even work? Aren't error messages about profile
> collisions a thing?
Unlike ‘guix package’, ‘guix environment/shell’ explicitly disables
collision checks—see #:allow-collisions? in environment.scm.
The rationale back then was that if you do:
guix shell -D guile
then you likely end up with profile collisions, like so (I modified the
code to do #:allow-collisions? #f):
--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix shell -D guile -n
guix shell: error: profile contains conflicting entries for bash-minimal
guix shell: error: first entry: bash-minimal@5.1.8 /gnu/store/chfwin3a4qp1znnpsjbmydr2jbzk0d6y-bash-minimal-5.1.8
guix shell: error: second entry: bash-minimal@5.1.8 /gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8
hint: You cannot have two different versions or variants of `bash-minimal' in the same profile.
--8<---------------cut here---------------end--------------->8---
These collisions are harmless but frequent in package development
environments, which is why ‘guix environment’ had to turn off those
checks (commit afd06f605bf88a796acefc7ed598b43879346a6b).
That’s a bit of a hack though.
What we could do, as a mitigation, is to enable collision checks unless
there’s at least one ‘-D’ flag. We’d also need to introduce
‘--allow-collisions’ for ‘guix shell’.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-03-15 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 9:45 bug#54350: Profile collisions are ignored, installing multiple versions of the same package is silently broken Maxime Devos
2022-03-12 14:34 ` Liliana Marie Prikler
2022-03-15 13:50 ` Ludovic Courtès [this message]
2022-03-15 15:58 ` Maxime Devos
2022-03-16 10:18 ` Ludovic Courtès
2022-03-16 20:31 ` Greg Hogan
2023-12-12 13:10 ` bug#54350: Profile collisions in "guix shell" Konrad Hinsen
2023-12-15 6:51 ` Konrad Hinsen
2024-01-16 18:36 ` Suhail
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=87zglrjpef.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54350@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.