qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"seabios@seabios.org" <seabios@seabios.org>,
	Bruce Rogers <brogers@suse.com>
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 2.0.0-rc0 is now available
Date: Mon, 17 Mar 2014 19:30:20 +0100	[thread overview]
Message-ID: <53273F3C.6040500@suse.de> (raw)
In-Reply-To: <1394767188-7074-1-git-send-email-aliguori@amazon.com>

Hi,

Am 14.03.2014 04:19, schrieb Anthony Liguori:
> On behalf of the QEMU Team, I'd like to announce the availability of the
> first release candidate for the QEMU 2.0 release.  This release is meant
> for testing purposes and should not be used in a production environment.
> 
> http://wiki.qemu.org/download/qemu-2.0.0-rc0.tar.bz2

I've run into an issue with the SeaBIOS submodule included in the QEMU
tarball: The SeaBIOS scripts/buildversion.sh script looks for a .git
directory or file and, if absent, goes on to look for a .version file,
neither of which the QEMU tarball ships. That means it will fall back to
"?" as version, whereas the binary blob contributed by Gerd displays
"rel-1.7.4-0-g96917a8".

Should our tarball workflow include generating a roms/seabios/.version
file based on git-describe in that directory to fix this mismatch?

Thanks,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2014-03-17 18:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14  3:19 [Qemu-devel] [ANNOUNCE] QEMU 2.0.0-rc0 is now available Anthony Liguori
2014-03-14 14:11 ` Riku Voipio
2014-03-17 18:30 ` Andreas Färber [this message]
2014-03-18  7:06   ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2014-03-14  3:20 Anthony Liguori

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=53273F3C.6040500@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=brogers@suse.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).