unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 32316@debbugs.gnu.org
Subject: bug#32316: Build failure with installed guix that does not happen with pre-inst-env
Date: Tue, 31 Jul 2018 11:42:14 +0200	[thread overview]
Message-ID: <m1r2jjwxl5.fsf@fastmail.net> (raw)
In-Reply-To: <20180730214222.4c08be42@alma-ubu>

Hi Björn,

> thanks for the precise error report.

Thanks for your quick reply!

> Could it be the case that in your `guix build ...` you are not using
> the guix you pulled?
>
> What does `guix --version` say?
>
> Where does `which guix` point to?
>
> It should point to
>
> ~/.config/guix/current/bin/guix

It points to $HOME/.guix-profile/bin/guix, and since I have the package
"guix" installed in my profile, that looks OK to me. At the very least I
am used to it: guix has always been in my profile, and has always worked
well that way.

But I do see how this could cause various failures after a guix pull,
because the guix in my profile has to work with the updated stuff the
pull has placed under ~/.config. So perhaps the real mystery is that I
haven't had any trouble before. And I wonder what strategy to adopt to
avoid it - remove guix from my profile? There was a good reason to
install it last year, but I don't remember what it was. If installing
guix into a profile is not a good idea, perhaps the guix package should
disappear or be renamed to something that indicates its true purpose?

BTW, since I updated my profile with the pre-inst-env guix, I now also
have a new guix in my profile and the build failure has disappeared.

Konrad.

  reply	other threads:[~2018-07-31  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 16:16 bug#32316: Build failure with installed guix that does not happen with pre-inst-env Konrad Hinsen
2018-07-30 19:42 ` Björn Höfling
2018-07-31  9:42   ` Konrad Hinsen [this message]
2018-07-31 10:04     ` Julien Lepiller
2018-08-22 15:51 ` bug#32316: Thanks! Konrad Hinsen

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=m1r2jjwxl5.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=32316@debbugs.gnu.org \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    /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).