From: Ricardo Wurmus <rekado@elephly.net>
To: Blackbeard <barbanegra@posteo.mx>
Cc: 35108@debbugs.gnu.org
Subject: bug#35108: ungoogled-chromium fails to install
Date: Tue, 02 Apr 2019 22:09:28 +0200 [thread overview]
Message-ID: <87ftr0yxs7.fsf@elephly.net> (raw)
In-Reply-To: <87mul8ibcy.fsf@posteo.mx>
Blackbeard <barbanegra@posteo.mx> writes:
> Hello, I am having trouble to install ungoogled-chromium.
>
> I've tried several times and with different 'guix pull' commits, but it
> keeps failing at around 84%. This is from the logs:
>
>
> ninja: build stopped: subcommand failed.
> Backtrace:
> 4 (primitive-load "/gnu/store/25402q0d5mdh4rkp155rh9j3vpj…")
> In ice-9/eval.scm:
> 191:35 3 (_ _)
> In srfi/srfi-1.scm:
> 863:16 2 (every1 #<procedure 487ce0 at /gnu/store/gfprsx2m62cvq…> …)
> In /gnu/store/gfprsx2m62cvqbh7ysc9ay9slhijvmal-module-import/guix/build/gnu-build-system.scm:
> 799:28 1 (_ _)
> In /gnu/store/gfprsx2m62cvqbh7ysc9ay9slhijvmal-module-import/guix/build/utils.scm:
> 616:6 0 (invoke _ . _)
>
> /gnu/store/gfprsx2m62cvqbh7ysc9ay9slhijvmal-module-import/guix/build/utils.scm:616:6: In procedure invoke:
> Throw to key `srfi-34' with args `(#<condition &invoke-error [program: "ninja" arguments: ("-C" "out/Release" "-j" "5" "chrome" "chromedriver") exit-status: 1 term-signal: #f stop-signal: #f] ab9b40>)'.
Unfortunately, you cropped the interesting part of the error message.
Can you show us more? It would interesting to see what happened before.
This backtrace just shows us that the command we invoke with “invoke”
returned an error. That’s not very helpful.
--
Ricardo
next prev parent reply other threads:[~2019-04-02 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 17:08 bug#35108: ungoogled-chromium fails to install Blackbeard
2019-04-02 20:09 ` Ricardo Wurmus [this message]
2019-05-16 13:48 ` Jeff Bauer
2019-05-16 14:52 ` Marius Bakke
2019-05-16 17:31 ` Jeff Bauer
2019-05-25 11:06 ` Marius Bakke
2020-04-07 19:27 ` Marius Bakke
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=87ftr0yxs7.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35108@debbugs.gnu.org \
--cc=barbanegra@posteo.mx \
/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).