unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Langlois <pierre.langlois@gmx.com>
To: Brice Waegeneire <brice@waegenei.re>
Cc: 46623@debbugs.gnu.org
Subject: [bug#46623] [PATCH 4/4] gnu: libvirt: Update to 7.0.0.
Date: Fri, 02 Apr 2021 12:56:06 +0100	[thread overview]
Message-ID: <87ft08vr1l.fsf@gmx.com> (raw)
In-Reply-To: <20210218204812.21093-4-brice@waegenei.re>

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

Hi Brice,

Brice Waegeneire writes:

> * gnu/packages/virtualization.scm (libvirt): Update to 7.0.0.
> [arguemnts]: Switch to meson, only build system supported by upstream.
> [inputs]: Add libssh2 and readline.
> [native-inputs]: Add bash-completion, gettext, python-docutils and
> rpcsvc-proto.
> * gnu/packages/patches/libvirt-add-install-prefix.patch: New file...
> * gnu/local.mk: ...add it.
> * gnu/packages/patches/libvirt-create-machine-cgroup.patch: Delete file,
> merged by upstream.

I applied this patch locally on top of patch 1/4 and tested it, I can
confirm that it works and passes https://issues.guix.gnu.org/47541, as
opposed to my approach :-).

Here's a new patch series that adds your 1&4 patches, updated to 7.2.0
and then updates dependent packages.  I've also extended the system test
so that it can catch issues with the /var and /etc runtime directories.

I've not looked at patches 2&3, on the service itself yet though.

Anyways, WDYT? OK to commit?

Thanks,
Pierre

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]

  reply	other threads:[~2021-04-02 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 20:24 [bug#46623] [PATCH 0/4] gnu: libvirt: Update to 7.0.0 Brice Waegeneire
2021-02-18 20:48 ` [bug#46623] [PATCH 1/4] gnu: libvirt: Enable disk and directory storage Brice Waegeneire
2021-02-18 20:48 ` [bug#46623] [PATCH 2/4] services: libvirt: Change unix-sock-group default Brice Waegeneire
2021-02-18 20:48 ` [bug#46623] [PATCH 3/4] services: libvirt: Add qemu field Brice Waegeneire
2021-02-18 20:48 ` [bug#46623] [PATCH 4/4] gnu: libvirt: Update to 7.0.0 Brice Waegeneire
2021-04-02 11:56   ` Pierre Langlois [this message]
2021-04-02 11:58     ` [bug#46623] [PATCH 1/6] tests: libvirt: Catch issues with incorrect /var and /etc in package Pierre Langlois
2021-04-02 11:58       ` [bug#46623] [PATCH 2/6] gnu: libvirt: Enable disk and directory storage Pierre Langlois
2021-04-02 11:58       ` [bug#46623] [PATCH 3/6] gnu: libvirt: Update to 7.2.0 Pierre Langlois
2021-04-02 11:59       ` [bug#46623] [PATCH 4/6] gnu: python-libvirt: " Pierre Langlois
2021-04-02 11:59       ` [bug#46623] [PATCH 5/6] gnu: libvirt-glib: Update to 4.0.0 Pierre Langlois
2021-04-02 11:59       ` [bug#46623] [PATCH 6/6] gnu: virt-manager: Update to 3.2.0 Pierre Langlois
2021-04-05 16:37     ` [bug#46623] [PATCH 0/4] gnu: libvirt: Update to 7.0.0 Ludovic Courtès
2021-04-05 18:52       ` Pierre Langlois
2021-04-01 20:29 ` bug#46623: " Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ft08vr1l.fsf@gmx.com \
    --to=pierre.langlois@gmx.com \
    --cc=46623@debbugs.gnu.org \
    --cc=brice@waegenei.re \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).