help-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "profile contains conflicting entries..." for packages with the same


From: Tobias Geerinckx-Rice
Subject: Re: "profile contains conflicting entries..." for packages with the same version
Date: Sat, 18 Jun 2022 16:27:05 +0200

Hi Chris,

Chris Keschnat via 写道:

guix install: error: profile contains conflicting entries for glib
guix install: error:   first entry: glib@2.70.2
/gnu/store/zqy7rhv26ax5ng8ws3d3vs8gr1k1k491-glib-2.70.2
guix install: error:   second entry: glib@2.70.2
/gnu/store/1gdvmmgimszagxr0l78kcx398c5g6608-glib-2.70.2
guix install: error:    ... propagated from dconf@0.40.0
guix install: error:    ... propagated from remmina@1.4.23
hint: Try upgrading both `glib' and `remmina', or remove one of them
from the profile.


In general I think the solution would be to use multiple profiles[1]
if I had need for multiple versions of the same package?

In *general*, the solution is to upgrade both in the same transaction:

 $ guix install remmina glib

(because installing the latest remmina is equivalent to upgrading it).

However, in this particular case it won't work because remmina does seem to propagate a different glib than the ‘glib’ package exported to the CLI.

I don't have time to investigate, but it seems related to the :bin output, because

 $ guix install remmina glib:bin

works fine.

In general I think the solution would be to use multiple profiles[1]

Maybe, yes. For a meaningful answer we'll need to know why you're installing glib. Development? Installing libraries by hand isn't something ‘most average users regularly’ do in Guix.

But why does this happen here? The versions seem to be the same.

But the hashes aren't. Version numbers aren't very relevant in Guix (their main practical use is to make the CLI feel familiar), only whether the package is identical or not.

I did a "guix pull" and "guix upgrade" before and all packages should
be up to date.

Yes, they would be. That would often help mitigate this error, but sadly not in this case.

Kind regards,

T G-R

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]