From: Leo Famulari <leo@famulari.name>
To: Dale Mellor <guix-devel-0brg6a@rdmp.org>
Cc: 53561@debbugs.gnu.org
Subject: bug#53561: Failing: guix package -i gtkmm@3
Date: Sat, 29 Jan 2022 13:42:14 -0500 [thread overview]
Message-ID: <YfWKhlKvxnzNOu5C@jasmine.lan> (raw)
In-Reply-To: <5c45a856b27d319076357888e40d6c1cf5fc4271.camel@rdmp.org>
On Wed, Jan 26, 2022 at 10:24:01PM +0000, Dale Mellor wrote:
> The above command produces
>
> The following package will be installed:
> gtkmm 3.24.5
>
> guix package: error: profile contains conflicting entries for libsigc++
> guix package: error: first entry: libsigc++@3.0.6 /gnu/store/ng4k2yl94d758p5vnashd4nvyb1aw8s1-libsigc++-3.0.6
> guix package: error: ... propagated from cairomm@1.14.2
> guix package: error: ... propagated from gtkmm@3.24.5
> guix package: error: second entry: libsigc++@2.9.3 /gnu/store/iad8jg1fm7jsq0pqj547f3n5s2jn9rp0-libsigc++-2.9.3
> guix package: error: ... propagated from glibmm@2.64.5
> guix package: error: ... propagated from pangomm@2.46.0
> guix package: error: ... propagated from gtkmm@3.24.5
> hint: You cannot have two different versions or variants of `gtkmm' in the same profile.
To clarify, what is the bug that you are reporting?
Are you reporting that `guix package -i gtkmm@3` did not work?
Or are you reporting that the hint mentions the wrong package? (I think
it should talk about libsigc++, not gtkmm)
next prev parent reply other threads:[~2022-01-29 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 22:24 bug#53561: Failing: guix package -i gtkmm@3 Dale Mellor
2022-01-29 18:42 ` Leo Famulari [this message]
[not found] ` <1531652819c02abe9e095816895679a6d6719fe8.camel@rdmp.org>
2022-01-30 0:55 ` Leo Famulari
[not found] ` <81cbc842d9eebb9ee95044d37d97fc0d47ff9ea5.camel@rdmp.org>
2022-01-30 18:25 ` Leo Famulari
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=YfWKhlKvxnzNOu5C@jasmine.lan \
--to=leo@famulari.name \
--cc=53561@debbugs.gnu.org \
--cc=guix-devel-0brg6a@rdmp.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).