unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 44612@debbugs.gnu.org
Subject: bug#44612: Read standard input in `guix repl'
Date: Sat, 14 Nov 2020 15:12:10 +0100	[thread overview]
Message-ID: <875z6858p1.fsf@nckx> (raw)
In-Reply-To: <87pn4gxe8q.fsf@ambrevar.xyz>

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

Pierre Neidhardt 写道:
> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>
>> To ‘it does not work’ I can reply only that Nyxt doesn't build 
>> [log attached] on current master
>
> Shoot! :p
>
> Which architecture?

Boring old x86_64 I'm afraid.

> I builds for me on x86-64 at commit
> 403ba4140f52b9ea9483e4c775f102bbb9753e51.

I pulled to that commit but it's still the same ungrafted 
derivation 
(/gnu/store/bdi8dq8i3f59zxp7jrabas847dh80m7x-nyxt-2-pre-release-4.drv).

Building for the fourth time now, with -{M,c}1...

...nope, always the same error:

  Unhandled ASDF/FIND-COMPONENT:MISSING-DEPENDENCY in thread
    #<SB-THREAD:THREAD "main thread" RUNNING {1001898213}>:
  Component "cl-base64" not found, required by #<SYSTEM "dexador">

So I'm surprised it does build for you.  Weak Lisp-fu or not, that 
looks pretty deterministic to me.  Weird.

> Or is it a reproducibility issue?

No, it's an error in the ‘build’ phase.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2020-11-14 14:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  9:41 bug#44612: Read standard input in `guix repl' Pierre Neidhardt
2020-11-13 19:08 ` Bengt Richter
2020-11-13 22:24   ` zimoun
2020-11-16  9:25   ` Ludovic Courtès
2020-11-16 11:36     ` Pierre Neidhardt
2020-11-16 11:53       ` Pierre Neidhardt
2020-11-16 12:52       ` Ludovic Courtès
2020-11-16 16:11         ` Pierre Neidhardt
2020-11-13 20:27 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-14  9:52   ` Pierre Neidhardt
2020-11-14 11:23     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-14 13:19       ` Pierre Neidhardt
2020-11-14 13:58         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-14 15:03           ` Guillaume Le Vaillant
2020-11-14 15:07             ` Guillaume Le Vaillant
2020-11-14 16:06               ` Pierre Neidhardt
2020-11-14 15:22             ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-14 15:36               ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-14 16:11           ` Pierre Neidhardt
2020-11-14 15:43         ` Christopher Baines
2020-11-14 16:03           ` Pierre Neidhardt
2020-11-14 13:24       ` Pierre Neidhardt
2020-11-14 14:12         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-11-14 16:05           ` Pierre Neidhardt
2020-11-14 16:13             ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-14 16:25               ` Pierre Neidhardt
2020-11-14 17:08                 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-14 17:21                   ` Pierre Neidhardt
2020-11-14 17:33                     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-14 19:08                       ` zimoun
2020-11-16 10:45                         ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-16 11:38                           ` zimoun
2020-11-14 12:09     ` zimoun
2020-12-01  7:52 ` Ludovic Courtès
2020-12-01  8:29   ` Pierre Neidhardt
2020-12-03 10:22     ` Ludovic Courtès
2020-12-03 10:33       ` Pierre Neidhardt

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=875z6858p1.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=44612@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    --cc=me@tobias.gr \
    /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).