all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: 28743@debbugs.gnu.org
Cc: Alex Kost <alezost@gmail.com>
Subject: bug#28743: guix package dry-run upgrade shows not required derivations (UI issue)
Date: Sun, 08 Oct 2017 10:06:26 +0300	[thread overview]
Message-ID: <87376u5dal.fsf_-_@gmail.com> (raw)
In-Reply-To: <87tvzbj8o9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 07 Oct 2017 17:10:14 +0200")

Previous discussion thread and attached debugging files:
https://lists.gnu.org/archive/html/help-guix/2017-10/msg00000.html


After patching no new generation created.  But dry-run still shows
available upgrades and that will be build some derivations.

ludo@gnu.org (Ludovic Courtès) writes:

> I’ve pushed the above patch as eca16a3d1d9e6b2c064e0105c1015258bf2755f2.
> Now we need to fix the UI side of things.

  reply	other threads:[~2017-10-08  7:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02  2:15 Guix upgrade leads to different hashes Oleg Pykhalov
2017-10-02 19:35 ` Alex Kost
2017-10-03  9:40   ` Oleg Pykhalov
2017-10-03 19:56     ` Ludovic Courtès
2017-10-03 21:44       ` Oleg Pykhalov
2017-10-04  8:28         ` Ludovic Courtès
2017-10-05  0:10           ` Oleg Pykhalov
2017-10-05 13:08             ` Ludovic Courtès
2017-10-06 16:36               ` Oleg Pykhalov
2017-10-06 22:24                 ` Ludovic Courtès
2017-10-07  7:38                   ` Oleg Pykhalov
2017-10-07 15:10                     ` Ludovic Courtès
2017-10-08  7:06                       ` Oleg Pykhalov [this message]
2021-09-16  7:18                         ` bug#28743: guix package dry-run upgrade incorrect behaviour with verbosity zimoun
2022-01-04 23:06                           ` bug#28743: guix package dry-run upgrade shows not required derivations (UI issue) zimoun

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87376u5dal.fsf_-_@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=28743@debbugs.gnu.org \
    --cc=alezost@gmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.