Github messages for voidlinux
 help / color / mirror / Atom feed
From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: python3-curio-1.4
Date: Tue, 02 Feb 2021 23:59:37 +0100	[thread overview]
Message-ID: <20210202225937.7y5uxIgph6LWs1trhuMzv1QBrkbw-iHPpR9j15sfbwI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28419@inbox.vuxu.org>

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

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

https://github.com/ar-jan/void-packages python3-curio
https://github.com/void-linux/void-packages/pull/28419

New package: python3-curio-1.4
<!-- Mark items with [x] where applicable -->

#### General
- [x] 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.)
- [x] I built this PR locally for my native architecture, (x86_64)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl

### Reason

#28272 keeps getting stuck on CI so I want to see if adding dependencies one by one would pass tests.

A patch file from https://github.com/void-linux/void-packages/pull/28419.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-curio-28419.patch --]
[-- Type: text/x-diff, Size: 1232 bytes --]

From 490f8c559dc2a0abcd8069c39a602d03ea69cda8 Mon Sep 17 00:00:00 2001
From: Arjan Mossel <arjanmossel@gmail.com>
Date: Thu, 28 Jan 2021 01:01:20 +0100
Subject: [PATCH] New package: python3-curio-1.4

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

diff --git a/srcpkgs/python3-curio/template b/srcpkgs/python3-curio/template
new file mode 100644
index 00000000000..b154cd6f83f
--- /dev/null
+++ b/srcpkgs/python3-curio/template
@@ -0,0 +1,23 @@
+# Template file for 'python3-curio'
+pkgname=python3-curio
+version=1.4
+revision=1
+wrksrc="curio-${version}"
+build_style=python3-module
+hostmakedepends="python3-setuptools"
+depends="python3"
+checkdepends="python3-pytest python3-Sphinx"
+short_desc="Coroutine-based library for concurrent programming using async/await"
+maintainer="Arjan Mossel <arjanmossel@gmail.com>"
+license="BSD-3-Clause"
+homepage="https://github.com/dabeaz/curio"
+distfiles="${PYPI_SITE}/c/curio/curio-${version}.tar.gz"
+checksum=57edce81c837f3c2cf42fbb346dee26e537d1659e6605269fb13bd179e068744
+
+do_check() {
+	PYTHONPATH=$(cd build/lib* && pwd) pytest
+}
+
+post_install() {
+	vlicense LICENSE
+}

  reply	other threads:[~2021-02-02 22:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 22:49 [PR PATCH] " ar-jan
2021-02-02 22:59 ` ar-jan [this message]
2021-02-08 14:26 ` [PR PATCH] [Updated] " ar-jan
2021-02-08 15:32 ` ar-jan
2021-02-08 15:40 ` ar-jan
2021-02-08 17:40 ` Chocimier
2021-02-08 17:40 ` [PR PATCH] [Closed]: " Chocimier
2021-02-08 18:06 ` ar-jan
2021-02-08 18:06 ` ar-jan
2021-02-08 18:19 ` Chocimier

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=20210202225937.7y5uxIgph6LWs1trhuMzv1QBrkbw-iHPpR9j15sfbwI@z \
    --to=ar-jan@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).