From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Maxime Devos" <maximedevos@telenet.be>,
"Nicolas Graves" <ngraves@ngraves.fr>, <56775@debbugs.gnu.org>
Subject: [bug#56775] [PATCH 2/4] gnu: rust-adler32-1: Update to 1.2.0.
Date: Tue, 26 Jul 2022 11:51:24 +0100 [thread overview]
Message-ID: <CLPJ3Z5BGCM3.1EVER0OMAPG7F@guix-aspire> (raw)
In-Reply-To: <e6617370-0c4f-664c-d8d5-08454ab6dcb2@telenet.be>
On Tue Jul 26, 2022 at 11:47 AM BST, Maxime Devos wrote:
> This is true for some kind of dependencies (e.g., build-dependencies
> IIRC) but not for other kind of dependencies (e.g. dependencies) IIRC. I
> don't know which of them is the case for dev-dependencies.
That has not been the case in my experience; Cargo seems to want them all
to be provided.
-- (
next prev parent reply other threads:[~2022-07-26 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 6:41 [bug#56775] [PATCH] gnu: rust-miniz-oxide: Do not skip build Nicolas Graves via Guix-patches via
2022-07-26 7:26 ` [bug#56775] [PATCH 1/4] gnu: Add rust-adler-1 Nicolas Graves via Guix-patches via
2022-07-26 7:26 ` [bug#56775] [PATCH 2/4] gnu: rust-adler32-1: Update to 1.2.0 Nicolas Graves via Guix-patches via
2022-07-26 10:14 ` Maxime Devos
2022-07-26 10:21 ` ( via Guix-patches via
2022-07-26 10:47 ` Maxime Devos
2022-07-26 10:51 ` ( via Guix-patches via [this message]
2022-07-26 16:33 ` Nicolas Graves via Guix-patches via
2022-07-27 9:45 ` Marius Bakke
2022-07-26 7:26 ` [bug#56775] [PATCH 3/4] gnu: Add rust-simd-adler32-0.3 Nicolas Graves via Guix-patches via
2022-07-26 7:26 ` [bug#56775] [PATCH 4/4] gnu: Add rust-miniz-oxide-0.5 Nicolas Graves via Guix-patches via
2022-07-26 10:17 ` Maxime Devos
2022-07-26 17:06 ` [bug#56775] [PATCH] " Nicolas Graves via Guix-patches via
2022-07-26 18:17 ` Nicolas Graves via Guix-patches via
2022-07-27 9:52 ` bug#56775: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CLPJ3Z5BGCM3.1EVER0OMAPG7F@guix-aspire \
--to=guix-patches@gnu.org \
--cc=56775@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=ngraves@ngraves.fr \
--cc=paren@disroot.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 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.