unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Luis Felipe via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "42595@debbugs.gnu.org" <42595@debbugs.gnu.org>
Subject: bug#42595: conflicts in propagated imports must be resolved manually
Date: Mon, 15 Feb 2021 23:50:58 +0000	[thread overview]
Message-ID: <26TPPMNuR0Hbjdp46UOl0a-R5TI3dAXwtWvtlEhC14cJkW-QLhH6sKKNb7OxNjjFvMsr1KQr7r8DROortI9YNpouh81eiqTGERtxwpSDThg=@protonmail.com> (raw)
In-Reply-To: <87o8nylpsw.fsf@web.de>

I get this problem from time to time in my user profile, and it is really annoying because doing what the hint says rarely fixes the problem easily. If you follow the hint, you end up wasting a lot of time when you get into that loop of "hint: Try upgrading both `PACKAGE_I_WANT_TO_INSTALL' and `SOME_PACKAGE_IN_THE_PROFILE', or remove one of them from the profile."

I always forget that the solution is to upgrade all packages in the profile. So maybe the hint should suggest that instead?

So it seems I always get into this problem because I use "guix install PACKAGE" and also "guix upgrade SINGLE_PACKAGE", as I don't always have the time to upgrade the whole profile (which contains almost 100 packages, some of which may have no substitutes and may also have a failing phase, which can result in more wasted time).

I'll need to build the habit of using the declarative approach instead to modify my profile, as Mark Weaver suggests in https://issues.guix.gnu.org/37940 (which, by the way, seems like a duplicate of this issue).

> Also, Arne, it seems to me that Guix alone cannot decide how to solve that conflict; it’s up to the user.

That's understandable but unsatisfying :)




      parent reply	other threads:[~2021-02-15 23:52 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
2022-07-15 13:31       ` Ludovic Courtès
2021-02-15 23:50 ` Luis Felipe via Bug reports for GNU Guix [this message]

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='26TPPMNuR0Hbjdp46UOl0a-R5TI3dAXwtWvtlEhC14cJkW-QLhH6sKKNb7OxNjjFvMsr1KQr7r8DROortI9YNpouh81eiqTGERtxwpSDThg=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=42595@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    /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).