linux/poky.git/bitbake, branch fido

bitbake: lib/bs4: Fix imports from html5lib >= 0.9999999/1.0b8

2018-03-28T11:56:38+00:00

As of html5lib 0.9999999/1.0b8 (released on July 14, 2016), some modules have moved from _base to base. Handle this, while staying compatible with earlier versions. (Bitbake rev: edd90cd858da5da564e9849ebc0849a8a8173d4f) Signed-off-by: Daniel Lublin Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: Fixed porno hack for hello world example

2018-01-17T22:32:46+00:00

Someone hacked the http://hambedded site or it was moved and some links to that site in the BB manual had been hijacked to point to an entry portal for a pornography site. Replaced the link with an archived version that restores the integrity of the links. (Bitbake rev: e42c645955e972e75f979a33f26cc33ddd61315a) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

bitbake: tests/fetch: ensure fetch tests preserve current dir

2016-05-09T10:10:58+00:00

The fetcher calls os.chdir() in a number of places, which can affect other tests (since the directory it changes into gets deleted) - let's just put the current directory back to where it was when we're done. (This fixes bb.tests.Path.test_unsafe_delete_path failing if it was run as part of a full bitbake-selftest run, where the fetcher tests get to run before it.) (Bitbake rev: fdb6c123593fd2255b9b09e6bdf7306d64a82892) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: bb/tests/fetch: Update cups url

2016-05-09T10:10:58+00:00

Update the upstream url used for testing cups versions after upstream website changes. (Bitbake rev: 27ae1b39c400cf7edbd6902ff050a39147d64217) Signed-off-by: Richard Purdie

bitbake: toaster: Rework mimetype guessing to fix artifact downloads

2015-12-18T13:52:00+00:00

Artifact download links were broken because the function to get the mimetype for the artifact was incorrectly using the underlying mimetype library. The function was also attached to the build environment controller, which was unnecessary, as we only support local controllers anyway. Remove the mimetype getter on the build environment and use the one in the view code instead. This prevents the download error from occurring. (Backport of dd957fe0f261db6481882fee0413f459425000c2 and dd957fe0f261db6481882fee0413f459425000c2 from master to Yocto 1.8) [YOCTO #8472] (Bitbake rev: b09966906ef054834f0b465f0c5a2a937b4c4a4c) Signed-off-by: Elliot Smith Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

bitbake: toaster: buildinfohelper Skip packages we have no build info about

2015-10-24T11:01:07+00:00

If there are more packages listed as installed than we know about from bitbake, and therefore have insufficient information to be able to create a Toaster Package object then skip it. Also handle the case where a dependency references such a package. Also clarify the error logging. (Bitbake rev: a9e23e0066ea4dc16806ed3d269587ad1c895353) Signed-off-by: Paul Barker Cc: Michael Wood Cc: Elliot Smith Signed-off-by: Richard Purdie

bitbake: bitbake: cooker: properly fix bitbake.lock handling

2015-09-01T20:37:20+00:00

If the PR server or indeed any other child process takes some time to exit (which it sometimes does when saving its database), it can end up holding bitbake.lock after the UI exits, which led to errors if you ran bitbake commands successively - we saw this when running the PR server oe-selftest tests in OE-Core. The recent attempt to fix this wasn't quite right and ended up breaking memory resident bitbake. This time we close the lock file when cooker shuts down (inside the UI process) instead of unlocking it, and this is done in the cooker code rather than the actual UI code so it doesn't matter which UI is in use. Additionally we report that we're waiting for the lock to be released, using lsof or fuser if available to list the processes with the lock open. The 'magic' in the locking is due to all spawned subprocesses of bitbake holding an open file descriptor to the bitbake.lock. It is automatically unlocked when all those fds close the file (as all the processes terminate). We close the UI copy of the lock explicitly, then close the server process copy, any remaining open copy is therefore some proess exiting. (The reproducer for the problem is to set PRSERV_HOST = "localhost:0" and add a call to time.sleep(20) after self.server_close() in lib/prserv/serv.py, then run "bitbake -p; bitbake -p" ). Cleanup work done by Paul Eggleton . This reverts bitbake commit 69ecd15aece54753154950c55d7af42f85ad8606 and e97a9f1528d77503b5c93e48e3de9933fbb9f3cd. (Bitbake rev: a29780bd43f74b7326fe788dbd65177b86806fcf) (Bitbake rev: ed30f4ee1cef8db9ea422c5e54b2375c4f3b1d6f) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie Conflicts: bitbake/lib/bb/tinfoil.py

bitbake: runqueue: Add message to explain the problem if diffsigs multiple tasks don't exist

2015-09-01T20:37:19+00:00

(Bitbake rev: 8292c64e6edae1bf6f554140e8f603cedbd01047) Signed-off-by: Richard Purdie

bitbake: cooker: Fire BuildCompleted before finishing the command

2015-06-29T08:49:12+00:00

Some handlers hook on BuildComplete so it avoids certain event races to finish the command after the BuildComplete event is sent out. This means the UI is available to handle events until the command completes. What appears to be a race on one of the sanity tests for event handlers triggered this change although the failure is hard to reproduce. [YOCTO #7921] (Bitbake rev: ac66fac162e68b568f986fe1917772e61c982f8e) Signed-off-by: Richard Purdie

bitbake: bitbake-diffsigs: consider the situation where sigdata and siginfo files having the same hash values

2015-06-28T08:44:19+00:00

For now, `bitbake-diffsigs -t ' doesn't work. It always outputs nothing. The problem is that bitbake-diffsigs are comparing sigdata and siginfo files that have the same hash value. This is not what we want. These two files are actually duplicates considering the purpose of bitbake-diffsigs. So we need to remove one of them so that bitbake-diffsigs could actually compare the correct signature files. (Bitbake rev: e14873d6847fae8abd3baf4bdc804d52d3b0c4f5) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie