From: tjkirch <tjkirch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] lvm2: update to 2.02.188.
Date: Fri, 20 Jan 2023 19:41:46 +0100 [thread overview]
Message-ID: <20230120184146.OL1EqdwzFCWiQWhyAbgt44CctZtuWEfXilm5B1b3_Nc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39821@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
There is an updated pull request by tjkirch against master on the void-packages repository
https://github.com/tjkirch/void-packages lvm2-2.02.188
https://github.com/void-linux/void-packages/pull/39821
lvm2: update to 2.02.188.
#### Testing the changes
- I tested the changes in this PR: **briefly** - my disks are all in LVM; I installed the update, rebooted, and all is still well.
#### Local build testing
- I built this PR locally for my native architecture, x86-64 glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- armv6l
- aarch64-musl
- x86_64-musl
I don't have the experience to update to 2.03.x, but the latest 2.02.x release seems smart. Here are the changes: https://mirrors.kernel.org/sourceware/lvm2/WHATS_NEW-2.02
A patch file from https://github.com/void-linux/void-packages/pull/39821.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lvm2-2.02.188-39821.patch --]
[-- Type: text/x-diff, Size: 1221 bytes --]
From 1ff6c0175560414b32033a27180bc6f8e68b564e Mon Sep 17 00:00:00 2001
From: Tom Kirchner <git@halffull.org>
Date: Sat, 8 Oct 2022 15:18:35 -0700
Subject: [PATCH] lvm2: update to 2.02.188.
---
srcpkgs/lvm2/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/lvm2/template b/srcpkgs/lvm2/template
index eccc6145f004..28d973a4cc5a 100644
--- a/srcpkgs/lvm2/template
+++ b/srcpkgs/lvm2/template
@@ -1,7 +1,7 @@
# Template file for 'lvm2'
pkgname=lvm2
-version=2.02.187
-revision=2
+version=2.02.188
+revision=1
build_style=gnu-configure
configure_args="--disable-selinux --enable-readline --enable-pkgconfig
--enable-fsadm --enable-applib --enable-dmeventd --enable-cmdlib
@@ -18,7 +18,7 @@ license="GPL-2.0-only, LGPL-2.1-only"
homepage="https://sourceware.org/lvm2/"
changelog="https://abi-laboratory.pro/?view=changelog&l=lvm2&v=${version}"
distfiles="https://mirrors.kernel.org/sourceware/lvm2/releases/LVM2.${version}.tgz"
-checksum=0e0d521a863a5db2440f2e1e7627ba82b70273ae4ab0bbe130851db0d58e5af1
+checksum=7101e8b0816ad77e4390fed9749a090214ba520061cd083437871e19e50cc9bd
conf_files="/etc/lvm/*.conf /etc/lvm/profile/*"
make_dirs="
/etc/lvm/archive 0755 root root
next prev parent reply other threads:[~2023-01-20 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 22:22 [PR PATCH] " tjkirch
2022-10-21 21:42 ` tjkirch
2023-01-20 2:01 ` github-actions
2023-01-20 18:39 ` tjkirch
2023-01-20 18:41 ` tjkirch [this message]
2023-04-22 1:53 ` github-actions
2023-04-22 2:59 ` tjkirch
2023-07-23 1:58 ` github-actions
2023-07-23 16:05 ` tjkirch
2023-08-05 18:56 ` [PR PATCH] [Merged]: " leahneukirchen
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=20230120184146.OL1EqdwzFCWiQWhyAbgt44CctZtuWEfXilm5B1b3_Nc@z \
--to=tjkirch@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).