unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mikko Räsänen via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 47760@debbugs.gnu.org
Subject: bug#47760: guix pull: error: You found a bug
Date: Mon, 19 Apr 2021 03:20:19 +0200	[thread overview]
Message-ID: <dd43697d-be49-cb7c-a974-c8ed6b5f8cd5@a22.dk> (raw)
In-Reply-To: <87o8ee2cen.fsf@gnu.org>

I have no idea what happened. Only that I was encouraged to send the bug 
report - so I did.

On 2021-04-16 22:38, Ludovic Courtès wrote:
> Hi,
>
> Mikko Räsänen <mikko@a22.dk> skribis:
>
>> applying 3 grafts for
>> /gnu/store/cdnrvbr03nhg8ly1msi65lz4m8k5l3cl-curl-7.76.0.drv ...
>> building /gnu/store/lam6h0qnr7bj7mr5hlix4glnf5f2wymk-zip-3.0.drv...
>> Backtrace:
> [...]
>
>> ./guix/store.scm:1373:15: ERROR:
>>    1. &store-protocol-error:
>>        message: "while setting up the build environment: getting
>> attributes of path `/etc/nsswitch.conf': No such file or directory"
>>        status: 1
>> guix pull: error: You found a bug: the program
> It looks as though /etc/nsswitch.conf disappeared while ‘guix pull’ was
> running.  Could it be what happened?
>
> The daemon currently assumes that this file exists.  We could remove
> that assumption since I think glibc is happy when it doesn’t exist, but
> that still looks weird.
>
> Thanks,
> Ludo’.




  reply	other threads:[~2021-04-19 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 20:15 bug#47760: guix pull: error: You found a bug Mikko Räsänen via Bug reports for GNU Guix
2021-04-16 20:38 ` Ludovic Courtès
2021-04-19  1:20   ` Mikko Räsänen via Bug reports for GNU Guix [this message]
2021-04-19 14:16     ` Maxime Devos
2021-09-05 15:54 ` bug#47760: Daemon fails to create build environment when /etc/nsswitch.conf is missing András Vöröskői

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=dd43697d-be49-cb7c-a974-c8ed6b5f8cd5@a22.dk \
    --to=bug-guix@gnu.org \
    --cc=47760@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mikko@a22.dk \
    /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).