From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] cargo-geiger: update to 0.11.2.
Date: Fri, 08 Apr 2022 13:23:09 +0200 [thread overview]
Message-ID: <20220408112309.ig_WqbUpwKqCNQrFe1kfOdVOeXtEj6wonFCa826003w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36580@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-geiger-0.11.2_1
https://github.com/void-linux/void-packages/pull/36580
cargo-geiger: update to 0.11.2.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### 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 add ci skip tag as described in
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/36580.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cargo-geiger-0.11.2_1-36580.patch --]
[-- Type: text/x-diff, Size: 1296 bytes --]
From 600f2eaff2791c38b18bcc48f9a8058d9aca9737 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
<jan.christian@gruenhage.xyz>
Date: Fri, 8 Apr 2022 12:53:10 +0200
Subject: [PATCH] cargo-geiger: update to 0.11.2.
---
srcpkgs/cargo-geiger/template | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/cargo-geiger/template b/srcpkgs/cargo-geiger/template
index ffe49404187e..d88a94ef7cdd 100644
--- a/srcpkgs/cargo-geiger/template
+++ b/srcpkgs/cargo-geiger/template
@@ -1,6 +1,6 @@
# Template file for 'cargo-geiger'
pkgname=cargo-geiger
-version=0.11.1
+version=0.11.2
revision=1
wrksrc="${pkgname}-${pkgname}-${version}"
build_wrksrc="${pkgname}"
@@ -12,10 +12,14 @@ maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
license="MIT, Apache-2.0"
homepage="https://github.com/rust-secure-code/cargo-geiger"
distfiles="https://github.com/rust-secure-code/cargo-geiger/archive/cargo-geiger-${version}.tar.gz"
-checksum=d3c88fc3bdb574108504a1a49ae7b8ee5b55b1744a47d58214d0f088d2b2ef00
+checksum=425638232f4c617a1dde1071f865c5140546bf9b6b61b9a9a186d0a5c146ac03
post_install() {
vlicense LICENSE-MIT
vlicense LICENSE-APACHE
vdoc README.md
}
+
+post_patch() {
+ cargo update -p autocfg:1.0.1 --precise 1.1.0
+}
next prev parent reply other threads:[~2022-04-08 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 10:54 [PR PATCH] " jcgruenhage
2022-04-08 11:23 ` jcgruenhage [this message]
2022-04-09 9:42 ` [PR PATCH] [Merged]: " paper42
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=20220408112309.ig_WqbUpwKqCNQrFe1kfOdVOeXtEj6wonFCa826003w@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).