Github messages for voidlinux
 help / color / mirror / Atom feed
* [PR PATCH] lvm2: update to 2.02.187.
@ 2020-05-27 19:45 rmccask
  2020-05-28  4:49 ` Anachron
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: rmccask @ 2020-05-27 19:45 UTC (permalink / raw)
  To: ml

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

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

https://github.com/rmccask/void-packages lvm2-2.02.187
https://github.com/void-linux/void-packages/pull/22365

lvm2: update to 2.02.187.


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

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

From 28d98bede3a1ffc34912ea10640f3bae65c97d4f Mon Sep 17 00:00:00 2001
From: Randy McCaskill <randy@mccaskill.us>
Date: Wed, 27 May 2020 15:45:14 -0400
Subject: [PATCH] lvm2: update to 2.02.187.

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

diff --git a/srcpkgs/lvm2/template b/srcpkgs/lvm2/template
index 48ce82aeb45..d0e676b2566 100644
--- a/srcpkgs/lvm2/template
+++ b/srcpkgs/lvm2/template
@@ -1,6 +1,6 @@
 # Template file for 'lvm2'
 pkgname=lvm2
-version=2.02.186
+version=2.02.187
 revision=1
 wrksrc="LVM2.${version}"
 build_style=gnu-configure
@@ -19,7 +19,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=d8421eee702982dc0d8b0c9e40cc1443ee487eff1460a00244a9f4bf439a27be
+checksum=0e0d521a863a5db2440f2e1e7627ba82b70273ae4ab0bbe130851db0d58e5af1
 conf_files="/etc/lvm/*.conf /etc/lvm/profile/*"
 make_dirs="
  /etc/lvm/archive 0755 root root

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: lvm2: update to 2.02.187.
  2020-05-27 19:45 [PR PATCH] lvm2: update to 2.02.187 rmccask
@ 2020-05-28  4:49 ` Anachron
  2020-05-28 13:26 ` rmccask
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: Anachron @ 2020-05-28  4:49 UTC (permalink / raw)
  To: ml

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

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/pull/22365#issuecomment-635098270

Comment:
Is this tested?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: lvm2: update to 2.02.187.
  2020-05-27 19:45 [PR PATCH] lvm2: update to 2.02.187 rmccask
  2020-05-28  4:49 ` Anachron
@ 2020-05-28 13:26 ` rmccask
  2020-05-28 18:43 ` Anachron
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: rmccask @ 2020-05-28 13:26 UTC (permalink / raw)
  To: ml

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

New comment by rmccask on void-packages repository

https://github.com/void-linux/void-packages/pull/22365#issuecomment-635349060

Comment:
I attached a 2nd virtual drive to my build vm.  I verified I had the new lvm2 installed.  Then I created a lvm partition on the drive.  I used pvcreate, vgcreate, lvcreate and  lvdisplay.  I rebooted and verified the lv is still there.  Is there more I need to try?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: lvm2: update to 2.02.187.
  2020-05-27 19:45 [PR PATCH] lvm2: update to 2.02.187 rmccask
  2020-05-28  4:49 ` Anachron
  2020-05-28 13:26 ` rmccask
@ 2020-05-28 18:43 ` Anachron
  2020-05-28 18:59 ` rmccask
  2020-05-31 11:24 ` [PR PATCH] [Merged]: " Hoshpak
  4 siblings, 0 replies; 6+ messages in thread
From: Anachron @ 2020-05-28 18:43 UTC (permalink / raw)
  To: ml

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

New comment by Anachron on void-packages repository

https://github.com/void-linux/void-packages/pull/22365#issuecomment-635527186

Comment:
Ah good, no, that should suffice. I just realized you updated to another `2.02` release, the `2.03` one doesn't correctly build without modifications: https://github.com/void-linux/void-packages/pull/20188

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: lvm2: update to 2.02.187.
  2020-05-27 19:45 [PR PATCH] lvm2: update to 2.02.187 rmccask
                   ` (2 preceding siblings ...)
  2020-05-28 18:43 ` Anachron
@ 2020-05-28 18:59 ` rmccask
  2020-05-31 11:24 ` [PR PATCH] [Merged]: " Hoshpak
  4 siblings, 0 replies; 6+ messages in thread
From: rmccask @ 2020-05-28 18:59 UTC (permalink / raw)
  To: ml

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

New comment by rmccask on void-packages repository

https://github.com/void-linux/void-packages/pull/22365#issuecomment-635535490

Comment:
Yes, I saw your efforts with 2.03 and took the easy one.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PR PATCH] [Merged]: lvm2: update to 2.02.187.
  2020-05-27 19:45 [PR PATCH] lvm2: update to 2.02.187 rmccask
                   ` (3 preceding siblings ...)
  2020-05-28 18:59 ` rmccask
@ 2020-05-31 11:24 ` Hoshpak
  4 siblings, 0 replies; 6+ messages in thread
From: Hoshpak @ 2020-05-31 11:24 UTC (permalink / raw)
  To: ml

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

There's a merged pull request on the void-packages repository

lvm2: update to 2.02.187.
https://github.com/void-linux/void-packages/pull/22365

Description:


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-05-31 11:24 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-27 19:45 [PR PATCH] lvm2: update to 2.02.187 rmccask
2020-05-28  4:49 ` Anachron
2020-05-28 13:26 ` rmccask
2020-05-28 18:43 ` Anachron
2020-05-28 18:59 ` rmccask
2020-05-31 11:24 ` [PR PATCH] [Merged]: " Hoshpak

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