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-hcloud: update to 1.18.0.
Date: Thu, 18 Aug 2022 17:31:27 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38762@inbox.vuxu.org> (raw)

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

There is a new pull request by jcgruenhage against master on the void-packages repository

https://github.com/jcgruenhage/void-packages python3-hcloud-1.18.0_1
https://github.com/void-linux/void-packages/pull/38762

python3-hcloud: update to 1.18.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/38762.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-hcloud-1.18.0_1-38762.patch --]
[-- Type: text/x-diff, Size: 1160 bytes --]

From 83c062090decc2237b83eaca44f37700f327facc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Thu, 18 Aug 2022 17:29:28 +0200
Subject: [PATCH] python3-hcloud: update to 1.18.0.

---
 srcpkgs/python3-hcloud/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/python3-hcloud/template b/srcpkgs/python3-hcloud/template
index 12eb46af1027..89dcd070b280 100644
--- a/srcpkgs/python3-hcloud/template
+++ b/srcpkgs/python3-hcloud/template
@@ -1,6 +1,6 @@
 # Template file for 'python3-hcloud'
 pkgname=python3-hcloud
-version=1.17.0
+version=1.18.0
 revision=1
 wrksrc="${pkgname/python3-/}-${version}"
 build_style=python3-module
@@ -12,7 +12,7 @@ maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
 license="MIT"
 homepage="https://github.com/hetznercloud/hcloud-python"
 distfiles="${PYPI_SITE}/h/${pkgname/python3-/}/${pkgname/python3-/}-${version}.tar.gz"
-checksum=f8142e0438be277c6fa1ddee13aecd5da152b48c6dec7fd4970def1b5dc219e2
+checksum=a21d940cde8f0c1fd10a0581b0618eb840a6f592404faafdb6070101f4525ff6
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2022-08-18 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 15:31 jcgruenhage [this message]
2022-08-20 22:05 ` [PR PATCH] [Merged]: " paper42

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-38762@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).