From: Csepp <raingloom@riseup.net>
To: Csepp <raingloom@riseup.net>
Cc: 63727@debbugs.gnu.org
Subject: bug#63727: libffi propagation in glib versions causes issues
Date: Mon, 05 Jun 2023 23:50:36 +0200 [thread overview]
Message-ID: <87cz29inir.fsf@riseup.net> (raw)
In-Reply-To: <87v8ggnqr3.fsf@riseup.net>
Csepp <raingloom@riseup.net> writes:
> guix upgrade: error: profile contains conflicting entries for libffi
> guix upgrade: error: first entry: libffi@3.4.4 /gnu/store/w8b0l8hk6g0fahj4fvmc4qqm3cvaxnmv-libffi-3.4.4
> guix upgrade: error: ... propagated from glib@2.72.3
> guix upgrade: error: ... propagated from dconf@0.40.0
> guix upgrade: error: ... propagated from eog@42.3
> guix upgrade: error: second entry: libffi@3.3 /gnu/store/wgqhlc12qvlwiklam7hz2r311fdcqfim-libffi-3.3
> guix upgrade: error: ... propagated from glib@2.70.2
> guix upgrade: error: ... propagated from gdk-pixbuf@2.42.4
> guix upgrade: error: ... propagated from libnotify@0.7.9
>
> Why do these need to be propagated?
This issue still persists, stopping me from being able to upgrade.
I also can't have both eog (Eye of GNOME) and the default glib
package installed, so just removing libnotify didn't help, and I'd
rather not play whack-a-mole with removing packages.
Some more insight into why there are multiple propagated versions of
libffi and glib would be greatly appreciated.
prev parent reply other threads:[~2023-06-05 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 19:37 bug#63727: libffi propagation in glib versions causes issues Csepp
2023-06-05 21:50 ` Csepp [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=87cz29inir.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=63727@debbugs.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.
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).