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.7.
Date: Wed, 20 Mar 2024 08:35:52 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49385@inbox.vuxu.org> (raw)

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

mercurial: update to 6.7.
#### Testing the changes
- I tested the changes in this PR: **YES** (Ran all Tests and checked my normal workflow)

#### 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
  - aarch64-musl (crossbuild)
  - armv7l (crossbuild)



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

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

From aae2855c3ef7db6b32b50e0627092b2e3a68b6fb Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Wed, 20 Mar 2024 07:58:21 +0100
Subject: [PATCH] mercurial: update to 6.7.

---
 .../patches/00-fix-test-remotefilelog-gc.diff         | 11 -----------
 srcpkgs/mercurial/template                            |  4 ++--
 2 files changed, 2 insertions(+), 13 deletions(-)
 delete mode 100644 srcpkgs/mercurial/patches/00-fix-test-remotefilelog-gc.diff

diff --git a/srcpkgs/mercurial/patches/00-fix-test-remotefilelog-gc.diff b/srcpkgs/mercurial/patches/00-fix-test-remotefilelog-gc.diff
deleted file mode 100644
index 53439ae3786e11..00000000000000
--- a/srcpkgs/mercurial/patches/00-fix-test-remotefilelog-gc.diff
+++ /dev/null
@@ -1,11 +0,0 @@
---- ./tests/hghave.py	2023-10-11 02:51:10.038038013 +0200
-+++ ./tests/hghave.py	2023-10-11 02:50:44.353035951 +0200
-@@ -868,7 +868,7 @@
-
- # Add "py36", "py37", ... as possible feature checks. Note that there's no
- # punctuation here.
--@checkvers("py", "Python >= %s", (3.6, 3.7, 3.8, 3.9, 3.10, 3.11))
-+@checkvers("py", "Python >= %s", (3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 3.12))
- def has_python_range(v):
-     major, minor = v.split('.')[0:2]
-     py_major, py_minor = sys.version_info.major, sys.version_info.minor
diff --git a/srcpkgs/mercurial/template b/srcpkgs/mercurial/template
index 270e531e682b73..01ac6a747298ba 100644
--- a/srcpkgs/mercurial/template
+++ b/srcpkgs/mercurial/template
@@ -1,6 +1,6 @@
 # Template file for 'mercurial'
 pkgname=mercurial
-version=6.6.3
+version=6.7
 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=f75d6a4a75823a1b7d713a4967eca2f596f466e58fc6bc06d72642932fd7e307
+checksum=5358ed20604c67a7bc7ff81141f735586c328fbb6a18440d2e1e6cd0c044a4c6
 
 pre_check() {
 	if [ "$XBPS_TARGET_LIBC" = musl ]; then

             reply	other threads:[~2024-03-20  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20  7:35 dataCobra [this message]
2024-03-24 17:12 ` cinerea0
2024-03-24 17:48 ` [PR PATCH] [Updated] " dataCobra
2024-03-24 17:49 ` mercurial: update to 6.7.1 dataCobra
2024-03-25 19:33 ` [PR PATCH] [Merged]: " cinerea0

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