Github messages for voidlinux
 help / color / mirror / Atom feed
From: TeddyDD <TeddyDD@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] k3d: update to 5.4.6.
Date: Tue, 30 Aug 2022 18:04:27 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38985@inbox.vuxu.org> (raw)

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

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

https://github.com/TeddyDD/void-packages-1 update-k3d
https://github.com/void-linux/void-packages/pull/38985

k3d: update to 5.4.6.
<!-- 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/38985.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-k3d-38985.patch --]
[-- Type: text/x-diff, Size: 1067 bytes --]

From 71bd65290a672cf90df8e80eca98882b29119e17 Mon Sep 17 00:00:00 2001
From: Daniel Lewan <vision360.daniel@gmail.com>
Date: Tue, 30 Aug 2022 18:03:40 +0200
Subject: [PATCH] k3d: update to 5.4.6.

---
 srcpkgs/k3d/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/k3d/template b/srcpkgs/k3d/template
index a972bf447bac..56f52b04e370 100644
--- a/srcpkgs/k3d/template
+++ b/srcpkgs/k3d/template
@@ -1,17 +1,18 @@
 # Template file for 'k3d'
 pkgname=k3d
-version=5.4.4
+version=5.4.6
 revision=1
 build_style=go
 build_helper=qemu
 go_import_path="github.com/k3d-io/k3d/v5"
+go_mod_mode=default
 depends="docker"
 short_desc="Creates containerized k3s clusters"
 maintainer="Daniel Lewan <vision360.daniel@gmail.com>"
 license="MIT"
 homepage="https://k3d.io/"
 distfiles="https://github.com/k3d-io/k3d/archive/v${version}.tar.gz"
-checksum=f970b63ca9d1b02f6fe11b9894267c2a99138021e9cdc1dda0d1796b682bd134
+checksum=da23261c03715e351c1ff4cf0d4c905020929afe79005891c275fb6f8e180f1d
 _completions="bash zsh fish"
 
 post_build() {

             reply	other threads:[~2022-08-30 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 16:04 TeddyDD [this message]
2022-09-06  5:51 ` [PR REVIEW] " classabbyamp
2022-09-10 18:39 ` [PR PATCH] [Updated] " TeddyDD
2022-09-13 20:33 ` [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-38985@inbox.vuxu.org \
    --to=teddydd@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).