From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Roman I Khimov : bitbake.conf: trust server certificate when doing svn over https
Date: Thu, 5 Aug 2010 11:10:47 +0200 [thread overview]
Message-ID: <20100805091047.GF29578@jama> (raw)
In-Reply-To: <AANLkTimfaAw_wmNddavmknv4O5haMqLuXDa8v7ECYZyF@mail.gmail.com>
On Thu, Aug 05, 2010 at 10:55:05AM +0200, Frans Meulenbroeks wrote:
> 2010/8/5 Roman I Khimov <khimov@altell.ru>:
> > В сообщении от Четверг 05 августа 2010 12:24:40 автор Martin Jansa написал:
>
> >
> >> I don't know if it's worth it to force builders to upgrade subversion or
> >> add their FETCHCOMMAND_svn UPDATECOMMAND_svn to local.conf.
> >
> > IMO we should not break support for major stable (or LTS) distros, so my patch
> > is broken.
> >
> I agree that we should not break support for major distros. but
> without your patch some of the recipes cannot be build easily.
> The solution of Martin seems a good inbetween.
>
> Frans
I've pushed my patch removing --trust-server-cert and adding --accept,
but --accept is only for >=1.5
If we want to support svn older than that ie:
svn, version 1.1.1 (r11581) in RHEL4
maybe we should add subversion-native and drop ASSUME_PROVIDED?
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-08-05 9:10 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 ` [oe-commits] Roman I Khimov : bitbake.conf: trust server certificate when doing svn over https Martin Jansa
2010-08-05 7:38 ` 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 [this message]
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=20100805091047.GF29578@jama \
--to=martin.jansa@gmail.com \
--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.