From: Paolo Bonzini <pbonzini@redhat.com>
To: "John Snow" <jsnow@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Qemu-block <qemu-block@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: iotests and python dependencies
Date: Thu, 5 May 2022 15:15:54 +0200 [thread overview]
Message-ID: <07a829c2-4eb8-01e3-0c8c-691c1420f51a@redhat.com> (raw)
In-Reply-To: <CAFn=p-ZpoJvoZSnk9gN+uiaas=h-tvZqBCZw2kJf88=rq_5LYQ@mail.gmail.com>
On 5/5/22 15:10, John Snow wrote:
>
> > Hm, do we need iotests during an rpm build? Is it because of
> "make check"?
>
> Yes, and this is good, because it prevents us from outputting an
> RPM build that has a broken QEMU in it.
>
> Guess this means I need to make a Fedora package too, though. My hubris.
I would rather keep python/qemu/qmp as a submodule for a longer time,
and still go through a virtual environment that installs it together
with its pip dependencies.
Paolo
next prev parent reply other threads:[~2022-05-05 13:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 19:38 iotests and python dependencies John Snow
2022-05-05 8:09 ` Daniel P. Berrangé
2022-05-05 12:08 ` John Snow
2022-05-05 12:33 ` Daniel P. Berrangé
2022-05-05 13:10 ` John Snow
2022-05-05 13:15 ` Paolo Bonzini [this message]
2022-05-05 14:13 ` John Snow
2022-05-05 15:50 ` Paolo Bonzini
2022-05-05 15:57 ` Daniel P. Berrangé
2022-05-08 14:23 ` Paolo Bonzini
2022-05-05 8:51 ` Kevin Wolf
2022-05-05 9:28 ` Paolo Bonzini
2022-05-05 10:59 ` Kevin Wolf
2022-05-05 12:24 ` Paolo Bonzini
2022-05-05 12:39 ` Kevin Wolf
2022-05-10 17:40 ` John Snow
2022-05-05 11:55 ` John Snow
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=07a829c2-4eb8-01e3-0c8c-691c1420f51a@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=v.sementsov-og@mail.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.