From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-markdown-it: update to 2.2.0 [unbreak python3-rich]
Date: Thu, 09 Mar 2023 21:19:59 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42682@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-markdown-it
https://github.com/void-linux/void-packages/pull/42682
python3-markdown-it: update to 2.2.0 [unbreak python3-rich]
#### 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**
python3-rich-13.3.2 needs this version of markdown-it-py
https://github.com/Textualize/rich/blob/v13.3.2/pyproject.toml#L33
A patch file from https://github.com/void-linux/void-packages/pull/42682.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-markdown-it-42682.patch --]
[-- Type: text/x-diff, Size: 1207 bytes --]
From 2ffe88d9f850a3c18ced06be497acacc1267a9f2 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Thu, 9 Mar 2023 13:15:37 +0530
Subject: [PATCH] python3-markdown-it: update to 2.2.0.
---
srcpkgs/python3-markdown-it/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-markdown-it/template b/srcpkgs/python3-markdown-it/template
index 40104b64dd37..acd48c68a10a 100644
--- a/srcpkgs/python3-markdown-it/template
+++ b/srcpkgs/python3-markdown-it/template
@@ -1,6 +1,6 @@
# Template file for 'python3-markdown-it'
pkgname=python3-markdown-it
-version=2.1.0
+version=2.2.0
revision=1
build_style=python3-pep517
make_install_target="dist/markdown_it_py-${version}-*-*-*.whl"
@@ -12,7 +12,7 @@ license="MIT"
homepage="https://github.com/executablebooks/markdown-it-py"
changelog="https://raw.githubusercontent.com/executablebooks/markdown-it-py/master/CHANGELOG.md"
distfiles="${PYPI_SITE}/m/markdown-it-py/markdown-it-py-${version}.tar.gz"
-checksum=cf7e59fed14b5ae17c0006eff14a2d9a00ed5f3a846148153899a0224e2c07da
+checksum=7c9a5e412688bc771c67432cbfebcdd686c93ce6484913dccf06cb5a0bea35a1
# Tests not shipped in PYPI tarball
make_check=no
next reply other threads:[~2023-03-09 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 20:19 icp1994 [this message]
2023-03-09 20:24 ` [PR PATCH] [Merged]: " abenson
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-42682@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).