unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37940@debbugs.gnu.org
Subject: bug#37940: endless "try upgrading both" cycles
Date: Mon, 28 Oct 2019 01:03:48 +0100	[thread overview]
Message-ID: <87a79l7n2z.fsf@web.de> (raw)
In-Reply-To: <871ruxhkml.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]


Hi Mark and Ludovic,

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

> Hi Arne & Mark,
>
> Mark H Weaver <mhw@netris.org> skribis:
>> 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.

I’m just using guix install when I need a new package and guix remove
to clean up. Shouldn’t that be equivalent?

> Indeed.  Even if you don’t use the declarative approach, usually just
> upgrade everything (“guix upgrade”) and you won’t have any problems
> either.
>
> Problems arise when you try to upgrade only part of the packages.

This problem cuts in when the system is not fully up to date and I use
guix install.

> Now, it doesn’t sound right that ‘util-linux’ is propagated from glib
> and from poppler…?

Poppler needs glib at runtime and glib needs tools from util-linux at
runtime?

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

  reply	other threads:[~2019-10-28  0:05 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
2019-10-27 22:46   ` Ludovic Courtès
2019-10-28  0:03     ` Arne Babenhauserheide [this message]
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=87a79l7n2z.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=37940@debbugs.gnu.org \
    --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).