From: 宋文武 <iyzsong@envs.net>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: problems with "gedit"
Date: Mon, 13 Feb 2023 14:43:43 +0800 [thread overview]
Message-ID: <87lel2jc9s.fsf@envs.net> (raw)
In-Reply-To: <0214a088-9aa8-929d-1f57-6a386a5dbe48@posteo.de> (gottfried@posteo.de's message of "Sun, 12 Feb 2023 09:15:45 +0000")
Gottfried <gottfried@posteo.de> writes:
> Hi,
>
> gfp@Tuxedo ~$ guix upgrade gedit
> The following package will be upgraded:
> gedit 42.2 -> 44.1
>
> guix upgrade: error: profile contains conflicting entries for dconf
> guix upgrade: error: first entry: dconf@0.40.0
> /gnu/store/gkr4pbmc7320zvrnl48mjacpb3km00j7-dconf-0.40.0
> guix upgrade: error: ... propagated from gedit@44.1
> guix upgrade: error: second entry: dconf@0.40.0
> /gnu/store/0fpkqzkbwl43apj6ls4sfggj17i3nvvv-dconf-0.40.0
> guix upgrade: error: ... propagated from gedit@42.2
> hint: You cannot have two different versions or variants of `gedit' in
> the same profile.
Um, seems like a bug here that upgrade didn't exclude previous
propagated packages from conflicts checking, not very sure, need check
though..
>
>
> How can I solve this problem?
> Should I uninstall "gedit" and then reinstall it?
> or are there other possibilities?
I think uninstall should works, or maybe "guix upgrade gedit dconf"?
prev parent reply other threads:[~2023-02-13 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 9:15 problems with "gedit" Gottfried
2023-02-12 13:20 ` Leo Famulari
2023-02-12 16:32 ` Gottfried
2023-02-12 17:04 ` Andreas Enge
2023-02-13 6:43 ` 宋文武 [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=87lel2jc9s.fsf@envs.net \
--to=iyzsong@envs.net \
--cc=gottfried@posteo.de \
--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).