From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bfs: update to 2.6.2.
Date: Fri, 21 Oct 2022 23:52:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40090@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
There is a new pull request by daniel-eys against master on the void-packages repository
https://github.com/daniel-eys/void-packages bfs
https://github.com/void-linux/void-packages/pull/40090
bfs: update to 2.6.2.
<!-- 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)
- 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/40090.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bfs-40090.patch --]
[-- Type: text/x-diff, Size: 1053 bytes --]
From 6cfef09a655151869e77b8475fb78ea09ba8fde5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Fri, 21 Oct 2022 23:50:09 +0200
Subject: [PATCH] bfs: update to 2.6.2.
---
srcpkgs/bfs/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/bfs/template b/srcpkgs/bfs/template
index b1d011a206e0..f003661046f7 100644
--- a/srcpkgs/bfs/template
+++ b/srcpkgs/bfs/template
@@ -1,6 +1,6 @@
# Template file for 'bfs'
pkgname=bfs
-version=2.6.1
+version=2.6.2
revision=1
build_style=gnu-makefile
makedepends="acl-devel libcap-devel oniguruma-devel"
@@ -11,7 +11,7 @@ license="0BSD"
homepage="https://github.com/tavianator/bfs"
changelog="https://raw.githubusercontent.com/tavianator/bfs/main/docs/CHANGELOG.md"
distfiles="https://github.com/tavianator/bfs/archive/${version}.tar.gz"
-checksum=15e35b46774af305cbdfbfaa9889591440579a8233bc7308e050ec27b791647d
+checksum=1d50f7fdeda2bafd3ce6e4eacbe88de43f3ec14fb904aa8f81641aefba465afe
post_install() {
vlicense LICENSE
next reply other threads:[~2022-10-21 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 21:52 daniel-eys [this message]
2022-10-21 21:58 ` daniel-eys
2022-10-22 0:42 ` [WIP] " tavianator
2022-10-22 16:22 ` tavianator
2022-10-23 13:34 ` [PR PATCH] [Updated] " daniel-eys
2022-10-23 13:38 ` daniel-eys
2023-01-22 2:00 ` github-actions
2023-01-22 12:11 ` [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-40090@inbox.vuxu.org \
--to=daniel-eys@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).