[bitbake-devel] Problem using Subversion in Pyro

[Alan Levy]

Richard,

I can see that you don't want to force the host system to support subversion and I concur that the resulting error message is unhelpful.

However under Morty this worked just fine so Pyro breaks existing recipes in a way that's very hard to understand, even if the solution is easy once you know how.  I would suggest that as well as providing a helpful error message the documentation should also explain what's going on and how to fix it.

Regards

Alan

ALAN LEVY, Lead Consultant, Embedded Systems

Plextek Consulting, The Plextek Building, London Road, Great Chesterford, Saffron Walden, CB10 1NY, UK
T: +44 (0) 1799 533200    E: alan.levy at plextek.com  W: www.plextek.com




-----Original Message-----
From: Richard Purdie [mailto:richard.purdie at linuxfoundation.org] 
Sent: 19 May 2017 10:49
To: Alan Levy; bitbake-devel at lists.openembedded.org
Subject: Re: [bitbake-devel] Problem using Subversion in Pyro

On Thu, 2017-05-18 at 14:22 +0000, Alan Levy wrote:
> --limit 1 --no-auth-cache ! http://server/path/my_module/ failed with 
> exit code 127, output:
> /usr/bin/env: 'svn': No such file or directory
>  
> If I comment out the line containing SRCPV, all is well. Digging into 
> the code it appears that svn is missing from ${HOSTTOOLS} in 
> bitbake.conf.

I can understand how we end up in this situation.

In general, subversion-native is built before the recipe's do_fetch so things work.

When you use SRCREV = "${AUTOREV}", it needs subversion at parse time and its obviously not built it. You therefore need to use the host version. You can enable that with:

HOSTTOOLS_append = " svn"

in your config. I'm not sure I see any way around that. We don't really want to require subversion in general, its only needed if you're using autorev svn recipes.

Obviously we could do with improving the failure messages though...

Cheers,

Richard