unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 31142@debbugs.gnu.org, ludo@gnu.org, mail@ambrevar.xyz
Subject: bug#31142: guix package --upgrade reverses the order of packages
Date: Thu, 28 Mar 2019 13:01:29 +0000	[thread overview]
Message-ID: <783C112A-8BD6-4BB6-B20C-65B74F3BF649@gmail.com> (raw)
In-Reply-To: <87ftr7cgfz.fsf@gnu.org>



On March 28, 2019 12:49:04 PM UTC, "Ludovic Courtès" <ludo@gnu.org> wrote:
>Hello,
>
>Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>
>> This issue fixes the list order, but it was initially supposed to
>address
>> https://lists.gnu.org/archive/html/help-guix/2018-04/msg00070.html.
>>
>> In the linked conversation, the issue that was raised is that "guix
>> package --upgrade" always upgrades some (propagated?) inputs, even
>when
>> there is nothing to upgrade.
>>
>> I can still reproduce this issue on latest Guix.
>> Anyone else?
>> Shall we open a new bug?
>
>Yes, and I think we’ll close it as “wontfix”.  :-)

May I ask why? It seems it'd be ideal if packages got upgraded only when needed; the false upgrades pollute the output of an upgrade and makes it less useful.

Maxim

  parent reply	other threads:[~2019-03-28 13:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13  5:57 bug#31142: guix package --upgrade reverses the order of packages Chris Marusich
2018-04-18 21:15 ` Ludovic Courtès
2019-01-15 11:07   ` Ludovic Courtès
2019-03-27 11:33 ` Pierre Neidhardt
2019-03-28 12:49   ` Ludovic Courtès
2019-03-28 12:56     ` Pierre Neidhardt
2019-03-28 13:30       ` Ludovic Courtès
2019-03-28 13:53         ` Pierre Neidhardt
2019-03-28 14:10           ` Ludovic Courtès
2019-03-28 13:01     ` Maxim Cournoyer [this message]
2019-03-28 13:13       ` Pierre Neidhardt

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=783C112A-8BD6-4BB6-B20C-65B74F3BF649@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=31142@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).