From: Suhail <suhail@bayesians.ca>
To: 54350@debbugs.gnu.org
Subject: bug#54350: Profile collisions in "guix shell"
Date: Tue, 16 Jan 2024 18:36:04 +0000 [thread overview]
Message-ID: <87wms9nn1p.fsf@> (raw)
In-Reply-To: <afde4231155f7fe32e709dc0d3a4c12d71ea8011.camel@telenet.be>
Hello Guix,
I came across this issue the other day when attempting to create a
profile that could act as a development environment for Guix. In
addition to noting my observations below, I'd like to understand why
there are collisions in a *new* profile tasked with installing the
dependencies of guix? Is this a bug?
The [documentation] notes the below command to start "a new shell where
all the dependencies and appropriate environment variables are set up to
hack on Guix":
#+begin_src sh
guix shell -D guix -CPW
#+end_src
Using guix-shell to export the manifest corresponding to the above one
gets:
#+header: :tangle ./manifest.scm
#+begin_src scheme
;; What follows is a "manifest" equivalent to the command line you gave.
;; You can store it in a file that you may then pass to any 'guix' command
;; that accepts a '--manifest' (or '-m') option.
(package->development-manifest
(specification->package "guix"))
#+end_src
Saving the above to manifest.scm and evaluating the below:
#+begin_src sh
mkdir -p ${GUIX_EXTRA_PROFILES}/guix-build-2
guix package -p ${GUIX_EXTRA_PROFILES}/guix-build-2/guix-build-2 -m ./manifest.scm
#+end_src
Results in the following error:
#+begin_example
...
guix package: error: profile contains conflicting entries for bzip2
guix package: error: first entry: bzip2@1.0.8 /gnu/store/4jkvfh9hp9zf9plrcw490ci6vpvc033d-bzip2-1.0.8
guix package: error: second entry: bzip2@1.0.8 /gnu/store/0ngy7fmrp9g3q35wwccnjxzaaqq9f8wi-bzip2-1.0.8
hint: You cannot have two different versions or variants of `bzip2' in the same profile.
#+end_example
Adding --allow-collisions to match guix-shell behaviour makes the
installation succeed, as expected.
[documentation]: <https://guix.gnu.org/en/manual/devel/en/guix.html#Building-from-Git>
--
Suhail
This email is not an offer capable of acceptance, does not evidence an
intention to enter into an agreement, has no operative effect until a
definitive agreement is signed in writing by both parties, and that no
party should act in reliance on the email or any representations of the
sender until a definitive agreement is signed in writing by both
parties.
prev parent reply other threads:[~2024-01-17 20:14 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
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 [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=87wms9nn1p.fsf@ \
--to=suhail@bayesians.ca \
--cc=54350@debbugs.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 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).