From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] carapace: update to 0.29.0.
Date: Wed, 17 Jan 2024 20:01:01 +0100 [thread overview]
Message-ID: <20240117190101.78A462B248@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48110@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
There is an updated pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages carapace
https://github.com/void-linux/void-packages/pull/48110
carapace: update to 0.29.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
A patch file from https://github.com/void-linux/void-packages/pull/48110.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-carapace-48110.patch --]
[-- Type: text/x-diff, Size: 1246 bytes --]
From 7753385a2cfc4086db5b6a7b9d0d6357fe2a1348 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Thu, 4 Jan 2024 14:54:44 +0530
Subject: [PATCH] carapace: update to 0.29.1.
---
srcpkgs/carapace/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/carapace/template b/srcpkgs/carapace/template
index 0b59e2282f200..4b4f3572fdbda 100644
--- a/srcpkgs/carapace/template
+++ b/srcpkgs/carapace/template
@@ -1,6 +1,6 @@
# Template file for 'carapace'
pkgname=carapace
-version=0.28.5
+version=0.29.1
revision=1
build_style=go
go_import_path=github.com/rsteube/carapace-bin
@@ -10,9 +10,10 @@ go_ldflags="-X main.version=${version}"
short_desc="Multi-shell multi-command argument completer"
maintainer="icp <pangolin@vivaldi.net>"
license="MIT"
-homepage="https://github.com/rsteube/carapace-bin"
+homepage="https://carapace.sh/"
+changelog="https://rsteube.github.io/carapace-bin/release_notes.html"
distfiles="https://github.com/rsteube/carapace-bin/archive/refs/tags/v${version}.tar.gz"
-checksum=fbe3fc36f0f74ebda761bcdfaa922ce23599ba0701c0c914db8f40914a73ab86
+checksum=1197b0ef630533488cf5cd986e522e3dc8a3d410f6197371ae8614a14b355fbf
pre_build() {
GOARCH= go generate ./cmd/...
next prev parent reply other threads:[~2024-01-17 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 19:40 [PR PATCH] " icp1994
2024-01-17 18:27 ` [PR REVIEW] " classabbyamp
2024-01-17 19:01 ` icp1994 [this message]
2024-01-17 19:02 ` [PR REVIEW] carapace: update to 0.29.1 icp1994
2024-01-17 19:07 ` icp1994
2024-01-17 19:13 ` [PR PATCH] [Updated] " icp1994
2024-01-17 19:16 ` icp1994
2024-01-17 19:19 ` [PR REVIEW] " icp1994
2024-01-17 19:22 ` [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=20240117190101.78A462B248@inbox.vuxu.org \
--to=icp1994@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).