From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] hg-evolve: update to 11.1.3.
Date: Sat, 20 Apr 2024 21:00:46 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49938@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages hg-evolve
https://github.com/void-linux/void-packages/pull/49938
hg-evolve: update to 11.1.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**
A patch file from https://github.com/void-linux/void-packages/pull/49938.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hg-evolve-49938.patch --]
[-- Type: text/x-diff, Size: 1450 bytes --]
From b45015e89650ee2aed37bf6af92a6f7034004813 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Tue, 16 Apr 2024 11:25:20 +0530
Subject: [PATCH] hg-evolve: update to 11.1.3.
---
srcpkgs/hg-evolve/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/hg-evolve/template b/srcpkgs/hg-evolve/template
index 5408d1cac55dcb..11b817a2471261 100644
--- a/srcpkgs/hg-evolve/template
+++ b/srcpkgs/hg-evolve/template
@@ -1,8 +1,8 @@
# Template file for 'hg-evolve'
pkgname=hg-evolve
-version=11.1.2
+version=11.1.3
revision=1
-_hg_version=6.6.3 # sync with mercurial version in void repos
+_hg_version=6.7.2 # sync with mercurial version in void repos
build_style=python3-module
build_wrksrc="hg-evolve-${version}"
hostmakedepends="python3-setuptools"
@@ -15,8 +15,8 @@ homepage="https://www.mercurial-scm.org/doc/evolution/"
changelog="https://repo.mercurial-scm.org/evolve/file/tip/CHANGELOG"
distfiles="${PYPI_SITE}/h/hg-evolve/hg-evolve-${version}.tar.gz
https://www.mercurial-scm.org/release/mercurial-${_hg_version}.tar.gz"
-checksum="ba0f93d6c45207e279172ab375347bc59b6fc9b85dcc165823b838ad7d780c7a
- f75d6a4a75823a1b7d713a4967eca2f596f466e58fc6bc06d72642932fd7e307"
+checksum="5943cea24feda59252a2893308810744a0254f3799e91258d0889c9604143acf
+ 1c22070c05dfaac41ff88a39ce2508dde480f0dd05d45d7efab4c5cdc6ddd806"
do_check() {
_skips="check-compat-strings check-sdist version-install"
next reply other threads:[~2024-04-20 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 19:00 icp1994 [this message]
2024-04-22 19:35 ` [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-49938@inbox.vuxu.org \
--to=icp1994@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).