From: Eloitor <Eloitor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pandocfilters: update to 1.5.0, adopt
Date: Thu, 11 Jan 2024 14:52:10 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48166@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
There is a new pull request by Eloitor against master on the void-packages repository
https://github.com/Eloitor/void-packages pandocfilters
https://github.com/void-linux/void-packages/pull/48166
python3-pandocfilters: update to 1.5.0, adopt
#### 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)
A patch file from https://github.com/void-linux/void-packages/pull/48166.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pandocfilters-48166.patch --]
[-- Type: text/x-diff, Size: 1264 bytes --]
From df181020b25084752ee28abed750272021d52079 Mon Sep 17 00:00:00 2001
From: Eloi Torrents <eloitor@duck.com>
Date: Thu, 11 Jan 2024 15:50:41 +0100
Subject: [PATCH] python3-pandocfilters: update to 1.5.0, adopt
---
srcpkgs/python3-pandocfilters/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-pandocfilters/template b/srcpkgs/python3-pandocfilters/template
index 24c382e5d39d7..86c4a34849026 100644
--- a/srcpkgs/python3-pandocfilters/template
+++ b/srcpkgs/python3-pandocfilters/template
@@ -1,16 +1,16 @@
# Template file for 'python3-pandocfilters'
pkgname=python3-pandocfilters
-version=1.4.3
-revision=4
+version=1.5.0
+revision=1
build_style=python3-module
hostmakedepends="python3-setuptools"
depends="python3"
short_desc="Python3 module for writing pandoc filters"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Eloi Torrents <eloitor@disroot.org>"
license="BSD-3-Clause"
homepage="http://github.com/jgm/pandocfilters"
distfiles="${PYPI_SITE}/p/pandocfilters/pandocfilters-${version}.tar.gz"
-checksum=bc63fbb50534b4b1f8ebe1860889289e8af94a23bff7445259592df25a3906eb
+checksum=0b679503337d233b4339a817bfc8c50064e2eff681314376a47cb582305a7a38
post_install() {
vlicense LICENSE
next reply other threads:[~2024-01-11 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 13:52 Eloitor [this message]
2024-01-31 15:46 ` [PR PATCH] [Merged]: " ahesford
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-48166@inbox.vuxu.org \
--to=eloitor@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).