diff options
| author | Nicolas Dechesne <nicolas.dechesne@linaro.org> | 2013-10-31 17:36:25 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-12-03 17:51:31 +0000 |
| commit | 1c8c9f1e532ad29731feb4e63a3f74934105e69c (patch) | |
| tree | 2bfdeb157deff5c64ab243432aa22682b46546d9 /scripts | |
| parent | 2238d4a63f55721aad4557f862bd6c86a3e2c904 (diff) | |
| download | poky-1c8c9f1e532ad29731feb4e63a3f74934105e69c.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 master rev: 17d8ef0b813a05c231e3dbe6e8bc82a4a9b1d2f8)
(Bitbake rev: d14e532f07f31b99c55bec9d87470eb54251c8db)
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions