Github messages for voidlinux
 help / color / mirror / Atom feed
From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mercurial: update to 6.3.2.
Date: Wed, 18 Jan 2023 17:10:36 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41719@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 598 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/41719

mercurial: update to 6.3.2.
#### 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):
  - x86_64-musl
  - i686


A patch file from https://github.com/void-linux/void-packages/pull/41719.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mercurial-41719.patch --]
[-- Type: text/x-diff, Size: 1095 bytes --]

From 9673c302e8d1e78e9b55ccf2b3b42c75de9bab28 Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Wed, 18 Jan 2023 17:08:02 +0100
Subject: [PATCH] mercurial: update to 6.3.2.

---
 srcpkgs/mercurial/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/mercurial/template b/srcpkgs/mercurial/template
index 6e2581fe9a0d..dcf2f7bbfbe2 100644
--- a/srcpkgs/mercurial/template
+++ b/srcpkgs/mercurial/template
@@ -1,6 +1,6 @@
 # Template file for 'mercurial'
 pkgname=mercurial
-version=6.3.1
+version=6.3.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=6c39ab8732948d89cf1208751dd7d85d4042aa82153977451b9eb13367585072
+checksum=cfe6eeb5dd893ab32c0b79c1531aac420773e0fc837a35db3d4d92703df45a98
 
 pre_check() {
 	if [ "$XBPS_TARGET_LIBC" = musl ]; then

             reply	other threads:[~2023-01-18 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 16:10 dataCobra [this message]
2023-01-18 19:31 ` icp1994
2023-01-20  5:29 ` [PR PATCH] [Updated] " dataCobra
2023-01-20  5:30 ` dataCobra
2023-01-22  8:49 ` [PR PATCH] [Merged]: " sgn

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-41719@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).