From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [WIP] New package: deno-1.32.3
Date: Thu, 27 Jul 2023 03:47:02 +0200 [thread overview]
Message-ID: <20230727014702.LsDVb93ViJGThRFaOUzGeK5DqEPMlUsotbvl4SPf8sA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43368@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2909 bytes --]
There's a closed pull request on the void-packages repository
[WIP] New package: deno-1.32.3
https://github.com/void-linux/void-packages/pull/43368
Description:
[ci skip]
Closes [21937](https://github.com/void-linux/void-packages/issues/21937)
Supersedes:
- [22043](https://github.com/void-linux/void-packages/pull/22043)
- [25436](https://github.com/void-linux/void-packages/pull/25436)
#### Testing the changes
- I tested the changes in this PR: **NO**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
Current error log:
```
Compiling futures v0.3.27
error: failed to run custom build command for `v8 v0.68.0`
Caused by:
process didn't exit successfully: `/builddir/deno-1.32.3/target/release/build/v8-b2ba9187d5e6450d/build-script-build` (exit status: 101)
--- stdout
cargo:rerun-if-changed=.gn
cargo:rerun-if-changed=BUILD.gn
cargo:rerun-if-changed=src/binding.cc
cargo:rerun-if-env-changed=CCACHE
cargo:rerun-if-env-changed=CLANG_BASE_PATH
cargo:rerun-if-env-changed=DENO_TRYBUILD
cargo:rerun-if-env-changed=DOCS_RS
cargo:rerun-if-env-changed=GN
cargo:rerun-if-env-changed=GN_ARGS
cargo:rerun-if-env-changed=HOST
cargo:rerun-if-env-changed=NINJA
cargo:rerun-if-env-changed=OUT_DIR
cargo:rerun-if-env-changed=RUSTY_V8_ARCHIVE
cargo:rerun-if-env-changed=RUSTY_V8_MIRROR
cargo:rerun-if-env-changed=SCCACHE
cargo:rerun-if-env-changed=V8_FORCE_DEBUG
cargo:rerun-if-env-changed=V8_FROM_SOURCE
cargo:rerun-if-env-changed=PYTHON
cargo:rustc-link-lib=static=rusty_v8
download lockfile: "/builddir/deno-1.32.3/target/release/build/lib_download.fslock"
static lib URL: https://github.com/denoland/rusty_v8/releases/download/v0.68.0/librusty_v8_release_x86_64-unknown-linux-gnu.a
cargo:rustc-link-search=/builddir/deno-1.32.3/target/release/gn_out/obj
Downloading https://github.com/denoland/rusty_v8/releases/download/v0.68.0/librusty_v8_release_x86_64-unknown-linux-gnu.a
Python downloader failed, trying with curl.
--- stderr
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', /host/cargo/registry/src/index.crates.io-6f17d22bba15001f/v8-0.68.0/build.rs:409:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
=> ERROR: deno-1.32.3_1: do_build: '${make_cmd} build --release --target ${RUST_TARGET} ${configure_args}' exited with 101
=> ERROR: in do_build() at common/build-style/cargo.sh:8
```
prev parent reply other threads:[~2023-07-27 1:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 4:43 [PR PATCH] " astralchan
2023-04-10 5:30 ` icp1994
2023-04-10 5:44 ` icp1994
2023-04-10 7:34 ` [PR PATCH] [Updated] " astralchan
2023-04-10 7:34 ` astralchan
2023-04-10 11:17 ` astralchan
2023-04-10 13:03 ` astralchan
2023-04-12 10:34 ` [PR PATCH] [Updated] " astralchan
2023-04-12 10:44 ` astralchan
2023-04-12 11:02 ` astralchan
2023-04-12 11:04 ` astralchan
2023-07-12 2:06 ` github-actions
2023-07-27 1:47 ` github-actions [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230727014702.LsDVb93ViJGThRFaOUzGeK5DqEPMlUsotbvl4SPf8sA@z \
--to=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).