From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-poetry-core: update to 1.3.1.
Date: Thu, 06 Oct 2022 14:45:09 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39770@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-poetry-core
https://github.com/void-linux/void-packages/pull/39770
python3-poetry-core: update to 1.3.1.
#### 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
#### Rev dep checks
- [x] jrnl
- [x] python3-aiofiles
- [x] python3-hypercorn
- [x] python3-msoffcrypto-tool
- [x] python3-pendulum
- [x] python3-pytest-httpserver
- [x] python3-pytzdata
- [x] python3-quart
- [x] python3-unpaddedbase64
- [x] synapse
A couple of these fail some tests, same as https://github.com/void-linux/void-packages/pull/39136
A patch file from https://github.com/void-linux/void-packages/pull/39770.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-poetry-core-39770.patch --]
[-- Type: text/x-diff, Size: 1184 bytes --]
From 1d8bd260d11cc78b2487029b3f42c8ff28bcbfd1 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Thu, 6 Oct 2022 18:02:46 +0530
Subject: [PATCH] python3-poetry-core: update to 1.3.1.
---
srcpkgs/python3-poetry-core/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-poetry-core/template b/srcpkgs/python3-poetry-core/template
index 9c099f80a870..760493d3d33c 100644
--- a/srcpkgs/python3-poetry-core/template
+++ b/srcpkgs/python3-poetry-core/template
@@ -1,6 +1,6 @@
# Template file for 'python3-poetry-core'
pkgname=python3-poetry-core
-version=1.1.0
+version=1.3.1
revision=1
wrksrc="poetry-core-${version}"
build_style="python3-pep517"
@@ -14,7 +14,7 @@ license="MIT"
homepage="https://github.com/python-poetry/poetry-core"
changelog="https://raw.githubusercontent.com/python-poetry/poetry-core/main/CHANGELOG.md"
distfiles="https://github.com/python-poetry/poetry-core/archive/refs/tags/${version}.tar.gz"
-checksum=44535d5c20e20189041714a45758774f713e4a53c3db071dca11a59d32aeba44
+checksum=8da8ce8f2e861527f660d7205a77095279d462b44d1d11bcf9e8ce74d96219ee
make_check_pre="env PYTHONPATH=src"
pre_check() {
next reply other threads:[~2022-10-06 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 12:45 icp1994 [this message]
2022-10-06 14:35 ` [PR PATCH] [Merged]: " ahesford
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-39770@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).