linux/poky.git/bitbake/lib, branch dylan

bitbake: hob: disable layer drag and drop outside the containing widget

2014-04-04T14:06:57+00:00

[YOCTO #6008] (Bitbake rev: 0f7b6a03c64292983d2cc715e5e5badb1cdc5cae) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie

bitbake: fetch2: Don't allow '/' in user:pass, fix branch containing '@'

2014-02-17T14:44:37+00:00

* currently decode_url regexp parses branch=@foo as username so it ends like this: - ('git', '', 'foo', 'git.openembedded.org/bitbake;branch=', '', {}) + ('git', 'git.openembedded.org', '/bitbake', '', '', {'branch': '@foo'}) * http://hg.python.org/cpython/file/2.7/Lib/urlparse.py also assumes that there is at least one '/' as separator between netloc and path, params, so it looks reasonable to prevent including '/' in username (Bitbake rev: 66d01338ab1095775b854ad7509f4d2631c6e6ed) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

bitbake: bitbake: lib/bb/cache.py: Change debugging note to a debug message

2014-02-17T14:44:37+00:00

Some apparently debugging was left in in a previous commit. This caused bitbake to return a list of bbappends when things changed from the cache. Make this a proper debug message. (Bitbake master rev: 1965e5cbdfede18d7b7cb0218e0a5147c3f1c884) (Bitbake rev: 586adebdafdd4d11e5a277f72206875ae8828864) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

bitbake: hob/hoblistmodel: check if vals of packages/recipes names are not None

2014-01-08T17:41:21+00:00

[YOCTO #5053] (Corresponds to BitBake master rev: ba9fe77e37be31e8246431578902e871dd94515e) (Bitbake rev: d2bfdb12d64e8dfa6c4518c159065d39456667bb) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie

bitbake: perforce: Fix path subdirectory issues

2013-12-03T17:51:35+00:00

With a SRC_URI = " \ p4://depot/folder/...;module=localfolder/localsubfolder;changeslist=${P4CHANGELIST} \ " the subfolders of //depot/folder/... get renamed when mapped to the local folder structure. They lose the first 3 letters. This patch fixes that. Issue reported by and patch sent from katutxakurra@gmail.com [YOCTO #5380] (Bitbake master rev: 40e06dc459d9c0b5d42d65b2d2c846196fd36b1f) (Bitbake rev: a779ae4d4ef47fc36b98ec5753289af7755fcd03) Signed-off-by: Richard Purdie

bitbake: fetch/hg: Improve user/password handling

2013-12-03T17:51:35+00:00

Trying to use a server with username and password authentication within the URL of the SRC_URI variable doesn't appear to work. This patch adds the missing parts to the hg fetcher to make this work properly. (Bitbake master rev: dc3d6d73e44802c203b3f7247f6f212acc2f69bf) (Bitbake rev: f1e82236c2d30897bb863fb8948dd48614fc262a) Signed-off-by: Richard Purdie

bitbake: fetch2/svn.py: use log instead of info to retrieve revision

2013-12-03T17:51:35+00:00

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: 91e3735c2e73094b49f99b01008bb5bf47dacf04) Signed-off-by: Nicolas Dechesne Signed-off-by: Richard Purdie

bitbake: methodpool: Retire it, remove global method scope

2013-09-11T16:58:33+00:00

Having a global method scope confuses users and with the introduction of parallel parsing, its not even possible to correctly detect conflicting functions. Rather than try and fix that, its simpler to retire the global method scope and restrict functions to those locations they're defined within. This is more what users actually expect too. If we remove the global function scope, the need for methodpool is reduced to the point we may as well retire it. There is some small loss of caching of parsed functions but timing measurements so the impact to be neglibile in the overall parsing time. (Bitbake rev: bbb4fa427739912ff3b87379bf629066f6662458) Signed-off-by: Richard Purdie Tested-by: Denys Dmytriyenko

bitbake: bitbake: data_smart: Ensure variable flags are accounted for in config data hash

2013-07-29T12:28:24+00:00

Currently if the flags set against a variable in the base data store change, it doesn't automatically trigger a reparse when it really should. For example with the blacklist class setting: PNBLACKLIST[qemu] = "bar" PNBLACKLIST[bash] = "foo" will not trigger a reparse if only one entry is changed and a blacklisted recipe can still be built. I did consider using BB_SIGNATURE_EXCLUDE_FLAGS in here however it doesn't make sense, we want to trigger a reparse when any of the flags change too (which is different to the sstate signatures which we wouldn't want to change in those cases). [YOCTO #4627] (Bitbake master rev: ed74ea50043f6feb698c891e571feda2b9f8513d) (Bitbake rev: 9313ff77f39abf776556cd7b0edb3c08854d68ef) Signed-off-by: Richard Purdie

bitbake: hob: save the base image name for the customized images

2013-07-29T12:28:24+00:00

Building an image, after customizing it, was failing because the base image was not saved. [YOCTO #4751] (Bitbake rev: c109e1fb18c5541aa5bf500c4622f4f7b677db08) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie