From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mercurial: update to 6.4.3.
Date: Mon, 15 May 2023 08:13:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43876@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
There is a new pull request by dataCobra against master on the void-packages repository
https://github.com/dataCobra/void-packages mercurial
https://github.com/void-linux/void-packages/pull/43876
mercurial: update to 6.4.3.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- 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/43876.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mercurial-43876.patch --]
[-- Type: text/x-diff, Size: 1095 bytes --]
From c2ec43d95ffab0b6135181fef19c25a992194de8 Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Mon, 15 May 2023 08:11:02 +0200
Subject: [PATCH] mercurial: update to 6.4.3.
---
srcpkgs/mercurial/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/mercurial/template b/srcpkgs/mercurial/template
index b61f9dba94a1..518a0238193d 100644
--- a/srcpkgs/mercurial/template
+++ b/srcpkgs/mercurial/template
@@ -1,6 +1,6 @@
# Template file for 'mercurial'
pkgname=mercurial
-version=6.3.2
+version=6.4.3
revision=1
build_style=python3-module
hostmakedepends="python3 python3-setuptools python3-devel gettext git"
@@ -14,7 +14,7 @@ maintainer="dataCobra <datacobra@thinkbot.de>"
license="GPL-2.0-or-later"
homepage="https://www.mercurial-scm.org/"
distfiles="https://www.mercurial-scm.org/release/mercurial-${version}.tar.gz"
-checksum=cfe6eeb5dd893ab32c0b79c1531aac420773e0fc837a35db3d4d92703df45a98
+checksum=a77fb62d325934a83a00b2fc6db109f44c67b86768fc40490366f513640c7f64
pre_check() {
if [ "$XBPS_TARGET_LIBC" = musl ]; then
next reply other threads:[~2023-05-15 6:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 6:13 dataCobra [this message]
2023-06-16 11:35 ` [PR PATCH] [Updated] " dataCobra
2023-07-02 9:46 ` [PR PATCH] [Updated] mercurial: update to 6.4.5 dataCobra
2023-07-05 14:31 ` void-linux
2023-07-10 7:48 ` dataCobra
2023-07-10 7:50 ` classabbyamp
2023-07-10 8:03 ` [PR PATCH] [Updated] " dataCobra
2023-07-10 8:30 ` [PR PATCH] [Merged]: mercurial: update to 6.5 classabbyamp
2023-05-24 19:42 [PR PATCH] mercurial: update to 6.4.3 akierig
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-43876@inbox.vuxu.org \
--to=datacobra@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).