unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Nathan Wilcox via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 55249@debbugs.gnu.org
Subject: bug#55249: `guix pull` crash
Date: Thu, 5 May 2022 14:54:15 -0700	[thread overview]
Message-ID: <CAK8perB1M1OPi_vGh9cAALVTLaXMB26a4rWGAmeicTjbpjh-WQ@mail.gmail.com> (raw)
In-Reply-To: <AE6CCE48-4B71-4E24-8255-A05A1A01FF47@lepiller.eu>

[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]

It completed successfully.

On Tue, May 3, 2022 at 10:27 PM Julien Lepiller <julien@lepiller.eu> wrote:

> Hi Nathan,
>
> I believe this was caused by a network issue (&nar-error). We lost our
> main server for a few hours when you tried running guix pull.
>
> Could you try again and report success/failure?
>
> Thanks for reporting the issue! It's much appreciated :)
>
> On May 3, 2022 9:44:19 PM GMT+02:00, Nathan Wilcox via Bug reports for GNU
> Guix <bug-guix@gnu.org> wrote:
>>
>> Hi,
>>
>> I just started using guix and have only used `guix pull` and `guix
>> search` so far. I used `guix pull` successfully a few days ago, and decided
>> to rerun it today to see if it takes less time, and it resulted in a
>> stacktrace (attached).
>>
>> This is a foreign-distro install on Debian 10 Buster. It's running inside
>> a 'crostini' lxc vm built into ChromeOS.
>>
>> Also, while I'm here, I read about `guix shell` and it was the primary
>> motivation for me to install since I wanted to do a project-specific
>> dependency configuration, but after following the instructions in [1]
>> running `guix shell` says `guix: shell: command not found`. I have tried
>> `guix search` with various patterns (`shell`, `guix.*shell`, etc…) but I
>> haven't been able to find out how to install it. Furthermore [1] introduces
>> it, so I am confused if I missed some critical setup step, even though I
>> followed the install section. Any advice?
>>
>> links:
>> [1]  https://guix.gnu.org/manual/devel/en/html_node/Installation.html
>>
>> --
>>
>> Nathan Wilcox
>>
>> Chief Research Officer
>>
>> nathan@electriccoin.co | @least_nathan <https://twitter.com/least_nathan>
>>
>>
>>

-- 

Nathan Wilcox

Chief Research Officer

nathan@electriccoin.co | @least_nathan <https://twitter.com/least_nathan>

[-- Attachment #2: Type: text/html, Size: 5994 bytes --]

  reply	other threads:[~2022-05-05 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 19:44 bug#55249: `guix pull` crash Nathan Wilcox via Bug reports for GNU Guix
2022-05-04  5:27 ` Julien Lepiller
2022-05-05 21:54   ` Nathan Wilcox via Bug reports for GNU Guix [this message]
2022-05-06  4:57     ` Julien Lepiller

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=CAK8perB1M1OPi_vGh9cAALVTLaXMB26a4rWGAmeicTjbpjh-WQ@mail.gmail.com \
    --to=bug-guix@gnu.org \
    --cc=55249@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=nathan@electriccoin.co \
    /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).