From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] eva: fix checksum
Date: Wed, 02 Nov 2022 11:59:34 +0100 [thread overview]
Message-ID: <20221102105934.Eg9yD9R0t-o_gB4a4Y9xHXKf6aR__M4T3CeTezysk0g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40280@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
There is an updated pull request by jcgruenhage against master on the void-packages repository
https://github.com/jcgruenhage/void-packages eva-0.3.0_1
https://github.com/void-linux/void-packages/pull/40280
eva: fix checksum
<!-- Uncomment relevant sections and delete options which are not applicable -->
Checksum changed since this was packaged. Does a revbump for stuff like this make sense? Probably not, right?
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-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/40280.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-eva-0.3.0_1-40280.patch --]
[-- Type: text/x-diff, Size: 1211 bytes --]
From 9015829893abc368cdc809f9d54ecad7229b84b1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
<jan.christian@gruenhage.xyz>
Date: Tue, 1 Nov 2022 20:43:14 +0100
Subject: [PATCH] eva: bump revision and update checksum
Upstream re-released v0.3.0, so the builds fail with bad checksum right
now.
---
srcpkgs/eva/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/eva/template b/srcpkgs/eva/template
index d364c98f9516..f9909970861b 100644
--- a/srcpkgs/eva/template
+++ b/srcpkgs/eva/template
@@ -1,14 +1,14 @@
# Template file for 'eva'
pkgname=eva
version=0.3.0
-revision=1
+revision=2
build_style=cargo
short_desc="Simple calculator REPL, similar to bc(1)"
maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
license="MIT"
homepage="https://github.com/NerdyPepper/eva"
-distfiles="https://github.com/NerdyPepper/eva/archive/v${version}.tar.gz"
-checksum=05e2cdcfd91e6abef91cb01ad3074583b8289f6e74054e070bfbf6a4e684865e
+distfiles="https://github.com/NerdyPepper/eva/archive/refs/tags/v${version}.tar.gz"
+checksum=5ee80a64de05ff952e9fd69fff6050d8e5c602428ad8ad3b357db6b813e1372f
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2022-11-02 10:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 19:46 [PR PATCH] " jcgruenhage
2022-11-01 19:47 ` classabbyamp
2022-11-01 20:02 ` [PR REVIEW] " tranzystorek-io
2022-11-01 21:23 ` jcgruenhage
2022-11-01 21:26 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-01 22:34 ` classabbyamp
2022-11-02 5:35 ` jcgruenhage
2022-11-02 6:50 ` tranzystorek-io
2022-11-02 8:55 ` jcgruenhage
2022-11-02 8:58 ` tranzystorek-io
2022-11-02 9:34 ` pickfire
2022-11-02 9:37 ` tranzystorek-io
2022-11-02 10:59 ` jcgruenhage [this message]
2022-11-02 23:25 ` [PR PATCH] [Merged]: eva: bump revision and update checksum classabbyamp
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=20221102105934.Eg9yD9R0t-o_gB4a4Y9xHXKf6aR__M4T3CeTezysk0g@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).