Github messages for voidlinux
 help / color / mirror / Atom feed
From: benalb <benalb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] lazydocker: update to 0.19.0.
Date: Tue, 11 Oct 2022 17:45:07 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39892@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1103 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/39892

lazydocker: update to 0.19.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)



A patch file from https://github.com/void-linux/void-packages/pull/39892.patch is attached

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

From 0cc349d7232e0f49ce8ba399102aca91225b8548 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benjam=C3=ADn=20Albi=C3=B1ana?= <benalb@gmail.com>
Date: Tue, 11 Oct 2022 17:43:59 +0200
Subject: [PATCH] lazydocker: update to 0.19.0.

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

diff --git a/srcpkgs/lazydocker/template b/srcpkgs/lazydocker/template
index 50a36c7a5899..4cae4aae3305 100644
--- a/srcpkgs/lazydocker/template
+++ b/srcpkgs/lazydocker/template
@@ -1,6 +1,6 @@
 # Template file for 'lazydocker'
 pkgname=lazydocker
-version=0.18.1
+version=0.19.0
 revision=1
 wrksrc="lazydocker-${version}"
 build_style=go
@@ -12,7 +12,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=f5081b846d530818e1f04b9e8479c801f287ac77ebdf063425a142ff50fc395b
+checksum=65f6f6f9a205c46dd721b05df17c31b90a02c10d3485f7b257e77e8e1db4e123
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2022-10-11 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 15:45 benalb [this message]
2022-10-11 15:50 ` [PR PATCH] [Updated] " benalb
2022-10-11 17:46 ` [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-39892@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).