From: Leo Famulari <leo@famulari.name>
To: 47667@debbugs.gnu.org
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: bug#47667: rust-rav1e-0.4 fails to build
Date: Fri, 9 Apr 2021 01:27:53 -0400 [thread overview]
Message-ID: <YG/l2c5WaPM9/Vp6@jasmine.lan> (raw)
While looking into upgrading the rav1e package, I noticed a new
rust-rav1e-0.4.0 package. However, it fails to build, like this:
------
starting phase `package'
Packaging rav1e v0.4.0 (/tmp/guix-build-rust-rav1e-0.4.0.drv-0/rav1e-0.4.0)
error: failed to prepare local package for uploading
Caused by:
no matching package named `assert_cmd` found
location searched: registry `https://github.com/rust-lang/crates.io-index`
required by package `rav1e v0.4.0 (/tmp/guix-build-rust-rav1e-0.4.0.drv-0/rav1e-0.4.0)`
command "cargo" "package" "--no-metadata" "--no-verify" failed with status 101
builder for `/gnu/store/71dd3d1q50iwmqjab9528csp44k2nrh4-rust-rav1e-0.4.0.drv' failed with exit code 1
------
I checked the CI history:
https://ci.guix.gnu.org/search?query=rust-rav1e
The last successful build:
https://ci.guix.gnu.org/build/81950/details
The first failing build:
https://ci.guix.gnu.org/build/85107/details
By clicking the Evaluation number, you can learn the range of Git
commits that is different between these two builds. I took a look with
commands like this:
$ git log 77f1bd9dea3def1992603cbf24c4b0003fa3e0f0^..e598556ee524a62544e777b1f0dd80316ef41754 guix/build-system/cargo.scm
Maybe the build failure is fallout from 4d00185d6 (build-system/cargo:
Propagate crates across builds.)?
next reply other threads:[~2021-04-09 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 5:27 Leo Famulari [this message]
2021-04-09 5:48 ` bug#47667: rust-rav1e-0.4 fails to build Leo Famulari
2021-04-09 13:18 ` Nicolas Goaziou
2021-04-09 18:43 ` Leo Famulari
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=YG/l2c5WaPM9/Vp6@jasmine.lan \
--to=leo@famulari.name \
--cc=47667@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.