guix-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

02/02: doc: Sync the client and daemon --rounds options documentation.


From: guix-commits
Subject: 02/02: doc: Sync the client and daemon --rounds options documentation.
Date: Fri, 9 Oct 2020 16:57:59 -0400 (EDT)

apteryx pushed a commit to branch master
in repository guix.

commit 5918cb5341ecd76304eef2cb529e20896b56f4e5
Author: Maxim Cournoyer <maxim.cournoyer@gmail.com>
AuthorDate: Fri Oct 9 16:50:01 2020 -0400

    doc: Sync the client and daemon --rounds options documentation.
    
    Fixes <https://issues.guix.gnu.org/40867>.
    
    * doc/guix.texi (Common Build Options): Suggest using '--keep-failed' to 
keep
    differing build results in the store rather than 'guix archive'.
    
    Reported-by: Jonathan Brielmaier <jonathan.brielmaier@web.de>
---
 doc/guix.texi | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 94afdff..8514dfe 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -9155,11 +9155,9 @@ Non-deterministic build processes are a problem because 
they make it
 practically impossible for users to @emph{verify} whether third-party
 binaries are genuine.  @xref{Invoking guix challenge}, for more.
 
-Note that, currently, the differing build results are not kept around,
-so you will have to manually investigate in case of an error---e.g., by
-stashing one of the build results with @code{guix archive --export}
-(@pxref{Invoking guix archive}), then rebuilding, and finally comparing
-the two results.
+When used in conjunction with @option{--keep-failed}, the differing
+output is kept in the store, under @file{/gnu/store/@dots{}-check}.
+This makes it easy to look for differences between the two results.
 
 @item --no-offload
 Do not use offload builds to other machines (@pxref{Daemon Offload



reply via email to

[Prev in Thread] Current Thread [Next in Thread]