From: m3tav3rse <m3tav3rse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-markdown2: update to 2.4.0.
Date: Sat, 27 Mar 2021 19:25:50 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29787@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
There is a new pull request by m3tav3rse against master on the void-packages repository
https://github.com/m3tav3rse/void-packages markdown2
https://github.com/void-linux/void-packages/pull/29787
python3-markdown2: update to 2.4.0.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/29787.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-markdown2-29787.patch --]
[-- Type: text/x-diff, Size: 1174 bytes --]
From 318f5ace839de5276bf24e58dced1853679179df Mon Sep 17 00:00:00 2001
From: m3tav3rse <mtvrs@tuta.io>
Date: Sat, 27 Mar 2021 10:14:17 +0100
Subject: [PATCH] python3-markdown2: update to 2.4.0.
---
srcpkgs/python3-markdown2/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/python3-markdown2/template b/srcpkgs/python3-markdown2/template
index a79bc5fee6dc..5d60d3c7ce42 100644
--- a/srcpkgs/python3-markdown2/template
+++ b/srcpkgs/python3-markdown2/template
@@ -1,7 +1,7 @@
# Template file for 'python3-markdown2'
pkgname=python3-markdown2
-version=2.3.8
-revision=4
+version=2.4.0
+revision=1
wrksrc=python-markdown2-$version
build_style=python3-module
hostmakedepends="python3-setuptools"
@@ -10,7 +10,7 @@ maintainer="Aluísio Augusto Silva Gonçalves <aluisio@aasg.name>"
license="MIT"
homepage="https://github.com/trentm/python-markdown2"
distfiles="https://github.com/trentm/python-markdown2/archive/${version}.tar.gz"
-checksum=@f2439906b925fb3991b8e4c01909bd2e6cb3aa75ce64a053b5495f9c72726f77
+checksum=372fc64b1a6f949fb6379cc0fdb47c832b875b575d50b9c641d09c4971ca9f30
do_check() {
PY3PATH="${PWD}/build/lib"
next reply other threads:[~2021-03-27 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 18:25 m3tav3rse [this message]
2021-03-28 4:30 ` [PR PATCH] [Merged]: " ericonr
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-29787@inbox.vuxu.org \
--to=m3tav3rse@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).