From: Mark H Weaver <mhw@netris.org>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 37940@debbugs.gnu.org
Subject: bug#37940: endless "try upgrading both" cycles
Date: Sun, 27 Oct 2019 13:37:50 -0400 [thread overview]
Message-ID: <87v9saqeba.fsf@netris.org> (raw)
In-Reply-To: <87r22yldiv.fsf@web.de> (Arne Babenhauserheide's message of "Sun, 27 Oct 2019 10:54:16 +0100")
Hi Arne,
Arne Babenhauserheide <arne_bab@web.de> writes:
> When installing a package while some packages are not up to date, guix
> can require adding more and more packages to guix install:
[...]
> guix install: error: profile contains conflicting entries for util-linux
> guix install: error: first entry: util-linux@2.34 /gnu/store/xymkwf57x988q8cny2is1dgzrbr9xdfi-util-linux-2.34
> guix install: error: ... propagated from glib@2.60.6
> guix install: error: ... propagated from poppler@0.79.0
> guix install: error: second entry: util-linux@2.32.1 /gnu/store/8k4pnixpz73kxvxbjqajgbprjjmmgpxy-util-linux-2.32.1
> hint: Try upgrading both `poppler' and `util-linux', or remove one of them from the profile.
I just wanted to briefly mention that if you use the "declarative
approach" to specifying user profiles, via the --manifest option to
"guix package", you will avoid this problem entirely. I've been happily
using that approach for years, and I literally cannot remember the last
time I saw a "conflicting entries" message. I heartily recommend it.
Mark
next prev parent reply other threads:[~2019-10-27 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 9:54 bug#37940: endless "try upgrading both" cycles Arne Babenhauserheide
2019-10-27 17:37 ` Mark H Weaver [this message]
2019-10-27 22:46 ` Ludovic Courtès
2019-10-28 0:03 ` Arne Babenhauserheide
2019-10-31 9:28 ` Danny Milosavljevic
2019-10-30 11:20 ` Diego Nicola Barbato
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=87v9saqeba.fsf@netris.org \
--to=mhw@netris.org \
--cc=37940@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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).