From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-yamllint: update to 1.30.0.
Date: Sun, 02 Apr 2023 13:12:07 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43198@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
There is a new pull request by jcgruenhage against master on the void-packages repository
https://github.com/jcgruenhage/void-packages python3-yamllint-1.30.0_1
https://github.com/void-linux/void-packages/pull/43198
python3-yamllint: update to 1.30.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### 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, (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/43198.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-yamllint-1.30.0_1-43198.patch --]
[-- Type: text/x-diff, Size: 1288 bytes --]
From d550f65d42c72f08c7c4fcc383c7420460148da5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
<jan.christian@gruenhage.xyz>
Date: Sun, 2 Apr 2023 13:11:42 +0200
Subject: [PATCH] python3-yamllint: update to 1.30.0.
---
srcpkgs/python3-yamllint/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/python3-yamllint/template b/srcpkgs/python3-yamllint/template
index a754d9fe2f14..e8e1db1290a8 100644
--- a/srcpkgs/python3-yamllint/template
+++ b/srcpkgs/python3-yamllint/template
@@ -1,6 +1,6 @@
# Template file for 'python3-yamllint'
pkgname=python3-yamllint
-version=1.29.0
+version=1.30.0
revision=1
build_style=python3-module
hostmakedepends="python3-setuptools"
@@ -12,7 +12,7 @@ license="GPL-3.0-or-later"
homepage="https://github.com/adrienverge/yamllint"
changelog="https://github.com/adrienverge/yamllint/raw/master/CHANGELOG.rst"
distfiles="https://github.com/adrienverge/yamllint/archive/refs/tags/v${version}.tar.gz"
-checksum=8593180056e788b595e476b3d093146988dcc04452b72ae9d41dfc9d25e484cb
+checksum=8a4a6b2d15f9c6d97f012408eb811e62dd00554fbb4db4a2017dc2c8d1ee1da5
conflicts="python-yamllint>=0"
# These test cases require locale support, which musl libc lacks, so these tests are expected to fail
next reply other threads:[~2023-04-02 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 11:12 jcgruenhage [this message]
2023-04-13 22:49 ` [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-43198@inbox.vuxu.org \
--to=jcgruenhage@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).