Re: shr-image failure

[Tom Rini <tom_rini@mentor.com>]

On 02/28/2011 01:04 PM, Martin Jansa wrote:
> On Mon, Feb 28, 2011 at 09:55:32AM -0700, Tom Rini wrote:
>> On 02/28/2011 09:13 AM, Martin Jansa wrote:
>>> On Mon, Feb 28, 2011 at 05:06:59PM +0100, Martin Jansa wrote:
>>>> On Mon, Feb 28, 2011 at 08:36:10AM -0700, Tom Rini wrote:
>>>>> Hey all,
>>>>>
>>>>> Trying to build shr/shr-image/nokia900 fails with the following:
>>>>> http://pastebin.com/Z13aYd2Z which seems odd in that we're building:
>>>>>
>>>>> NOTE: Running task 5802 of 10948 (ID: 2141,
>>>>> /var/hudson/workspace/sb_openembedded_autobuilder/BBPKGS/shr-image/DISTRO/shr/MACHINE/nokia900/label/sb-u804/recipes/efl1/elementary_svn.bb,
>>>>> do_setscene)
>>>>> NOTE: package elementary-2_0.7.0+svnr56372-r11: task do_setscene: Started
>>>>>
>>>>> And it's already past do_populate_sysroot before this starts.  I do see
>>>>> some svn complaining (and not doing something...) earlier on in the
>>>>> do_configure here.
>>>>
>>>> This looks like related to
>>>> http://www.mail-archive.com/bitbake-dev@lists.berlios.de/msg00880.html
>>>>
>>>> which was resolved later with scmdata=keep param
>>>> http://git.openembedded.org/cgit.cgi/bitbake/commit/?id=05cbc1d1a01c667c77688f36fbc5b61c5f452a3a
>>>>
>>>> but that patch didn't make it to bitbake-1.10.2 release, but neither did
>>>> patch causing this in master/1.12
>>>> http://git.openembedded.org/cgit.cgi/bitbake/commit/?id=f264cb6d43472525ad787b0887764ea696ec52ba
>>>>
>>>> Can you try that svnversion call in your checkout to get thath svn
>>>> error? It seems to be working here fine.
>>>
>>> $ mkdir test&&   cd test
>>> $ tar xzvf ../downloads/elementary_svn.enlightenment.org_.svn.e.trunk_56372_.tar.gz
>>> $ cd elementary
>>> $ (svnversion . | grep -v export || echo 0) | awk -F : '{printf("%s\n",$1);}' | tr -d ':MSP\n'
>>> 56372$
>>
>> The error is that the svn version is too old for the checkout.  Is there
>> a way we can figure this out without calling svn?
>
> I guess you have subversion<  1.6
> and 1.6 changed the format, so if efl repo was upgraded then it needs
> newer svn client
>
> http://subversion.apache.org/docs/release-notes/1.6.html
>
> Maybe it's time to force subversion-native as there were issues before
> ie with -trust-server-cert.

Stupid question.  Why aren't we just using ${SRCREV} ?  Or is this 
really bitbake calling out svn to do something?

-- 
Tom Rini
Mentor Graphics Corporation