From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] cargo-crev: update to 0.23.1.
Date: Wed, 08 Jun 2022 16:52:31 +0200 [thread overview]
Message-ID: <20220608145231.sgUgT__Xresmo-NrYSI13yP0Km1gQiQ3d30WjcYX8_0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35486@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
There is an updated pull request by jcgruenhage against master on the void-packages repository
https://github.com/jcgruenhage/void-packages cargo-crev-0.23.0_1
https://github.com/void-linux/void-packages/pull/35486
cargo-crev: update to 0.23.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->
Build currently fails..
#### Testing the changes
- I tested the changes in this PR: **NO**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/35486.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cargo-crev-0.23.0_1-35486.patch --]
[-- Type: text/x-diff, Size: 1139 bytes --]
From ae9554df386ea555162cbfae7c02fb9cd7ceaa74 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
<jan.christian@gruenhage.xyz>
Date: Wed, 9 Feb 2022 17:43:35 +0100
Subject: [PATCH] cargo-crev: update to 0.23.2.
---
srcpkgs/cargo-crev/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/cargo-crev/template b/srcpkgs/cargo-crev/template
index 673cede92bd4..2c06721582ef 100644
--- a/srcpkgs/cargo-crev/template
+++ b/srcpkgs/cargo-crev/template
@@ -1,6 +1,6 @@
# Template file for 'cargo-crev'
pkgname=cargo-crev
-version=0.21.3
+version=0.23.2
revision=1
build_style=cargo
make_install_args="--path ./cargo-crev"
@@ -12,7 +12,7 @@ maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
license="MPL-2.0, MIT, Apache-2.0"
homepage="https://github.com/crev-dev/cargo-crev"
distfiles="https://github.com/crev-dev/cargo-crev/archive/refs/tags/v${version}.tar.gz"
-checksum=2d848c38772013bce638dd9056e32a4922afa3a88d0450f71ac158e7ad22b76e
+checksum=b37ca10e252bcd352634aed7ea366dfa84900446dbd74888f3178c0c10068d10
post_install() {
vlicense LICENSE-APACHE
next prev parent reply other threads:[~2022-06-08 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 16:44 [PR PATCH] cargo-crev: update to 0.23.0 jcgruenhage
2022-04-08 10:32 ` [PR PATCH] [Updated] " jcgruenhage
2022-04-08 10:33 ` cargo-crev: update to 0.23.1 jcgruenhage
2022-06-08 14:52 ` jcgruenhage [this message]
2022-06-10 13:15 ` [PR PATCH] [Merged]: cargo-crev: update to 0.23.2 leahneukirchen
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=20220608145231.sgUgT__Xresmo-NrYSI13yP0Km1gQiQ3d30WjcYX8_0@z \
--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).