From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rust-sccache: update to 0.4.2.
Date: Tue, 25 Apr 2023 21:43:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43613@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages rust-sccache
https://github.com/void-linux/void-packages/pull/43613
rust-sccache: update to 0.4.2.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
A patch file from https://github.com/void-linux/void-packages/pull/43613.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rust-sccache-43613.patch --]
[-- Type: text/x-diff, Size: 1209 bytes --]
From e80534f43d348f12c148618d045766630dca4479 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Mon, 24 Apr 2023 19:54:42 +0530
Subject: [PATCH] rust-sccache: update to 0.4.2.
---
srcpkgs/rust-sccache/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/rust-sccache/template b/srcpkgs/rust-sccache/template
index ff1b3a4d27bf..5a4133d4d283 100644
--- a/srcpkgs/rust-sccache/template
+++ b/srcpkgs/rust-sccache/template
@@ -1,7 +1,7 @@
# Template file for 'rust-sccache'
pkgname=rust-sccache
-version=0.4.1
-revision=2
+version=0.4.2
+revision=1
build_style=cargo
# 1. requires expensive extra feature 2. requires clang 3. requires libc
make_check_args="-- --skip test_s3_invalid_args --skip test_sccache_command
@@ -14,7 +14,7 @@ license="Apache-2.0"
homepage="https://crates.io/crates/sccache"
changelog="https://github.com/mozilla/sccache/releases"
distfiles="https://static.crates.io/crates/sccache/sccache-${version}.crate"
-checksum=c2651cae8522bfad07ab58f8cd44886a4b47232c6e2b2e3be007825176b213b4
+checksum=5e4e2e0d3e14abc7a1698e3f873f9c7871c7f12d05bab4241fa38389881cdda9
case "$XBPS_TARGET_MACHINE" in
x86_64*|i686*|arm*|aarch64*) ;;
next reply other threads:[~2023-04-25 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 19:43 icp1994 [this message]
2023-04-25 20:11 ` [PR PATCH] [Updated] " icp1994
2023-04-27 2:31 ` [PR PATCH] [Merged]: " abenson
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-43613@inbox.vuxu.org \
--to=icp1994@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).