Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-yamllint: update to 1.28.0.
Date: Tue, 13 Sep 2022 23:02:22 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39270@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.28.0_1
https://github.com/void-linux/void-packages/pull/39270

python3-yamllint: update to 1.28.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/39270.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-yamllint-1.28.0_1-39270.patch --]
[-- Type: text/x-diff, Size: 1184 bytes --]

From 9ca3bbabe953831b9fca8aa2d91f74f1c7372441 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Tue, 13 Sep 2022 23:01:27 +0200
Subject: [PATCH] python3-yamllint: update to 1.28.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 1d35905803cc..24544b67001f 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.27.1
+version=1.28.0
 revision=1
 wrksrc="${pkgname/python3-/}-${version}"
 build_style=python3-module
@@ -13,7 +13,7 @@ license="GPL-3.0-or-later"
 homepage="https://github.com/adrienverge/yamllint"
 changelog="https://github.com/adrienverge/yamllint/raw/master/CHANGELOG.rst"
 distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=71195467c92705121e7bea72b920d56747d1e7f1c36374943ab65ac534ec7856
+checksum=28e3386b3985fa97e0827f669434361f9ba18451cbe7ec7a37746883ceecdcb9
 conflicts="python-yamllint>=0"
 
 case "$XBPS_TARGET_MACHINE" in

             reply	other threads:[~2022-09-13 21:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 21:02 jcgruenhage [this message]
2022-09-14  6:28 ` [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-39270@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).