From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pytest-env: touch for build
Date: Fri, 07 Mar 2025 20:03:23 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54620@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages python3-pytest-env
https://github.com/void-linux/void-packages/pull/54620
python3-pytest-env: touch for build
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
A patch file from https://github.com/void-linux/void-packages/pull/54620.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-pytest-env-54620.patch --]
[-- Type: text/x-diff, Size: 724 bytes --]
From e9a6c07dddee75010ec0c042aa43b3e12a2758af Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Sat, 8 Mar 2025 00:31:12 +0530
Subject: [PATCH] python3-pytest-env: touch for build
---
srcpkgs/python3-pytest-env/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/python3-pytest-env/template b/srcpkgs/python3-pytest-env/template
index ecfb96cdbbea7a..294976f1ced0c7 100644
--- a/srcpkgs/python3-pytest-env/template
+++ b/srcpkgs/python3-pytest-env/template
@@ -1,7 +1,7 @@
# Template file for 'python3-pytest-env'
pkgname=python3-pytest-env
version=1.1.5
-revision=1
+revision=2
build_style=python3-pep517
hostmakedepends="hatchling hatch-vcs"
depends="python3-pytest"
next reply other threads:[~2025-03-07 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 19:03 icp1994 [this message]
2025-03-13 16:01 ` [PR PATCH] [Merged]: " classabbyamp
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-54620@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).