Github messages for voidlinux
 help / color / mirror / Atom feed
From: 4ricci <4ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] lzip: update to 1.23.
Date: Thu, 03 Feb 2022 14:34:33 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35380@inbox.vuxu.org> (raw)

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

There is a new pull request by 4ricci against master on the void-packages repository

https://github.com/4ricci/void-packages lzip
https://github.com/void-linux/void-packages/pull/35380

lzip: update to 1.23.
<!-- 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 [skip CI](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/35380.patch is attached

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

From 224b4c15ffbcd3d0c706c76f4b88e658460d3ecb Mon Sep 17 00:00:00 2001
From: Roberto Ricci <ricci@disroot.org>
Date: Thu, 3 Feb 2022 12:02:53 +0100
Subject: [PATCH] lzip: update to 1.23.

---
 srcpkgs/lzip/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/lzip/template b/srcpkgs/lzip/template
index 288a8163fae4..d6c2c1326f92 100644
--- a/srcpkgs/lzip/template
+++ b/srcpkgs/lzip/template
@@ -1,6 +1,6 @@
 # Template file for 'lzip'
 pkgname=lzip
-version=1.22
+version=1.23
 revision=1
 build_style=gnu-configure
 short_desc="Lossless data compressor based on the LZMA algorithm"
@@ -8,7 +8,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later"
 homepage="https://www.nongnu.org/lzip/lzip.html"
 distfiles="${NONGNU_SITE}/lzip/lzip-${version}.tar.gz"
-checksum=c3342d42e67139c165b8b128d033b5c96893a13ac5f25933190315214e87a948
+checksum=4792c047ddf15ef29d55ba8e68a1a21e0cb7692d87ecdf7204419864582f280d
 
 do_configure() {
 	./configure --prefix=/usr CXX="$CXX" CXXFLAGS="$CXXFLAGS" LDFLAGS="$LDFLAGS"

             reply	other threads:[~2022-02-03 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 13:34 4ricci [this message]
2022-02-04 23:38 ` [PR PATCH] [Merged]: " paper42

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-35380@inbox.vuxu.org \
    --to=4ricci@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).