unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>,
	Efraim Flashner <efraim@flashner.co.il>,
	42595@debbugs.gnu.org
Subject: bug#42595: conflicts in propagated imports must be resolved manually
Date: Wed, 13 Jul 2022 23:09:40 -0400	[thread overview]
Message-ID: <878rowz8y3.fsf@gmail.com> (raw)
In-Reply-To: <87364c2jem.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 24 Aug 2020 16:44:17 +0200")

Hi,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi Arne & Efraim,
>
> efraim Flashner <efraim@flashner.co.il> 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: 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.

[...]

> 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; 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.

--8<---------------cut here---------------start------------->8---
hint: To avoid conflicts, you can upgrade all of your package collection
at once with 'guix upgrade'.
--8<---------------cut here---------------end--------------->8---

Is this worth it?

Maxim




  reply	other threads:[~2022-07-14  3:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29  7:54 bug#42595: conflicts in propagated imports must be resolved manually Dr. Arne Babenhauserheide
2020-07-29  8:14 ` Efraim Flashner
2020-08-24 14:44   ` Ludovic Courtès
2022-07-14  3:09     ` Maxim Cournoyer [this message]
2022-07-15 13:31       ` Ludovic Courtès
2021-02-15 23:50 ` Luis Felipe via Bug reports for GNU Guix

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=878rowz8y3.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=42595@debbugs.gnu.org \
    --cc=arne_bab@web.de \
    --cc=efraim@flashner.co.il \
    --cc=ludo@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).