Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=dora 2014-05-06T15:16:33+00:00 2014-05-06T15:16:33+00:00 Robert Yang liezhi.yang@windriver.com 2013-12-25T16:01:26+00:00 urn:sha1:6a92f7ede3be3edd58d7819aa611b0c5270756bf The fetcher will try: 1) PREMIRROR 2) Upstream 3) MIRROR If it fails to download from the Upstream, but succeeds from the MIRROR, and ud.localpath != origud.localpath (for example, the git tarball), then we will get the error (e.g.: xf86-video-omapfb): ERROR: Function failed: Fetcher failure for URL: 'xxx'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /path/to/log.do_fetch.28024 It should not show the error and let the build go on since it succeeds. (e.g.: xf86-video-omapfb) [YOCTO #5686] (Bitbake rev: 3bb3f1823bdd46ab34577d43f1e39046a32bca77) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-05-06T15:16:33+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-02-24T12:57:38+00:00 urn:sha1:8a5af7ff337e452fc9d0d26bcbc3072af3472ef4 A typo was meaning that the mirror creation method wasn't being called when it should have been. Fix the type to fix mirror tarball creation. [YOCTO #5284] (Bitbake rev: 66cdc2e21660847c50317e8bfd28cf3595422e28) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-04-19T10:04:48+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-01-20T14:30:11+00:00 urn:sha1:50e9ccb2aff7b9f9dca4fda99a6832c60f64de3b When specifying tags, they're searched for unanchored so foo/bar could match: refs/heads/abc/foo/bar refs/heads/xyz/foo/bar refs/heads/foo/bar This change anchors the expressions so they are based against heads or tags (or any other base level tree that has been created). (Bitbake master rev: df2e0972cd1db7abd5ec8b7cb295fb0c42e284a4) (Bitbake rev: da93afe9834e137ed1e9410380181286c80198b5) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-02-17T14:44:30+00:00 Martin Jansa martin.jansa@gmail.com 2014-01-21T15:46:28+00:00 urn:sha1:e8dfafda71b7340004ce5ecdc60a63d27664ceaf * 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: 3c694e20df3b1d442603300786580e4b2f4bf5f3) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-01-08T17:41:17+00:00 Cristiana Voicu cristiana.voicu@intel.com 2014-01-08T17:40:04+00:00 urn:sha1:8c102dba491927745d34b15176f9e4ba6c3c07c6 [YOCTO #5053] (Corresponds to BitBake master rev: ba9fe77e37be31e8246431578902e871dd94515e) (Bitbake rev: a1ced88ae46926e28005b83a74eaf89d70dc2b74) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-01-02T13:08:48+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-12-02T17:41:58+00:00 urn:sha1:9cea2e49d025a5493b43f826b69deca09bc9f400 If you had more than 15 layers the system would crash since one more value is added to one array than the other. This fixes the code so equal numbers of values are added to the arrays and hence doesn't crash when many layers are enabled. (Bitbake rev: ae420d37fd57a567cf3d2d8096cc9aa28ed01385) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-01-02T13:08:47+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-11-29T23:15:56+00:00 urn:sha1:564c687c2a2b90f277f444eed298b6defc51c467 Currently bitbake only adds files to its dependency list if they exist. If you add 'include foo.inc' to your recipe and the file doesn't exist, then later you add the file, the cache will not be invalidated. This leads to another bug which is that if files don't exist and then you add them and they should be found first due to BBPATH, again the cache won't invalidate. This patch adds in tracking of files we check for the existence of so that if they are added later, the cache correctly invalidates. This necessitated a new version of bb.utils.which which returns a list of files tested for. The patch also adds in checks for duplicate file includes and for now prints a warning about this. That will likely become a fatal error at some point since its never usually desired to include a file twice. The same issue is also fixed for class inheritance. Now when a class is added which would be found in the usual search path, it will cause the cache to be invalidated. Unfortunately this is old code in bitbake and the patch isn't the neatest since we have to work within that framework. [YOCTO #5611] [YOCTO #4425] (Bitbake rev: 22e6b1c4c4afb27057689bbc94cbdf1f19f93e3d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-01-02T13:08:47+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-11-22T16:17:39+00:00 urn:sha1:54534a61003fee8075458c3a7f117fc7c7c4f34f VAL = "" (not shown) VAL = " " (shown as "") VAL = " x" (shown as "x") would all show up rather differently to what would be expected in the bitbake -e output. This fixes things so they appear consistently. The output for running some shell functions may also change slightly but shouldn't change in a way that is likely to cause problems. [YOCTO #5507] (Bitbake rev: 9f37afff200d748beddc2a70f55a72c2714e3120) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2014-01-02T13:08:47+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-11-22T13:31:47+00:00 urn:sha1:faef2d9588821077b289e06021da76fa6da53d9a When using the dry run option (-n), bitbake would still try and fire a specific fakeroot worker. This is doomed to failure since it might well not have been built. Add in some checks to prevent the failures. [YOCTO #5367] (Bitbake rev: 78ae96e667d3fbb8649fe25eb073e15a99d61cc8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2013-12-11T14:16:04+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-12-10T15:09:39+00:00 urn:sha1:64fc47ba1240a6c620f3d10cb9051465b9f179ed 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 <richard.purdie@linuxfoundation.org> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>