Re: iotests and python dependencies

From: John Snow <jsnow@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	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 10:13:22 -0400	[thread overview]
Message-ID: <CAFn=p-Zfonw462fKT=TBKCRLbZ2xPUwsK-SeRJhgfxYwNRJEsg@mail.gmail.com> (raw)
In-Reply-To: <07a829c2-4eb8-01e3-0c8c-691c1420f51a@redhat.com>

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

On Thu, May 5, 2022, 9:16 AM Paolo Bonzini <pbonzini@redhat.com> wrote:

> 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.
>

A small headache relating fixes to both locations, but if you'd like to see
it to prove that the installation mechanism works in general, then OK. I'm
willing to deal with the pain until the next release to let us go through a
testing cycle. Reluctantly. Maybe.

I'm assuming you mean as a subpackage and not a [git] submodule. If you do
mean git, then ... uh. That might be messy.

[-- Attachment #2: Type: text/html, Size: 1640 bytes --]