From: Stefan sat <stefansat@telenet.be>
To: openembedded-core@lists.openembedded.org
Subject: Re: Subversion does not support http protocol anymore
Date: Sat, 26 Jul 2014 00:55:13 +0200 [thread overview]
Message-ID: <53D2E051.2000503@telenet.be> (raw)
In-Reply-To: <53D2BE03.5060805@linux.intel.com>
Op 25-07-14 om 22:28 schreef Saul Wold:
> On 07/25/2014 11:30 AM, Stefan sat wrote:
>> Hello since a certain time native subversion build of
>> openembedded-oe-core does not support http protocol anymore.
>>
>> I found out that it is just the missing neon-config script file.
>>
>> Whitout this the subversion_1.7.10.bb builds whitout neon support.
>>
>> It was just ok by removing binconfig-disabled by
>> meta/recipes-support/neon/neon_0.30.0.bb
>>
>> Then rebuild neon and subversion.
>>
>> Included git patch file
>>
>
> Richard recently updated subversion to 1.8.9, which uses serf instead
> of neon. If this patch is for Daisy, please update it as mentioned here.
>
> Can you please add a Signed-off-by: and use git format-patch, also
> look at this wiki:
>
> http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
>
> Please format the commit message correctly and then re-submit with a
> [daisy] tag if appropriate.
>
> Thanks
> Sau!
>
>> Thank's
>>
>>
>
I just saw that the used openembedded-core in openpli-4.0 is not up to
date with the current master, and so still has the head rev where
subversion_1.7.10 was used . But by neon the binconfig-disabled was
inherited. No with 1.8.9 neon is not needed any more
sorry, disregard the patch
Thanks anyway.
prev parent reply other threads:[~2014-07-25 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 18:30 Subversion does not support http protocol anymore Stefan sat
2014-07-25 20:13 ` Martin Jansa
2014-07-25 20:28 ` Saul Wold
2014-07-25 22:55 ` Stefan sat [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=53D2E051.2000503@telenet.be \
--to=stefansat@telenet.be \
--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