From: clyhtsuriva <clyhtsuriva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bcal: update to 2.4
Date: Fri, 02 Sep 2022 11:25:45 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39058@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
There is a new pull request by clyhtsuriva against master on the void-packages repository
https://github.com/clyhtsuriva/void-packages bcal-update
https://github.com/void-linux/void-packages/pull/39058
bcal: update to 2.4
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64
- I crossbuilded this PR locally for these architectures:
- aarch64-musl
A patch file from https://github.com/void-linux/void-packages/pull/39058.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bcal-update-39058.patch --]
[-- Type: text/x-diff, Size: 1053 bytes --]
From e2b77aebcd9d7046b5170985864579e11ccd334b Mon Sep 17 00:00:00 2001
From: clyhtsuriva <aimeric@adjutor.xyz>
Date: Fri, 2 Sep 2022 11:25:34 +0200
Subject: [PATCH] bcal: update to 2.4
---
srcpkgs/bcal/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/bcal/template b/srcpkgs/bcal/template
index b0b19b4db9b0..b13e097cbb2f 100644
--- a/srcpkgs/bcal/template
+++ b/srcpkgs/bcal/template
@@ -1,6 +1,6 @@
# Template file for 'bcal'
pkgname=bcal
-version=2.3
+version=2.4
revision=1
build_style=gnu-makefile
makedepends="readline-devel"
@@ -10,7 +10,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-3.0-or-later"
homepage="https://github.com/jarun/bcal"
distfiles="https://github.com/jarun/bcal/archive/v${version}.tar.gz"
-checksum=e295b022e5187079b4cc5310447da5c787cb6bade86936dabf34a42bb85348ba
+checksum=141f39d866f62274b2262164baaac6202f60749862c84c2e6ed231f6d03ee8df
if [ "$XBPS_TARGET_WORDSIZE" -ne 64 ]; then
broken="Can only be built for 64 bit targets which define __uint128_t."
next reply other threads:[~2022-09-02 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 9:25 clyhtsuriva [this message]
2022-09-02 16:03 ` [PR REVIEW] " paper42
2022-09-02 16:50 ` [PR PATCH] [Updated] " clyhtsuriva
2022-09-02 16:52 ` [PR REVIEW] " clyhtsuriva
2022-09-05 10:06 ` [PR PATCH] [Merged]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39058@inbox.vuxu.org \
--to=clyhtsuriva@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).