linux/poky.git/bitbake, branch dora-10.0.1

bitbake: bitbake: runqueue: Fix hole in setsceneverify skipped task logic

2013-12-11T14:16:04+00:00

We have do_bundle_initramfs which is a task inserted after compile and before build. It is not covered by sstate. If we run a build with a valid sstate cache present, the setsceneverify function realises it will rerun the do_compile step (due to the bundle_initramfs task) and hence marks do_populate_sysroot to rerun. do_install, a dependency of do_populate_sysroot is left as marked as covered by sstate. What we need to do is traverse the dependency tree for any setsceneverify invalided task and ensure any dependencies are also invalidated. We can stop at any point we reach another setscene task though. This means the do_populate_sysroot task has the data from do_install available and doesn't crash. (Bitbake master rev: f21910157d873c030b149c4cdc5b57c5062ab5a6) (Bitbake rev: 1484905373ad717cedcaef37a0addde034ebdc60) Signed-off-by: Richard Purdie Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: bitbake: build.py: add single-quotes around already-expanded directory name

2013-12-11T14:16:04+00:00

If the computed name of a directory contains an undefined variable reference, bitbake dutifully creates a directory with a name that has ${...} in it. However, the actual task script created then tries to cd to that directory, and the cd command fails, because no such directory exists -- because the shell has helpfully removed the ${...} which did not match any actual variables. Since we want the name to be used exactly-as-is, add single quotes around the name so this doesn't cause strange failures running tasks, which allows us to progress past such failures and get to a point where they can be diagnosed. (Bitbake master rev: 2809c2e6f2f35f9b08058950be896947ab5a0284) (Bitbake rev: 3059ee335b7ae1bf77d6fd02e66ea5ba37d96c7b) Signed-off-by: Peter Seebach Signed-off-by: Richard Purdie Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: bitbake: fetch2: Fix handling of SCM mirrors in MIRRORS

2013-12-11T14:16:03+00:00

If an SCM mirror is in PREMIRRORS, the tarball is downloaded and then found by the "upstream" check and handled correctly. If an SCM mirror is in MIRRORS, the tarball is downloaded but not used since there is no "upstream" run after MIRRORS completes. It therefore sits there useless and unused. This code change forces the upstream to run after a mirror tarball is found and fixes the usage of SCM mirrors in MIRRORS. (Bitbake master rev: a66ee0994645aa5658b2f5ea134ed17d89f8751a) (Bitbake rev: 98d2cd8576a8d035e2b073cd54bb737a3c22bc4d) Signed-off-by: Richard Purdie Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: bitbake: monitordisk: lower inode check warning to note

2013-12-11T14:16:03+00:00

Filesystems like btrfs and reiserfs sets the inode count to 0, since they don't have an inode concept. This is expected, and having a warning show up every time you run bitbake can cause undue concern. (Bitbake master rev: f3ac2d3678f48c68a250a0a20c08cf8687322d38) (Bitbake rev: 04e2a1e4e3b3580660cdd3926caadeb0a9fbd4d3) Signed-off-by: Olof Johansson Signed-off-by: Richard Purdie Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: bitbake: cooker/command: Add error state for the server and use for pre_serve errors

2013-12-11T14:16:03+00:00

Currently if errors occur when starting the PR service, there is a race that occurs since the UI runs various commands including starting builds before processing the CookerExit(). By adding the error state and refusing to run async commands in this mode, builds are prevented from starting and the UI reaches the exit code with the system shutting down cleanly. (Bitbake master rev: 42fa34142ea685f91115a551e74416ca28ef1c91) (Bitbake rev: bc2e0796c1846d1567db6343b24b85fd7dba9163) Signed-off-by: Richard Purdie Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: perforce: Fix path subdirectory issues

2013-12-03T17:51:31+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: df0f92cdc925fe7f3bb2e6afe76cf10b0656ead6) Signed-off-by: Richard Purdie

bitbake: fetch/hg: Improve user/password handling

2013-12-03T17:51:31+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: 76b50d0d72c4e2b03fc53fade255e87c1922e88d) Signed-off-by: Richard Purdie

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

2013-12-03T17:51:31+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: d14e532f07f31b99c55bec9d87470eb54251c8db) Signed-off-by: Nicolas Dechesne Signed-off-by: Richard Purdie

bitbake: hob: change tooltip for live images

2013-10-07T15:25:02+00:00

This change is needed to inform the user that selecting live type means that the system will build a hddimg and iso image. (Bitbake rev: 5051f59976de4e099bb434aeea414de5a67a069f) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie

bitbake: bitbake: replace comment added in conf files

2013-10-07T11:52:05+00:00

The patch that implements removeConfigurationVar method was made before merging the patch that replaces "added by bitbake" with "added by hob". This patch corrects this issue. [YOCTO #5284] (Bitbake rev: 42601a5edef0316767b952b162123534aa8fee18) Signed-off-by: Cristiana Voicu Signed-off-by: Richard Purdie