From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>,
Luis Felipe <luis.felipe.la@protonmail.com>
Cc: 43753@debbugs.gnu.org
Subject: bug#43753: rust-clippy does not provide the clippy command
Date: Fri, 02 Oct 2020 11:46:54 +0200 [thread overview]
Message-ID: <87h7rd7yep.fsf@nckx> (raw)
In-Reply-To: <2rbIiYx4GllHj49TJv9xIQllQEZFa8B_vusvuULy6SB0xRaiBpFOEBYiTkelDgNCegAhGiil7XNCO_hbSsMVN4Wmg3Du3uiYrwOf7dja-kU=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
Luis Felipe via Bug reports for GNU Guix 写道：
> In the #guix channel, mroh checked the "rust-clippy" package and
> mentioned that it doesn't seem to have any output, which looks
> like a bug.
No, it's intentional:
(arguments
`(#:skip-build? #t
This means that Clippy was packaged to satisfy a dependency of
another package, but not (yet) to be useful on its own.
When I try to build it, I get:
--8<---------------cut here---------------start------------->8---
error: failed to run custom build command for `clippy v0.0.302
Caused by:
process didn't exit successfully:
`/tmp/guix-build-rust-clippy-0.0.302.drv-0/clippy-0.0.302/target/release/build/clippy-bee5bea0d583d718/build-script-build`
(exit code: 1)
--- stderr
error: Clippy is no longer available via crates.io
help: please run `rustup component add clippy-preview` instead
--8<---------------cut here---------------end--------------->8---
It seems[0] to track Rust releases now.
Kind regards,
T G-R
[0]: https://github.com/rust-lang/rust-clippy/releases
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2020-10-02 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 0:08 bug#43753: rust-clippy does not provide the clippy command Luis Felipe via Bug reports for GNU Guix
2020-10-02 9:46 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [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
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=87h7rd7yep.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=43753@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=me@tobias.gr \
/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).