Github messages for voidlinux
 help / color / mirror / Atom feed
From: ljnsn <ljnsn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] hatch: update to 1.9.3.
Date: Mon, 29 Apr 2024 18:31:07 +0200	[thread overview]
Message-ID: <20240429163107.6EAD7201BE@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48483@inbox.vuxu.org>

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

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

https://github.com/ljnsn/void-packages hatch
https://github.com/void-linux/void-packages/pull/48483

hatch: update to 1.9.3.
#### Testing the changes
- I tested the changes in this PR: **YES**

- I built this PR locally for my native architecture, (x86_64-glibc)

supersedes #47776 

I had to skip some of the tests, explanation is in the comments. Is there a way to make the pytest tmp_dir fixture work in the build environment?

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

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

From e7aae42d84223f6f833f352b6007a336c6f4d7f5 Mon Sep 17 00:00:00 2001
From: ljnsn <info@ljnsn.com>
Date: Fri, 2 Feb 2024 00:58:29 +0100
Subject: [PATCH] hatch: update to 1.9.3.

---
 srcpkgs/hatch/template | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

diff --git a/srcpkgs/hatch/template b/srcpkgs/hatch/template
index f8f9e156ab3a06..1d5b21e05e4a0c 100644
--- a/srcpkgs/hatch/template
+++ b/srcpkgs/hatch/template
@@ -1,17 +1,22 @@
 # Template file for 'hatch'
 pkgname=hatch
-version=1.6.3
-revision=3
+version=1.9.3
+revision=1
 build_style=python3-pep517
 # ignore backend tests, because updating hatchling when there is no new hatch
 # version yet breaks these in hatch.
 make_check_args="--ignore tests/backend
- --deselect tests/cli/run/test_run.py::test_scripts_no_environment"
-_deps="python3-click hatchling python3-httpx python3-hyperlink python3-keyring
- python3-packaging python3-pexpect python3-platformdirs python3-pyperclip
+# these tests create temporary files in /tmp, which does not work in the build
+# process
+ --ignore tests/cli/python/test_install.py
+ --deselect tests/cli/run/test_run.py::test_scripts_no_environment
+ --deselect tests/cli/env/test_create.py::test_plugin_dependencies_met
+ --deselect tests/cli/env/test_create.py::test_plugin_dependencies_met_as_app"
+_deps="python3-click hatchling python3-httpx python3-hyperlink
+ python3-keyring python3-packaging python3-pexpect python3-platformdirs
  python3-rich python3-shellingham python3-tomli-w python3-tomlkit
- python3-userpath python3-virtualenv"
-hostmakedepends="hatchling ${_deps}"
+ python3-userpath python3-virtualenv python3-zstandard"
+hostmakedepends="hatchling hatch-vcs ${_deps}"
 depends="${_deps}"
 checkdepends="${_deps} python3-pytest python3-pytest-mock
  python3-pytest-xdist git python3-pip"
@@ -21,7 +26,7 @@ license="MIT"
 homepage="https://hatch.pypa.io/latest/"
 changelog="https://raw.githubusercontent.com/pypa/hatch/master/docs/history/hatch.md"
 distfiles="${PYPI_SITE}/h/hatch/hatch-${version}.tar.gz"
-checksum=650e671ba300318e498ef93bbe3b99b32ce14920764fb8753f89993f63eed79a
+checksum=672017e349c548f8a957a5fee9aa2f8cfc2c8a994307378e45a8427972bdf8d9
 make_check_pre="env PYTHONPATH=./src"
 
 post_install() {

      parent reply	other threads:[~2024-04-29 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  0:33 [PR PATCH] " ljnsn
2024-02-02  5:30 ` classabbyamp
2024-02-02 22:44 ` jcgruenhage
2024-02-02 22:58 ` ljnsn
2024-02-02 23:26 ` [PR PATCH] [Updated] " ljnsn
2024-02-12 20:06 ` ljnsn
2024-02-17  0:51 ` ljnsn
2024-03-01 10:46 ` ljnsn
2024-04-29 16:31 ` ljnsn [this message]

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=20240429163107.6EAD7201BE@inbox.vuxu.org \
    --to=ljnsn@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).