From: znavko@disroot.org
To: 35532@debbugs.gnu.org
Subject: bug#35532: guix-daemon was freezed
Date: Thu, 02 May 2019 05:44:06 +0000 [thread overview]
Message-ID: <39ad7bbe21c64ad71e2d7029f57d9f24@disroot.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
Yesterday, I ran updates with `guix pull && guix package -u`. My laptop warked all night long.
But this morning, I've discovered the update process stops without life on this step:
$ guix pull && guix package -u
...
downloading from https://ci.guix.info/nar/gzip/zqfbh4whwrzzhqa811i43dggyqh2lmwx-libevent-2.1.8...
libevent-2.1.8 787KiB 787KiB/s 00:01 [##################] 100.0%
building /gnu/store/9y4j59sbxg9igj774q8r04vz31c5clrc-bitcoin-core-0.17.1.drv...
substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
I think the Internet connection was the reason.
I stopped guix process and tryed to delete bitcoin-core, but this was not going again:
$ guix package -r bitcoin-core
The following package will be removed:
bitcoin-core 0.17.1 /gnu/store/3gi4m4c2x1hybxlxnh5ll7s474mzz0lj-bitcoin-core-0.17.1
^C^C
After that I typed remove fluidsynth in other terminal and the process was not going again:
$ guix package -r fluidsynth
The following package will be removed:
fluidsynth 2.0.4 /gnu/store/6zpn2p85412dalq7bpfz6sv89pg0hfsp-fluidsynth-2.0.4
^C
So, there I reconnect to Internet and restart guix-daemon with `# herd restart guix-daemon`, and everything goes fine.
I think it is a bug, cause guix-daemon did not delete packages. Some blocks present there when Internet goes down.
[-- Attachment #2: Type: text/html, Size: 1749 bytes --]
next reply other threads:[~2019-05-02 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 5:44 znavko [this message]
2019-05-03 9:46 ` bug#35532: guix-daemon was freezed Ludovic Courtès
2021-12-14 16:52 ` Maxim Cournoyer
2021-12-28 22:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=39ad7bbe21c64ad71e2d7029f57d9f24@disroot.org \
--to=znavko@disroot.org \
--cc=35532@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).