From: Ricardo Wurmus <rekado@elephly.net>
To: "Wiktor Żelazny" <wz@freeshell.de>
Cc: jsmith <jsmith8365@protonmail.com>, help-guix@gnu.org
Subject: Re: readline problem
Date: Wed, 19 Jan 2022 20:45:51 +0100 [thread overview]
Message-ID: <875yqftsms.fsf@elephly.net> (raw)
In-Reply-To: <20220119182112.3kbonwk3m5orivud@wzguix>
Wiktor Żelazny <wz@freeshell.de> writes:
> [[PGP Signed Part:Undecided]]
> On Tue, Jan 18, 2022 at 03:51:35PM +0100, Ricardo Wurmus wrote:
>>
>> Wiktor Żelazny <wz@freeshell.de> writes:
>>
>> > Hey, this sounds just like the problem I reported earlier this
>> > month.
>>
>> Can you please tell us the issue number?
>
> I did not file an issue as I wasn’t sure if that was a bug. I’m talking
> about the “"libc.so.6: version `GLIBC_2.33' not found" with guix
> time-machine --channels” thread on this mailing list, started on January
> 8th.
Oh, okay. I thought there had been a bug report with a discussion I
missed.
>> Builds are isolated, of course, but it’s common that people who don’t
>> use manifests end up building a profile that consists of a colorful
>> mosaic of packages from different versions of Guix.
>>
>> guix install foo
>> guix pull
>> guix install bar
>> guix pull
>> guix install baz
>
> I suppose that this problem does not arise if `guix package -u` is run
> after each `guix pull`?
It should not happen then, correct.
Though I have had reports from confused users at work who say that “guix
upgrade” doesn’t necessarily help, and that they actually had to use
“guix install” on all packages again. I haven’t been able to confirm
this yet.
--
Ricardo
next prev parent reply other threads:[~2022-01-19 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 8:13 readline problem jsmith via
2022-01-17 11:57 ` Ricardo Wurmus
2022-01-18 11:20 ` Wiktor Żelazny
2022-01-18 14:51 ` Ricardo Wurmus
2022-01-19 18:21 ` Wiktor Żelazny
2022-01-19 19:45 ` Ricardo Wurmus [this message]
2022-01-28 11:13 ` James Smith
2022-01-28 11:22 ` Ricardo Wurmus
2022-01-30 8:33 ` No upgrade after pull, and Guix philosophy (was: readline problem) Wiktor Żelazny
2022-01-30 8:53 ` Ricardo Wurmus
2022-01-31 19:16 ` Wiktor Żelazny
2022-01-31 19:26 ` Ricardo Wurmus
2022-01-28 12:54 ` readline problem Dr. Arne Babenhauserheide
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=875yqftsms.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=jsmith8365@protonmail.com \
--cc=wz@freeshell.de \
/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).