qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/10] Ui 20171011 patches
Date: Thu, 12 Oct 2017 10:00:01 +0100	[thread overview]
Message-ID: <CAFEAcA_Nxw4totmmuJK814SBy8=1vxpXKQpA3GNtafpHXSAAtg@mail.gmail.com> (raw)
In-Reply-To: <20171012082456.GB16125@redhat.com>

On 12 October 2017 at 09:24, Daniel P. Berrange <berrange@redhat.com> wrote:
> On Wed, Oct 11, 2017 at 05:45:04PM +0100, Peter Maydell wrote:
>> $ ./scripts/git-submodule.sh update ui/keycodemapdb dtc
>> Cloning into 'ui/keycodemapdb'...
>> fatal: unable to access
>> 'https://gitlab.com/keycodemap/keycodemapdb.git/': Problem with the
>> SSL CA cert (path? access rights?)
>> fatal: clone of 'https://gitlab.com/keycodemap/keycodemapdb.git' into
>> submodule path 'ui/keycodemapdb' failed
>
> I'm not sure what I can do about this one - if GIT can't checkout
> a normal git repo, this looks like a OS distro / setup bug on the
> build host.

Build system (which is a chroot) didn't have openssl or ca-certificates
packages installed. That hasn't been a problem so far because we
haven't used https:// for git previously.

I've updated the packages on the build system, but it would be nice
if we had a clearer error message when the problem is "we now
depend on some packages that we didn't previously and so you
should install them".

thanks
-- PMM

  reply	other threads:[~2017-10-12  9:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  8:35 [Qemu-devel] [PULL 00/10] Ui 20171011 patches Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 01/10] build: automatically handle GIT submodule checkout for dtc Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 02/10] docker: don't rely on submodules existing in the main checkout Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 03/10] ui: add keycodemapdb repository as a GIT submodule Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 04/10] ui: convert common input code to keycodemapdb Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 05/10] ui: convert key events to QKeyCodes immediately Gerd Hoffmann
2017-10-11  8:36 ` [Qemu-devel] [PULL 06/10] ui: don't export qemu_input_event_new_key Gerd Hoffmann
2017-10-11  8:36 ` [Qemu-devel] [PULL 07/10] tools: add qemu-keymap Gerd Hoffmann
2017-10-11  8:36 ` [Qemu-devel] [PULL 08/10] Add pc-bios/keymaps/Makefile Gerd Hoffmann
2017-10-11  8:36 ` [Qemu-devel] [PULL 10/10] ui/gtk: Fix deprecation of vte_terminal_copy_clipboard Gerd Hoffmann
2017-10-11 14:37 ` [Qemu-devel] [PULL 00/10] Ui 20171011 patches Peter Maydell
2017-10-11 14:49   ` Kamil Rytarowski
2017-10-11 15:49   ` Daniel P. Berrange
2017-10-11 16:45     ` Peter Maydell
2017-10-12  8:24       ` Daniel P. Berrange
2017-10-12  9:00         ` Peter Maydell [this message]
2017-10-12  9:30         ` Gerd Hoffmann
2017-10-12  9:33           ` Daniel P. Berrange
2017-10-12 10:04             ` Gerd Hoffmann
2017-10-12 10:07               ` Daniel P. Berrange
2017-10-12 10:11                 ` Peter Maydell
2017-10-12 10:13                 ` Gerd Hoffmann
2017-10-12 10:14                   ` Daniel P. Berrange
2017-10-12  9:51           ` Peter Maydell
2017-10-12 10:01   ` Gerd Hoffmann
2017-10-13  8:15   ` Gerd Hoffmann

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='CAFEAcA_Nxw4totmmuJK814SBy8=1vxpXKQpA3GNtafpHXSAAtg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=berrange@redhat.com \
    --cc=kraxel@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 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).