From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Michael Roth <michael.roth@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: how to build qemu 8.1 - keycodemapdb?
Date: Wed, 26 Jul 2023 10:18:37 +0100 [thread overview]
Message-ID: <ZMDk7V9qfzab94Hg@redhat.com> (raw)
In-Reply-To: <0b562fb1-5fc0-38d8-f0d0-65f52f726bc5@tls.msk.ru>
On Wed, Jul 26, 2023 at 12:05:41PM +0300, Michael Tokarev wrote:
> 26.07.2023 11:50, Daniel P. Berrangé wrote:
> ..
> > > make-release.sh apparently does the right thing. But the published
> > > tarball does not include the 3 required sub-projects anyway.
> > >
> > > Is it about how the release is made? What is used to make the
> > > actual release tarball, is it not make-release.sh?
> >
> > make-release is what I expect to be used for making release
> > tarballs.
>
> When I run ./scripts/make-release 8.1.0-rc1 , the resulting tarball
> includes the necessary submodules in subprojects/.
>
> It is more: it includes 2 copies of berkeley-softfloat & berkeley-testfloat,
> one in subprojects/ and one in roms/edk2/ArmPkg/Library/ArmSoftFloatLib/ .
>
> But the tarballs published on qemu.org does not include these.
>
> So I conclude the tarballs were not created using make-release.sh.
I filed an issue for this and marked it as a release blocker.
https://gitlab.com/qemu-project/qemu/-/issues/1791
rc0 was broken in the same way too.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-07-26 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 6:20 how to build qemu 8.1 - keycodemapdb? Michael Tokarev
2023-07-26 6:41 ` Michael Tokarev
2023-07-26 7:15 ` Michael Tokarev
2023-07-26 8:50 ` Daniel P. Berrangé
2023-07-26 9:05 ` Michael Tokarev
2023-07-26 9:18 ` Daniel P. Berrangé [this message]
2023-07-26 23:47 ` Michael Roth
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=ZMDk7V9qfzab94Hg@redhat.com \
--to=berrange@redhat.com \
--cc=michael.roth@amd.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.