From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libjaylink: update to 0.3.0.
Date: Wed, 17 Aug 2022 00:23:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38728@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
There is a new pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages update/libjaylink-0.3.0
https://github.com/void-linux/void-packages/pull/38728
libjaylink: update to 0.3.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
- I don't have the money to buy any J-Link hardware, but it builds
A patch file from https://github.com/void-linux/void-packages/pull/38728.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/libjaylink-0.3.0-38728.patch --]
[-- Type: text/x-diff, Size: 1249 bytes --]
From 73b27d286a50d682102906c601e51f5ed6bb8333 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Tue, 16 Aug 2022 18:21:00 -0400
Subject: [PATCH] libjaylink: update to 0.3.0.
---
srcpkgs/libjaylink/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libjaylink/template b/srcpkgs/libjaylink/template
index 232a30004d4b..b19101d64114 100644
--- a/srcpkgs/libjaylink/template
+++ b/srcpkgs/libjaylink/template
@@ -1,6 +1,6 @@
# Template file for 'libjaylink'
pkgname=libjaylink
-version=0.2.0
+version=0.3.0
revision=1
build_style=gnu-configure
hostmakedepends="automake libtool pkg-config"
@@ -9,8 +9,9 @@ short_desc="Library to access SEGGER J-Link and compatible devices"
maintainer="classabbyamp <void@placeviolette.net>"
license="GPL-2.0-or-later"
homepage="https://gitlab.zapb.de/libjaylink/libjaylink"
+changelog="https://gitlab.zapb.de/libjaylink/libjaylink/-/raw/master/NEWS"
distfiles="https://gitlab.zapb.de/libjaylink/libjaylink/-/archive/${version}/libjaylink-${version}.tar.gz"
-checksum=ac10d03088a2f28ebfc0411f9e617433936220dc183050f2e429694dcadc4f2a
+checksum=7885e295a567bcacb3f5ec825647d99b2bb0f7e37ccb390019813ff6e249b9b5
pre_configure() {
./autogen.sh
next reply other threads:[~2022-08-16 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 22:23 classabbyamp [this message]
2022-08-16 22:42 ` [PR PATCH] [Updated] " classabbyamp
2022-09-01 0:15 ` unspecd
2022-09-01 0:16 ` unspecd
2022-09-01 0:22 ` [PR PATCH] [Merged]: " classabbyamp
2022-09-01 0:22 ` 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-38728@inbox.vuxu.org \
--to=classabbyamp@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).