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.21.0.
Date: Fri, 21 Jul 2023 17:38:00 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45174@inbox.vuxu.org> (raw)

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

lazydocker: update to 0.21.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, (X86_64-LIBC)



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

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

From 73c7dc3f7bb7c1f48569725b4d372536b1248f88 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benjam=C3=ADn=20Albi=C3=B1ana?= <benalb@gmail.com>
Date: Fri, 21 Jul 2023 17:36:31 +0200
Subject: [PATCH] lazydocker: update to 0.21.0.

---
 srcpkgs/lazydocker/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/lazydocker/template b/srcpkgs/lazydocker/template
index 5c4a8c3e27894..2782ed5b8166a 100644
--- a/srcpkgs/lazydocker/template
+++ b/srcpkgs/lazydocker/template
@@ -1,7 +1,7 @@
 # Template file for 'lazydocker'
 pkgname=lazydocker
-version=0.20.0
-revision=2
+version=0.21.0
+revision=1
 build_style=go
 go_import_path=github.com/jesseduffield/lazydocker
 go_ldflags="-X main.version=${version}"
@@ -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=570ce8127b148bc99c2faa1d4a3530504e81d531d3546dd1f29a7258c4d9d9ea
+checksum=0cf998e1487aac9152e413369d1a250cb0510ac6df19d8c24090e1c4da43f55b
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2023-07-21 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 15:38 benalb [this message]
2023-07-22 19:35 ` [PR PATCH] [Merged]: " Duncaen

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