"profile contains conflicting entries"

"profile contains conflicting entries"

[Andy Tai]

Hi, I run into this:

$ guix install guile-g-golf
The following package will be installed:
   guile-g-golf 0.8.0-a.1

guix install: error: profile contains conflicting entries for glib
guix install: error:   first entry: glib@2.73.3
/gnu/store/514nix1lfipx98hd3prjhq9vcv9iiw01-glib-2.73.3
guix install: error:    ... propagated from gobject-introspection@1.73.1
guix install: error:    ... propagated from guile-g-golf@0.8.0-a.1
guix install: error:   second entry: glib@2.70.2
/gnu/store/c4vz6q8i552yhqj6sq8cw5xqcjv8g3cf-glib-2.70.2
guix install: error:    ... propagated from dconf@0.40.0
guix install: error:    ... propagated from meld@3.20.4
hint: Try upgrading both `guile-g-golf' and `meld', or remove one of
them from the profile.

while the suggested solution works (I did not install one of the two),
I wonder is there a better way to solve this, like somehow
automatically update the dependency, as clearly meld shall be able to
use the later glib present?

Re: "profile contains conflicting entries"

[Andy Tai]

Hi, to add some info,

currently gnu/packages/glib.scm in guix.git defines
glib at version 2.70.2
and
glib-next at version 2.73.3

and meld depends on glib while  guile-g-golf depends on glib-next

supposedly glib-next can replace glib but I assume that may impact
many gnome things and may be risky.

In any case, suggestions on work sounds would be greatly appreciated

On Mon, Jan 16, 2023 at 10:49 AM Andy Tai <atai@atai.org> wrote:
>
> Hi, I run into this:
>
> $ guix install guile-g-golf
> The following package will be installed:
>    guile-g-golf 0.8.0-a.1
>
> guix install: error: profile contains conflicting entries for glib
> guix install: error:   first entry: glib@2.73.3
> /gnu/store/514nix1lfipx98hd3prjhq9vcv9iiw01-glib-2.73.3
> guix install: error:    ... propagated from gobject-introspection@1.73.1
> guix install: error:    ... propagated from guile-g-golf@0.8.0-a.1
> guix install: error:   second entry: glib@2.70.2
> /gnu/store/c4vz6q8i552yhqj6sq8cw5xqcjv8g3cf-glib-2.70.2
> guix install: error:    ... propagated from dconf@0.40.0
> guix install: error:    ... propagated from meld@3.20.4
> hint: Try upgrading both `guile-g-golf' and `meld', or remove one of
> them from the profile.
>
> while the suggested solution works (I did not install one of the two),
> I wonder is there a better way to solve this, like somehow
> automatically update the dependency, as clearly meld shall be able to
> use the later glib present?

Re: "profile contains conflicting entries"

[Andy Tai]

for what it is worth, this succeeds in installation

guix package  --allow-collisions -i  guile-g-golf  meld

whether something may not work properly, will see...

On Mon, Jan 16, 2023 at 2:17 PM Andy Tai <atai@atai.org> wrote:
>
> Hi, to add some info,
>
> currently gnu/packages/glib.scm in guix.git defines
> glib at version 2.70.2
> and
> glib-next at version 2.73.3
>
> and meld depends on glib while  guile-g-golf depends on glib-next
>
> supposedly glib-next can replace glib but I assume that may impact
> many gnome things and may be risky.
>
> In any case, suggestions on work sounds would be greatly appreciated
>
> On Mon, Jan 16, 2023 at 10:49 AM Andy Tai <atai@atai.org> wrote:
> >
> > Hi, I run into this:
> >
> > $ guix install guile-g-golf
> > The following package will be installed:
> >    guile-g-golf 0.8.0-a.1
> >
> > guix install: error: profile contains conflicting entries for glib
> > guix install: error:   first entry: glib@2.73.3

Re: "profile contains conflicting entries"

[Simon Tournier]

Hi Andy,

On Mon, 16 Jan 2023 at 10:49, Andy Tai <atai@atai.org> wrote:
> Hi, I run into this:
>
> $ guix install guile-g-golf
> The following package will be installed:
>    guile-g-golf 0.8.0-a.1
>
> guix install: error: profile contains conflicting entries for glib

That’s why propagated-inputs as submitted in:

    [bug#59829] [PATCH core-updates] gnu: wlroots: Add propagated input xcb-util-renderutil

<http://issues.guix.gnu.org/msgid/CAJsg1E8R14VGwoy6Lf=MO4BMYtCp44wETku5t8tEgksK_r2PXw@mail.gmail.com>

should be really avoided when it is possible. ;-)


Cheers,
simon