linux/poky.git/bitbake/lib/bb, branch yocto-2.4.4

bitbake: checksum: sanity check path when recursively checksumming

2018-08-29T14:23:58+00:00

In case something goes tragically wrong, catch a request to checksum / and refuse. (Bitbake rev: 8bd16328a9332c57b03198826e22b48fadcd21d9) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: utils/md5_file: don't iterate line-by-line

2018-08-29T14:23:58+00:00

Opening a file in binary mode and iterating it seems like the simple solution but will still break on newlines, which for binary files isn't really useful as the size of the chunks could be huge or tiny. Instead, let's be a bit more clever: we'll be MD5ing lots of files, but we don't want to fill up memory: use mmap() to open the file and read the file in 8k blocks. (Bitbake rev: f3f28ec7e6cad5003014462feeb9178496107e08) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: tests/fetch: Update gnome.org urls after upstream changes

2018-08-29T09:44:21+00:00

(Bitbake rev: cdda992d4eedcf8e23b9a7222c16d49dee1586bd) Signed-off-by: Richard Purdie

bitbake: fetch2/init: Disable pseudo in runfetchcmd()

2018-07-02T10:56:01+00:00

If a fetcher, e.g., git, is run when pseudo is active it will think it is running as root. If it in turn uses ssh (as git does), ssh too will think it is running as root. This will cause it to try to read root's ssh configuration from /root/.ssh which will fail. If ssh then needs to ask for credentials it will hang indefinitely as there is nowhere for it to ask the user for them (and even if there was it would not access the correct private keys). The solution to the above is to temporarily disable pseudo while executing any fetcher commands. There should be no reason for them to be executed under pseudo anyway so this should not be a problem. RP Ammendum: We finally did get more information about how to reproduce this problem, something needs to trigger bb.fetch2.get_srcrev() in a pseudo context, for example when AUTOREV is in use or the recipe doesn't have a defined SRCREV. That SRC_URI needs to be using protocol=ssh. This would trigger an ls-remote of the remote repo and if that happens under pseudo, the wrong ssh credentials may be attempted which can hang. [YOCTO #12464] (Bitbake rev: d0fb46eead1f23356d8c3bd53a85047521ef29a7) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

bitbake: fetch2: fix import error for Python 3.6.5

2018-07-02T10:44:00+00:00

When running bitbake command with Python 3.6.5 always result in import error causing by the change of distutils module. This patch replaces the method to search executable in PATH by "/usr/bin/env ". (Bitbake rev: e4fcf4d9cef6816afac9eebb8d57c82cd1ceb293) Signed-off-by: Tzu Hsiang Lin Signed-off-by: Richard Purdie

bitbake: providers: Fix determinism issue

2018-03-09T14:12:02+00:00

We saw builds where runtime providers were sometimes changing order and the build result was therefore non-deterministic. For example it could show: DEBUG: providers for lib32-initd-functions are: ['lib32-lsbinitscripts', 'lib32-initscripts'] or DEBUG: providers for lib32-initd-functions are: ['lib32-initscripts', 'lib32-lsbinitscripts'] which could cause a test to pass or fail. This change ensures we don't rely on the random order of dictonaries in memory and act deterministically. (Bitbake rev: 223a0f68530571d2280f526bddbc718fa803a3dc) Signed-off-by: Richard Purdie

bitbake: toaster: some recipe events do not include packages

2017-12-18T15:05:36+00:00

Allow for "SinglePackageInfo" events that do not include package data, for example OPKGN equal 'lib32-*' or 'lib64-*'. [YOCTO #12204] (Bitbake rev: 0c7aee74003dbd29da7e5e35cab466c8f858cad3) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: tinfoil: Ensure we clean up loggers

2017-12-04T17:24:01+00:00

This is primarily paranoid but ensure we remove any loggers we setup either directly or indirectly so the initial state is restored after we exit. (Bitbake rev: 230493d9b99f7d315bc4e5e8d0093bd62ec8f9eb) Signed-off-by: Richard Purdie (cherry picked from commit af7d63b1f76fd3f7fa92ed15ae61ca47d9e13472) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

bitbake: event: Ensure we clean up loggers

2017-12-04T17:24:01+00:00

Whilst we're likely exiting in this case, clean up the loggers we add so that in the case of certain server retries there is no possibility multiple loggers stack up. (Bitbake rev: e52bf5f066618dfabecbd4197f77f78fa463af64) Signed-off-by: Richard Purdie (cherry picked from commit 25b7bf6672be66bcbfe5760610dce7d3e866cdcc) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

bitbake: tests/fetch: Add ftp test url

2017-12-04T17:24:01+00:00

Add in a tets ftp url so we ensure ftp urls contnue to work after the loss of the ftp.gnu.org ones. (Bitbake rev: 7016bd9c4b05df2e888ec98e37a8ae6f3ac398bd) Signed-off-by: Richard Purdie (cherry picked from commit e1e8565b5e19dd3f7ef6e7e41932456adaa3df81) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

linux/poky.git/bitbake/lib/bb, branch yocto-2.4.4

bitbake: checksum: sanity check path when recursively checksumming

bitbake: utils/md5_file: don't iterate line-by-line

bitbake: tests/fetch: Update gnome.org urls after upstream changes

bitbake: fetch2/__init__: Disable pseudo in runfetchcmd()

bitbake: fetch2: fix import error for Python 3.6.5

bitbake: providers: Fix determinism issue

bitbake: toaster: some recipe events do not include packages

bitbake: tinfoil: Ensure we clean up loggers

bitbake: event: Ensure we clean up loggers

bitbake: tests/fetch: Add ftp test url

bitbake: fetch2/init: Disable pseudo in runfetchcmd()