From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cryptsetup: update to 2.6.0.
Date: Fri, 06 Jan 2023 02:27:59 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41486@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
There is a new pull request by mhmdanas against master on the void-packages repository
https://github.com/mhmdanas/void-packages cryptsetup-2.6.0
https://github.com/void-linux/void-packages/pull/41486
cryptsetup: update to 2.6.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES** (booted into my FDE installation)
This package is rather sensitive, so maybe it's worth having more people test this PR just to be sure that everything is working okay.
<!--
#### 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/41486.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cryptsetup-2.6.0-41486.patch --]
[-- Type: text/x-diff, Size: 1805 bytes --]
From fd6918415981be8ee7534bee7fb4a25f81120fa5 Mon Sep 17 00:00:00 2001
From: mhmdanas <triallax@tutanota.com>
Date: Fri, 6 Jan 2023 01:24:06 +0000
Subject: [PATCH] cryptsetup: update to 2.6.0.
---
srcpkgs/cryptsetup/template | 14 ++++----------
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/srcpkgs/cryptsetup/template b/srcpkgs/cryptsetup/template
index 89f75fedfc62..92a512660884 100644
--- a/srcpkgs/cryptsetup/template
+++ b/srcpkgs/cryptsetup/template
@@ -1,6 +1,6 @@
# Template file for 'cryptsetup'
pkgname=cryptsetup
-version=2.5.0
+version=2.6.0
revision=1
build_style=gnu-configure
configure_args="--with-crypto_backend=openssl --enable-cryptsetup-reencrypt
@@ -15,19 +15,13 @@ maintainer="Daniel Eyßer <daniel.eysser@gmail.com>"
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=9184a6ebbd9ce7eb211152e7f741a6c82f2d1cc0e24a84ec9c52939eee0f0542
+distfiles="${KERNEL_SITE}/utils/cryptsetup/v${version%.*}/cryptsetup-${version}.tar.xz"
+checksum=44397ba76e75a9cde5b02177bc63cd7af428a785788e3a7067733e7761842735
subpackages="libcryptsetup cryptsetup-devel"
build_options="pwquality"
desc_option_pwquality="Enable support for checking password quality via libpwquality"
-if [ "$XBPS_LIBC" = "musl" ]
-then
- make_check=no # Test fail on musl see upstream:
- # https://gitlab.com/cryptsetup/cryptsetup/-/issues/781
-else
- make_check=ci-skip # tests depend on acessing /dev/mapper/control fails on CI
-fi
+make_check=ci-skip # tests depend on acessing /dev/mapper/control fails on CI
post_patch() {
if [ "$XBPS_TARGET_LIBC" = musl ]; then
next reply other threads:[~2023-01-06 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 1:27 mhmdanas [this message]
2023-01-12 20:57 ` [PR PATCH] [Closed]: " abenson
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-41486@inbox.vuxu.org \
--to=mhmdanas@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).