all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Csepp <raingloom@riseup.net>,
	Maxime Devos <maximedevos@telenet.be>, jgart <jgart@dismail.de>,
	guix-devel@gnu.org
Subject: Re: crate importer throws
Date: Thu, 20 Oct 2022 14:56:48 +0200	[thread overview]
Message-ID: <87o7u63b3v.fsf@riseup.net> (raw)
In-Reply-To: <Y1BSDrIDEVnRDA+v@3900XT>


Efraim Flashner <efraim@flashner.co.il> writes:

> [[PGP Signed Part:Undecided]]
> On Sat, Oct 15, 2022 at 02:58:53PM +0200, Csepp wrote:
>> 
>> Maxime Devos <maximedevos@telenet.be> writes:
>> 
>> > Could you check if
>> >
>> > $ guix shell --pure -- "$(which guix)" import crate the-way
>> >
>> > (i.e. a pure environment without any packages) works for you?  Maybe
>> > somehow there is some other guile-semver in your usual environment
>> > that breaks Guix.
>> 
>> Weirdly enough it works.
>> ...oh it also works without importing guile-semver.
>> HhmmMM!
>> Maybe my channels config makes a difference?
>
> More likely something in your .bashrc

It's a standard Guix System bashrc and bash_profile.
...oh, I actually use zsh, so not sure why I even checked that.  But
yeah, that is not customized much either, I just added the GRML config.


      reply	other threads:[~2022-10-20 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 21:39 crate importer throws jgart
2022-10-12  9:09 ` Csepp
2022-10-12 12:24 ` Maxime Devos
2022-10-12 15:50   ` jgart
2022-10-12 21:51     ` Csepp
2022-10-15 11:18       ` Maxime Devos
2022-10-13  8:47     ` Maxime Devos
2022-10-14 23:35       ` Csepp
2022-10-15 11:10         ` Maxime Devos
2022-10-15 12:58           ` Csepp
2022-10-19 19:37             ` Efraim Flashner
2022-10-20 12:56               ` Csepp [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7u63b3v.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --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.