Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] python3-rich: update to 9.11.0.
Date: Sat, 20 Feb 2021 19:56:49 +0100	[thread overview]
Message-ID: <20210220185649.FO9QpiOFi-OyFu4rVGugTr7VUq7b38hZjOlZ5GPOWjs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28934@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]

There is an updated pull request by abenson against master on the void-packages repository

https://github.com/abenson/void-packages rich_9.11.0
https://github.com/void-linux/void-packages/pull/28934

python3-rich: update to 9.11.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?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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/28934.patch is attached

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

From eb8e62df7939d6e521252b86e7d69115ba84cd71 Mon Sep 17 00:00:00 2001
From: Andrew Benson <abenson@gmail.com>
Date: Sat, 20 Feb 2021 12:55:06 -0600
Subject: [PATCH 1/2] New package: python3-commonmark-0.9.1

---
 srcpkgs/python3-commonmark/template | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 srcpkgs/python3-commonmark/template

diff --git a/srcpkgs/python3-commonmark/template b/srcpkgs/python3-commonmark/template
new file mode 100644
index 00000000000..f93defe33d8
--- /dev/null
+++ b/srcpkgs/python3-commonmark/template
@@ -0,0 +1,23 @@
+# Template file for 'python3-commonmark'
+pkgname=python3-commonmark
+version=0.9.1
+revision=1
+build_style=python3-module
+wrksrc="commonmark-${version}"
+hostmakedepends="python3-setuptools"
+checkdepends="python3-wheel python3-flake8 python3-hypothesis python3-colorama"
+short_desc="Parser for the CommonMark Markdown spec"
+maintainer="Andrew Benson <abenson@gmail.com>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/rtfd/commonmark.py"
+distfiles="${PYPI_SITE}/c/commonmark/commonmark-${version}.tar.gz"
+checksum=452f9dc859be7f06631ddcb328b6919c67984aca654e5fefb3914d54691aed60
+
+post_extract() {
+	vsed -i commonmark/tests/run_spec_tests.py -e \
+	 "/^import sys$/a sys.path.append('$wrksrc/build/lib')"
+}
+
+post_install() {
+	vlicense LICENSE
+}

From 2aefbd077072cf66cd28bcb4ab86564e7ab12c53 Mon Sep 17 00:00:00 2001
From: Andrew Benson <abenson@gmail.com>
Date: Sat, 20 Feb 2021 11:58:59 -0600
Subject: [PATCH 2/2] python3-rich: update to 9.11.0.

---
 srcpkgs/python3-rich/template | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/python3-rich/template b/srcpkgs/python3-rich/template
index 5bc8426f438..3d1ce246e4f 100644
--- a/srcpkgs/python3-rich/template
+++ b/srcpkgs/python3-rich/template
@@ -1,16 +1,19 @@
 # Template file for 'python3-rich'
 pkgname=python3-rich
-version=9.10.0
+version=9.11.0
 revision=1
 wrksrc="rich-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools"
+depends="python3-typing_extensions python3-Pygments python3-commonmark
+ python3-colorama"
+checkdepends="python3-wheel $depends"
 short_desc="Library for rich text and beautiful formatting in the terminal"
 maintainer="Andrew Benson <abenson+void@gmail.com>"
 license="MIT"
 homepage="https://github.com/willmcgugan/rich"
 distfiles="${PYPI_SITE}/r/rich/rich-${version}.tar.gz"
-checksum=e0f2db62a52536ee32f6f584a47536465872cae2b94887cf1f080fb9eaa13eb2
+checksum=f8f08fdac6bd67dc2dd7fe976da702d748487aa9eb5d050c48b2321bc67ed659
 
 post_install() {
 	vlicense LICENSE

  reply	other threads:[~2021-02-20 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 18:09 [PR PATCH] " abenson
2021-02-20 18:56 ` abenson [this message]
2021-02-20 19:02 ` [PR PATCH] [Updated] " abenson
2021-02-20 19:13 ` [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=20210220185649.FO9QpiOFi-OyFu4rVGugTr7VUq7b38hZjOlZ5GPOWjs@z \
    --to=abenson@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).