Subject: Re: bug#42595: conflicts in propagated imports must be resolved manually

From: Ludovic Courtès <[email-masked]>
Date: Fri, 15 Jul 2022 15:31:32 +0200

Hi,

Maxim Cournoyer <[email-masked]> skribis:

> Ludovic Courtès <[email-masked]> writes:

[...]

>>>> guix package: error: profile contains conflicting entries for glib
>>>> guix package: error: first entry: [email-masked]
>>>> /gnu/store/xr6zfqxklmr7skalljn5i071xmgqxbrm-glib-2.62.6
>>>> guix package: error:    ... propagated from [email-masked]
>>>> guix package: error:    ... propagated from [email-masked]
>>>> guix package: error: second entry: [email-masked]
>>>> /gnu/store/q4100sjqcsdi6b232ndr93vxfzv9bzij-glib-2.62.6
>>>> guix package: error:    ... propagated from [email-masked]
>>>> 
>>>> 
>>>> This should be automated, so there would be just one step to add all
>>>> updates I need.
>
> [...]
>
>> Also, Arne, it seems to me that Guix alone cannot decide how to solve
>> that conflict; it’s up to the user.  Thoughts?
>
> I guess it could compute all the conflicts and then fail and show the
> results, so that the user wouldn't need to slowly iterate on its
> per-package findings;

Yes, that’d be an improvement.

> perhaps recommend to simply upgrade wholesale when the conflicts are
> too numerous?
> Perhaps it could even *already* make such a recommendation when
> encountering conflicts, e.g.
>
> hint: To avoid conflicts, you can upgrade all of your package collection
> at once with 'guix upgrade'.

Yes, we could adjust the second message in
‘display-collision-resolution-hint’ along these lines.

Thanks,
Ludo’.