From: "Daniel P. Berrangé" <berrange@redhat.com>
To: CLEMENT MATHIEU--DRIF <clement.mathieu--drif@eviden.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"alex.bennee@linaro.org" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [QUESTION/ISSUE] edk2 missing dependency
Date: Mon, 4 Nov 2024 14:43:39 +0000 [thread overview]
Message-ID: <Zyjdm6TC7jfa-wlR@redhat.com> (raw)
In-Reply-To: <d9aaedd4-80a7-40d1-b5ab-c75afda794e3@eviden.com>
On Mon, Nov 04, 2024 at 02:32:53PM +0000, CLEMENT MATHIEU--DRIF wrote:
> Hi everyone,
>
> It seems that https://github.com/Zeex/subhook (EDK2 submodule) is not
> longer available on github (which makes recursive pull of submodules
> fail for a lot of people).
> Do you think we should do something on our side?
Once EDK2 fix the problem, then QEMU can update its EDK2 submodule to
get the fix.
It should not be a major problem meanwhile because there's no compelling
reason for QEMU contributors to do a recursive checkout of all submodules.
It'll only affect those with EDK2 checked out, which is not a common thing
to need to do to start with, since we provide rebuilt EDK2.
Our make-release script checks out EDK2 submodule, but does not do this
recursively - it only pulls a couple of hand-picked sub-submodules, not
including Zeex/subhook.
If you know of any other scenarios that are a problem please say.
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:[~2024-11-04 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 14:32 [QUESTION/ISSUE] edk2 missing dependency CLEMENT MATHIEU--DRIF
2024-11-04 14:43 ` Daniel P. Berrangé [this message]
2024-11-05 16:48 ` Peter Maydell
2024-11-08 16:56 ` 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=Zyjdm6TC7jfa-wlR@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=clement.mathieu--drif@eviden.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--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).