Hi Arne & Efraim, efraim Flashner <[email protected]> skribis:
> 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. [...] >> 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: [email protected] >> /gnu/store/xr6zfqxklmr7skalljn5i071xmgqxbrm-glib-2.62.6 >> guix package: error: ... propagated from [email protected] >> guix package: error: ... propagated from [email protected] >> guix package: error: second entry: [email protected] >> /gnu/store/q4100sjqcsdi6b232ndr93vxfzv9bzij-glib-2.62.6 >> guix package: error: ... propagated from [email protected] >> >> >> 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? Also, Arne, it seems to me that Guix alone cannot decide how to solve that conflict; it’s up to the user. Thoughts? Ludo’.
