unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 74958-done@debbugs.gnu.org
Subject: bug#74958: [PATCH rust-team 1/5] build/cargo.scm: Remove '--release' from default cargo-test-flags.
Date: Thu, 19 Dec 2024 14:52:16 +0200	[thread overview]
Message-ID: <Z2QXAFMAz4bGOtKr@3900XT> (raw)
In-Reply-To: <625c1e42f8e5cc01fd402d050710027431e2aab0.1734572533.git.maxim.cournoyer@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 498 bytes --]

I tried removing the '--release' from some of the cargo-test-flags and I
found other packaging errors that allowed me to remove entire
cargo-test-flags and not just '--release'. I've pushed this to the
rust-team branch.  This should help improve the quality of our rust
packages.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-12-19 12:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  1:43 [bug#74958] [PATCH rust-team 0/5] build/cargo.scm: Remove '--release' from default cargo-test-flags Maxim Cournoyer
2024-12-19  1:46 ` [bug#74958] [PATCH rust-team 1/5] " Maxim Cournoyer
2024-12-19  8:09   ` Efraim Flashner
2024-12-19 12:50     ` Maxim Cournoyer
2024-12-19 12:52   ` Efraim Flashner [this message]
2024-12-19  1:46 ` [bug#74958] [PATCH rust-team 2/5] gnu: rust-zerocopy-0.8: Reinstate all tests Maxim Cournoyer
2024-12-19  1:46 ` [bug#74958] [PATCH rust-team 3/5] gnu: rust-libc-0.2: Update to 0.2.168 Maxim Cournoyer
2024-12-19  1:46 ` [bug#74958] [PATCH rust-team 4/5] gnu: rust-zerocopy-0.8: Update to 0.8.13 Maxim Cournoyer
2024-12-19  1:46 ` [bug#74958] [PATCH rust-team 5/5] gnu: rust-zerocopy-derive-0.8: " Maxim Cournoyer

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=Z2QXAFMAz4bGOtKr@3900XT \
    --to=efraim@flashner.co.il \
    --cc=74958-done@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).