linux/poky.git/bitbake, branch pyro

bitbake: fetch2: Change git fetcher not to destroy old references

2020-09-08T13:46:38+00:00

It looks like we're about to see a lot of changes in branch names in repos. If we have the prune option here, those old names are lost, the changes propagate to our source mirrors and our old releases break. We have the force option so any replaced references should be replaced, its only orphaned branches which will now be preserved. I believe this behaviour will cause us fewer problems given the changes that look likely to happen. (Bitbake rev: 08aafc53ba911337d2d3558654b06f294ae634e2) Signed-off-by: Richard Purdie

bitbake: bitbake-user-manual: Added "usehead" parameter.

2018-12-10T20:42:54+00:00

(Bitbake rev: 0d436ff788f019c366cd4e66097fce928b6ff6c5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

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

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

(Bitbake rev: 98b8ea103390d5bc3583efb2e72dbac6529822a5) Signed-off-by: Richard Purdie

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

2018-07-02T10:56:15+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: 5d42dce5e612060f4181c14e1cfdec2388bb7adf) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

bitbake: fetch2: fix import error for Python 3.6.5

2018-07-02T10:44:05+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: 86a4cc7248afd3e561dc70f3490f45549265470a) Signed-off-by: Tzu Hsiang Lin Signed-off-by: Richard Purdie

bitbake: providers: Fix determinism issue

2018-03-09T14:12:09+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: eddab52a4e7c49bfcdc2c26004d0bc777a1e5c25) Signed-off-by: Richard Purdie

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

2018-01-17T22:32:18+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: 533e1840d553c183e6ab37a350d492187c5eca96) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

bitbake: toaster: allow dots in user path names

2017-11-05T22:41:27+00:00

The dot '.' character should be allowed in the user paths for local non-git layers, DL_DIR, and SSTATE_DIR. [YOCTO #10650] (Bitbake rev: ca9b9ffc250eb3ece5af3d64ff5febef69d555b0) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: toaster: reserve HEAD from imported layers

2017-11-05T22:41:27+00:00

The HEAD reference in Toaster layers are reserved for the "Local Yocto Project" layers, stored at the top directory. Imported layers are not allowed to use this since they are managed differently - for example the 'remotes' will collide. Fix the add layer handler to not drop the data fields when it is a git repo. Explicitly inform the user when an internal Toaster error is returned via AJAX, so that they know why clicking the layer add button did not do anything. [YOCTO #9924] (Bitbake rev: 90fb89e5e3ada9e36ab0b2a5a0dbfd74f9be279f) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: tests/fetch: handle network failures gracefully

2017-11-05T22:37:29+00:00

If there is a network failure the return value from latest_versionstring() is ('','') which later causes an exception when comparing versions. Improve this by checking the return value and failing the test early. [ YOCTO #12053 ] (Bitbake rev: 4284d918dc7451f6a4d00be065369e86bbaec4d2) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

linux/poky.git/bitbake, branch pyro

bitbake: fetch2: Change git fetcher not to destroy old references

bitbake: bitbake-user-manual: Added "usehead" parameter.

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: bitbake-user-manual: Fixed porno hack for hello world example

bitbake: toaster: allow dots in user path names

bitbake: toaster: reserve HEAD from imported layers

bitbake: tests/fetch: handle network failures gracefully

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