qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Michal Privoznik <mprivozn@redhat.com>,
	Doug Goldstein <cardoe@gentoo.org>
Cc: libvir-list@redhat.com, Yan Vugenfirer <yan@daynix.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [libvirt] [PATCH 0/2] Fixed QEMU 1.0.1 support
Date: Wed, 26 Sep 2012 15:46:56 -0500	[thread overview]
Message-ID: <87wqzgv7en.fsf@codemonkey.ws> (raw)
In-Reply-To: <5062B82D.1080203@redhat.com>

Michal Privoznik <mprivozn@redhat.com> writes:

> On 25.09.2012 19:08, Doug Goldstein wrote:
>> On Tue, Sep 25, 2012 at 12:01 PM, Daniel P. Berrange
>> <berrange@redhat.com> wrote:
>>> On Tue, Sep 25, 2012 at 10:57:23AM -0600, Eric Blake wrote:
>>>> On 09/25/2012 06:54 AM, Daniel P. Berrange wrote:
>>>>> On Tue, Sep 25, 2012 at 02:49:00PM +0200, Michal Privoznik wrote:
>>>>>> On 25.09.2012 10:58, Dmitry Fleytman wrote:
>>>>>>> This patch fixes incorrect help screen parsing for QEMU 1.0.1 package
>>>>>>> Version line changed from
>>>>>>>     QEMU emulator version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008 Fabrice Bellard
>>>>>>> To
>>>>>>>     QEMU emulator version 1.0,1 (qemu-kvm-1.0.1), Copyright (c) 2003-2008 Fabrice Bellard
>>>>>>
>>>>>> This seems like a bug to me. If it is a micro version number, why is it
>>>>>> delimited with comma instead of dot? If it is not a micro version
>>>>>> number, can we threat it like it is?
>>>>>
>>>>> I agree, it smells very much like a QEMU/distro bug to me.
>>>>
>>>> It is an upstream bug:
>>>>
>>>> https://lists.gnu.org/archive/html/qemu-devel/2012-02/msg02527.html
>>>>
>>>> Distros should probably be backporting that particular patch, but
>>>> there's still the question of whether we should deal with it in libvirt
>>>> because it is upstream.
>>>
>>> Well it is a bug on only one branch of upstream, that was promptly
>>> fixed, so I still don't think we should complicate libvirt by dealing
>>> with it. It is trivial for QEMU maintainers to fix
>>>
>>>
>>> Daniel
>>> --
>> 
>> FWIW, the raw tarball from qemu.org still contains the bug. They
>> didn't reissue the tarball. First commit on the list here:
>> http://wiki.qemu.org/ChangeLog/1.0
>> 
>
> [CC'ing QEMU devel list]
>
> Maybe QEMU guys can reissue the tarball since Fedora (and probably other
> distros as well) is using this tarball when building a package?
> Or is it distro's business to backport the patch?

We released a qemu-1.0.1-1.tar.bz2 that contained the fixed VERSION
file.

Regards,

Anthony Liguori

>
> Michal

  reply	other threads:[~2012-09-26 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1348563490-15598-1-git-send-email-dmitry@daynix.com>
     [not found] ` <5061A83C.2070801@redhat.com>
     [not found]   ` <20120925125429.GI5408@redhat.com>
     [not found]     ` <5061E273.8010009@redhat.com>
     [not found]       ` <20120925170109.GC24588@redhat.com>
     [not found]         ` <CAFWqQMRCnf_7NLWWiuCjGXpwS+vBzp0gjKj_rAmC0Y_dEcUstQ@mail.gmail.com>
2012-09-26  8:09           ` [Qemu-devel] [libvirt] [PATCH 0/2] Fixed QEMU 1.0.1 support Michal Privoznik
2012-09-26 20:46             ` Anthony Liguori [this message]
2012-09-27  6:45               ` Michal Privoznik

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=87wqzgv7en.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=cardoe@gentoo.org \
    --cc=libvir-list@redhat.com \
    --cc=mprivozn@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yan@daynix.com \
    /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).