Problems with svn + build system?

Michael 'Mickey' Lauer mickey at
Tue Oct 16 11:52:16 CEST 2007

Sudharshan S wrote:

> On Mon, 2007-10-15 at 18:36 +0200, Michael 'Mickey' Lauer wrote:
>> Do you set PV = "0.1.0+r${SRCREV}" ? Otherwise your new revision might
>> not be picked up by the svn fetcher using autorevs.
> Ok, so I modified my bitbake recipes by adding r${SRCREV}, I tried
> adding "+svn${SRCDATE}" and it did seem to checkout correctly, but on
> subsequent builds, got the same conf/checksums.ini thingy. Maybe it will
> work tomorrow when the date changes, heh.
> So anyway, one thing bothers me. The ${SRCREV} is always 1, whereas the
> code in the svn revision currently is now around 30. Just in case, I am
> pasting my bitbake recipe and attaching the build log. So maybe the
> problem lies with the fact that ${SRCREV} is still stuck at revision1
> and hence the initial revision is getting built?

Sorry, I forgot to add that once you use SRCREV to always check out
the latest version, you will have to add two more things:

a) SRCREV_pn-python-gsmd = "${AUTOREV}"


b) a small fix for bitbake's autorev behaviour:

Index: lib/bb/fetch/
--- lib/bb/fetch/ (revision 970)
+++ lib/bb/fetch/ (working copy)
@@ -77,6 +77,9 @@
                 if rev and "get_srcrev" in rev:
                     ud.revision = self.latest_revision(url, ud, d)
            = ""
+                elif rev and "AUTOREV" in rev:
+                    ud.revision = self.latest_revision(url, ud, d)
+           = ""
                 elif rev:
                     ud.revision = rev
            = "" 

To improve quality and stability, we no longer use floating SRCREV's
in OpenEmbedded .dev, that's why you have to do a) to enable it
explicitly for a package.

Hope that helps.
- Michael Lauer <mickey at>         
Software for the worlds' first truly open Free Software mobile phone

More information about the openmoko-devel mailing list