unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Chris Keschnat via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Re: "profile contains conflicting entries..." for packages with the same version
Date: Sat, 18 Jun 2022 20:14:45 +0200	[thread overview]
Message-ID: <bf36b38b-2341-2364-9067-a1d16d1b3d8c@catsu.it> (raw)
In-Reply-To: <e0f0126d-19d1-2fae-d288-06378392db8d@catsu.it>

Just for completeness:

I now realized that the mu package installs mu4e and have disabled 
building mu4e in straight.el (:straight (:type built-in)).

That solves every problem I had.

On 6/18/2022 6:51 PM, Chris Keschnat via wrote:
> 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: 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


      reply	other threads:[~2022-06-18 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18 14:04 "profile contains conflicting entries..." for packages with the same version Chris Keschnat via
2022-06-18 14:27 ` Tobias Geerinckx-Rice
2022-06-18 16:51   ` Chris Keschnat via
2022-06-18 18:14     ` Chris Keschnat via [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=bf36b38b-2341-2364-9067-a1d16d1b3d8c@catsu.it \
    --to=help-guix@gnu.org \
    --cc=chris@catsu.it \
    /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.
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).