From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] virt-manager: update to 4.0.0
Date: Sun, 06 Mar 2022 00:51:07 +0100 [thread overview]
Message-ID: <20220305235107.YJlVM4mg_hOBGgPhopP6yJMomHR4BD3Fz3-ThgAmwdg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35955@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
There is an updated pull request by zen0bit against master on the void-packages repository
https://github.com/oSoWoSo/VUR virt-manager
https://github.com/void-linux/void-packages/pull/35955
virt-manager: update to 4.0.0
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/35955.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-virt-manager-35955.patch --]
[-- Type: text/x-diff, Size: 1536 bytes --]
From ff9f50480b7d35acbb18f831e4cc281251ac49b9 Mon Sep 17 00:00:00 2001
From: zenobit <zen@osowoso.xyz>
Date: Sun, 6 Mar 2022 00:21:42 +0100
Subject: [PATCH] virt-manager: update to 4.0.0
---
srcpkgs/virt-manager/template | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/virt-manager/template b/srcpkgs/virt-manager/template
index f3f6a7424a1b..b6ecd0fc84f0 100644
--- a/srcpkgs/virt-manager/template
+++ b/srcpkgs/virt-manager/template
@@ -1,10 +1,11 @@
# Template file for 'virt-manager'
pkgname=virt-manager
-version=3.2.0
-revision=2
+version=4.0.0
+revision=1
build_style=python3-module
pycompile_dirs="/usr/share/${pkgname}/virtManager"
-hostmakedepends="gettext python3-docutils gtk-update-icon-cache"
+make_install_args="--no-compile-schemas --no-update-icon-cache"
+hostmakedepends="gettext python3-docutils python3-setuptools gtk-update-icon-cache"
depends="virt-manager-tools>=${version}_${revision} libvirt-glib
gtk-vnc spice-gtk gtksourceview4 dconf vte3 gir-freedesktop"
_coredeps="python3-gobject libvirt-python3 libosinfo
@@ -16,7 +17,7 @@ license="GPL-2.0-or-later"
homepage="https://virt-manager.org"
changelog="https://raw.githubusercontent.com/virt-manager/virt-manager/master/NEWS.md"
distfiles="https://virt-manager.org/download/sources/${pkgname}/${pkgname}-${version}.tar.gz"
-checksum=2b6fe3d90d89e1130227e4b05c51e6642d89c839d3ea063e0e29475fd9bf7b86
+checksum=515aaa2021a4bf352b0573098fe6958319b1ba8ec508ea37e064803f97f17086
python_version=3
post_install() {
next prev parent reply other threads:[~2022-03-05 23:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 22:16 [PR PATCH] " zen0bit
2022-03-03 22:23 ` zen0bit
2022-03-04 21:47 ` MouadCharradi
2022-03-04 22:58 ` paper42
2022-03-05 23:18 ` [PR PATCH] [Closed]: " zen0bit
2022-03-05 23:18 ` [PR PATCH] [Updated] " zen0bit
2022-03-05 23:22 ` zen0bit
2022-03-05 23:51 ` zen0bit [this message]
2022-03-05 23:54 ` zen0bit
2022-03-05 23:55 ` zen0bit
2022-04-07 11:34 ` [PR PATCH] [Closed]: " paper42
2022-03-04 16:51 [PR PATCH] " MouadCharradi
2022-03-04 17:20 ` [PR PATCH] [Updated] " MouadCharradi
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=20220305235107.YJlVM4mg_hOBGgPhopP6yJMomHR4BD3Fz3-ThgAmwdg@z \
--to=zen0bit@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).