unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gottfried <gottfried@posteo.de>
To: Leo Famulari <leo@famulari.name>, help-guix@gnu.org
Subject: Re: problems with "gedit"
Date: Sun, 12 Feb 2023 16:32:05 +0000	[thread overview]
Message-ID: <3712bafe-10a8-c843-d245-20255c3928a9@posteo.de> (raw)
In-Reply-To: <Y+jnmzQrdAaFlawh@jasmine.lan>


[-- Attachment #1.1.1: Type: text/plain, Size: 934 bytes --]

Hi,

> You can upgrade all of your packages, not just gedit.

When upgrading "gedit" this message below was shown.
So upgrading didn’t help.
Kind regards

Gottfried



Am 12.02.23 um 14:20 schrieb Leo Famulari:
> On Sun, Feb 12, 2023 at 09:15:45AM +0000, Gottfried wrote:
>> 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.
>>
>>
>> How can I solve this problem?
>> Should I uninstall "gedit" and then reinstall it?
>> or are there other possibilities?
> 
> You can upgrade all of your packages, not just gedit.

-- 

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-02-12 16:32 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 [this message]
2023-02-12 17:04     ` Andreas Enge
2023-02-13  6:43 ` 宋文武

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=3712bafe-10a8-c843-d245-20255c3928a9@posteo.de \
    --to=gottfried@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    /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).