Github messages for voidlinux
 help / color / mirror / Atom feed
From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] cryptsetup: update to 2.4.1.
Date: Tue, 12 Oct 2021 21:35:27 +0200	[thread overview]
Message-ID: <20211012193527.flJW1d1vf8vi9aegmVeor2xapNmQjzUkM4ukymlEuqA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33324@inbox.vuxu.org>

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

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

https://github.com/Piraty/void-packages cryptsetup-2.4.1
https://github.com/void-linux/void-packages/pull/33324

cryptsetup: update to 2.4.1.
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

A patch file from https://github.com/void-linux/void-packages/pull/33324.patch is attached

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

From 880302c24784f468484db45426a47a4ac9ee62db Mon Sep 17 00:00:00 2001
From: Piraty <piraty1@inbox.ru>
Date: Mon, 4 Oct 2021 20:37:11 +0200
Subject: [PATCH] cryptsetup: update to 2.4.1.

---
 srcpkgs/cryptsetup/template | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/srcpkgs/cryptsetup/template b/srcpkgs/cryptsetup/template
index 949a2ce214a3..94f6260a1e00 100644
--- a/srcpkgs/cryptsetup/template
+++ b/srcpkgs/cryptsetup/template
@@ -1,14 +1,14 @@
 # Template file for 'cryptsetup'
 pkgname=cryptsetup
-version=2.3.6
+version=2.4.1
 revision=1
 build_style=gnu-configure
-configure_args="--with-crypto_backend=openssl $(vopt_enable pwquality)
- --enable-cryptsetup-reencrypt --enable-libargon2"
+configure_args="--with-crypto_backend=openssl --enable-cryptsetup-reencrypt
+ --enable-libargon2 $(vopt_enable pwquality)"
 make_check_args="-C tests"
 hostmakedepends="pkg-config"
 makedepends="device-mapper-devel json-c-devel openssl-devel popt-devel
- libargon2-devel $(vopt_if pwquality 'libpwquality-devel')"
+ libargon2-devel libssh-devel $(vopt_if pwquality libpwquality-devel)"
 checkdepends="procps-ng which jq tar xz xxd"
 short_desc="Setup virtual encryption devices under Linux dm-crypt"
 maintainer="Daniel Eyßer <daniel.eysser@gmail.com>"
@@ -16,7 +16,7 @@ license="GPL-2.0-or-later"
 homepage="https://gitlab.com/cryptsetup/cryptsetup"
 changelog="https://gitlab.com/cryptsetup/cryptsetup/raw/master/docs/v${version}-ReleaseNotes"
 distfiles="${KERNEL_SITE}/utils/cryptsetup/v${version%.*}/${pkgname}-${version}.tar.xz"
-checksum=b296b7a21ea576c2b180611ccb19d06aec8dddaedf7c704b0c6a81210c25635f
+checksum=a356a727a83a464ade566e95239622a22dbe4e0f482b198fdb04ab0d3a5a9c5f
 make_check=extended
 subpackages="libcryptsetup cryptsetup-devel"
 
@@ -32,12 +32,13 @@ post_patch() {
 	fi
 }
 
-case $XBPS_TARGET_MACHINE in
-	*-musl)
-		configure_args+=" --enable-static-cryptsetup"
-		subpackages+=" cryptsetup-static"
-		;;
-esac
+if [ "$XBPS_TARGET_LIBC" = musl ]; then
+	configure_args+=" --enable-static-cryptsetup"
+	subpackages+=" cryptsetup-static"
+
+	makedepends+=" argp-standalone"
+	LDFLAGS+=" -largp"
+fi
 
 cryptsetup-static_package() {
 	short_desc+=" - static cryptsetup"

  reply	other threads:[~2021-10-12 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 18:40 [PR PATCH] " Piraty
2021-10-12 19:35 ` Piraty [this message]
2021-10-15 22:11 ` [PR PATCH] [Merged]: " Piraty

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=20211012193527.flJW1d1vf8vi9aegmVeor2xapNmQjzUkM4ukymlEuqA@z \
    --to=piraty@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    --subject='Re: [PR PATCH] [Updated] cryptsetup: update to 2.4.1.' \
    /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

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).