Github messages for voidlinux
 help / color / mirror / Atom feed
From: karl-nilsson <karl-nilsson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [WIP] python3-utils: update to 3.3.3.
Date: Sat, 01 Oct 2022 04:47:51 +0200	[thread overview]
Message-ID: <20221001024751.NnkP_1R0Vc_ueP8C4PJuByR5Bu5SR_Mxs1fbh1ymCZU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39562@inbox.vuxu.org>

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

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

https://github.com/karl-nilsson/void-packages pyutils
https://github.com/void-linux/void-packages/pull/39562

[WIP] python3-utils: update to 3.3.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, x64-glibc

Tests currently broken, I need to omit the loguru test.


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

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

From d1787415431a083f832697339b5346768a3b304b Mon Sep 17 00:00:00 2001
From: Karl Nilsson <karl.robert.nilsson@gmail.com>
Date: Fri, 20 May 2022 21:30:30 -0400
Subject: [PATCH] python3-utils: update to 3.3.3.

---
 srcpkgs/python3-utils/template | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/python3-utils/template b/srcpkgs/python3-utils/template
index a4db83649ac7..73cd0e8fee3d 100644
--- a/srcpkgs/python3-utils/template
+++ b/srcpkgs/python3-utils/template
@@ -1,11 +1,11 @@
 # Template file for 'python3-utils'
 pkgname=python3-utils
-version=3.1.0
+version=3.3.3
 revision=1
 wrksrc="python-utils-${version}"
 build_style=python3-module
 # skip coverage and mypy tests https://github.com/WoLpH/python-utils/issues/29
-make_check_args="-o addopts=--doctest-modules"
+make_check_args="-o addopts=--doctest-modules --ignore-glob=test_logger* --ignore-glob=loguru*"
 hostmakedepends="python3-setuptools"
 checkdepends="python3-pytest python3-pytest-asyncio"
 short_desc="Convenient utilities not included with the standard Python3 install"
@@ -13,8 +13,12 @@ maintainer="Karl Nilsson <karl.robert.nilsson@gmail.com>"
 license="BSD-3-Clause"
 homepage="https://github.com/WoLpH/python-utils"
 distfiles="https://github.com/WoLpH/python-utils/archive/v${version}.tar.gz"
-checksum=6f20e784af79dd0f2c330c88496b3d08fa29e27bcfba398ba78f73d8ae85f670
+checksum=aae5bbe0737dadb8ac73bc631a59d4c822a1c52296dbff1ad255d54119b178b0
 
 post_install() {
 	vlicense LICENSE
 }
+
+pre_check() {
+	msg_warn "python3 -m pytest ${testjobs} ${make_check_args} ${make_check_target}\n"
+}

  reply	other threads:[~2022-10-01  2:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01  1:25 [PR PATCH] " karl-nilsson
2022-10-01  2:47 ` karl-nilsson [this message]
2022-10-01 15:45 ` [PR PATCH] [Updated] " karl-nilsson
2022-10-03  1:26 ` karl-nilsson
2023-01-01  2:05 ` github-actions
2023-01-16  1:59 ` [PR PATCH] [Closed]: " github-actions

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=20221001024751.NnkP_1R0Vc_ueP8C4PJuByR5Bu5SR_Mxs1fbh1ymCZU@z \
    --to=karl-nilsson@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).