GNU bug report logs -
#42595
conflicts in propagated imports must be resolved manually
Previous Next
Full log
View this message in rfc822 format
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
> Ludovic Courtès <ludo <at> gnu.org> writes:
[...]
>>>> guix package: error: profile contains conflicting entries for glib
>>>> guix package: error: first entry: glib <at> 2.62.6
>>>> /gnu/store/xr6zfqxklmr7skalljn5i071xmgqxbrm-glib-2.62.6
>>>> guix package: error: ... propagated from cairo <at> 1.16.0
>>>> guix package: error: ... propagated from pango <at> 1.44.7
>>>> guix package: error: second entry: glib <at> 2.62.6
>>>> /gnu/store/q4100sjqcsdi6b232ndr93vxfzv9bzij-glib-2.62.6
>>>> guix package: error: ... propagated from libnotify <at> 0.7.7
>>>>
>>>>
>>>> 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’.
This bug report was last modified 2 years and 334 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.