From: zimoun <zimon.toutoune@gmail.com>
To: "André A. Gomes" <andremegafone@gmail.com>, help-guix@gnu.org
Subject: Re: Upgrading profile error
Date: Thu, 20 Oct 2022 10:38:22 +0200 [thread overview]
Message-ID: <87ilkekhz5.fsf@gmail.com> (raw)
In-Reply-To: <87o7u7tud8.fsf@gmail.com>
Hi,
On mer., 19 oct. 2022 at 23:45, André A. Gomes <andremegafone@gmail.com> wrote:
> $ guix package --upgrade emacs
>
> --8<---------------cut here---------------start------------->8---
> guix package: error: profile contains conflicting entries for gnupg
> guix package: error: first entry: gnupg@2.2.32 /gnu/store/khviv1d2nhdm2ykaiva936b0jdfkmf9w-gnupg-2.2.32
> guix package: error: ... propagated from emacs-pinentry@0.1-1.dcc9ba0
> guix package: error: second entry: gnupg@2.2.32 /gnu/store/0jlw8kk0ll25lzbz939jaz4sbfkr8gqj-gnupg-2.2.32
> guix package: error: ... propagated from emacs-pinentry@0.1-1.dcc9ba0
> hint: You cannot have two different versions or variants of `emacs-pinentry' in the same
> profile.
> --8<---------------cut here---------------end--------------->8---
>
> I don't understand what's going on here. Any piece of advice? Thank
> you.
Well, it depends on what you already have in this profile. Yes, the
message can be confusing. :-)
BTW, instead of,
$ guix package --upgrade emacs
I think it is better to upgrade the complete manifest. See [1] for some
details. For instance,
When partially upgrading a profile, conflicts may arise (due to
diverging dependencies between the updated and the non-updated
packages) and they can be annoying to resolve
manually. Manifests remove this problem altogether since all
packages are always upgraded at once.
1: <https://guix.gnu.org/en/cookbook/en/guix-cookbook.html#Guix-Profiles-in-Practice>
Cheers,
simon
prev parent reply other threads:[~2022-10-20 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 20:45 Upgrading profile error André A. Gomes
2022-10-20 8:38 ` zimoun [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=87ilkekhz5.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=andremegafone@gmail.com \
--cc=help-guix@gnu.org \
/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).