From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-commits@openembedded.org
Subject: Re: [oe-commits] Roman I Khimov : bitbake.conf: trust server certificate when doing svn over https
Date: Thu, 5 Aug 2010 09:12:01 +0200 [thread overview]
Message-ID: <20100805071201.GB29578@jama> (raw)
In-Reply-To: <E1OguCD-00023v-03@melo.openembedded.org>
On Thu, Aug 05, 2010 at 06:44:53AM +0000, git version control wrote:
> Module: openembedded.git
> Branch: org.openembedded.dev
> Commit: 64b73f5d3bc4516de7deaf2c3647a96a1d5285e1
> URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=64b73f5d3bc4516de7deaf2c3647a96a1d5285e1
>
> Author: Roman I Khimov <khimov@altell.ru>
> Date: Thu Aug 5 10:16:54 2010 +0400
>
> bitbake.conf: trust server certificate when doing svn over https
>
> Fixes fetching from https:// svn repos with self-signed certs.
Maybe we should add also
--accept theirs-full (just in case)
--force (to force overwrite of existing files)
ie
matchbox-panel-2-icon-themes_0.0.1.bb
matchbox-panel-2_svn.bb
are checkouting/updating tiwo different SRCREVs and every few builds you
end up removing svn checkout from downloads dir, just because it
refuses to upgrade to newer revision (applets dir already exists there).
Any objections (someone intentionaly keeping dirty checkouts in his
DL_DIR)?
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next parent reply other threads:[~2010-08-05 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1OguCD-00023v-03@melo.openembedded.org>
2010-08-05 7:12 ` Martin Jansa [this message]
2010-08-05 7:38 ` [oe-commits] Roman I Khimov : bitbake.conf: trust server certificate when doing svn over https Roman I Khimov
2010-08-05 8:24 ` Martin Jansa
2010-08-05 8:41 ` Roman I Khimov
2010-08-05 8:55 ` Frans Meulenbroeks
2010-08-05 9:04 ` Roman I Khimov
2010-08-05 9:10 ` Martin Jansa
2010-08-05 14:54 ` Tom Rini
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=20100805071201.GB29578@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@openembedded.org \
--cc=openembedded-devel@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 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.