all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Csepp <raingloom@riseup.net>
Cc: 66553@debbugs.gnu.org
Subject: bug#66553: Request to merge rust-team
Date: Sun, 15 Oct 2023 15:37:46 +0300	[thread overview]
Message-ID: <ZSvdGvi23nJwxjZx@3900XT> (raw)
In-Reply-To: <cuclec4gj9r.fsf@riseup.net>

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

On Sun, Oct 15, 2023 at 02:30:07PM +0200, Csepp wrote:
> 
> Efraim Flashner <efraim@flashner.co.il> writes:
> 
> > [[PGP Signed Part:Undecided]]
> > IMO rust-team branch is ready to merge. We've updated rust to 1.70,
> > librsvg to 2.56.4 and many new and updated packages. We've added a
> > phase
> > to the cargo-build-system to fail if it detects pre-built files and
> > we've set the cargo-build-system to skip the test phase by default,
> > allowing us to make sure that the packages have the correct inputs.
> > With
> > these changes I've gotten 100% of the packages built using the
> > cargo-build-system to build successfully.
> >
> > We're looking forward to this merge so we can continue bumping the
> > rust
> > version, work on cross-compilation and try to reduce the number of
> > packages which skip the build phase entirely.
> 
> Is the new build system still being worked on?

I haven't started working on integrating it yet.

-- 
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 --]

      reply	other threads:[~2023-10-15 12:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15  6:43 bug#66553: Request to merge rust-team Efraim Flashner
2023-10-15 12:30 ` Csepp
2023-10-15 12:37   ` Efraim Flashner [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=ZSvdGvi23nJwxjZx@3900XT \
    --to=efraim@flashner.co.il \
    --cc=66553@debbugs.gnu.org \
    --cc=raingloom@riseup.net \
    /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.