[oe] buildindex is always 0, using BB_GIT_CLONE_FOR_SRCREV = "1"
Radoslav Kolev
radoslav at kolev.info
Mon May 2 10:18:08 UTC 2011
Hi,
I'm trying to make a recipe which gets the newest revision from a git
repository.
Also to get upgradable packages on different build machines I have the
BB_GIT_CLONE_FOR_SRCREV = "1"
option set in my local.conf.
In the recipe I have
SRCREV = "${AUTOREV}"
PV = "0.4+gitr-${SRCPV}"
but I always get a PV of the form
0.4+gitr-0+f5bb7404c351a08cf405fbe8d667b446ae8e0ef5-r10 where the
buildindex stays at zero, even though new revisions are correctly
checked out from the git repository.
I added some print statements to bitbake/lib/bb/fetch/__init__.py and
git.py and it seems to work fine until some point.
The _sortable_buildindex in git.py returns the correct incrementing
value, also the first invocation of get_srcrev() returns a correct
value with incrementing buildindex like
168+f5bb7404c351a08cf405fbe8d667b446ae8e0ef5l. But then something
happens and in all subsequent invocations by bitbakeit get_srcrev()
always returns 0+f5bb7404c351a08cf405fbe8d667b446ae8e0ef5l.
Any help or ideas how to further debug the issue are greatly
appreciated. I'm using bitbake 1.10.
Best regards,
Radoslav Kolev
More information about the Openembedded-devel
mailing list