unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Wiktor Żelazny" <wz@freeshell.de>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: "libc.so.6: version `GLIBC_2.33' not found" with guix time-machine --channels
Date: Mon, 10 Jan 2022 20:04:04 +0100	[thread overview]
Message-ID: <20220110190404.bxexn767xobd3fgw@wzguix> (raw)
In-Reply-To: <874k6cspts.fsf@nckx>

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

On Sun, Jan 09, 2022 at 07:09:21PM +0100, Tobias Geerinckx-Rice wrote:

> that could prevent you from grokking & fully enjoying it, which is why
> it's so important to correct.

Hi Tobias,

Thank you, I appreciate it.

> ‘guix time machine --commit=COMMIT -- COMMAND’ builds guix@COMMIT, and
> then everything to the right of the ‘--’ happens inside guix@COMMIT,
> i.e., ‘the past’.  There is no link to the present.

This is great news.

> Your kernel analogy is more accurate: somehow, once released from its
> functionally pure build environment, package P is being fed a glibc it
> was never compiled against.

Do you think it may be relevant to my current problem or is this a
general comment?

> There are many ways this could happen and there's (obviously) a bug
> here,

If that’s a bug, it sounds like one of those that are hard to track
down, at least as long as nobody else is reporting a similar issue.
Maybe another upgrade will help.

Regards,

WŻ

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

      reply	other threads:[~2022-01-10 19:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 15:11 "libc.so.6: version `GLIBC_2.33' not found" with guix time-machine --channels Wiktor Żelazny
2022-01-08 18:50 ` Leo Famulari
2022-01-09 17:57   ` Wiktor Żelazny
2022-01-09 18:03     ` Ricardo Wurmus
2022-01-09 18:49       ` Wiktor Żelazny
2022-02-03 14:18         ` Wiktor Żelazny
2022-01-09 19:37       ` André A. Gomes
2022-01-09 20:51         ` Ricardo Wurmus
2022-01-09 18:09     ` Tobias Geerinckx-Rice
2022-01-10 19:04       ` Wiktor Żelazny [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=20220110190404.bxexn767xobd3fgw@wzguix \
    --to=wz@freeshell.de \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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.
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).