linux/poky.git, branch pyro-enea

bitbake: cookerdata: Add support for BBFILES_DYNAMIC

2023-10-20T13:58:38+00:00

BBFILES_DYNAMIC can be used to activate content only when some other layers are present. The other layers are identified by the collections that they define. The main use case is to avoid .bbappends without the corresponding .bb file in layers that want to modify other layers via .bbappends without introducing a hard dependency on those other layers. .bb files could also be handled via BBFILES_DYNAMIC. Entries in BBFILES_DYNAMIC must have the form :. Example usage: BBFILES_DYNAMIC += " \ clang-layer:${LAYERDIR}/bbappends/meta-clang/*/*/*.bbappend \ core:${LAYERDIR}/bbappends/openembedded-core/meta/*/*/*.bbappend \ " Parsing is aborted when invalid entries are found with an error message like this: ERROR: BBFILES_DYNAMIC entries must be of the form :, not: /work/my-layer/bbappends/meta-security-isafw/*/*/*.bbappend /work/my-layer/bbappends/openembedded-core/meta/*/*/*.bbappend Based on a patch by Richard Purdie. (Bitbake rev: 04f8bd50aa04b12cf91dd6a3154527ad2c24695c) Signed-off-by: Patrick Ohly Signed-off-by: Richard Purdie

devtool: deploy-target: Let script continue even if rm fails

2023-10-19T10:20:55+00:00

The remote script is run with `set -e`, so doing rm without -f on a $file that is already gone will exit the whole script, failing any redeployment. Assume a use case where packages sometimes produces certain test binaries stored on volatile media (tmpfs), and where the system is occasionally rebooted. (From OE-Core rev: db54c9a22a9b66c673df8e836de5e47fc9edda0b) Signed-off-by: Daniel Lublin Signed-off-by: Ross Burton 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

poky.ent: Updated the release date to July 2018.

2018-08-15T09:28:27+00:00

Variable updated. (From yocto-docs rev: 67f09425798f1172da9d99aeefb9ed5b7cfc7cbe) Signed-off-by: Scott Rifenbark 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

poky.ent: Updated release month variable to "June 2018"

2018-05-29T20:08:16+00:00

Preparation for a 2.3.4 (Pyro) release. (From yocto-docs rev: 834733897e900da254a607527492de218d89c28f) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation: Updated release date scheme to use variable.

2018-05-24T16:18:18+00:00

The release date is moving on Pyro. Added a new variable that I set to "May 2018" for the release date. This way if it pushes past May, I just need to update poky.ent. (From yocto-docs rev: 928c6a2bf1c31e3819ec33e09bec6c69e2ccea76) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

documentation: Updated Manual Notes

2018-05-24T16:18:18+00:00

Updated the notes on the title page to give the user some advice for when he searches for the manual and gets old manuals. (From yocto-docs rev: 7dedbb67272a18bd768ab5fe637b20a09801d904) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie

build-appliance-image: Update to pyro head revision

2018-05-24T16:18:18+00:00

(From OE-Core rev: 819aa151bd634122a46ffdd822064313c67f5ba5) Signed-off-by: Richard Purdie

linux/poky.git, branch pyro-enea

bitbake: cookerdata: Add support for BBFILES_DYNAMIC

devtool: deploy-target: Let script continue even if rm fails

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

poky.ent: Updated the release date to July 2018.

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

bitbake: fetch2: fix import error for Python 3.6.5

poky.ent: Updated release month variable to "June 2018"

documentation: Updated release date scheme to use variable.

documentation: Updated Manual Notes

build-appliance-image: Update to pyro head revision

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