From: tranzystorekk <tranzystorekk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] ripgrep: update to 14.1.0
Date: Sun, 07 Jan 2024 13:34:56 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48103@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
There is a new pull request by tranzystorekk against master on the void-packages repository
https://github.com/tranzystorekk/void-packages ripgrep
https://github.com/void-linux/void-packages/pull/48103
ripgrep: update to 14.1.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
cc @leahneukirchen
<!--
#### 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/48103.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ripgrep-48103.patch --]
[-- Type: text/x-diff, Size: 1105 bytes --]
From 1edf7202780d6dcb105cf3970796316313dd765b Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Sun, 7 Jan 2024 13:29:33 +0100
Subject: [PATCH] ripgrep: update to 14.1.0
---
srcpkgs/ripgrep/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/ripgrep/template b/srcpkgs/ripgrep/template
index b97ca425fa04c..db014de3d7f3c 100644
--- a/srcpkgs/ripgrep/template
+++ b/srcpkgs/ripgrep/template
@@ -1,6 +1,6 @@
# Template file for 'ripgrep'
pkgname=ripgrep
-version=14.0.3
+version=14.1.0
revision=1
build_style=cargo
build_helper=qemu
@@ -13,7 +13,7 @@ license="Unlicense, MIT"
homepage="https://github.com/BurntSushi/ripgrep/"
changelog="https://raw.githubusercontent.com/BurntSushi/ripgrep/master/CHANGELOG.md"
distfiles="https://github.com/BurntSushi/ripgrep/archive/refs/tags/${version}.tar.gz"
-checksum=f5794364ddfda1e0411ab6cad6dd63abe3a6b421d658d9fee017540ea4c31a0e
+checksum=33c6169596a6bbfdc81415910008f26e0809422fda2d849562637996553b2ab6
post_patch() {
rm -f .cargo/config.toml # tries to do weird things on musl
next reply other threads:[~2024-01-07 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 12:34 tranzystorekk [this message]
2024-01-07 14:14 ` [PR PATCH] [Merged]: " leahneukirchen
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-48103@inbox.vuxu.org \
--to=tranzystorekk@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).