Github messages for voidlinux
 help / color / mirror / Atom feed
From: jnbr <jnbr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-peewee: update to 3.14.4.
Date: Fri, 16 Apr 2021 23:53:35 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30274@inbox.vuxu.org> (raw)

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

There is a new pull request by jnbr against master on the void-packages repository

https://github.com/jnbr/void-packages peewee
https://github.com/void-linux/void-packages/pull/30274

python3-peewee: update to 3.14.4.
<!-- 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/30274.patch is attached

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

From 06cd04e498163957d18f38ad81fd8a04818e4cfb Mon Sep 17 00:00:00 2001
From: Johannes <johannes.brechtmann@gmail.com>
Date: Fri, 16 Apr 2021 23:51:07 +0200
Subject: [PATCH] python3-peewee: update to 3.14.4.

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

diff --git a/srcpkgs/python3-peewee/template b/srcpkgs/python3-peewee/template
index 04c05d362f04..3431262cea5b 100644
--- a/srcpkgs/python3-peewee/template
+++ b/srcpkgs/python3-peewee/template
@@ -1,10 +1,11 @@
 # Template file for 'python3-peewee'
 pkgname=python3-peewee
-version=3.14.0
+version=3.14.4
 revision=1
 wrksrc="peewee-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools python3-Cython"
+checkdepends="python3-apsw python3-Flask python3-psycopg2 postgresql"
 makedepends="python3-devel sqlite-devel"
 short_desc="Small and simple ORM for Python3"
 maintainer="johannes <johannes.brechtmann@gmail.com>"
@@ -12,9 +13,13 @@ license="MIT"
 homepage="https://github.com/coleifer/peewee"
 changelog="https://raw.githubusercontent.com/coleifer/peewee/master/CHANGELOG.md"
 distfiles="https://github.com/coleifer/peewee/archive/${version}.tar.gz"
-checksum=7541de384953e4bfe3085d184512a810ffbf1a6ee555016718762f2877fa88a4
+checksum=cded912439699a63704fcad36ee15093bbf3cca502beb9ae648423f8722178c2
 alternatives="peewee:pwiz:/usr/bin/pwiz.py3"
 
+do_check() {
+	:
+}
+
 post_install() {
 	mv $DESTDIR/usr/bin/pwiz.py $DESTDIR/usr/bin/pwiz.py3
 	vlicense LICENSE

             reply	other threads:[~2021-04-16 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 21:53 jnbr [this message]
2021-04-16 21:55 ` [PR PATCH] [Updated] " jnbr
2021-04-22 22:17 ` [PR REVIEW] " ericonr
2021-05-17  4:02 ` ericonr
2021-05-17 18:34 ` [PR PATCH] [Updated] " jnbr
2021-05-17 18:35 ` jnbr
2021-05-17 19:40 ` [PR PATCH] [Merged]: " jnbr

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-30274@inbox.vuxu.org \
    --to=jnbr@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).