Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] cargo-crev: update to 0.20.1
Date: Sat, 30 Oct 2021 22:27:17 +0200	[thread overview]
Message-ID: <20211030202717.yKI8xKYhZWaFH7sG4Yqw40VnkblTyu1zy9ZQsEo8Tq0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33251@inbox.vuxu.org>

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

There is an updated pull request by cinerea0 against master on the void-packages repository

https://github.com/cinerea0/void-packages crev
https://github.com/void-linux/void-packages/pull/33251

cargo-crev: update to 0.20.1
<!-- 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/33251.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-crev-33251.patch --]
[-- Type: text/x-diff, Size: 1221 bytes --]

From e6bafa2942b13060efab7db2be3f96f964593ab6 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Sat, 30 Oct 2021 16:26:58 -0400
Subject: [PATCH] cargo-crev: update to 0.21.1

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

diff --git a/srcpkgs/cargo-crev/template b/srcpkgs/cargo-crev/template
index 4b6121655aff..05b0635dcf51 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.19.2
+version=0.21.1
 revision=1
 build_style=cargo
 make_install_args="--path ./cargo-crev"
@@ -10,8 +10,8 @@ short_desc="Cryptographically verifiable code review system for cargo"
 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="${homepage}/archive/v${version}.tar.gz"
-checksum=d4b1ab0089ce25d73f2516209d80102e7e674dc851cf49f08e34a963d16e97ad
+distfiles="https://github.com/crev-dev/cargo-crev/archive/refs/tags/${version}.tar.gz"
+checksum=223f2603afe739a618275b89c4b79528fc5b766beab70614f22dddfebef3935d
 
 post_install() {
 	vlicense LICENSE-APACHE

  parent reply	other threads:[~2021-10-30 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02  3:39 [PR PATCH] " cinerea0
2021-10-02 19:43 ` ericonr
2021-10-04  1:05 ` cinerea0
2021-10-04  2:12 ` ericonr
2021-10-04 20:34 ` cinerea0
2021-10-29  3:47 ` cinerea0
2021-10-30 18:51 ` ericonr
2021-10-30 20:27 ` cinerea0 [this message]
2021-10-30 23:58 ` cargo-crev: update to 0.21.1 cinerea0
2021-10-31  1:05 ` [PR PATCH] [Merged]: " ericonr

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=20211030202717.yKI8xKYhZWaFH7sG4Yqw40VnkblTyu1zy9ZQsEo8Tq0@z \
    --to=cinerea0@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).