From: zimoun <zimon.toutoune@gmail.com>
To: pierce glenn <pierceglenn@hotmail.com>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: guix install nyxt failure
Date: Wed, 02 Nov 2022 13:33:24 +0100 [thread overview]
Message-ID: <87o7tpfsdn.fsf@gmail.com> (raw)
In-Reply-To: <SN7PR14MB44464C8371C46BE49403F5F7A9359@SN7PR14MB4446.namprd14.prod.outlook.com>
Hi,
On sam., 29 oct. 2022 at 00:59, pierce glenn <pierceglenn@hotmail.com> wrote:
> For the past few weeks, I have had install failures with nyxt.
>
> I am running guix package manager on the Librem 5 and get the
> following. Always fails when it gets to inkscape. Anyone got pointers?
> I've heard to try --subsitute-urls, but I am already using the
> standard bordeaux and ci.guix. This is only a recent problem. Nyxt
> installed fine a month and a half ago, and I have loaded other
> software through guix without issue.
Currently, substitutes are only available for x86_64-linux and
i686-linux. For other systems – as Librem 5, I guess – Nyxt is failing,
probably because some dependencies.
However, you report an issue with inkscape when there is no path between
nyxt and inkscape; at least, it is what “guix graph --path nyxt
inkscape” says.
Then, you report,
--8<---------------cut here---------------start------------->8---
269 | Rect boundsFast() const override {
| ^~~~~~~~~~
47% [############### ]guix install: error: corrupt input while restoring archive from socket
;;If I try to run again
~ $ guix install nyxt
guix install: error: failed to connect to `/var/guix/daemon-socket/socket': Connection refused
--8<---------------cut here---------------end--------------->8---
when guix-daemon had been stopped. And that’s unexpected.
Cheers,
simon
next prev parent reply other threads:[~2022-11-02 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 0:59 guix install nyxt failure pierce glenn
2022-11-02 12:33 ` zimoun [this message]
2023-03-07 21:09 ` Simon Tournier
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=87o7tpfsdn.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=pierceglenn@hotmail.com \
/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).