From: DragonGhost7 <DragonGhost7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] hackrf: update to 2023.01.1.
Date: Thu, 15 Jun 2023 22:19:33 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44459@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
There is a new pull request by DragonGhost7 against master on the void-packages repository
https://github.com/DragonGhost7/void-packages hackrf
https://github.com/void-linux/void-packages/pull/44459
hackrf: update to 2023.01.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### 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):
- x86_64-musl
- aarch64
- aarch64-musl
- armv7l
- armv6l
- i686
A patch file from https://github.com/void-linux/void-packages/pull/44459.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hackrf-44459.patch --]
[-- Type: text/x-diff, Size: 1085 bytes --]
From 45a3f3955ce4e56b2e390430fb284c2fda9f1b81 Mon Sep 17 00:00:00 2001
From: DragonGhost7 <darkiridiumghost@gmail.com>
Date: Thu, 15 Jun 2023 16:09:38 -0400
Subject: [PATCH] hackrf: update to 2023.01.1.
---
srcpkgs/hackrf/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/hackrf/template b/srcpkgs/hackrf/template
index 962cc7f4e856..189ab5b1f00a 100644
--- a/srcpkgs/hackrf/template
+++ b/srcpkgs/hackrf/template
@@ -1,6 +1,6 @@
# Template file for 'hackrf'
pkgname=hackrf
-version=2022.09.1
+version=2023.01.1
revision=1
build_wrksrc=host
build_style=cmake
@@ -14,7 +14,7 @@ maintainer="DragonGhost7 <darkiridiumghost@gmail.com>"
license="GPL-2.0-or-later"
homepage="https://greatscottgadgets.com/hackrf/"
distfiles="https://github.com/greatscottgadgets/hackrf/releases/download/v${version}/${pkgname}-${version}.tar.xz"
-checksum=bacd4e7937467ffa14654624444c8b5c716ab470d8c1ee8d220d2094ae2adb3e
+checksum=32a03f943a30be4ba478e94bf69f14a5b7d55be6761007f4a4f5453418206a11
post_install() {
for f in ../firmware-bin/*.{bin,dfu}; do
next reply other threads:[~2023-06-15 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 20:19 DragonGhost7 [this message]
2023-06-15 20:24 ` [PR PATCH] [Updated] " DragonGhost7
2023-06-15 20:31 ` DragonGhost7
2023-06-19 19:09 ` [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-44459@inbox.vuxu.org \
--to=dragonghost7@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).