Hi Tobias,
thank you. I did have a look at the remmina package and also suspected
the bin output but wasn't sure. Installing glib:bin does work.
| Installing libraries by hand isn't something ‘most average users
regularly’ do in Guix.
This is due to me not yet knowing "the guix way" / packaging very well,
but I also liking to go all-in (meaning I do use guix as my main machine).
I wanted to (and have) installed mu4e. The installation with straight.el
failed so I went into the directory to see what the problem was and
installed the dependencies that "make test" told me were missing.
Thanks
Chris
On 6/18/2022 4:27 PM, Tobias Geerinckx-Rice wrote:
Hi Chris,
Chris Keschnat via 写道：
guix install: error: profile contains conflicting entries for glib
guix install: error: first entry: [email protected]
/gnu/store/zqy7rhv26ax5ng8ws3d3vs8gr1k1k491-glib-2.70.2
guix install: error: second entry: [email protected]
/gnu/store/1gdvmmgimszagxr0l78kcx398c5g6608-glib-2.70.2
guix install: error: ... propagated from [email protected]
guix install: error: ... propagated from [email protected]
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
