The upstream version get from checkpkg for package using git looks like: <latest_versionstring>+gitAUTOINC+<latest_revision_master> which seems not right, because <latest_versionstring> is the release tag, but the follwoing hash valure points ot the master. Take babeltrace as axample, it's confusing if we see: http://recipes.yoctoproject.org/ The upstream version listed is: 1.2.4+gitAUTOINC+3730724040 but if we compile it, we get: tmp/work/core2-64-poky-linux/babeltrace/1.2.4+gitAUTOINC+90395824ef-r0/ Checked the git repo of babeltrace, the commit for tag v1.2.4 is: $ git log -1 --oneline v1.2.4 9039582 Version 1.2.4 I think it should be changed to: <latest_versionstring>+gitAUTOINC+<sha1_for_latest_versionstring> Maybe we should add a method like the _get_tag_sha1(self, new_tag) in http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/tree/gitrecipe.py for the bitbake git fetcher.
Count me in, it would be great to have a clear picture of "current version tag and respective revision" vs. "latest version tag and respective revision". In the future it could be even used for semi-automatic recipe version updates.
At, http://lists.openembedded.org/pipermail/bitbake-devel/2015-July/006034.html
Merged at, http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb?id=bd5167d154ac04dbecbda3a157ae8ef6304e0b4e