GNU bug report logs - #63727
libffi propagation in glib versions causes issues

Previous Next

Full log

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Csepp <raingloom <at> riseup.net>
To: Csepp <raingloom <at> riseup.net>
Cc: 63727 <at> debbugs.gnu.org, bug-guix <at> gnu.org
Subject: Re: bug#63727: libffi propagation in glib versions causes issues
Date: Mon, 05 Jun 2023 23:50:36 +0200

Csepp <raingloom <at> riseup.net> writes:

> guix upgrade: error: profile contains conflicting entries for libffi
> guix upgrade: error:   first entry: libffi <at> 3.4.4 /gnu/store/w8b0l8hk6g0fahj4fvmc4qqm3cvaxnmv-libffi-3.4.4
> guix upgrade: error:    ... propagated from glib <at> 2.72.3
> guix upgrade: error:    ... propagated from dconf <at> 0.40.0
> guix upgrade: error:    ... propagated from eog <at> 42.3
> guix upgrade: error:   second entry: libffi <at> 3.3 /gnu/store/wgqhlc12qvlwiklam7hz2r311fdcqfim-libffi-3.3
> guix upgrade: error:    ... propagated from glib <at> 2.70.2
> guix upgrade: error:    ... propagated from gdk-pixbuf <at> 2.42.4
> guix upgrade: error:    ... propagated from libnotify <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.