From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: QEMU Developers <qemu-devel@nongnu.org>,
Thomas Huth <thuth@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Stefan Weil <sw@weilnetz.de>
Subject: [Qemu-devel] No archives to download from www.qemu.org/download/
Date: Thu, 18 Jul 2019 08:25:32 +0200 [thread overview]
Message-ID: <cb727b5d-683f-115d-f3c0-06f5a6761aea@redhat.com> (raw)
When building from the GitHub generated archive
(https://github.com/qemu/qemu/archive/v4.1.0-rc0.tar.gz)
we get:
---
$ ./configure
ERROR: missing file /tmp/qemu-4.1.0-rc0/ui/keycodemapdb/README
This is not a GIT checkout but module content appears to
be missing. Do not use 'git archive' or GitHub download links
to acquire QEMU source archives. Non-GIT builds are only
supported with source archives linked from:
https://www.qemu.org/download/
Developers working with GIT can use scripts/archive-source.sh
if they need to create valid source archives.
---
Now there are no archive to download at this url...
However from the last mail from Michael Roth, we use:
http://download.qemu-project.org/
Which contains all archives.
Should we update the url display by ./configure?
Or sync the other website?
Regards,
Phil.
next reply other threads:[~2019-07-18 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 6:25 Philippe Mathieu-Daudé [this message]
2019-07-18 7:10 ` [Qemu-devel] No archives to download from www.qemu.org/download/ Thomas Huth
2019-07-18 8:58 ` Philippe Mathieu-Daudé
[not found] ` <CAL1e-=iLLQfAdfFrKpAT9k48X0sEMevBXFWAmny7PRPwtBMiEQ@mail.gmail.com>
2019-07-18 11:29 ` Thomas Huth
2019-07-18 11:43 ` Daniel P. Berrangé
2019-07-18 11:53 ` Thomas Huth
2019-07-18 12:20 ` Aleksandar Markovic
2019-07-18 11:49 ` Stefan Weil
2019-07-18 13:14 ` Peter Maydell
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=cb727b5d-683f-115d-f3c0-06f5a6761aea@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=thuth@redhat.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).