diff options
author | Nicolas Dechesne <nicolas.dechesne@linaro.org> | 2013-10-31 17:36:25 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-11-01 17:59:30 +0000 |
commit | de7e6efb80e3155e74f65fbb4f1e9058ca71d1f9 (patch) | |
tree | e533ec04a60b626b653e40610ea7c259a250d919 /bitbake/lib/toaster | |
parent | ba84fbe8319b11bdc207e0d43fa303f7bf01416f (diff) | |
download | poky-de7e6efb80e3155e74f65fbb4f1e9058ca71d1f9.tar.gz |
bitbake: fetch2/svn.py: use log instead of info to retrieve revision
We have faced a corner case situation where the 'last changed
revision' returned from svn info is wrong. It happens when the last
revision is a directory move. e.g. if we assume that the svn
repository at revA has root/x/y/z/foo/bar and it is moved to
root/a/b/c/foo/bar in revB, then svn info 'last change revision' will
return revA. As such when using AUTOREV, we are going to attempt to
retrieve root/a/b/c/foo/bar (as per SRC_URI) but at revA when it did
not exist.
So this patch changes how we retrieve the latest revision and uses
'svn log --limit 1' which gives correct result in all tested cases.
(Bitbake rev: 17d8ef0b813a05c231e3dbe6e8bc82a4a9b1d2f8)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/toaster')
0 files changed, 0 insertions, 0 deletions