Github messages for voidlinux
 help / color / mirror / Atom feed
From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libvirt 6.2.0
Date: Fri, 03 Apr 2020 19:02:58 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20609@inbox.vuxu.org> (raw)

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

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

https://github.com/Hoshpak/void-packages libvirt-6.2.0
https://github.com/void-linux/void-packages/pull/20609

libvirt 6.2.0
None

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libvirt-6.2.0-20609.patch --]
[-- Type: text/x-diff, Size: 2211 bytes --]

From badb2efb7d8a9e33455da69e8e5ae9dc4f64ada9 Mon Sep 17 00:00:00 2001
From: Helmut Pozimski <helmut@pozimski.eu>
Date: Fri, 3 Apr 2020 19:01:15 +0200
Subject: [PATCH 1/2] libvirt: update to 6.2.0.

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

diff --git a/srcpkgs/libvirt/template b/srcpkgs/libvirt/template
index 066c51dd626..2dabd9196e7 100644
--- a/srcpkgs/libvirt/template
+++ b/srcpkgs/libvirt/template
@@ -1,6 +1,6 @@
 # Template file for 'libvirt'
 pkgname=libvirt
-version=6.1.0
+version=6.2.0
 revision=1
 build_wrksrc="build"
 build_style=gnu-configure
@@ -15,7 +15,7 @@ license="LGPL-2.1-or-later"
 homepage="https://libvirt.org"
 changelog="https://libvirt.org/news.html"
 distfiles="https://libvirt.org/sources/${pkgname}-${version}.tar.xz"
-checksum=167c185be45560e73dd3e14ed375778b555c01455192de2dafc4d0f74fabebc0
+checksum=aec8881f236917c4f8064918df546ed3aacd0bb8a2f312f4d37485721cce0fb1
 
 # FIX https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701649
 system_accounts="libvirt"

From 973652a78161cea0f182ee043b59bbc309380595 Mon Sep 17 00:00:00 2001
From: Helmut Pozimski <helmut@pozimski.eu>
Date: Fri, 3 Apr 2020 19:02:15 +0200
Subject: [PATCH 2/2] libvirt-python3: update to 6.2.0.

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

diff --git a/srcpkgs/libvirt-python3/template b/srcpkgs/libvirt-python3/template
index c75e61eb9e7..402f86862a2 100644
--- a/srcpkgs/libvirt-python3/template
+++ b/srcpkgs/libvirt-python3/template
@@ -1,6 +1,6 @@
 # Template file for 'libvirt-python3'
 pkgname=libvirt-python3
-version=6.1.0
+version=6.2.0
 revision=1
 wrksrc="libvirt-python-${version}"
 build_style=python3-module
@@ -11,7 +11,7 @@ maintainer="Helmut Pozimski <helmut@pozimski.eu>"
 license="LGPL-2.1-or-later"
 homepage="https://pypi.org/project/libvirt-python/"
 distfiles="https://libvirt.org/sources/python/libvirt-python-${version}.tar.gz"
-checksum=be644f4809c0e1d368e3ac065df3c66a26dcfe61ecb607ee9706e1799f22c35a
+checksum=d9ff49257ef768d2187ae92f550e96d9e4b13124d8acd3e78af83e5c4c1dec5d
 
 case "$XBPS_TARGET_MACHINE" in
 	aarch64*) broken="Builders need libvirt update for the host" ;;

             reply	other threads:[~2020-04-03 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 17:02 Hoshpak [this message]
2020-04-05 18:25 ` [PR PATCH] [Merged]: " Hoshpak

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-20609@inbox.vuxu.org \
    --to=hoshpak@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).