From: sirmacik <sirmacik@wioo.waw.pl>
To: 37421@debbugs.gnu.org
Subject: bug#37421: node fails to build during update
Date: Mon, 16 Sep 2019 10:57:55 +0200 [thread overview]
Message-ID: <877e6839f0.fsf@wioo.waw.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hi,
I'm trying to update ungoogled-chromium package but it fails on node
build and this happens repeatedly:
(guix pull done before)
$ guix package -u
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
building /gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv...
| 'check' phasebuilder for `/gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv' failed with exit code 1
build of /gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv failed
View build log at '/var/log/guix/drvs/vk/49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv.bz2'.
cannot build derivation `/gnu/store/n6h5fv4isjjnqchpjfb5m7cv765s3vi0-ungoogled-chromium-76.0.3809.132-0.8eba5c0.drv': 1 dependencies couldn't be built
guix package: error: build of `/gnu/store/n6h5fv4isjjnqchpjfb5m7cv765s3vi0-ungoogled-chromium-76.0.3809.132-0.8eba5c0.drv' failed
I'm attaching log file from the build.
[-- Attachment #2: Log file from failed node build --]
[-- Type: application/octet-stream, Size: 115686 bytes --]
[-- Attachment #3: Type: text/plain, Size: 62 bytes --]
--
Thank you for your time!
sirmacik
PGP: 0xE0DC81D523891771
next reply other threads:[~2019-09-16 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 8:57 sirmacik [this message]
2019-09-16 13:52 ` bug#37421: [PATCH] gnu: node: Disable tests that fail with openssl@1.1.1d Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-09-16 16:09 ` Ludovic Courtès
2019-09-16 18:57 ` Jelle Licht
2019-09-16 21:39 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-09-17 14:43 ` Jelle Licht
2019-09-20 15:11 ` bug#37421: Apply nodejs test workaround? Jack Hill
2019-09-20 15: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=877e6839f0.fsf@wioo.waw.pl \
--to=sirmacik@wioo.waw.pl \
--cc=37421@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).