Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] [NOMERGE] rustup: update to 1.24.0.
Date: Wed, 28 Apr 2021 10:55:16 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30557@inbox.vuxu.org> (raw)

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

There is a new pull request by jcgruenhage against master on the void-packages repository

https://github.com/jcgruenhage/void-packages rustup-1.24.0_1
https://github.com/void-linux/void-packages/pull/30557

[NOMERGE] rustup: update to 1.24.0.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

This release of rustup does have a bug, so we shouldn't merge this one yet, just built this in prep for rustup 1.24.1, or how their fix release is going to be called.

> Shortly after publishing the release we got reports of a regression preventing users from running rustfmt and cargo fmt after upgrading to Rustup 1.24.0. To limit the damage we reverted the release to version 1.23.1.

A patch file from https://github.com/void-linux/void-packages/pull/30557.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rustup-1.24.0_1-30557.patch --]
[-- Type: text/x-diff, Size: 1131 bytes --]

From 0b2578543e017f233d0aea2f2862e575bc3aafb1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Wed, 28 Apr 2021 10:49:58 +0200
Subject: [PATCH] rustup: update to 1.24.0.

---
 srcpkgs/rustup/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/rustup/template b/srcpkgs/rustup/template
index e4f985f74ec4..6f34ed22bfb2 100644
--- a/srcpkgs/rustup/template
+++ b/srcpkgs/rustup/template
@@ -1,7 +1,7 @@
 # Template file for 'rustup'
 pkgname=rustup
-version=1.23.1
-revision=3
+version=1.24.0
+revision=1
 # rustup doesn't recognize this target
 archs="~armv*-musl"
 build_style=cargo
@@ -14,7 +14,7 @@ maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
 license="Apache-2.0, MIT"
 homepage="https://www.rustup.rs"
 distfiles="https://github.com/rust-lang/${pkgname}/archive/${version}.tar.gz"
-checksum=0203231bfe405ee1c7d5e7e1c013b9b8a2dc87fbd8474e77f500331d8c26365f
+checksum=ac19cc27458e581cc66929655fce30e26a66e13c53f7ef7fb22f08f2a1d85db9
 
 post_build() {
 	RUSTUP="target/${RUST_TARGET}/release/rustup-init"

             reply	other threads:[~2021-04-28  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  8:55 jcgruenhage [this message]
2021-05-03  9:43 ` [PR PATCH] [Updated] " jcgruenhage
2021-06-11  1:04 ` rustup: update to 1.24.1 cinerea0
2021-06-18 18:46 ` jcgruenhage
2021-06-18 19:13 ` [PR PATCH] [Updated] " jcgruenhage

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30557@inbox.vuxu.org \
    --to=jcgruenhage@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).