unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Creating environments using Guix package manager and collision
Date: Sun, 7 Jun 2020 16:22:29 +0200	[thread overview]
Message-ID: <b5031284-d268-c1ce-0e7c-7348a38ef24b@posteo.de> (raw)
In-Reply-To: <CAJ3okZ0Gocsgqc446=LopbvcS42kZATj4+xccBh1_gikrkThxw@mail.gmail.com>

I'll have to read up on the `--allow-collisions` flag and see, whether
it does anything dangerous. It sounds dangerous.

I also just noticed, that the conflict seems to have messed up my Guile.
Cannot run Guile any longer, as there is now an issue with readline,
although it is installed:

~~~~
[14:54:09]:[~/development/Guile/risk-calculator]: guile
;;; WARNING: loading compiled file
/home/user/.guix-profile/lib/guile/2.2/site-ccache/ice-9/readline.go
failed:
;;; In procedure load-thunk-from-memory: incompatible bytecode kind
;;; WARNING: loading compiled file
/home/user/.guix-profile/lib/guile/2.2/site-ccache/ice-9/readline.go
failed:
;;; In procedure load-thunk-from-memory: incompatible bytecode kind
Backtrace:
In ice-9/boot-9.scm:
    702:2 19 (call-with-prompt ("prompt") #<procedure 1c57a60 at ic…> …)
In ice-9/eval.scm:
    619:8 18 (_ #(#(#<directory (guile-user) 1aaf750>)))
In unknown file:
          17 (primitive-load "/home/user/.guile")
In ice-9/eval.scm:
   721:20 16 (primitive-eval (use-modules (ice-9 readline) (# #) # #))
In ice-9/psyntax.scm:
  1241:36 15 (expand-top-sequence ((use-modules (ice-9 readline) …)) …)
  1233:19 14 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …)
   285:10 13 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)
In ice-9/boot-9.scm:
  3373:20 12 (process-use-modules _)
   222:17 11 (map1 (((ice-9 readline)) ((ice-9 format)) ((ice-9 …)) …))
  3374:31 10 (_ ((ice-9 readline)))
  2790:17  9 (resolve-interface (ice-9 readline) #:select _ #:hide _ …)
In ice-9/threads.scm:
    390:8  8 (_ _)
In ice-9/boot-9.scm:
  2716:13  7 (_)
In ice-9/threads.scm:
    390:8  6 (_ _)
In ice-9/boot-9.scm:
  2985:20  5 (_)
   2299:4  4 (save-module-excursion #<procedure 1ac05d0 at ice-9/boo…>)
  3005:26  3 (_)
In unknown file:
           2 (primitive-load-path "ice-9/readline" #<procedure 1c570…>)
In /home/user/.guix-profile/share/guile/site/2.2/ice-9/readline.scm:
     44:4  1 (_)
In unknown file:
           0 (load-extension "/gnu/store/2fsg1jl3hwxnak9h39f6vzx87h…" …)

ERROR: In procedure load-extension:
In procedure dynamic-link: file:
"/gnu/store/2fsg1jl3hwxnak9h39f6vzx87hp48dsm-guile-readline-2.2.4/lib/guile/3.0/extensions/guile-readline",
message: "file not found"
~~~~

So I commented out the `(use-modules (ice-9 readline))` and the
`(activate-readline)` from my `~/.guile` file and then it works again.
Perhaps because Guile was updated there is no suitable version of
guile-readline any longer. Guile is now at: 2.9.4.

(That is also something strange, that on one machine I get
`guile-next@2.9.4` and on the other I cannot get a `guile-next` (no
`guix search` result) but can get `guile@3.0.2`. And no matter how often
I run guix pull && guix package -u, it does not appear on the machine
with the older Guile version showing up.)

Thanks for the hint!

On 07.06.20 15:48, zimoun wrote:
> Dear,
>
> On Sun, 7 Jun 2020 at 14:28, Zelphir Kaltstahl
> <zelphirkaltstahl@posteo.de> wrote:
>
>> ~~~~
>> building /gnu/store/yniz1rh5cih92i72flj1x2cmlwv1nngk-keepassxc-2.5.4.drv...
>> guix package: error: profile contains conflicting entries for gmp
>> guix package: error:   first entry: gmp@6.2.0 /gnu/store/35afkywncrr5xsb4cxcljf6rpjcb7f61-gmp-6.2.0
>> guix package: error:    ... propagated from guile@3.0.2
>> guix package: error:   second entry: gmp@6.1.2 /gnu/store/y7qk8raalgvdnxcglvxa320cfxrjk1x6-gmp-6.1.2
>> guix package: error:    ... propagated from nettle@3.5.1
>> guix package: error:    ... propagated from gnutls@3.6.A
>> hint: Try upgrading both `guile' and `gnutls', or remove one of them from the profile.
>> ~~~~
>>
>> So I cannot complete `guix package -u`. I guess some of those packages
>> in my base profile are not even needed for most things I do and would be
>> better contained in project-specific environments, so that they do not
>> cause conflicts.
> Does the option '--allow-collisions' of "guix package" fit your needs?
>
>
>> Is it possible to create such kind of environments using Guix? I feel
>> like it should probably be an easy thing to do, once I know how to do
>> it, but I could not find a tutorial, which tells me how to do this.
>> Perhaps my idea about how Guix is used usually is wrong?
> I will reply to your other message. :-)
>
>
> All the best,
> simon

  reply	other threads:[~2020-06-07 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 12:28 Creating environments using Guix package manager Zelphir Kaltstahl
2020-06-07 12:37 ` Julien Lepiller
2020-06-07 13:27   ` Zelphir Kaltstahl
2020-06-07 14:41     ` zimoun
2020-06-07 14:11   ` Zelphir Kaltstahl
2020-06-07 14:44     ` zimoun
2020-06-07 13:48 ` zimoun
2020-06-07 14:22   ` Zelphir Kaltstahl [this message]
2020-06-07 14:55     ` Creating environments using Guix package manager and collision zimoun

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=b5031284-d268-c1ce-0e7c-7348a38ef24b@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.
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).