all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: James Smith <jsmith8365@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: readline problem
Date: Fri, 28 Jan 2022 13:54:30 +0100	[thread overview]
Message-ID: <87wnikj9r1.fsf@web.de> (raw)
In-Reply-To: <ehyzL6MAB_tlOHUW8LG5zD7Y2XboF2PJqNi71Z7X7y7S97SMyNA9w6pSz9fv7H9wDppRMhNYTpY-LxjrTWzP8pNcNRpRbK_dKmTEshRjwug=@protonmail.com>

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


>> 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.

I had that problem, too. It’s why I switched to manifests: I could not
upgrade, but had to add more and more packages to the upgrade, maybe
choosing different versions to get them consistent.

I think that it was because guix upgrade keeps some version information,
so it might have too strict constraints when calculating the next
possible state.

Then I get something like "package conflict: dbus5 in profile and dbus4
pulled in by emacs". (not actual version numbers, this is just an example)

I’d like to have the situation where I can just say `guix upgrade emacs`
and guix calculates all affected packages recursively, resolving version
conflicts by itself to find the set of packages that need to be upgraded.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

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

      parent reply	other threads:[~2022-01-28 13:52 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
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             ` Dr. Arne Babenhauserheide [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=87wnikj9r1.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=help-guix@gnu.org \
    --cc=jsmith8365@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 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.