From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] broot: update to 1.14.1
Date: Fri, 08 Jul 2022 05:51:54 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37921@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
There is a new pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages broot
https://github.com/void-linux/void-packages/pull/37921
broot: update to 1.14.1
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/37921.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-broot-37921.patch --]
[-- Type: text/x-diff, Size: 1095 bytes --]
From d588e2fcf95682d63d89e1dc8c22b47870c680f5 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Thu, 7 Jul 2022 23:49:28 -0400
Subject: [PATCH] broot: update to 1.14.1
---
srcpkgs/broot/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/broot/template b/srcpkgs/broot/template
index d57eb2f7b588..48ff908d0215 100644
--- a/srcpkgs/broot/template
+++ b/srcpkgs/broot/template
@@ -1,6 +1,6 @@
# Template file for 'broot'
pkgname=broot
-version=1.13.3
+version=1.14.1
revision=1
build_style=cargo
short_desc="Interactive directory tree view, fuzzy search, balanced BFS descent"
@@ -9,7 +9,7 @@ license="MIT"
homepage="https://dystroy.org/broot/"
changelog="https://raw.githubusercontent.com/Canop/broot/master/CHANGELOG.md"
distfiles="https://github.com/Canop/broot/archive/v${version}.tar.gz"
-checksum=a7f9e98ff1371eff065a8dabbe9e31ef42d264b7d93c18f920d6a5399016da33
+checksum=acbcf7adb950c05e6fe2ed3de8f4fed4537bef0150aad0d9917934fbd98bc0a1
if [ "$XBPS_TARGET_ENDIAN" = "be" ]; then
broken="exr crate errors on big endian"
next reply other threads:[~2022-07-08 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 3:51 cinerea0 [this message]
2022-07-08 5:08 ` archbtw24
2022-07-08 13:27 ` cinerea0
2022-07-08 18:15 ` [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-37921@inbox.vuxu.org \
--to=cinerea0@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).