Github messages for voidlinux
 help / color / mirror / Atom feed
From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] vultr-cli: update to 2.12.0.
Date: Fri, 21 Jan 2022 20:11:49 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35156@inbox.vuxu.org> (raw)

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

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

https://github.com/steinex/void-packages vultr-cli
https://github.com/void-linux/void-packages/pull/35156

vultr-cli: update to 2.12.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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/35156.patch is attached

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

From 8cb7745ea7c0f93c6b034608e4a6cbdf89f6768a Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Fri, 21 Jan 2022 20:07:29 +0100
Subject: [PATCH] vultr-cli: update to 2.12.0.

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

diff --git a/srcpkgs/vultr-cli/template b/srcpkgs/vultr-cli/template
index ff6371fab666..f09631babfe0 100644
--- a/srcpkgs/vultr-cli/template
+++ b/srcpkgs/vultr-cli/template
@@ -1,6 +1,6 @@
 # Template file for 'vultr-cli'
 pkgname=vultr-cli
-version=2.11.3
+version=2.12.0
 revision=1
 build_style=go
 go_import_path=github.com/vultr/vultr-cli/v2
@@ -10,4 +10,4 @@ license="Apache-2.0"
 homepage="https://github.com/vultr/vultr-cli"
 changelog="https://github.com/vultr/vultr-cli/blob/master/CHANGELOG.md"
 distfiles="https://github.com/vultr/vultr-cli/archive/refs/tags/v${version}.tar.gz"
-checksum=39da0ace6f8bf842bad41bf36a218a3c91e68a3139a353cd493c5ef476ea9ad5
+checksum=8e268bc42775ce2ff43f225b52fc5a665762374e4f24fd39bfc5850543b6067a

             reply	other threads:[~2022-01-21 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 19:11 steinex [this message]
2022-01-21 20:01 ` [PR PATCH] [Merged]: " ericonr

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-35156@inbox.vuxu.org \
    --to=steinex@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).