On Wed, Jul 29, 2020 at 09:54:07AM +0200, Dr. Arne Babenhauserheide wrote:
> Hi,
> 
> When I get conflicts in propagated imports, I must follow a mechanical
> multi-step process to resolve them manually.
> 
> A recent example: I wanted to install guile-gi. In the first step I was
> told to also update python-pycairo, and in the next steps I had to add,
> one by one,
> 
> 
> dbus-glib cairo guile-charting libsoup poppler pango
> 
> And now I gave up. I’m now here and out of time:
> 
> LANG=C guix package -i guile-gi python-pycairo dbus-glib cairo guile-charting libsoup poppler pango
> The following packages will be upgraded:
>    python-pycairo (dependencies or package changed)
>    dbus-glib      (dependencies or package changed)
>    cairo          (dependencies or package changed)
>    guile-charting (dependencies or package changed)
>    libsoup        (dependencies or package changed)
>    poppler        (dependencies or package changed)
>    pango          (dependencies or package changed)
> 
> The following package will be installed:
>    guile-gi 0.3.0
> 
> guix package: error: profile contains conflicting entries for glib
> guix package: error:   first entry: glib@2.62.6 /gnu/store/xr6zfqxklmr7skalljn5i071xmgqxbrm-glib-2.62.6
> guix package: error:    ... propagated from cairo@1.16.0
> guix package: error:    ... propagated from pango@1.44.7
> guix package: error:   second entry: glib@2.62.6 /gnu/store/q4100sjqcsdi6b232ndr93vxfzv9bzij-glib-2.62.6
> guix package: error:    ... propagated from libnotify@0.7.7
> 
> 
> This should be automated, so there would be just one step to add all
> updates I need.

Are all of the packages from the same guix commit? What if you try
running 'guix package -u' to upgrade all your packages first and then
installing new ones?


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted