unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Brian Woodcox <bw@inskydata.com>
Cc: help-guix@gnu.org
Subject: Re: *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS ***
Date: Thu, 01 Nov 2018 03:35:35 -0400	[thread overview]
Message-ID: <874ld1p7vh.fsf@netris.org> (raw)
In-Reply-To: <DC8E292C-1B94-4061-B1C6-B85162E48160@inskydata.com> (Brian Woodcox's message of "Wed, 31 Oct 2018 12:47:33 -0600")

Brian Woodcox <bw@inskydata.com> writes:
> Just to avoid me having to search, what command would I use to get the
> tail of the build log file.

If you know the file name in /gnu/store of one of the build's outputs,
you can pass that file name, e.g.:

  guix build --log-file /gnu/store/1mr5izrbxwd7cbq8m1xrqm45rzkibpsj-guile-2.2.3

If you know the file name of the derivation (/gnu/store/….drv) of the
build you're looking for, then you can use "guix build --log-file
/gnu/store/….drv".

If you built the package locally, another useful trick is to look for
the newest files in /var/log/guix/drvs/*/*, which you can list by
running "ls -ltr */* | tail" or "ls -ltr */*-guile-* | tail" from
/var/log/guix/drvs.

In some cases, it is sufficient to pass the package name with optional
version, e.g. "guix build --log-file guile@2.2.3", but not always.
Roughly, that command finds the log for the derivation that would have
been built right now if you ran the same command without "--log-file".
Note that this won't be the build you're looking for if you've run "guix
pull" since the relevant build was fresh, if either the package or one
of its transitive dependencies have changed.  Passing a simple package
name also won't work if the derivation you're looking for is a special
variant package which is hidden or not bound to a public variable.

For example, 'guile-final' in gnu/packages/commencement.scm is one such
variant.  It is one of the products of the early bootstrap, and the
Guile variant used to build most of the other packages in Guix.  This is
not the same guile that you get by running "guix build guile".

'guile-final' is a "hidden" package, but it can be specified using the
more general "--expression=<scheme-expression>" syntax:

  guix build --log-file --expression="(@@ (gnu packages commencement) \
                                          guile-final)"

Also note that there is a very simple mapping between build log file
names and derivation file names, perhaps best shown by example:

__/var/log/guix/drvs/wc/47q5cw4b23gy9hzzhxp09b804nippx-guile-2.2.3.drv.bz2
___________/gnu/store/wc47q5cw4b23gy9hzzhxp09b804nippx-guile-2.2.3.drv

       Mark

  reply	other threads:[~2018-11-01  7:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 15:42 *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS *** Brian Woodcox
2018-10-31 17:41 ` Leo Famulari
2018-10-31 18:23   ` Brian Woodcox
2018-10-31 18:35 ` Mark H Weaver
2018-10-31 18:47   ` Brian Woodcox
2018-11-01  7:35     ` Mark H Weaver [this message]
2018-10-31 20:50   ` Brian Woodcox
2018-10-31 21:54     ` George Clemmer
2018-10-31 22:30       ` Brian Woodcox
2018-10-31 23:44         ` George Clemmer
2018-11-01  2:33           ` Mark H Weaver
2018-11-01  3:35             ` George Clemmer
2018-10-31 22:47       ` Mark H Weaver
2018-10-31 23:57         ` George Clemmer
2018-11-01  0:09           ` George Clemmer
2018-11-06 15:27             ` swedebugia
2018-11-06 18:24               ` George Clemmer
2018-11-07 11:40                 ` swedebugia
2018-11-07 13:01                   ` George Clemmer
2018-11-07 15:16         ` Christopher Lemmer Webber
2018-11-01  1:35     ` Mark H Weaver
2018-11-01  2:58       ` Brian Woodcox
2018-11-06  5:14       ` Mark H Weaver
2018-11-06 17:08         ` Brian Woodcox
2018-11-06 23:22           ` Brian Woodcox

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=874ld1p7vh.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=bw@inskydata.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).