From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Fam Zheng" <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] docker: fedora: test more components
Date: Fri, 16 Mar 2018 11:15:25 +0100 [thread overview]
Message-ID: <3a776827-ee8b-781f-1485-2fb5de01b8a2@redhat.com> (raw)
In-Reply-To: <20180316094351.GD3066@redhat.com>
On 16/03/2018 10:43, Daniel P. Berrangé wrote:
>> I wonder if we should simply do "dnf build-dep qemu" and only list additional
>> (mingw, for example) packages explicitly, like the debian dockerfiles.
> From an upstream POV it feels wrong to have our builds depend on the state
> of stuff listed in the Fedora RPM spec file, as we don't want changes in
> Fedora to randomly break QEMU upstream CI.
I agree---I'll send v2 of this patch.
Paolo
prev parent reply other threads:[~2018-03-16 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 12:05 [Qemu-devel] [PATCH] docker: fedora: test more components Paolo Bonzini
2018-03-13 12:33 ` Fam Zheng
2018-03-15 14:31 ` Philippe Mathieu-Daudé
2018-03-15 14:47 ` Daniel P. Berrangé
2018-03-16 2:40 ` Fam Zheng
2018-03-16 9:43 ` Daniel P. Berrangé
2018-03-16 10:15 ` Paolo Bonzini [this message]
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=3a776827-ee8b-781f-1485-2fb5de01b8a2@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.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).