Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] hamlib: update to 4.5.4.
Date: Sun, 12 Feb 2023 00:13:30 +0100	[thread overview]
Message-ID: <20230211231330.XrualS4k_lI897CUTdfqeVQ1HZbEF4dcOMIOtUygbvE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42000@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages hamlib
https://github.com/void-linux/void-packages/pull/42000

hamlib: update to 4.5.4.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**

<!--
#### 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/42000.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hamlib-42000.patch --]
[-- Type: text/x-diff, Size: 1182 bytes --]

From e9b4773dc570bddd8f3904d62ec73d849491ef15 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Tue, 31 Jan 2023 13:19:02 -0500
Subject: [PATCH] hamlib: update to 4.5.4.

---
 srcpkgs/hamlib/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/hamlib/template b/srcpkgs/hamlib/template
index 04357f6c913b..6e74d94ffa17 100644
--- a/srcpkgs/hamlib/template
+++ b/srcpkgs/hamlib/template
@@ -1,7 +1,7 @@
 # Template file for 'hamlib'
 pkgname=hamlib
-version=4.5
-revision=2
+version=4.5.4
+revision=1
 build_style=gnu-configure
 configure_args="--disable-static --with-perl-binding --with-python-binding
  --with-tcl-binding --with-xml-support"
@@ -15,7 +15,7 @@ license="LGPL-2.1-or-later, GPL-2.0-or-later"
 homepage="https://hamlib.github.io"
 changelog="https://raw.githubusercontent.com/Hamlib/Hamlib/master/NEWS"
 distfiles="https://github.com/Hamlib/Hamlib/releases/download/${version}/hamlib-${version}.tar.gz"
-checksum=14a2ce76a647a75e71d8ccf1f16999a6708e84823d9f74137f2173fcee94ad52
+checksum=b1aea97d6093990b77d5dc4bde6b9ca06183ddb7e24da7e2367a2acc957b7ac2
 
 CFLAGS="-DNO_POSIX_2008_LOCALE -D_GNU_SOURCE"
 

  reply	other threads:[~2023-02-11 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 18:19 [PR PATCH] " classabbyamp
2023-02-11 23:13 ` classabbyamp [this message]
2023-02-11 23:18 ` [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=20230211231330.XrualS4k_lI897CUTdfqeVQ1HZbEF4dcOMIOtUygbvE@z \
    --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).