all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brian Cully via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 62936@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: bug#62936: [core-updates] pre-inst-env no longer works
Date: Wed, 19 Apr 2023 10:14:59 -0400	[thread overview]
Message-ID: <87r0sg0x8r.fsf@psyduck.jhoto.kublai.com> (raw)
In-Reply-To: <87leiogfa3.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Make sure everything is in sync, and use ‘guix shell -D guix -C’ 
> to
> avoid interference!

This has made the glibc locale error and the libgit2 bindings to 
work. Thank you!

However, I'm not sure how this happened in the first place. The 
system I'm running on is running core-updates, from a ‘guix system 
reconfigure’ and reboot. Where is the improperly linked libgit2 
coming from that guix is loading it (and then, only when used with 
‘pre-inst-env’).

-bjc




  reply	other threads:[~2023-04-19 14:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 14:51 bug#62936: [core-updates] pre-inst-env no longer works Brian Cully via Bug reports for GNU Guix
2023-04-19  8:51 ` Simon Tournier
2023-04-19 11:29   ` Brian Cully via Bug reports for GNU Guix
2023-04-19 13:41     ` Ludovic Courtès
2023-04-19 14:14       ` Brian Cully via Bug reports for GNU Guix [this message]
2023-04-19 16:28 ` bug#62949: libgcrypt version in core-updates Andreas Enge
2023-04-19 16:37   ` Ludovic Courtès
2023-04-19 18:19     ` Andreas Enge
2023-04-19 20:40       ` Ludovic Courtès
2023-04-19 19:51   ` bug#62936: [core-updates] pre-inst-env no longer works Brian Cully via Bug reports for GNU Guix
2023-04-24  8:34     ` Josselin Poiret via Bug reports for GNU Guix
2023-04-24 14:44       ` Brian Cully via Bug reports for GNU Guix

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=87r0sg0x8r.fsf@psyduck.jhoto.kublai.com \
    --to=bug-guix@gnu.org \
    --cc=62936@debbugs.gnu.org \
    --cc=bjc@spork.org \
    --cc=ludo@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.
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.