From: Giovanni Biscuolo <g@xelera.eu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: guix pull extremely verbose (with no ----verbose)
Date: Thu, 23 May 2019 16:48:03 +0200 [thread overview]
Message-ID: <87o93t5isc.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <87d0k9gsol.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1955 bytes --]
Hi Ricardo,
Thank you for helping
Ricardo Wurmus <rekado@elephly.net> writes:
>> I've run "guix pull" many many times since today but now after that
>> command I see a lot of logs like this one:
>>
>> --8<---------------cut here---------------start------------->8---
>> @ build-log 9461 44
>> checking if GSS-API support is requested... @ build-log 9461 4
>> yes
>> @ build-log 9461 28
>> checking gss.h usability... @ build-log 9461 4
>> yes
> […]
>
> Are you using an old daemon? These are hints that are filtered by the
> daemon — if it is recent enough.
Is guix-daemon 1.0.0 recent enough?
On the Guix System machine:
--8<---------------cut here---------------start------------->8---
~$ sudo -i guix-daemon --version
guix-daemon (GNU Guix) 1.0.1-1.8204295
--8<---------------cut here---------------end--------------->8---
That machine finished "guix pull" in more or less 33 mins, it's a 32
cores machine with 64GB RAM
After that now "guix pull" does not output debug messages
On the foreign distro machine:
--8<---------------cut here---------------start------------->8---
$ sudo -i guix-daemon --version
guix-daemon (GNU Guix) 1.0.0-1.326dcbf
--8<---------------cut here---------------end--------------->8---
Anyway it was running since Wed 2019-05-15 11:43:04 CEST (1 weeks 1 days
ago): I restarted and "guix pull"ed again...
--8<---------------cut here---------------start------------->8---
$ time guix pull
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
Building from this channel:
guix https://git.savannah.gnu.org/git/guix.git a9150d4
--8<---------------cut here---------------end--------------->8---
and I still get a lot of verbose output... this time I'm going to wait
until it'll finish (previously I always interrupted it)
[...]
Thanks! Gio'.
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-05-23 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 10:40 guix pull extremely verbose (with no ----verbose) Giovanni Biscuolo
[not found] ` <87d0k9gsol.fsf@elephly.net>
2019-05-23 14:48 ` Giovanni Biscuolo [this message]
2019-05-24 6:24 ` Ricardo Wurmus
2019-05-24 7:38 ` bug#35877: " Giovanni Biscuolo
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=87o93t5isc.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).