From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] mercurial: update to 6.6.2.
Date: Wed, 07 Feb 2024 15:08:04 +0100 [thread overview]
Message-ID: <20240207140804.9BDA223B67@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48287@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
There is an updated 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/48287
mercurial: update to 6.6.2.
#### 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-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
- i686
A patch file from https://github.com/void-linux/void-packages/pull/48287.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mercurial-48287.patch --]
[-- Type: text/x-diff, Size: 1097 bytes --]
From bd3a982f122b2b235e49dd15381288aa76712c83 Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Fri, 19 Jan 2024 19:09:09 +0100
Subject: [PATCH] mercurial: update to 6.6.2.
---
srcpkgs/mercurial/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/mercurial/template b/srcpkgs/mercurial/template
index 8785977d09a7d..4061a3836949b 100644
--- a/srcpkgs/mercurial/template
+++ b/srcpkgs/mercurial/template
@@ -1,6 +1,6 @@
# Template file for 'mercurial'
pkgname=mercurial
-version=6.6.1
+version=6.6.2
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=a29465a3fe40a3e8d49ba8343134ac2aba286b683ffeb838da0cf6e4521f9695
+checksum=cb494d7be7ddc2fc9d3171c88830af9c02b21c753e3e5113defac9c0373b4b60
pre_check() {
if [ "$XBPS_TARGET_LIBC" = musl ]; then
next prev parent reply other threads:[~2024-02-07 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 18:10 [PR PATCH] " dataCobra
2024-02-07 14:08 ` dataCobra [this message]
2024-02-12 14:00 ` [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=20240207140804.9BDA223B67@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).