Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: FETCHCMD_svn add --non-interactive --trust-server-cert
Date: Tue, 04 Sep 2012 13:38:30 +0100	[thread overview]
Message-ID: <1346762310.30964.38.camel@ted> (raw)
In-Reply-To: <1346749751-25699-1-git-send-email-Martin.Jansa@gmail.com>

On Tue, 2012-09-04 at 11:09 +0200, Martin Jansa wrote:
> * now with subversion-native we know those 2 options are supported
> * with https protocol used for SVN checkouts we cannot confirm certificate and do_fetch fails
>   Error validating server certificate for 'https://foo:443':
>   - The certificate is not issued by a trusted authority. Use the
>     fingerprint to validate the certificate manually!
>     Certificate information:
>     ...
>     (R)eject, accept (t)emporarily or accept (p)ermanently? svn: E175002: Unable to connect to a repository at URL 'https://foo/trunk'
>     svn: E175002: OPTIONS of 'https://foo/trunk': Server certificate verification failed: issuer is not trusted (https://foo)
>     ERROR: Function failed: Fetcher failure for URL: 'svn://foo;protocol=https;module=trunk'. Unable to fetch URL from any source.
> 
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  meta/conf/bitbake.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Merged to master, thanks.

Richard




      reply	other threads:[~2012-09-04 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04  9:09 [PATCH] bitbake.conf: FETCHCMD_svn add --non-interactive --trust-server-cert Martin Jansa
2012-09-04 12:38 ` Richard Purdie [this message]

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=1346762310.30964.38.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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