From: Bonface Munyoki K. <me@bonfacemunyoki.com>
To: "Frederick M. Muriithi" <fredmanglis@protonmail.com>
Cc: 42414-done@debbugs.gnu.org
Subject: bug#42414: Packages Installed With GNU Guix not finding Correct Glibc
Date: Thu, 15 Apr 2021 17:05:39 +0300 [thread overview]
Message-ID: <86lf9jmymk.fsf@bonfacemunyoki.com> (raw)
In-Reply-To: <mx4AY-IoegpkJ2n-XSvaw9OS1Co8EjdAl9EZW8qzBs_9WORf_v_8Q2IJGvR2htVC8h5onHxId7Z1_U6V_VRAcGOFTHqh68vlHGq0h0SK5eo=@protonmail.com> (Frederick M. Muriithi's message of "Sat, 18 Jul 2020 15:14:54 +0000")
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
"Frederick M. Muriithi"
<fredmanglis@protonmail.com> writes:
> After wrestling with this issue some more and
> trying to figure out the cause, I finally fingered
> Ubuntu as the culprit.
>
> Something in my upgrade from Ubuntu 18.04 LTS to
> Ubuntu 20.04 LTS subtly broke my system. Also I
> think a recent change in guix preventing me from
> doing a 'guix pull' unless logged in as root might
> have had something to do with it.
>
> I'm not quite sure what the final cause was, but I
> fixed the issue, and did a [quick
> write-up](https://fredmanglis.me.ke/blog/guix-apps-not-finding-glibc.html
> ) to help anyone else experiencing the issue.
>
This seems to have been fixed, so going ahead to
close this :)
tl;dr fix: Updating the package seemed to fix
things.
--
Bonface M. K. D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
Humble GNU Emacs User / Bearer of scheme-y parens
Curator: <https://upbookclub.com> / Twitter: @BonfaceKilz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
prev parent reply other threads:[~2021-04-15 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 6:04 bug#42414: Packages Installed With GNU Guix not finding Correct Glibc Frederick M. Muriithi via Bug reports for GNU Guix
2020-07-18 15:14 ` Frederick M. Muriithi via Bug reports for GNU Guix
2021-04-15 14:05 ` Bonface Munyoki K. [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
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=86lf9jmymk.fsf@bonfacemunyoki.com \
--to=me@bonfacemunyoki.com \
--cc=42414-done@debbugs.gnu.org \
--cc=fredmanglis@protonmail.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 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).