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: Andreas Enge <andreas@enge.fr>
Cc: 62936@debbugs.gnu.org
Subject: bug#62936: [core-updates] pre-inst-env no longer works
Date: Wed, 19 Apr 2023 15:51:16 -0400	[thread overview]
Message-ID: <877cu77irv.fsf_-_@psyduck.jhoto.kublai.com> (raw)
In-Reply-To: <ZEAWryOf8oblZG1l@jurong> (Andreas Enge's message of "Wed, 19 Apr 2023 18:28:31 +0200")

I did a full rebuild before submitting this bug: bootstrap -> configure
-> make clean -> make.

FWIW, I still have the issue with ‘pre-inst-env’ when not run from
within ‘guix shell -D guix’, which is a step I have never previously
needed. As I just explained on IRC:

--8<---------------cut here---------------start------------->8---
<bjc> i'm confused why it's suddenly a problem, though. i've never needed to
      use ‘guix shell’ with pre-inst-env before  [15:41]
<bjc> ludo says it's libgit2 linking against an old libc, but i have no idea
      how that's even possible
<bjc> for one thing: my system has been reconfigured. all my packages are now
      running core-updates, and that includes libgit2. for another: doesn't
      libgit link with a specific path in /gnu/store, so it'll use whatever
      glibc it needs regardless of what's in my “system” configuration?
--8<---------------cut here---------------end--------------->8---

Even if this is some particular problem to my build environment somehow,
I'd love an explanation as to what's going on because I'm extremely
confused.

In case it matters, I've re-run ‘system reconfigure’ and ‘home
reconfigure’ since moving to core-updates, thinking maybe there's some
bootstrapping issue. I'm now 2 system and home generations into
core-updates, but I have the same problem.

Thanks,




  parent reply	other threads:[~2023-04-19 19:52 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
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   ` Brian Cully via Bug reports for GNU Guix [this message]
2023-04-24  8:34     ` bug#62936: [core-updates] pre-inst-env no longer works 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=877cu77irv.fsf_-_@psyduck.jhoto.kublai.com \
    --to=bug-guix@gnu.org \
    --cc=62936@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=bjc@spork.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 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.