Github messages for voidlinux
 help / color / mirror / Atom feed
From: skmpz <skmpz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libblockdev: update to 2.28.
Date: Thu, 26 Jan 2023 19:33:48 +0100	[thread overview]
Message-ID: <20230126183348.KsMtI_PMmsk_ywL3DCF9AkPoSqawVo13KDelCxC8Av4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40642@inbox.vuxu.org>

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

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

https://github.com/skmpz/void-packages libblockdev-2.28
https://github.com/void-linux/void-packages/pull/40642

libblockdev: update to 2.28.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### 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/40642.patch is attached

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

From d85c7a9902a578c8392c20f21bdb6514e33ba3e0 Mon Sep 17 00:00:00 2001
From: skmpz <dem.procopiou@gmail.com>
Date: Sun, 20 Nov 2022 15:50:03 +0400
Subject: [PATCH] libblockdev: update to 2.28.

---
 srcpkgs/libblockdev/template | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/libblockdev/template b/srcpkgs/libblockdev/template
index b857dd3b4678..c3287673749e 100644
--- a/srcpkgs/libblockdev/template
+++ b/srcpkgs/libblockdev/template
@@ -1,7 +1,7 @@
 # Template file for 'libblockdev'
 pkgname=libblockdev
-version=2.26
-revision=2
+version=2.28
+revision=1
 build_style=gnu-configure
 hostmakedepends="pkg-config python3"
 makedepends="cryptsetup-devel device-mapper-devel dmraid-devel libbytesize-devel
@@ -11,9 +11,10 @@ short_desc="Library for manipulating block devices"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="LGPL-2.1-or-later"
 homepage="https://github.com/storaged-project/libblockdev"
-changelog="https://raw.githubusercontent.com/storaged-project/libblockdev/master/NEWS.rst"
+# changelog needs to be adjusted on major version changes
+changelog="https://raw.githubusercontent.com/storaged-project/libblockdev/2.x-branch/NEWS.rst"
 distfiles="https://github.com/storaged-project/libblockdev/releases/download/${version}-1/libblockdev-${version}.tar.gz"
-checksum=c4c0e10b35ac632bda8ce6d200b5601184984dec387fe59185921eb42432e069
+checksum=82c9c841e28a74fecadedebfae6a772df623cecdf652e5376650fa26da5b7df4
 conf_files="/etc/libblockdev/conf.d/10-lvm-dbus.cfg
  /etc/libblockdev/conf.d/00-default.cfg"
 

  parent reply	other threads:[~2023-01-26 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 11:50 [PR PATCH] " skmpz
2022-11-24  2:23 ` [PR REVIEW] " classabbyamp
2022-11-24  4:53 ` [PR PATCH] [Updated] " skmpz
2022-11-24  4:55 ` skmpz
2023-01-26 17:54 ` [PR REVIEW] " Vaelatern
2023-01-26 18:33 ` skmpz [this message]
2023-01-26 18:53 ` [PR PATCH] [Merged]: " Vaelatern
2023-01-26 18:53 ` Vaelatern

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=20230126183348.KsMtI_PMmsk_ywL3DCF9AkPoSqawVo13KDelCxC8Av4@z \
    --to=skmpz@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).