From: benalb <benalb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] lazydocker: update to 0.13.
Date: Wed, 12 Jan 2022 16:32:15 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35011@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
There is a new pull request by benalb against master on the void-packages repository
https://github.com/benalb/void-packages lazydocker
https://github.com/void-linux/void-packages/pull/35011
lazydocker: update to 0.13.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!-- 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, (X86_64-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/35011.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lazydocker-35011.patch --]
[-- Type: text/x-diff, Size: 1065 bytes --]
From 10a94c80c5be4761bb7b4dc89a811b4c070242b5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benjam=C3=ADn=20Albi=C3=B1ana?= <benalb@gmail.com>
Date: Wed, 12 Jan 2022 16:30:28 +0100
Subject: [PATCH] lazydocker: update to 0.13.
---
srcpkgs/lazydocker/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/lazydocker/template b/srcpkgs/lazydocker/template
index 9b058006b876..caf9198328f6 100644
--- a/srcpkgs/lazydocker/template
+++ b/srcpkgs/lazydocker/template
@@ -1,6 +1,6 @@
# Template file for 'lazydocker'
pkgname=lazydocker
-version=0.12
+version=0.13
revision=1
wrksrc="lazydocker-${version}"
build_style=go
@@ -11,7 +11,7 @@ maintainer="Benjamín Albiñana <benalb@gmail.com>"
license="MIT"
homepage="https://github.com/jesseduffield/lazydocker"
distfiles="https://github.com/jesseduffield/lazydocker/archive/v${version}.tar.gz"
-checksum=0509fdfffe78a0155cb54f8bbec1c3f9f3791ea5cbf397fb50fa5278954b2fcb
+checksum=4328ddcb3156ff57c1e21c0d2f9d9d67d48237a386d338f1d68831b6056dfe3e
post_install() {
vlicense LICENSE
next reply other threads:[~2022-01-12 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 15:32 benalb [this message]
2022-01-13 2:10 ` [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-35011@inbox.vuxu.org \
--to=benalb@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).