From: Alex Kost <alezost@gmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Guix upgrade leads to different hashes
Date: Mon, 02 Oct 2017 22:35:00 +0300 [thread overview]
Message-ID: <87tvzhcpi3.fsf@gmail.com> (raw)
In-Reply-To: <87o9pqz457.fsf@gmail.com> (Oleg Pykhalov's message of "Mon, 02 Oct 2017 05:15:32 +0300")
Oleg Pykhalov (2017-10-02 05:15 +0300) wrote:
> Hello Guix,
>
> Something strange happens on my machine with upgrades. I check for new
> available upgrades with dry-run and get “available upgrades” all the
> time.
[...]
> If I upgrade again I'll get same hashes as in “Check upgrades.”. Like a
> loop. It's not related to grafts, is it?
It is: since commit fd59105c4¹, --dry-run also disables grafts, so
using just "--dry-run" is the same as "--dry-run --no-grafts". It was
discussed in the following thread:
http://lists.gnu.org/archive/html/guix-devel/2016-07/msg01035.html
¹ http://git.savannah.gnu.org/cgit/guix.git/commit/?id=fd59105c49965db956fac73c68d8b00d068f5d5c
--
Alex
next prev parent reply other threads:[~2017-10-02 19:35 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 [this message]
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 ` bug#28743: guix package dry-run upgrade shows not required derivations (UI issue) Oleg Pykhalov
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=87tvzhcpi3.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=go.wigust@gmail.com \
--cc=help-guix@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 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.