[yocto] Problem using Subversion in Pyro

Alan Levy alan.levy at plextek.com
Thu May 18 06:32:22 PDT 2017


I want to assign SRCREV to PV, which is perfectly legitimate, so that I can capture the SVN revision number used to build the code. Here's a simple recipe which exhibits the problem:

DESCRIPTION = "Recipe to test SVN"
PACKAGE_ARCH = "${MACHINE_ARCH}"
LICENSE = "CLOSED"
PV = "${SRCPV}"
SRCREV = "${AUTOREV}"
SRC_URI = "svn://server/path;module=my_module"

If you comment out the line referring to SRCPV all is well, if you include it bitbake blows up, even if I just perform cleansstate.

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: Alexander Kanavin [mailto:alexander.kanavin at linux.intel.com] 
Sent: 18 May 2017 14:14
To: Alan Levy; yocto at yoctoproject.org
Subject: Re: [yocto] Problem using Subversion in Pyro

On 05/18/2017 04:04 PM, Alan Levy wrote:
> It does get built, and it apparently does get used to do the actual 
> fetching, just not for miscellaneous functions such as populating 
> SRCREV which rely on the svn executable being on the PATH. This 
> appears to be deliberate since there is a FETCHCMD_svn variable in 
> bitbake.conf. The simplest way for me to force an svn executable onto 
> PATH was to add it to HOSTTOOLS but that may not be what is really 
> intended.

SRCREV is supposed to be hardcoded in the recipe. What is the reason you need to use svn to set it? Can you show how it's specifically done in your recipe?


Alex



More information about the yocto mailing list