From: "Ludovic Courtès" <ludo@gnu.org>
To: Brett Gilio <brettg@posteo.net>
Cc: 34423@debbugs.gnu.org
Subject: bug#34423: gnome-shell-extensions and glib
Date: Tue, 12 Feb 2019 15:22:10 +0100 [thread overview]
Message-ID: <877ee5krxp.fsf@gnu.org> (raw)
In-Reply-To: <878synnf13.fsf@posteo.net> (Brett Gilio's message of "Sun, 10 Feb 2019 22:08:08 -0600")
Hello,
Brett Gilio <brettg@posteo.net> skribis:
> Hi all, when I try to install gnome-shell-extensions it is throwing this
> issue
>
> brettg@guixsd ~$ guix package -i gnome-shell-extensions
> The following package will be installed:
> gnome-shell-extensions 3.24.3 /gnu/store/bfw4wp2lm68s3gdhhbic0kr2rfzcab07-gnome-shell-extensions-3.24.3
>
> guix package: error: profile contains conflicting entries for glib
> guix package: error: first entry: glib@2.56.3 /gnu/store/lly2sqknlw8h59bfffpgh836r38ffsdc-glib-2.56.3
> guix package: error: ... propagated from gnome-shell-extensions@3.24.3
> guix package: error: second entry: glib@2.56.2 /gnu/store/qc5b998gnhb5p8lc9mf0knr1nyc648k9-glib-2.56.2
> guix package: error: ... propagated from cairo@1.14.12
> guix package: error: ... propagated from guile-cairo@1.10.0
> guix package: error: ... propagated from guile-gnome@2.16.5
> hint: Try upgrading both `gnome-shell-extensions' and `guile-gnome', or remove
> one of them from the profile.
>
>
>
>
>
> The strangeness of the issue is not only that glib seems to be
> referencing two different versions, but I don't even have guile-gnome
> installed for there to be a "conflict".
The message above suggests you do have ‘guile-gnome’ in this profile.
What does “guix package -I gnome” report?
Thanks,
Ludo’.
prev parent reply other threads:[~2019-02-12 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 4:08 bug#34423: gnome-shell-extensions and glib Brett Gilio
2019-02-12 14:22 ` Ludovic Courtès [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=877ee5krxp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34423@debbugs.gnu.org \
--cc=brettg@posteo.net \
/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.