From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: Alex Kost <alezost@gmail.com>, help-guix@gnu.org
Subject: Re: Guix upgrade leads to different hashes
Date: Tue, 03 Oct 2017 21:56:26 +0200 [thread overview]
Message-ID: <87k20catud.fsf@gnu.org> (raw)
In-Reply-To: <87wp4c7eo5.fsf@gmail.com> (Oleg Pykhalov's message of "Tue, 03 Oct 2017 12:40:10 +0300")
Hi,
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> I made a dry-run, then upgrade, then dry-run. After diff those dry-runs
> shows nothing interesting.
>
> * 1st dry-run
>
>
>
> * 1st upgrade
>
>
>
> * 2nd dry-run
>
>
>
> * diff '1st dry-run' '2nd dry-run'
What does ‘guix package --list-generations’ show? The output is a diff
of the contents of each generation.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-10-03 19:56 UTC|newest]
Thread overview: 12+ 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 [this message]
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
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=87k20catud.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=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.
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).