From: Jone <yeger9@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Error system reconfigure with guix-latest
Date: Sun, 4 Mar 2018 23:52:20 +0300 [thread overview]
Message-ID: <CAH6o9V-h7oPjOe8xw9hCMsoNAG=t3segpo4Q2ON7wQZtLVa+Gg@mail.gmail.com> (raw)
In-Reply-To: <87fu5fehqo.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]
Thanks. I rewrite config, following your advice and run 'guix system
--verbosity=10 reconfigure new.scm':
acquiring global GC lock `/var/guix/gc.lock'
acquiring read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
acquiring write lock on `/var/guix/temproots/434'
downgrading to read lock on `/var/guix/temproots/434'
...
and the same thing many more times.
This is a bug?
[-- Attachment #2: Type: text/html, Size: 2235 bytes --]
next prev parent reply other threads:[~2018-03-04 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 12:46 Error system reconfigure with guix-latest Jone
2018-03-04 15:01 ` 宋文武
2018-03-04 19:57 ` Alex Kost
2018-03-04 20:52 ` Jone [this message]
2018-03-05 8:38 ` Ludovic Courtès
2018-03-05 16:08 ` Jone
2018-03-05 17:05 ` Ludovic Courtès
2018-03-05 19:01 ` Jone
2018-03-06 15:47 ` Ludovic Courtès
2018-03-06 17:09 ` Jone
2018-03-07 21:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6o9V-h7oPjOe8xw9hCMsoNAG=t3segpo4Q2ON7wQZtLVa+Gg@mail.gmail.com' \
--to=yeger9@gmail.com \
--cc=alezost@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.