From: Preston Miller Firestone <firestone.preston@gmail.com>
To: 72990@debbugs.gnu.org
Cc: "Dan Hatton" <dan.hatton@btinternet.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Nicolas Graves" <ngraves@ngraves.fr>,
"Edison Ibáñez" <arkhan@riseup.net>
Subject: bug#72990: Core packages updated broke Guix
Date: Thu, 5 Sep 2024 11:45:53 -0500 [thread overview]
Message-ID: <0f89159f-99b9-5490-8a02-3e152f0e6b8a@gmail.com> (raw)
In-Reply-To: <5e6e3af01d53fa248d33a91b4155f400@riseup.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 481 bytes --]
> Thanks Ludo, by removing the value configured in LD_LIBRARY_PATH you can
> rebuild the entire system without problems and Guix worked well again.
I can also confirm: I was having this same problem on the same update
and unsetting LD_LIBRARY_PATH also fixed it for me. I was then able to
run `guix pull` and everything was good again.
Thanks Ludo for the fix! I wonder how LD_LIBRARY_PATH got set in the
first place? I'm running Guix system.
Thanks,
Preston
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 963 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2024-09-05 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 21:43 bug#72990: Core packages updated broke Guix Edison Ibáñez
2024-09-02 22:23 ` Nicolas Graves
2024-09-03 11:57 ` Ludovic Courtès
2024-09-03 12:05 ` Edison Ibáñez
2024-09-04 12:02 ` Ludovic Courtès
2024-09-03 20:24 ` bug#72990: unset LD_LIBRARY_PATH confirmed as good workaround Dan Hatton via Bug reports for GNU Guix
2024-09-04 12:14 ` bug#72990: Core packages updated broke Guix Edison Ibáñez
2024-09-05 16:45 ` Preston Miller Firestone [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=0f89159f-99b9-5490-8a02-3e152f0e6b8a@gmail.com \
--to=firestone.preston@gmail.com \
--cc=72990@debbugs.gnu.org \
--cc=arkhan@riseup.net \
--cc=dan.hatton@btinternet.com \
--cc=ludo@gnu.org \
--cc=ngraves@ngraves.fr \
/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.