diff options
| author | Patrick Williams <patrick@stwcx.xyz> | 2022-11-17 16:29:11 +0300 |
|---|---|---|
| committer | Patrick Williams <patrick@stwcx.xyz> | 2022-11-19 05:11:25 +0300 |
| commit | 7784c4292cd9e369da612736deb0691153d1b786 (patch) | |
| tree | 31368891eb9ce67a004712b5269b7b9b0f0a3c89 /poky/documentation | |
| parent | 4a4f35a2d76c72c60405581c889e2835ca49b641 (diff) | |
| download | openbmc-7784c4292cd9e369da612736deb0691153d1b786.tar.xz | |
subtree updates
- Remove systemd patches for object-manager due to upstream fix.
meta-arm: 3b7347cd67..d5f132b199:
Abdellatif El Khlifi (2):
kas: corstone1000: set branches to langdale
arm-bsp/documentation: corstone1000: 2022.11.10 RC: update the user guide
Anton Antonov (1):
arm-bsp/fvp-base: Enable virtio-rng support and unset preferred 5.15 kernel
Emekcan (2):
arm-bsp/trusted-services: add checks for null attributes in smm gateway
arm-bsp/trusted-services: Fix GetNextVariable max_name_len in smm gateway
Jon Mason (3):
arm/sbsa-acs: update to the latest version
arm/hafnium: cleanup the patches
arm/gn: update to the latest SHA
Luca Fancellu (1):
arm,arm-bsp/recipes-kernel: don't use PN in arm-ffa-transport.inc
Peter Hoyes (5):
arm/fvp: Join cli arguments in verbose logging
arm/lib: Factor out asyncio in FVPRunner
arm/lib: Decouple console parsing from the FVPRunner
arm/oeqa: Log the FVP output in OEFVPSSHTarget
runfvp: Fix verbose output when using --console
Ross Burton (1):
arm/linux-arm64-ack: fix buildpaths in the perf Python module
Rui Miguel Silva (3):
arm/trusted-services: check before applying patches
arm-bsp/trusted-services: psa test setup corstone1000
arm-bsp/trusted-firmware-m: adjust ps assets for corstone1000
Vishnu Banavath (2):
arm-bsp/documentation: corstone1000: 2022.11.10 RC: update the release notes
arm-bsp/documentation: corstone1000: 2022.11.10 RC: update the change log
meta-raspberrypi: a305f4804b..93dadf336c:
Andrei Gherzan (2):
ci: Bump actions/checkout to v3
ci: Fix dco-check job with newer git versions
Martin Jansa (1):
raspberrypi4-64: drop DEFAULTTUNE assignment
poky: 482c493cf6..44bb88cc86:
Alex Kiernan (1):
rust: update 1.64.0 -> 1.65.0
Alexander Kanavin (74):
man-pages: upgrade 5.13 -> 6.01
piglit: upgrade to latest revision
lsof: upgrade 4.96.3 -> 4.96.4
ffmpeg: upgrade 5.1.1 -> 5.1.2
ccache: upgrade 4.6.3 -> 4.7.2
python3-pip: upgrade 22.2.2 -> 22.3
ltp: upgrade 20220527 -> 20220930
alsa-utils: upgrade 1.2.7 -> 1.2.8
alsa-ucm-conf: upgrade 1.2.7.2 -> 1.2.8
libbsd: upgrade 0.11.6 -> 0.11.7
libunistring: upgrade 1.0 -> 1.1
puzzles: upgrade to latest revision
libsoup: upgrade 3.2.0 -> 3.2.1
linux-firmware: upgrade 20220913 -> 20221012
python3-git: upgrade 3.1.28 -> 3.1.29
xwayland: upgrade 22.1.3 -> 22.1.4
strace: upgrade 5.19 -> 6.0
python3-dtschema: upgrade 2022.8.3 -> 2022.9
fontconfig: upgrade 2.14.0 -> 2.14.1
python3-setuptools: upgrade 65.0.2 -> 65.5.0
taglib: upgrade 1.12 -> 1.13
nghttp2: upgrade 1.49.0 -> 1.50.0
python3-wheel: upgrade 0.37.1 -> 0.38.0
libffi: upgrade 3.4.2 -> 3.4.4
libical: upgrade 3.0.15 -> 3.0.16
mtd-utils: upgrade 2.1.4 -> 2.1.5
repo: upgrade 2.29.3 -> 2.29.5
libidn2: upgrade 2.3.3 -> 2.3.4
makedepend: upgrade 1.0.6 -> 1.0.7
diffoscope: upgrade 221 -> 224
mmc-utils: upgrade to latest revision
libsoup-2.4: upgrade 2.74.2 -> 2.74.3
gdk-pixbuf: upgrade 2.42.9 -> 2.42.10
harfbuzz: upgrade 5.3.0 -> 5.3.1
netbase: upgrade 6.3 -> 6.4
mpg123: upgrade 1.30.2 -> 1.31.1
sudo: upgrade 1.9.11p3 -> 1.9.12
alsa-lib: upgrade 1.2.7.2 -> 1.2.8
pango: upgrade 1.50.10 -> 1.50.11
pixman: upgrade 0.40.0 -> 0.42.2
vulkan: upgrade 1.3.224.1 -> 1.3.231.1
gstreamer1.0: upgrade 1.20.3 -> 1.20.4
shaderc: upgrade 2022.2 -> 2022.3
selftest: add a copy of previous mtd-utils version to meta-selftest
python3: correctly adjust include paths in sysconfigdata
vala: install vapigen-wrapper into /usr/bin/crosscripts and stage only that
sanity.bbclass: do not check for presence of distutils
pango: replace a recipe fix with an upstream submitted patch
libpciaccess: update 0.16 -> 0.17
libxinerama: update 1.1.4 -> 1.1.5
libxkbfile: update 1.1.0 -> 1.1.1
libxmu: update 1.1.3 -> 1.1.4
libxrender: update 0.9.10 -> 0.9.11
libxshmfence: update 1.3 -> 1.3.1
libxtst: update 1.2.3 -> 1.2.4
libxxf86vm: update 1.1.4 -> 1.1.5
xcb-util: update to latest revisions
xf86-input-vmmouse: update 13.1.0 -> 13.2.0
gnomebase.bbclass: return the whole version for tarball directory if it is a number
adwaita-icon-theme: update 42.0 -> 43
libepoxy: convert to git
libepoxy: update 1.5.9 -> 1.5.10
rgb: update 1.0.6 -> 1.1.0
meson: update 0.63.3 -> 0.64.0
systemd: update 251.4 -> 251.8
libxext: update 1.3.4 -> 1.3.5
gettext: update 0.21 -> 0.21.1
glib-2.0: update 2.72.3 -> 2.74.1
glib-networking: update 2.72.2 -> 2.74.0
readline: update 8.1.2 -> 8.2
llvm: update 15.0.1 -> 15.0.4
make: update 4.3 -> 4.4
bash: update 5.1.16 -> 5.2.9
mesa: do not rely on native llvm-config in target sysroot
Atanas Bunchev (1):
qemu.rst: audio: reference to Command-Line options
Benjamin Szőke (1):
image_types: Add 7-Zip support in conversion types and commands
Changhyeok Bae (1):
repo: upgrade 2.29.5 -> 2.29.9
Chase Qi (1):
libc-test: add libc testsuite for musl
Christoph Lauer (1):
populate_sdk_base: add zip options
David Bagonyi (1):
gpgme: Allow setuptools3-base to be excluded from the inherit list
Diego Sueiro (1):
kernel.bbclass: Include randstruct seed assets in STAGING_KERNEL_BUILDDIR
Etienne Cordonnier (1):
mirrors.bbclass: use shallow tarball for nativesdk-binutils
Jordan Crouse (2):
spirv-tools: Correctly set the prefix in exported cmake packages
vulkan-loader: Allow headless targets to build the loader
Jose Quaresma (3):
sstatesig: skip the rm_work task signature
rm_work: exclude the SSTATETASKS from the rm_work tasks sinature
sstate: Allow optimisation of do_deploy_archives task dependencies
Joshua Watt (2):
classes: create-spdx: Move to version specific class
scripts: convert-overrides: Allow command-line customizations
Kai Kang (1):
libuv: fixup SRC_URI
Konrad Weihmann (1):
create-spdx: default share_src for shared sources
Lee Chee Yang (1):
migration guides: add release notes for 4.0.5
Leon Anavi (2):
get_module_deps3.py: Check attribute '__file__'
python3-manifest.json: Fix re in core
Mark Asselstine (2):
bitbake: data: drop unused __expand_var_regexp__ and __expand_python_regexp__
bitbake: data_smart: allow python snippets to include a dictionary
Markus Volk (4):
webkitgtk: use libsoup-3.0 by default
epiphany: use libsoup-3.0 by default
gstreamer1.0-plugins-good: use libsoup-3.0 by default
libinput: upgrade 1.19.4 -> 1.21.0
Martin Jansa (1):
cargo.bbclass: avoid calling which ${RUSTC} with undefined ${RUSTC}
Michael Opdenacker (10):
ref-manual: terms.rst: add SBOM and SPDX terms
ref-manual: variables.rst: document spdx-create class variables
dev-manual: common-tasks.rst: add section about SPDX / SBOM generation
ref-manual: classes.rst: expand documentation of create-spdx class
ref-manual: terms.rst: add reference to new SBOM/SPDX section in dev manual
manuals: document "mime-xdg" class and MIME_XDG_PACKAGES
manuals: add shortcut for Wikipedia links
ref-manual/variables.rst: expand BB_NUMBER_THREADS description
ref-manual/variables.rst: expand PARALLEL_MAKE description
release-notes: use oe_git and yocto_git macros
Nathan Rossi (4):
oeqa/selftest/lic_checksum: Cleanup changes to emptytest include
oeqa/selftest/minidebuginfo: Create selftest for minidebuginfo
glibc-locale: Do not INHIBIT_DEFAULT_DEPS
package: Fix handling of minidebuginfo with newer binutils
Niko Mauno (1):
systemd: Consider PACKAGECONFIG in RRECOMMENDS
Paulo Neves (1):
manuals: remove xterm requirements
Pavel Zhukov (1):
bitbake: gitsm: Fix regression in gitsm submodule path parsing
Peter Kjellerstedt (1):
pango: Make it build with ptest disabled
Peter Marko (2):
systemd: add group render to udev package
meta-selftest/staticids: add render group for systemd
Quentin Schulz (3):
docs: ref-manual: classes: fix section name for github-releases
docs: ref-manual: classes: add missing closing parenthesis
docs: poky.yaml.in: remove pylint3 from Ubuntu/Debian host dependencies
Richard Purdie (7):
bitbake.conf: Drop export of SOURCE_DATE_EPOCH_FALLBACK
gcc-shared-source: Fix source date epoch handling
gcc-source: Fix gengtypes race
gcc-source: Drop gengtype manipulation
gcc-source: Ensure deploy_source_date_epoch sstate hash doesn't change
sanity: Drop data finalize call
bitbake: data/data_smart/build: Clean up datastore finalize/update_data references
Robert Yang (1):
bitbake: gitsm.py: process_submodules(): Set nobranch=1 for url
Ross Burton (19):
insane: add codeload.github.com to src-uri-bad check
populate_sdk_ext: use ConfigParser instead of SafeConfigParser
stress-ng: improve makefile use
linux-firmware: don't put the firmware into the sysroot
oeqa/qemurunner: update exception class for QMP API changes
oeqa/core/decorator: add decorators to skip based on HOST_ARCH
oeqa/selftest/buildoptions: skip test_read_only_image on qemuarm64
oeqa/selftest/efibootpartition: improve test
oeqa/selftest/imagefeatures: remove hardcoded MACHINE in test_image_gen_debugfs
oeqa/selftest/imagefeatures: don't use wic images in test_hypervisor_fmts
oeqa/selftest/imagefeatures: set a .wks in test_fs_types
oeqa/selftest/overlayfs: overlayfs: skip x86-specific tests
oeqa/selftest/package: generalise test_gdb_hardlink_debug()
oeqa/selftest/package: improve test_preserve_ownership
oeqa/selftest/runqemu: don't hardcode qemux86-64
oeqa/selftest/runtime_test: only run the virgl tests on qemux86-64
oeqa/selftest/wic: skip more tests on aarch64
oeqa/selftest/wic: use skipIfNotArch instead of custom decorator
classes/testexport: move to classes-recipe
Sergei Zhmylev (1):
wic: make ext2/3/4 images reproducible
Tim Orling (4):
python3-typing-extensions: upgrade 4.3.0 -> 4.4.0
bitbake: toaster: fixtures/README: django 1.8 -> 3.2
bitbake: toaster: fixtures/gen_fixtures.py: update branches
bitbake: toaster: Add refreshed oe-core and poky fixtures
Ulrich Ölmann (1):
dev-manual: common-tasks.rst: fix typos
Wang Mingyu (33):
bind: upgrade 9.18.7 -> 9.18.8
libedit: upgrade 20210910-3.1 -> 20221030-3.1
mtools: upgrade 4.0.41 -> 4.0.42
diffstat: upgrade 1.64 -> 1.65
inetutils: upgrade 2.3 -> 2.4
orc: upgrade 0.4.32 -> 0.4.33
socat: upgrade 1.7.4.3 -> 1.7.4.4
libxcrypt: upgrade 4.4.28 -> 4.4.30
python3-babel: upgrade 2.10.3 -> 2.11.0
python3-hatch-fancy-pypi-readme: upgrade 22.7.0 -> 22.8.0
python3-hatchling upgrade: 1.11.0 -> 1.11.1
gi-docgen: upgrade 2022.1 -> 2022.2
libdrm: upgrade 2.4.113 -> 2.4.114
mmc-utils: upgrade to latest revision
mobile-broadband-provider-info: upgrade 20220725 -> 20221107
libsdl2: upgrade 2.24.1 -> 2.24.2
mesa: upgrade 22.2.2 -> 22.2.3
python3-dtschema: upgrade 2022.9 -> 2022.11
python3-flit-core: upgrade 3.7.1 -> 3.8.0
python3-pip: update 22.3 -> 22.3.1
python3-psutil: upgrade 5.9.3 -> 5.9.4
python3-setuptools: upgrade 65.5.0 -> 65.5.1
python3-sphinx-rtd-theme: upgrade 1.1.0 -> 1.1.1
python3-subunit: upgrade 1.4.0 -> 1.4.1
python3-wheel: upgrade 0.38.0 -> 0.38.4
sed: update 4.8 -> 4.9
sudo: upgrade 1.9.12 -> 1.9.12p1
sysstat: upgrade 12.6.0 -> 12.6.1
babeltrace: upgrade 1.5.8 -> 1.5.11
iso-codes: upgrade 4.11.0 -> 4.12.0
libsoup: upgrade 3.2.1 -> 3.2.2
wayland-protocols: upgrade 1.27 -> 1.28
xwayland: upgrade 22.1.4 -> 22.1.5
zhengruoqin (5):
python3-jsonschema: upgrade 4.16.0 -> 4.17.0
python3-pyrsistent: upgrade 0.18.1 -> 0.19.2
python3-numpy: upgrade 1.23.3 -> 1.23.4
python3-sphinx-rtd-theme: upgrade 1.0.0 -> 1.1.0
python3-pbr: upgrade 5.10.0 -> 5.11.0
meta-openembedded: 6ebff843cc..d04444509a:
Armin Kuster (1):
meta-oe][PATCH] gst-editing-services: fix typo in LICENSE field.
Chen Pei (1):
python3-brotli: Add new recipe for 1.0.9
Kory Maincent (1):
openocd: fix build error
Leon Anavi (6):
python3-automat: Upgrade 20.2.0 -> 22.10.0
python3-asttokens: Upgrade 2.0.8 -> 2.1.0
python3-zeroconf: Upgrade 0.39.2 -> 0.39.4
python3-imageio: Upgrade 2.22.2 -> 2.22.3
python3-httplib: Upgrade 0.20.4 -> 0.21.0
python3-twisted: Upgrade 22.8.0 -> 22.10.0
Markus Volk (6):
pugixml: upgrade 1.12 -> 1.13
geary: update 40.0 -> 43.0
rest: upgrade 0.8.1 -> 0.9.0
gnome-online-accounts: update 3.44.0 -> 3.46.0
yelp: use libsoup-3.0 by default
surf: use libsoup-3.0 by default
Martin Jansa (1):
monkey: use git fetcher
Randy MacLeod (1):
nftables: use automake ptest output format
Sakib Sajal (1):
minio: add recipe for minio client
Tim Orling (5):
libcompress-raw-bzip2-perl: upgrade 2.096 -> 2.201
libcompress-raw-lzma-perl: upgrade 2.096 -> 2.201
libcompress-raw-zlib-perl: upgrade 2.096 -> 2.202
libio-compress-lzma-perl: upgrade 2.096 -> 2.201
libio-compress-perl: upgrade 2.096 -> 2.201
Wang Mingyu (43):
python3-lazy-object-proxy: upgrade 1.7.1 -> 1.8.0
python3-luma-oled: upgrade 3.8.1 -> 3.9.0
python3-nmap: upgrade 1.5.4 -> 1.6.0
python3-pint: upgrade 0.20 -> 0.20.1
python3-protobuf: upgrade 4.21.8 -> 4.21.9
python3-pytest-benchmark: upgrade 3.4.1 -> 4.0.0
python3-pytest-html: upgrade 3.1.1 -> 3.2.0
python3-pytest-xdist: upgrade 2.5.0 -> 3.0.2
python3-requests-toolbelt: upgrade 0.10.0 -> 0.10.1
python3-websockets: upgrade 10.3 -> 10.4
fetchmail: Fix buildpaths warning.
libxpresent: upgrade 1.0.0 -> 1.0.1
xkbprint: upgrade 1.0.5 -> 1.0.6
xmlsec1: upgrade 1.2.34 -> 1.2.36
openwsman: Change download branch from master to main.
hwdata: upgrade 0.363 -> 0.364
lcms: upgrade 2.13.1 -> 2.14
libdbd-sqlite-perl: upgrade 1.70 -> 1.72
mosh: upgrade 1.3.2 -> 1.4.0
xfstests: upgrade 2022.10.09 -> 2022.10.30
ulogd2: upgrade 2.0.7 -> 2.0.8
cli11: upgrade 2.3.0 -> 2.3.1
ctags: upgrade 5.9.20221023.0 -> 5.9.20221106.0
valijson: upgrade 0.7 -> 1.0
openvpn: upgrade 2.5.7 -> 2.5.8
poco: upgrade 1.12.3 -> 1.12.4
poppler: upgrade 22.10.0 -> 22.11.0
satyr: upgrade 0.39 -> 0.40
ser1net: upgrade 4.3.8 -> 4.3.9
stunnel: upgrade 5.66 -> 5.67
wolfssl: upgrade 5.5.2 -> 5.5.3
tio: upgrade 2.2 -> 2.3
uhubctl: upgrade 2.4.0 -> 2.5.0
zabbix: upgrade 6.2.3 -> 6.2.4
python3-spidev: upgrade 3.5 -> 3.6
python3-gevent: upgrade 22.10.1 -> 22.10.2
python3-google-auth: upgrade 2.13.0 -> 2.14.0
python3-greenlet: upgrade 1.1.3.post0 -> 2.0.0
python3-robotframework: upgrade 6.0 -> 6.0.1
python3-regex: upgrade 2022.9.13 -> 2022.10.31
python3-pillow: upgrade 9.2.0 -> 9.3.0
python3-paramiko: upgrade 2.11.0 -> 2.12.0
python3-jsonref: upgrade 0.3.0 -> 1.0.1
leimaohui (1):
samba: Fix install conflict with multilib enabled.
zhengrq.fnst@fujitsu.com (5):
python3-sqlalchemy: upgrade 1.4.42 -> 1.4.43
python3-websocket-client: upgrade 1.4.1 -> 1.4.2
python3-termcolor: upgrade 2.0.1 -> 2.1.0
python3-zopeinterface: upgrade 5.5.0 -> 5.5.1
python3-tqdm: upgrade 4.64.0 -> 4.64.1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I0a8f95b57a7b9433fe59a9055a4dae58694c1759
Diffstat (limited to 'poky/documentation')
35 files changed, 604 insertions, 200 deletions
diff --git a/poky/documentation/bsp-guide/bsp.rst b/poky/documentation/bsp-guide/bsp.rst index efdaf80f63..117056ebd1 100644 --- a/poky/documentation/bsp-guide/bsp.rst +++ b/poky/documentation/bsp-guide/bsp.rst @@ -1356,7 +1356,7 @@ Project Reference Manual. - :term:`EXTRA_IMAGECMD`: Specifies additional options for image creation commands. In this example, the "-lnp " option is used when creating the - `JFFS2 <https://en.wikipedia.org/wiki/JFFS2>`__ image. + :wikipedia:`JFFS2 <JFFS2>` image. - :term:`WKS_FILE`: The location of the :ref:`Wic kickstart <ref-manual/kickstart:openembedded kickstart (\`\`.wks\`\`) reference>` file used diff --git a/poky/documentation/conf.py b/poky/documentation/conf.py index 07a15ce7de..bd45a73fa6 100644 --- a/poky/documentation/conf.py +++ b/poky/documentation/conf.py @@ -106,6 +106,7 @@ extlinks = { 'oe_wiki': ('https://www.openembedded.org/wiki%s', None), 'oe_layerindex': ('https://layers.openembedded.org%s', None), 'oe_layer': ('https://layers.openembedded.org/layerindex/branch/master/layer%s', None), + 'wikipedia': ('https://en.wikipedia.org/wiki/%s', None), } # Intersphinx config to use cross reference with BitBake user manual diff --git a/poky/documentation/dev-manual/common-tasks.rst b/poky/documentation/dev-manual/common-tasks.rst index c747c0deac..b9c467526a 100644 --- a/poky/documentation/dev-manual/common-tasks.rst +++ b/poky/documentation/dev-manual/common-tasks.rst @@ -7157,8 +7157,7 @@ system. This section provides information for RPM, IPK, and DEB. Using RPM ^^^^^^^^^ -The `Dandified Packaging -Tool <https://en.wikipedia.org/wiki/DNF_(software)>`__ (DNF) performs +The :wikipedia:`Dandified Packaging <DNF_(software)>` (DNF) performs runtime package management of RPM packages. In order to use DNF for runtime package management, you must perform an initial setup on the target machine for cases where the ``PACKAGE_FEED_*`` variables were not @@ -7501,7 +7500,7 @@ test. Here is what you have to do for each recipe: Creating Node Package Manager (NPM) Packages -------------------------------------------- -`NPM <https://en.wikipedia.org/wiki/Npm_(software)>`__ is a package +:wikipedia:`NPM <Npm_(software)>` is a package manager for the JavaScript programming language. The Yocto Project supports the NPM :ref:`fetcher <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`. You can use this fetcher in combination with @@ -9374,8 +9373,7 @@ This command writes the following files in the current directory: - ``task-depends.dot``: A graph showing dependencies between tasks. -The graphs are in -`DOT <https://en.wikipedia.org/wiki/DOT_%28graph_description_language%29>`__ +The graphs are in :wikipedia:`DOT <DOT_%28graph_description_language%29>` format and can be converted to images (e.g. using the ``dot`` tool from `Graphviz <https://www.graphviz.org/>`__). @@ -11200,8 +11198,6 @@ to be covered by assuming that there are three main areas of concern: - Compilation scripts and modifications to the source code must be provided. -- spdx files can be provided. - There are other requirements beyond the scope of these three and the methods described in this section (e.g. the mechanism through which source code is distributed). @@ -11392,39 +11388,6 @@ layers (recipes, configuration files, and so forth) enables you to meet your requirements to include the scripts to control compilation as well as any modifications to the original source. -Providing spdx files -~~~~~~~~~~~~~~~~~~~~~~~~~ - -The spdx module has been integrated to a layer named meta-spdxscanner. -meta-spdxscanner provides several kinds of scanner. If you want to enable -this function, you have to follow the following steps: - -1. Add meta-spdxscanner layer into ``bblayers.conf``. - -2. Refer to the README in meta-spdxscanner to setup the environment (e.g, - setup a fossology server) needed for the scanner. - -3. Meta-spdxscanner provides several methods within the bbclass to create spdx files. - Please choose one that you want to use and enable the spdx task. You have to - add some config options in ``local.conf`` file in your :term:`Build Directory`. - Here is an example showing how to generate spdx files during BitBake using the - fossology-python.bbclass:: - - # Select fossology-python.bbclass. - INHERIT += "fossology-python" - # For fossology-python.bbclass, TOKEN is necessary, so, after setup a - # Fossology server, you have to create a token. - TOKEN = "eyJ0eXAiO..." - # The fossology server is necessary for fossology-python.bbclass. - FOSSOLOGY_SERVER = "http://xx.xx.xx.xx:8081/repo" - # If you want to upload the source code to a special folder: - FOLDER_NAME = "xxxx" //Optional - # If you don't want to put spdx files in tmp/deploy/spdx, you can enable: - SPDX_DEPLOY_DIR = "${DEPLOY_DIR}" //Optional - -For more usage information refer to :yocto_git:`the meta-spdxscanner repository -</meta-spdxscanner/>`. - Compliance Limitations with Executables Built from Static Libraries ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -11470,7 +11433,7 @@ Vulnerabilities in Poky and OE-Core The Yocto Project has an infrastructure to track and address unfixed known security vulnerabilities, as tracked by the public -`Common Vulnerabilities and Exposures (CVE) <https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures>`__ +:wikipedia:`Common Vulnerabilities and Exposures (CVE) <Common_Vulnerabilities_and_Exposures>` database. The Yocto Project maintains a `list of known vulnerabilities @@ -11518,7 +11481,7 @@ applied and that the issue needs to be investigated. ``Ignored`` means that afte analysis, it has been deemed to ignore the issue as it for example affects the software component on a different operating system platform. -After build with CVE check enabled, reports for each compiled source recipe will be +After a build with CVE check enabled, reports for each compiled source recipe will be found in ``build/tmp/deploy/cve``. For example the CVE check report for the ``flex-native`` recipe looks like:: @@ -11567,36 +11530,36 @@ product name when querying the CVE database. If this mapping contains false posi some reported CVEs are not for the software component in question, or false negatives like some CVEs are not found to impact the recipe when they should, then the problems can be in the recipe name to CVE product mapping. These mapping issues can be fixed by setting -the :term:`CVE_PRODUCT` variable inside the recipe. This defines the name of software component in the +the :term:`CVE_PRODUCT` variable inside the recipe. This defines the name of the software component in the upstream `NIST CVE database <https://nvd.nist.gov/>`__. The variable supports using vendor and product names like this:: CVE_PRODUCT = "flex_project:flex" -In this example from the vendor name used in CVE database is ``flex_project`` and +In this example the vendor name used in the CVE database is ``flex_project`` and the product is ``flex``. With this setting the ``flex`` recipe only maps to this specific product and not products from other vendors with same name ``flex``. -Similary, when the recipe version :term:`PV` is not compatible with software versions used by +Similarly, when the recipe version :term:`PV` is not compatible with software versions used by the upstream software component releases and the CVE database, these can be fixed using -:term:`CVE_VERSION` variable. +the :term:`CVE_VERSION` variable. -Note that if the CVE entries in NVD databse contain bugs or have missing or incomplete +Note that if the CVE entries in the NVD database contain bugs or have missing or incomplete information, it is recommended to fix the information there directly instead of working -around the issues for a possibly long time in Poky and OE-Core side recipes. Feedback to -NVD about CVEs entries can be provided through the `NVD contact form <https://nvd.nist.gov/info/contact-form>`__. +around the issues possibly for a long time in Poky and OE-Core side recipes. Feedback to +NVD about CVE entries can be provided through the `NVD contact form <https://nvd.nist.gov/info/contact-form>`__. Fixing vulnerabilities in recipes --------------------------------- If a CVE security issue impacts a software component, it can be fixed by updating to a newer version of the software component or by applying a patch. For Poky and OE-Core master branches, updating -to newer software component release with fixes is the best option, but patches can be applied +to a newer software component release with fixes is the best option, but patches can be applied if releases are not yet available. For stable branches, it is preferred to apply patches for the issues. For some software -components minor version updates can also applied if they are backwards compatible. +components minor version updates can also be applied if they are backwards compatible. Here is an example of fixing CVE security issues with patch files, an example from the :oe_layerindex:`ffmpeg recipe</layerindex/recipe/47350>`:: @@ -11610,8 +11573,8 @@ an example from the :oe_layerindex:`ffmpeg recipe</layerindex/recipe/47350>`:: file://fix-CVE-2020-22033-CVE-2020-22019.patch \ file://fix-CVE-2021-33815.patch \ -A good practice is to include the CVE identifier in both patch file name -and inside the patch file commit message use the format:: +A good practice is to include the CVE identifier in both the patch file name +and inside the patch file commit message using the format:: CVE: CVE-2020-22033 @@ -11619,7 +11582,7 @@ CVE checker will then capture this information and change the CVE status to ``Pa in the generated reports. If analysis shows that the CVE issue does not impact the recipe due to configuration, platform, -version or other reasons, the CVE can be marked as ``Ignored`` using :term:`CVE_CHECK_IGNORE` variable. +version or other reasons, the CVE can be marked as ``Ignored`` using the :term:`CVE_CHECK_IGNORE` variable. As mentioned previously, if data in the CVE database is wrong, it is recommend to fix those issues in the CVE database directly. @@ -11674,6 +11637,72 @@ When analyzing CVEs, it is recommended to: - follow public `open source security mailing lists <https://oss-security.openwall.org/wiki/mailing-lists>`__ for discussions and advance notifications of CVE bugs and software releases with fixes. +Creating a Software Bill of Materials +===================================== + +Once you are able to build an image for your project, once the licenses for +each software component are all identified (see +":ref:`dev-manual/common-tasks:working with licenses`") and once vulnerability +fixes are applied (see ":ref:`dev-manual/common-tasks:checking +for vulnerabilities`"), the OpenEmbedded build system can generate +a description of all the components you used, their licenses, their dependencies, +the changes that were applied and the known vulnerabilities that were fixed. + +This description is generated in the form of a *Software Bill of Materials* +(:term:`SBOM`), using the :term:`SPDX` standard. + +When you release software, this is the most standard way to provide information +about the Software Supply Chain of your software image and SDK. The +:term:`SBOM` tooling is often used to ensure open source license compliance by +providing the license texts used in the product which legal departments and end +users can read in standardized format. + +:term:`SBOM` information is also critical to performing vulnerability exposure +assessments, as all the components used in the Software Supply Chain are listed. + +The OpenEmbedded build system doesn't generate such information by default. +To make this happen, you must inherit the +:ref:`create-spdx <ref-classes-create-spdx>` class from a configuration file:: + + INHERIT += "create-spdx" + +You then get :term:`SPDX` output in JSON format as an +``IMAGE-MACHINE.spdx.json`` file in ``tmp/deploy/images/MACHINE/`` inside the +:term:`Build Directory`. + +This is a toplevel file accompanied by an ``IMAGE-MACHINE.spdx.index.json`` +containing an index of JSON :term:`SPDX` files for individual recipes, together +with an ``IMAGE-MACHINE.spdx.tar.zst`` compressed archive containing all such +files. + +The :ref:`create-spdx <ref-classes-create-spdx>` class offers options to include +more information in the output :term:`SPDX` data, such as making the generated +files more human readable (:term:`SPDX_PRETTY`), adding compressed archives of +the files in the generated target packages (:term:`SPDX_ARCHIVE_PACKAGED`), +adding a description of the source files handled by the target recipes +(:term:`SPDX_INCLUDE_SOURCES`) and adding archives of these source files +themselves (:term:`SPDX_ARCHIVE_SOURCES`). + +Though the toplevel :term:`SPDX` output is available in +``tmp/deploy/images/MACHINE/`` inside the :term:`Build Directory`, ancillary +generated files are available in ``tmp/deploy/spdx/MACHINE`` too, such as: + +- The individual :term:`SPDX` JSON files in the ``IMAGE-MACHINE.spdx.tar.zst`` + archive. + +- Compressed archives of the files in the generated target packages, + in ``packages/packagename.tar.zst`` (when :term:`SPDX_ARCHIVE_PACKAGED` + is set). + +- Compressed archives of the source files used to build the host tools + and the target packages in ``recipes/recipe-packagename.tar.zst`` + (when :term:`SPDX_ARCHIVE_SOURCES` is set). Those are needed to fulfill + "source code access" license requirements. + +See the `tools page <https://spdx.dev/resources/tools/>`__ on the :term:`SPDX` +project website for a list of tools to consume and transform the :term:`SPDX` +data generated by the OpenEmbedded build system. + Using the Error Reporting Tool ============================== @@ -11760,7 +11789,7 @@ Instructions on how to set it up are in the README document. Using Wayland and Weston ======================== -`Wayland <https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)>`__ +:wikipedia:`Wayland <Wayland_(display_server_protocol)>` is a computer display server protocol that provides a method for compositing window managers to communicate directly with applications and video hardware and expects them to communicate with input hardware @@ -11769,20 +11798,18 @@ in better control over graphics frame rendering than an application might otherwise achieve. The Yocto Project provides the Wayland protocol libraries and the -reference -`Weston <https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#Weston>`__ +reference :wikipedia:`Weston <Wayland_(display_server_protocol)#Weston>` compositor as part of its release. You can find the integrated packages in the ``meta`` layer of the :term:`Source Directory`. Specifically, you can find the recipes that build both Wayland and Weston at ``meta/recipes-graphics/wayland``. -You can build both the Wayland and Weston packages for use only with -targets that accept the `Mesa 3D and Direct Rendering -Infrastructure <https://en.wikipedia.org/wiki/Mesa_(computer_graphics)>`__, -which is also known as Mesa DRI. This implies that you cannot build and -use the packages if your target uses, for example, the Intel Embedded -Media and Graphics Driver (Intel EMGD) that overrides Mesa DRI. +You can build both the Wayland and Weston packages for use only with targets +that accept the :wikipedia:`Mesa 3D and Direct Rendering Infrastructure +<Mesa_(computer_graphics)>`, which is also known as Mesa DRI. This implies that +you cannot build and use the packages if your target uses, for example, the +Intel Embedded Media and Graphics Driver (Intel EMGD) that overrides Mesa DRI. .. note:: diff --git a/poky/documentation/dev-manual/qemu.rst b/poky/documentation/dev-manual/qemu.rst index 5a4a82ce6f..d9b9f69ab3 100644 --- a/poky/documentation/dev-manual/qemu.rst +++ b/poky/documentation/dev-manual/qemu.rst @@ -125,8 +125,9 @@ available. Follow these general steps to run QEMU: - This example specifies to boot an :term:`Initramfs` image and to enable audio in QEMU. For this case, ``runqemu`` sets the internal variable ``FSTYPE`` to ``cpio.gz``. Also, for audio to be enabled, - an appropriate driver must be installed (see the previous - description for the ``audio`` option for more information). + an appropriate driver must be installed (see the ``audio`` option + in :ref:`dev-manual/qemu:\`\`runqemu\`\` command-line options` + for more information). :: $ runqemu qemux86-64 ramfs audio diff --git a/poky/documentation/dev-manual/start.rst b/poky/documentation/dev-manual/start.rst index f90375471f..63d63fc27e 100644 --- a/poky/documentation/dev-manual/start.rst +++ b/poky/documentation/dev-manual/start.rst @@ -273,7 +273,7 @@ For Linux (WSL 2). .. note:: The Yocto Project is not compatible with version 1 of - `Windows Subsystem for Linux <https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux>`__. + :wikipedia:`Windows Subsystem for Linux <Windows_Subsystem_for_Linux>`. It is compatible but neither officially supported nor validated with WSL 2. If you still decide to use WSL please upgrade to `WSL 2 <https://learn.microsoft.com/en-us/windows/wsl/install>`__. diff --git a/poky/documentation/kernel-dev/common.rst b/poky/documentation/kernel-dev/common.rst index 690f61110b..028b6af84c 100644 --- a/poky/documentation/kernel-dev/common.rst +++ b/poky/documentation/kernel-dev/common.rst @@ -1043,7 +1043,7 @@ Using ``menuconfig`` The easiest way to define kernel configurations is to set them through the ``menuconfig`` tool. This tool provides an interactive method with which to set kernel configurations. For general information on -``menuconfig``, see https://en.wikipedia.org/wiki/Menuconfig. +``menuconfig``, see :wikipedia:`Menuconfig`. To use the ``menuconfig`` tool in the Yocto Project development environment, you must do the following: diff --git a/poky/documentation/migration-guides/migration-3.0.rst b/poky/documentation/migration-guides/migration-3.0.rst index 96aea2f332..90736e6009 100644 --- a/poky/documentation/migration-guides/migration-3.0.rst +++ b/poky/documentation/migration-guides/migration-3.0.rst @@ -108,7 +108,7 @@ Packaging Changes The following packaging changes have occurred. -- The `Epiphany <https://en.wikipedia.org/wiki/GNOME_Web>`__ browser +- The :wikipedia:`Epiphany <GNOME_Web>` browser has been dropped from ``packagegroup-self-hosted`` as it has not been needed inside ``build-appliance-image`` for quite some time and was causing resource problems. diff --git a/poky/documentation/migration-guides/migration-3.1.rst b/poky/documentation/migration-guides/migration-3.1.rst index a6106eefae..7fdd3b88a6 100644 --- a/poky/documentation/migration-guides/migration-3.1.rst +++ b/poky/documentation/migration-guides/migration-3.1.rst @@ -238,7 +238,7 @@ Warnings will now be shown at :ref:`ref-tasks-package_qa` time in the following circumstances: - A recipe installs ``.desktop`` files containing ``MimeType`` keys but - does not inherit the new ``mime-xdg`` class + does not inherit the new :ref:`mime-xdg <ref-classes-mime-xdg>` class - A recipe installs ``.xml`` files into ``${datadir}/mime/packages`` but does not inherit the :ref:`mime <ref-classes-mime>` class diff --git a/poky/documentation/migration-guides/migration-4.0.rst b/poky/documentation/migration-guides/migration-4.0.rst index 02d3c3e2bd..17b1d3c619 100644 --- a/poky/documentation/migration-guides/migration-4.0.rst +++ b/poky/documentation/migration-guides/migration-4.0.rst @@ -183,8 +183,8 @@ a new :term:`KERNEL_DEBUG_TIMESTAMPS` variable to "1". Supported host distribution changes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- Support for `AlmaLinux <https://en.wikipedia.org/wiki/AlmaLinux>`__ - hosts replacing `CentOS <https://en.wikipedia.org/wiki/CentOS>`__. +- Support for :wikipedia:`AlmaLinux <AlmaLinux>` + hosts replacing :wikipedia:`CentOS <CentOS>`. The following distribution versions were dropped: CentOS 8, Ubuntu 16.04 and Fedora 30, 31 and 32. - ``gcc`` version 7.5 is now required at minimum on the build host. For older diff --git a/poky/documentation/migration-guides/release-4.0.rst b/poky/documentation/migration-guides/release-4.0.rst index 9f67daaffb..eb0744cc76 100644 --- a/poky/documentation/migration-guides/release-4.0.rst +++ b/poky/documentation/migration-guides/release-4.0.rst @@ -9,3 +9,4 @@ Release 4.0 (kirkstone) release-notes-4.0.2 release-notes-4.0.3 release-notes-4.0.4 + release-notes-4.0.5 diff --git a/poky/documentation/migration-guides/release-notes-3.4.1.rst b/poky/documentation/migration-guides/release-notes-3.4.1.rst index 0503f29b2c..d15a8a8fbd 100644 --- a/poky/documentation/migration-guides/release-notes-3.4.1.rst +++ b/poky/documentation/migration-guides/release-notes-3.4.1.rst @@ -198,7 +198,7 @@ Repositories / Downloads for 3.4.1 poky -- Repository Location: https://git.yoctoproject.org/poky/ +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`honister </poky/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.1 </poky/tag/?h=yocto-3.4.1>` - Git Revision: :yocto_git:`b53230c08d9f02ecaf35b4f0b70512abbf10ae11 </poky/commit/?id=b53230c08d9f02ecaf35b4f0b70512abbf10ae11>` @@ -210,7 +210,7 @@ poky meta-mingw -- Repository Location: https://git.yoctoproject.org/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`honister </meta-mingw/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.1 </meta-mingw/tag/?h=yocto-3.4.1>` - Git Revision: :yocto_git:`f5d761cbd5c957e4405c5d40b0c236d263c916a8 </meta-mingw/commit/?id=f5d761cbd5c957e4405c5d40b0c236d263c916a8>` @@ -222,7 +222,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`honister </meta-gplv2/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.1 </meta-gplv2/tag/?h=yocto-3.4.1>` - Git Revision: :yocto_git:`f04e4369bf9dd3385165281b9fa2ed1043b0e400 </meta-gplv2/commit/?id=f04e4369bf9dd3385165281b9fa2ed1043b0e400>` @@ -246,7 +246,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`honister </yocto-docs/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.1 </yocto-docs/tag/?h=yocto-3.4.1>` - Git Revision: :yocto_git:`b250eda5a0beba8acc9641c55a5b0e30594b5178 </yocto-docs/commit/?b250eda5a0beba8acc9641c55a5b0e30594b5178>` diff --git a/poky/documentation/migration-guides/release-notes-3.4.2.rst b/poky/documentation/migration-guides/release-notes-3.4.2.rst index 2812b725c4..ddf25ef1bd 100644 --- a/poky/documentation/migration-guides/release-notes-3.4.2.rst +++ b/poky/documentation/migration-guides/release-notes-3.4.2.rst @@ -174,9 +174,9 @@ Repositories / Downloads for 3.4.2 poky -- Repository Location: https://git.yoctoproject.org/poky/ +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`honister </poky/log/?h=honister>` -- Tag: `yocto-3.4.2 <https://git.yoctoproject.org/poky/tag/?h=yocto-3.4.2>`__ +- Tag: :yocto_git:`yocto-3.4.2 </poky/tag/?h=yocto-3.4.2>` - Git Revision: :yocto_git:`e0ab08bb6a32916b457d221021e7f402ffa36b1a </poky/commit/?id=e0ab08bb6a32916b457d221021e7f402ffa36b1a>` - Release Artefact: poky-e0ab08bb6a32916b457d221021e7f402ffa36b1a - sha: 8580dc5067ee426fe347a0d0f7a74c29ba539120bbe8438332339a9c8bce00fd @@ -198,7 +198,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/meta-mingw +- Repository Location: :yocto_git:`meta-mingw` - Branch: :yocto_git:`honister </meta-mingw/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.2 </meta-mingw/tag/?h=yocto-3.4.2>` - Git Revision: :yocto_git:`f5d761cbd5c957e4405c5d40b0c236d263c916a8 </meta-mingw/commit/?id=f5d761cbd5c957e4405c5d40b0c236d263c916a8>` @@ -210,7 +210,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`honister </meta-gplv2/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.2 </meta-gplv2/tag/?h=yocto-3.4.2>` - Git Revision: :yocto_git:`f04e4369bf9dd3385165281b9fa2ed1043b0e400 </meta-gplv2/commit/?id=f04e4369bf9dd3385165281b9fa2ed1043b0e400>` @@ -234,7 +234,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`honister </yocto-docs/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.2 </yocto-docs/tag/?h=yocto-3.4.2>` - Git Revision: :yocto_git:`3061d3d62054a5c3b9e16bfce4bcd186fa7a23d2` </yocto-docs/commit/?3061d3d62054a5c3b9e16bfce4bcd186fa7a23d2>` diff --git a/poky/documentation/migration-guides/release-notes-3.4.3.rst b/poky/documentation/migration-guides/release-notes-3.4.3.rst index 2673abbbb9..9db53d71df 100644 --- a/poky/documentation/migration-guides/release-notes-3.4.3.rst +++ b/poky/documentation/migration-guides/release-notes-3.4.3.rst @@ -131,9 +131,9 @@ Repositories / Downloads for 3.4.3 poky -- Repository Location: https://git.yoctoproject.org/poky/ +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`honister </poky/log/?h=honister>` -- Tag: `yocto-3.4.3 <https://git.yoctoproject.org/poky/tag/?h=yocto-3.4.3>`__ +- Tag: :yocto_git:`yocto-3.4.3 </poky/tag/?h=yocto-3.4.3>` - Git Revision: :yocto_git:`ee68ae307fd951b9de6b31dc6713ea29186b7749 </poky/commit/?id=ee68ae307fd951b9de6b31dc6713ea29186b7749>` - Release Artefact: poky-ee68ae307fd951b9de6b31dc6713ea29186b7749 - sha: 92c3d73c3e74f0e1d5c2ab2836ce3a3accbe47772cea70df3755845e0db1379b @@ -155,7 +155,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`honister </meta-mingw/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.3 </meta-mingw/tag/?h=yocto-3.4.3>` - Git Revision: :yocto_git:`f5d761cbd5c957e4405c5d40b0c236d263c916a8 </meta-mingw/commit/?id=f5d761cbd5c957e4405c5d40b0c236d263c916a8>` @@ -167,7 +167,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`honister </meta-gplv2/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.3 </meta-gplv2/tag/?h=yocto-3.4.3>` - Git Revision: :yocto_git:`f04e4369bf9dd3385165281b9fa2ed1043b0e400 </meta-gplv2/commit/?id=f04e4369bf9dd3385165281b9fa2ed1043b0e400>` @@ -191,7 +191,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`honister </yocto-docs/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.3 </yocto-docs/tag/?h=yocto-3.4.3>` - Git Revision: :yocto_git:`15f46f97d9cad558c19fc1dc19cfbe3720271d04 </yocto-docs/commit/?15f46f97d9cad558c19fc1dc19cfbe3720271d04>` diff --git a/poky/documentation/migration-guides/release-notes-3.4.4.rst b/poky/documentation/migration-guides/release-notes-3.4.4.rst index 38e3965169..55a4583b29 100644 --- a/poky/documentation/migration-guides/release-notes-3.4.4.rst +++ b/poky/documentation/migration-guides/release-notes-3.4.4.rst @@ -89,9 +89,9 @@ Repositories / Downloads for 3.4.4 poky -- Repository Location: https://git.yoctoproject.org/poky/ +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`honister </poky/log/?h=honister>` -- Tag: `yocto-3.4.4 <https://git.yoctoproject.org/poky/tag/?h=yocto-3.4.4>`__ +- Tag: :yocto_git:`yocto-3.4.4 </poky/tag/?h=yocto-3.4.4>` - Git Revision: :yocto_git:`780eeec8851950ee6ac07a2a398ba937206bd2e4 </poky/commit/?id=780eeec8851950ee6ac07a2a398ba937206bd2e4>` - Release Artefact: poky-780eeec8851950ee6ac07a2a398ba937206bd2e4 - sha: 09558927064454ec2492da376156b716d9fd14aae57196435d742db7bfdb4b95 @@ -113,7 +113,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`honister </meta-mingw/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.4 </meta-mingw/tag/?h=yocto-3.4.4>` - Git Revision: :yocto_git:`f5d761cbd5c957e4405c5d40b0c236d263c916a8 </meta-mingw/commit/?id=f5d761cbd5c957e4405c5d40b0c236d263c916a8>` @@ -125,7 +125,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`honister </meta-gplv2/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.4 </meta-gplv2/tag/?h=yocto-3.4.4>` - Git Revision: :yocto_git:`f04e4369bf9dd3385165281b9fa2ed1043b0e400 </meta-gplv2/commit/?id=f04e4369bf9dd3385165281b9fa2ed1043b0e400>` @@ -149,7 +149,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`honister </yocto-docs/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4.4 </yocto-docs/tag/?h=yocto-3.4.4>` - Git Revision: :yocto_git:`5ead7d39aaf9044078dff27f462e29a8e31d89e4 </yocto-docs/commit/?5ead7d39aaf9044078dff27f462e29a8e31d89e4>` diff --git a/poky/documentation/migration-guides/release-notes-3.4.rst b/poky/documentation/migration-guides/release-notes-3.4.rst index de1d209682..62683b4a5c 100644 --- a/poky/documentation/migration-guides/release-notes-3.4.rst +++ b/poky/documentation/migration-guides/release-notes-3.4.rst @@ -721,7 +721,7 @@ Repositories / Downloads for 3.4 poky -- Repository Location: https://git.yoctoproject.org/poky/ +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`honister </poky/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4 </poky/tag/?h=yocto-3.4>` - Git Revision: :yocto_git:`f6d1126fff213460dc6954a5d5fc168606d76b66 </poky/commit/?id=f6d1126fff213460dc6954a5d5fc168606d76b66>` @@ -745,7 +745,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`honister </meta-mingw/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4 </meta-mingw/tag/?h=yocto-3.4>` - Git Revision: :yocto_git:`f5d761cbd5c957e4405c5d40b0c236d263c916a8 </meta-mingw/commit/?id=f5d761cbd5c957e4405c5d40b0c236d263c916a8>` @@ -757,7 +757,7 @@ meta-mingw meta-intel -- Repository Location: https://git.yoctoproject.org/meta-intel +- Repository Location: :yocto_git:`/meta-intel` - Branch: :yocto_git:`honister </meta-intel/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4 </meta-intel/tag/?h=yocto-3.4>` - Git Revision: :yocto_git:`90170cf85fe35b4e8dc00eee50053c0205276b63 </meta-intel/commit/?id=90170cf85fe35b4e8dc00eee50053c0205276b63>` @@ -769,7 +769,7 @@ meta-intel meta-gplv2 -- Repository Location: https://git.yoctoproject.org/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`honister </meta-gplv2/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4 </meta-gplv2/tag/?h=yocto-3.4>` - Git Revision: :yocto_git:`f04e4369bf9dd3385165281b9fa2ed1043b0e400 </meta-gplv2/commit/?id=f04e4369bf9dd3385165281b9fa2ed1043b0e400>` @@ -793,7 +793,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`honister </yocto-docs/log/?h=honister>` - Tag: :yocto_git:`yocto-3.4 </yocto-docs/tag/?h=yocto-3.4>` - Git Revision: :yocto_git:`d75c5450ecf56c8ac799a633ee9ac459e88f91fc </yocto-docs/commit/?id=d75c5450ecf56c8ac799a633ee9ac459e88f91fc>` diff --git a/poky/documentation/migration-guides/release-notes-4.0.1.rst b/poky/documentation/migration-guides/release-notes-4.0.1.rst index e4bfd5bb3d..28d1d71dcf 100644 --- a/poky/documentation/migration-guides/release-notes-4.0.1.rst +++ b/poky/documentation/migration-guides/release-notes-4.0.1.rst @@ -182,7 +182,7 @@ Repositories / Downloads for 4.0.1 poky -- Repository Location: https://git.yoctoproject.org/git/poky +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`kirkstone </poky/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.1 </poky/tag/?h=yocto-4.0.1>` - Git Revision: :yocto_git:`8c489602f218bcf21de0d3c9f8cf620ea5f06430 </poky/commit/?id=8c489602f218bcf21de0d3c9f8cf620ea5f06430>` @@ -206,7 +206,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/git/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`kirkstone </meta-mingw/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.1 </meta-mingw/tag/?h=yocto-4.0.1>` - Git Revision: :yocto_git:`a90614a6498c3345704e9611f2842eb933dc51c1 </meta-mingw/commit/?id=a90614a6498c3345704e9611f2842eb933dc51c1>` @@ -218,7 +218,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/git/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`kirkstone </meta-gplv2/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.1 </meta-gplv2/tag/?h=yocto-4.0.1>` - Git Revision: :yocto_git:`d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a </meta-mingw/commit/?id=d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a>` @@ -242,7 +242,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/git/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`kirkstone </yocto-docs/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.1 </yocto-docs/tag/?h=yocto-4.0>` - Git Revision: :yocto_git:`4ec9df3336a425719a9a35532504731ce56984ca </yocto-docs/commit/?id=4ec9df3336a425719a9a35532504731ce56984ca>` diff --git a/poky/documentation/migration-guides/release-notes-4.0.2.rst b/poky/documentation/migration-guides/release-notes-4.0.2.rst index 632af11297..2c79969f4d 100644 --- a/poky/documentation/migration-guides/release-notes-4.0.2.rst +++ b/poky/documentation/migration-guides/release-notes-4.0.2.rst @@ -230,7 +230,7 @@ Repositories / Downloads for Yocto-4.0.2 poky -- Repository Location: https://git.yoctoproject.org/git/poky +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`kirkstone </poky/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.2 </poky/log/?h=yocto-4.0.2>` - Git Revision: :yocto_git:`a5ea426b1da472fc8549459fff3c1b8c6e02f4b5 </poky/commit/?id=a5ea426b1da472fc8549459fff3c1b8c6e02f4b5>` @@ -242,7 +242,7 @@ poky openembedded-core -- Repository Location: https://git.openembedded.org/openembedded-core +- Repository Location: :oe_git:`/openembedded-core` - Branch: :oe_git:`kirkstone </openembedded-core/log/?h=kirkstone>` - Tag: :oe_git:`yocto-4.0.2 </openembedded-core/log/?h=yocto-4.0.2>` - Git Revision: :oe_git:`eea52e0c3d24c79464f4afdbc3c397e1cb982231 </openembedded-core/commit/?id=eea52e0c3d24c79464f4afdbc3c397e1cb982231>` @@ -254,7 +254,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/git/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`kirkstone </meta-mingw/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.2 </meta-mingw/log/?h=yocto-4.0.2>` - Git Revision: :yocto_git:`a90614a6498c3345704e9611f2842eb933dc51c1 </meta-mingw/commit/?id=a90614a6498c3345704e9611f2842eb933dc51c1>` @@ -266,7 +266,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/git/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`kirkstone </meta-gplv2/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.2 </meta-gplv2/log/?h=yocto-4.0.2>` - Git Revision: :yocto_git:`d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a </meta-gplv2/commit/?id=d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a>` @@ -278,7 +278,7 @@ meta-gplv2 bitbake -- Repository Location: https://git.openembedded.org/bitbake +- Repository Location: :oe_git:`/bitbake` - Branch: :oe_git:`2.0 </bitbake/log/?h=2.0>` - Tag: :oe_git:`yocto-4.0.2 </bitbake/log/?h=yocto-4.0.2>` - Git Revision: :oe_git:`b8fd6f5d9959d27176ea016c249cf6d35ac8ba03 </bitbake/commit/?id=b8fd6f5d9959d27176ea016c249cf6d35ac8ba03>` @@ -290,7 +290,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/git/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`kirkstone </yocto-docs/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.2 </yocto-docs/log/?h=yocto-4.0.2>` - Git Revision: :yocto_git:`662294dccd028828d5c7e9fd8f5c8e14df53df4b </yocto-docs/commit/?id=662294dccd028828d5c7e9fd8f5c8e14df53df4b>` diff --git a/poky/documentation/migration-guides/release-notes-4.0.3.rst b/poky/documentation/migration-guides/release-notes-4.0.3.rst index 83e12a64ef..9f51ff9b3e 100644 --- a/poky/documentation/migration-guides/release-notes-4.0.3.rst +++ b/poky/documentation/migration-guides/release-notes-4.0.3.rst @@ -247,7 +247,7 @@ Repositories / Downloads for Yocto-4.0.3 poky -- Repository Location: https://git.yoctoproject.org/git/poky +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`kirkstone </poky/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.3 </poky/log/?h=yocto-4.0.3>` - Git Revision: :yocto_git:`387ab5f18b17c3af3e9e30dc58584641a70f359f </poky/commit/?id=387ab5f18b17c3af3e9e30dc58584641a70f359f>` @@ -259,7 +259,7 @@ poky openembedded-core -- Repository Location: https://git.openembedded.org/openembedded-core +- Repository Location: :oe_git:`/openembedded-core` - Branch: :oe_git:`kirkstone </openembedded-core/log/?h=kirkstone>` - Tag: :oe_git:`yocto-4.0.3 </openembedded-core/log/?h=yocto-4.0.3>` - Git Revision: :oe_git:`2cafa6ed5f0aa9df5a120b6353755d56c7c7800d </openembedded-core/commit/?id=2cafa6ed5f0aa9df5a120b6353755d56c7c7800d>` @@ -271,7 +271,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/git/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`kirkstone </meta-mingw/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.3 </meta-mingw/log/?h=yocto-4.0.3>` - Git Revision: :yocto_git:`a90614a6498c3345704e9611f2842eb933dc51c1 </meta-mingw/commit/?id=a90614a6498c3345704e9611f2842eb933dc51c1>` @@ -283,7 +283,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/git/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`kirkstone </meta-gplv2/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.3 </meta-gplv2/log/?h=yocto-4.0.3>` - Git Revision: :yocto_git:`d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a </meta-gplv2/commit/?id=d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a>` @@ -295,7 +295,7 @@ meta-gplv2 bitbake -- Repository Location: https://git.openembedded.org/bitbake +- Repository Location: :oe_git:`/bitbake` - Branch: :oe_git:`2.0 </bitbake/log/?h=2.0>` - Tag: :oe_git:`yocto-4.0.3 </bitbake/log/?h=yocto-4.0.3>` - Git Revision: :oe_git:`b8fd6f5d9959d27176ea016c249cf6d35ac8ba03 </bitbake/commit/?id=b8fd6f5d9959d27176ea016c249cf6d35ac8ba03>` @@ -307,7 +307,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/git/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`kirkstone </yocto-docs/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.3 </yocto-docs/log/?h=yocto-4.0.3>` - Git Revision: :yocto_git:`d9b3dcf65ef25c06f552482aba460dd16862bf96 </yocto-docs/commit/?id=d9b3dcf65ef25c06f552482aba460dd16862bf96>` diff --git a/poky/documentation/migration-guides/release-notes-4.0.4.rst b/poky/documentation/migration-guides/release-notes-4.0.4.rst index 43f92cae84..9068841783 100644 --- a/poky/documentation/migration-guides/release-notes-4.0.4.rst +++ b/poky/documentation/migration-guides/release-notes-4.0.4.rst @@ -233,7 +233,7 @@ Repositories / Downloads for Yocto-4.0.4 poky -- Repository Location: https://git.yoctoproject.org/git/poky +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`kirkstone </poky/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.4 </poky/log/?h=yocto-4.0.4>` - Git Revision: :yocto_git:`d64bef1c7d713b92a51228e5ade945835e5a94a4 </poky/commit/?id=d64bef1c7d713b92a51228e5ade945835e5a94a4>` @@ -245,7 +245,7 @@ poky openembedded-core -- Repository Location: https://git.openembedded.org/openembedded-core +- Repository Location: oe_git:`/openembedded-core` - Branch: :oe_git:`kirkstone </openembedded-core/log/?h=kirkstone>` - Tag: :oe_git:`yocto-4.0.4 </openembedded-core/log/?h=yocto-4.0.4>` - Git Revision: :oe_git:`f7766da462905ec67bf549d46b8017be36cd5b2a </openembedded-core/commit/?id=f7766da462905ec67bf549d46b8017be36cd5b2a>` @@ -257,7 +257,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/git/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`kirkstone </meta-mingw/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.4 </meta-mingw/log/?h=yocto-4.0.4>` - Git Revision: :yocto_git:`a90614a6498c3345704e9611f2842eb933dc51c1 </meta-mingw/commit/?id=a90614a6498c3345704e9611f2842eb933dc51c1>` @@ -269,7 +269,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/git/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`kirkstone </meta-gplv2/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.4 </meta-gplv2/log/?h=yocto-4.0.4>` - Git Revision: :yocto_git:`d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a </meta-gplv2/commit/?id=d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a>` @@ -281,7 +281,7 @@ meta-gplv2 bitbake -- Repository Location: https://git.openembedded.org/bitbake +- Repository Location: :oe_git:`/bitbake` - Branch: :oe_git:`2.0 </bitbake/log/?h=2.0>` - Tag: :oe_git:`yocto-4.0.4 </bitbake/log/?h=yocto-4.0.4>` - Git Revision: :oe_git:`ac576d6fad6bba0cfea931883f25264ea83747ca </bitbake/commit/?id=ac576d6fad6bba0cfea931883f25264ea83747ca>` @@ -293,7 +293,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/git/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`kirkstone </yocto-docs/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0.4 </yocto-docs/log/?h=yocto-4.0.4>` - Git Revision: :yocto_git:`f632dad24c39778f948014029e74db3c871d9d21 </yocto-docs/commit/?id=f632dad24c39778f948014029e74db3c871d9d21>` diff --git a/poky/documentation/migration-guides/release-notes-4.0.5.rst b/poky/documentation/migration-guides/release-notes-4.0.5.rst new file mode 100644 index 0000000000..ea0280b03c --- /dev/null +++ b/poky/documentation/migration-guides/release-notes-4.0.5.rst @@ -0,0 +1,196 @@ +Release notes for Yocto-4.0.5 (Kirkstone) +----------------------------------------- + +Security Fixes in Yocto-4.0.5 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +- qemu: fix :cve:`2021-3750`, :cve:`2021-3611` and :cve:`2022-2962` +- binutils : fix :cve:`2022-38126`, :cve:`2022-38127` and :cve:`2022-38128` +- tff: fix :cve:`2022-2867`, :cve:`2022-2868` and :cve:`2022-2869` +- inetutils: fix :cve:`2022-39028` +- go: fix :cve:`2022-27664` + +Fixes in Yocto-4.0.5 +~~~~~~~~~~~~~~~~~~~~ + +- Revert "gcc-cross-canadian: Add symlink to real-ld alongside other symlinks" +- bind: upgrade to 9.18.7 +- binutils: stable 2.38 branch updates (dc2474e7) +- bitbake: Fix npm to use https rather than http +- bitbake: asyncrpc/client: Fix unix domain socket chdir race issues +- bitbake: bitbake: Add copyright headers where missing +- bitbake: gitsm: Error out if submodule refers to parent repo +- bitbake: runqueue: Drop deadlock breaking force fail +- bitbake: runqueue: Ensure deferred tasks are sorted by multiconfig +- bitbake: runqueue: Improve deadlock warning messages +- bitbake: siggen: Fix insufficent entropy in sigtask file names +- bitbake: tests/fetch: Allow handling of a file:// url within a submodule +- build-appliance-image: Update to kirkstone head revision (4a88ada) +- busybox: add devmem 128-bit support +- classes: files: Extend overlayfs-etc class +- coreutils: add openssl PACKAGECONFIG +- create-pull-request: don't switch the git remote protocol to git:// +- dev-manual: fix reference to BitBake user manual +- expat: upgrade 2.4.8 -> 2.4.9 +- files: overlayfs-etc: refactor preinit template +- gcc-cross-canadian: add default plugin linker +- gcc: add arm-v9 support +- git: upgrade 2.35.4 -> 2.35.5 +- glibc-locale: explicitly remove empty dirs in ${libdir} +- glibc-tests: use += instead of :append +- glibc: stable 2.35 branch updates.(8d125a1f) +- go-native: switch from SRC_URI:append to SRC_URI += +- image_types_wic.bbclass: fix cross binutils dependency +- kern-tools: allow 'y' or 'm' to avoid config audit warnings +- kern-tools: fix queue processing in relative TOPDIR configurations +- kernel-yocto: allow patch author date to be commit date +- libpng: upgrade to 1.6.38 +- linux-firmware: package new Qualcomm firmware +- linux-firmware: upgrade 20220708 -> 20220913 +- linux-libc-headers: switch from SRC_URI:append to SRC_URI += +- linux-yocto-dev: add qemuarm64 +- linux-yocto/5.10: update to v5.10.149 +- linux-yocto/5.15: cfg: fix ACPI warnings for -tiny +- linux-yocto/5.15: update to v5.15.68 +- local.conf.sample: correct the location of public hashserv +- ltp: Fix pread02 case trigger the glibc overflow detection +- lttng-modules: Fix crash on powerpc64 +- lttng-tools: Disable on qemuriscv32 +- lttng-tools: Disable on riscv32 +- migration-guides: add 4.0.4 release notes +- oeqa/runtime/dnf: fix typo +- own-mirrors: add crate +- perf: Fix for recent kernel upgrades +- poky.conf: bump version for 4.0.5 +- poky.yaml.in: update version requirements +- python3-rfc3986-validator: switch from SRC_URI:append to SRC_URI += +- python3: upgrade 3.10.4 -> 3.10.7 +- qemu: Backport patches from upstream to support float128 on qemu-ppc64 +- rpm: Remove -Wimplicit-function-declaration warnings +- rpm: update to 4.17.1 +- rsync: update to 3.2.5 +- stress-cpu: disable float128 math on powerpc64 to avoid SIGILL +- tune-neoversen2: support tune-neoversen2 base on armv9a +- tzdata: update to 2022d +- u-boot: switch from append to += in SRC_URI +- uninative: Upgrade to 3.7 to work with glibc 2.36 +- vim: Upgrade to 9.0.0598 +- webkitgtk: Update to 2.36.7 + + +Known Issues in Yocto-4.0.5 +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +- There are recent CVEs in key components such as openssl. They are not included in this release as it was built before the issues were known and fixes were available but these are now available on the kirkstone branch. + + +Contributors to Yocto-4.0.5 +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +- Adrian Freihofer +- Alexander Kanavin +- Alexandre Belloni +- Bhabu Bindu +- Bruce Ashfield +- Chen Qi +- Daniel McGregor +- Denys Dmytriyenko +- Dmitry Baryshkov +- Florin Diaconescu +- He Zhe +- Joshua Watt +- Khem Raj +- Martin Jansa +- Michael Halstead +- Michael Opdenacker +- Mikko Rapeli +- Mingli Yu +- Neil Horman +- Pavel Zhukov +- Richard Purdie +- Robert Joslyn +- Ross Burton +- Ruiqiang Hao +- Samuli Piippo +- Steve Sakoman +- Sundeep KOKKONDA +- Teoh Jay Shen +- Tim Orling +- Virendra Thakur +- Vyacheslav Yurkov +- Xiangyu Chen +- Yash Shinde +- pgowda +- Wang Mingyu + + +Repositories / Downloads for Yocto-4.0.5 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +poky + +- Repository Location: :yocto_git:`/poky` +- Branch: :yocto_git:`kirkstone </poky/log/?h=kirkstone>` +- Tag: :yocto_git:`yocto-4.0.5 </poky/log/?h=yocto-4.0.5>` +- Git Revision: :yocto_git:`2e79b199114b25d81bfaa029ccfb17676946d20d </poky/commit/?id=2e79b199114b25d81bfaa029ccfb17676946d20d>` +- Release Artefact: poky-2e79b199114b25d81bfaa029ccfb17676946d20d +- sha: 7bcf3f901d4c5677fc95944ab096e9e306f4c758a658dde5befd16861ad2b8ea +- Download Locations: + http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.5/poky-2e79b199114b25d81bfaa029ccfb17676946d20d.tar.bz2 + http://mirrors.kernel.org/yocto/yocto/yocto-4.0.5/poky-2e79b199114b25d81bfaa029ccfb17676946d20d.tar.bz2 + +openembedded-core + +- Repository Location: :oe_git:`/openembedded-core` +- Branch: :oe_git:`kirkstone </openembedded-core/log/?h=kirkstone>` +- Tag: :oe_git:`yocto-4.0.5 </openembedded-core/log/?h=yocto-4.0.5>` +- Git Revision: :oe_git:`fbdf93f43ff4b876487e1f26752598ec8abcb46e </openembedded-core/commit/?id=fbdf93f43ff4b876487e1f26752598ec8abcb46e>` +- Release Artefact: oecore-fbdf93f43ff4b876487e1f26752598ec8abcb46e +- sha: 2d9b5a8e9355b633bb57633cc8c2d319ba13fe4721f79204e61116b3faa6cbf1 +- Download Locations: + http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.5/oecore-fbdf93f43ff4b876487e1f26752598ec8abcb46e.tar.bz2 + http://mirrors.kernel.org/yocto/yocto/yocto-4.0.5/oecore-fbdf93f43ff4b876487e1f26752598ec8abcb46e.tar.bz2 + +meta-mingw + +- Repository Location: :yocto_git:`/meta-mingw` +- Branch: :yocto_git:`kirkstone </meta-mingw/log/?h=kirkstone>` +- Tag: :yocto_git:`yocto-4.0.5 </meta-mingw/log/?h=yocto-4.0.5>` +- Git Revision: :yocto_git:`a90614a6498c3345704e9611f2842eb933dc51c1 </meta-mingw/commit/?id=a90614a6498c3345704e9611f2842eb933dc51c1>` +- Release Artefact: meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1 +- sha: 49f9900bfbbc1c68136f8115b314e95d0b7f6be75edf36a75d9bcd1cca7c6302 +- Download Locations: + http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.5/meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1.tar.bz2 + http://mirrors.kernel.org/yocto/yocto/yocto-4.0.5/meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1.tar.bz2 + +meta-gplv2 + +- Repository Location: :yocto_git:`/meta-gplv2` +- Branch: :yocto_git:`kirkstone </meta-gplv2/log/?h=kirkstone>` +- Tag: :yocto_git:`yocto-4.0.5 </meta-gplv2/log/?h=yocto-4.0.5>` +- Git Revision: :yocto_git:`d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a </meta-gplv2/commit/?id=d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a>` +- Release Artefact: meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a +- sha: c386f59f8a672747dc3d0be1d4234b6039273d0e57933eb87caa20f56b9cca6d +- Download Locations: + http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.5/meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a.tar.bz2 + http://mirrors.kernel.org/yocto/yocto/yocto-4.0.5/meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a.tar.bz2 + +bitbake + +- Repository Location: :oe_git:`/bitbake` +- Branch: :oe_git:`2.0 </bitbake/log/?h=2.0>` +- Tag: :oe_git:`yocto-4.0.5 </bitbake/log/?h=yocto-4.0.5>` +- Git Revision: :oe_git:`c90d57497b9bcd237c3ae810ee8edb5b0d2d575a </bitbake/commit/?id=c90d57497b9bcd237c3ae810ee8edb5b0d2d575a>` +- Release Artefact: bitbake-c90d57497b9bcd237c3ae810ee8edb5b0d2d575a +- sha: 5698d548ce179036e46a24f80b213124c8825a4f443fa1d6be7ab0f70b01a9ff +- Download Locations: + http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.5/bitbake-c90d57497b9bcd237c3ae810ee8edb5b0d2d575a.tar.bz2 + http://mirrors.kernel.org/yocto/yocto/yocto-4.0.5/bitbake-c90d57497b9bcd237c3ae810ee8edb5b0d2d575a.tar.bz2 + +yocto-docs + +- Repository Location: :yocto_git:`/yocto-docs` +- Branch: :yocto_git:`kirkstone </yocto-docs/log/?h=kirkstone>` +- Tag: :yocto_git:`yocto-4.0.5 </yocto-docs/log/?h=yocto-4.0.5>` +- Git Revision: :yocto_git:`8c2f9f54e29781f4ee72e81eeaa12ceaa82dc2d3 </yocto-docs/commit/?id=8c2f9f54e29781f4ee72e81eeaa12ceaa82dc2d3>` + diff --git a/poky/documentation/migration-guides/release-notes-4.0.rst b/poky/documentation/migration-guides/release-notes-4.0.rst index a61ccc6913..d57227502e 100644 --- a/poky/documentation/migration-guides/release-notes-4.0.rst +++ b/poky/documentation/migration-guides/release-notes-4.0.rst @@ -32,7 +32,7 @@ New Features / Enhancements in 4.0 :ref:`overlayfs-etc <ref-classes-overlayfs-etc>` classes and ``overlayroot`` support in the :term:`Initramfs` framework to make it easier to overlay read-only filesystems (for example) with - `OverlayFS <https://en.wikipedia.org/wiki/OverlayFS>`__. + :wikipedia:`OverlayFS <OverlayFS>`. - Inclusive language adjustments to some variable names - see the :ref:`4.0 migration guide <migration-4.0-inclusive-language>` for details. @@ -104,7 +104,7 @@ New Features / Enhancements in 4.0 - Shared state (sstate) improvements: - - Switched to `ZStandard (zstd) <https://en.wikipedia.org/wiki/Zstd>`__ instead + - Switched to :wikipedia:`ZStandard (zstd) <Zstd>` instead of Gzip, for better performance. - Allow validation of sstate signatures against a list of keys - Improved error messages and exception handling @@ -866,7 +866,7 @@ Repositories / Downloads for 4.0 poky -- Repository Location: https://git.yoctoproject.org/git/poky +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`kirkstone </poky/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0 </poky/tag/?h=yocto-4.0>` - Git Revision: :yocto_git:`00cfdde791a0176c134f31e5a09eff725e75b905 </poky/commit/?id=00cfdde791a0176c134f31e5a09eff725e75b905>` @@ -890,7 +890,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/git/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`kirkstone </meta-mingw/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0 </meta-mingw/tag/?h=yocto-4.0>` - Git Revision: :yocto_git:`a90614a6498c3345704e9611f2842eb933dc51c1 </meta-mingw/commit/?id=a90614a6498c3345704e9611f2842eb933dc51c1>` @@ -902,7 +902,7 @@ meta-mingw meta-gplv2 -- Repository Location: https://git.yoctoproject.org/git/meta-gplv2 +- Repository Location: :yocto_git:`/meta-gplv2` - Branch: :yocto_git:`kirkstone </meta-gplv2/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0 </meta-gplv2/tag/?h=yocto-4.0>` - Git Revision: :yocto_git:`d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a </meta-mingw/commit/?id=d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a>` @@ -926,7 +926,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/git/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`kirkstone </yocto-docs/log/?h=kirkstone>` - Tag: :yocto_git:`yocto-4.0 </yocto-docs/tag/?h=yocto-4.0>` - Git Revision: :yocto_git:`a6f571ad5b087385cad8765ed455c4b4eaeebca6 </yocto-docs/commit/?id=a6f571ad5b087385cad8765ed455c4b4eaeebca6>` diff --git a/poky/documentation/migration-guides/release-notes-4.1.rst b/poky/documentation/migration-guides/release-notes-4.1.rst index d4ed23f63d..119cc4fd2e 100644 --- a/poky/documentation/migration-guides/release-notes-4.1.rst +++ b/poky/documentation/migration-guides/release-notes-4.1.rst @@ -704,7 +704,7 @@ Repositories / Downloads for 4.1 poky -- Repository Location: https://git.yoctoproject.org/git/poky +- Repository Location: :yocto_git:`/poky` - Branch: :yocto_git:`langdale </poky/log/?h=langdale>` - Tag: :yocto_git:`yocto-4.1 </poky/log/?h=yocto-4.1>` - Git Revision: :yocto_git:`5200799866b92259e855051112520006e1aaaac0 </poky/commit/?id=5200799866b92259e855051112520006e1aaaac0>` @@ -716,7 +716,7 @@ poky openembedded-core -- Repository Location: https://git.openembedded.org/openembedded-core +- Repository Location: :oe_git:`/openembedded-core` - Branch: :oe_git:`langdale </openembedded-core/log/?h=langdale>` - Tag: :oe_git:`yocto-4.1 </openembedded-core/log/?h=yocto-4.1>` - Git Revision: :oe_git:`744a2277844ec9a384a9ca7dae2a634d5a0d3590 </openembedded-core/commit/?id=744a2277844ec9a384a9ca7dae2a634d5a0d3590>` @@ -728,7 +728,7 @@ openembedded-core meta-mingw -- Repository Location: https://git.yoctoproject.org/git/meta-mingw +- Repository Location: :yocto_git:`/meta-mingw` - Branch: :yocto_git:`langdale </meta-mingw/log/?h=langdale>` - Tag: :yocto_git:`yocto-4.1 </meta-mingw/log/?h=yocto-4.1>` - Git Revision: :yocto_git:`b0067202db8573df3d23d199f82987cebe1bee2c </meta-mingw/commit/?id=b0067202db8573df3d23d199f82987cebe1bee2c>` @@ -740,7 +740,7 @@ meta-mingw bitbake -- Repository Location: https://git.openembedded.org/bitbake +- Repository Location: :oe_git:`/bitbake` - Branch: :oe_git:`2.2 </bitbake/log/?h=2.2>` - Tag: :oe_git:`yocto-4.1 </bitbake/log/?h=yocto-4.1>` - Git Revision: :oe_git:`074da4c469d1f4177a1c5be72b9f3ccdfd379d67 </bitbake/commit/?id=074da4c469d1f4177a1c5be72b9f3ccdfd379d67>` @@ -752,7 +752,7 @@ bitbake yocto-docs -- Repository Location: https://git.yoctoproject.org/git/yocto-docs +- Repository Location: :yocto_git:`/yocto-docs` - Branch: :yocto_git:`langdale </yocto-docs/log/?h=langdale>` - Tag: :yocto_git:`yocto-4.1 </yocto-docs/log/?h=yocto-4.1>` - Git Revision: :yocto_git:`42d3e26a0d04bc5951e640b471686f347dc9b74a </yocto-docs/commit/?id=42d3e26a0d04bc5951e640b471686f347dc9b74a>` diff --git a/poky/documentation/overview-manual/concepts.rst b/poky/documentation/overview-manual/concepts.rst index b323a6fdf4..c495e4cc41 100644 --- a/poky/documentation/overview-manual/concepts.rst +++ b/poky/documentation/overview-manual/concepts.rst @@ -110,7 +110,7 @@ Class files (``.bbclass``) contain information that is useful to share between recipes files. An example is the :ref:`autotools <ref-classes-autotools>` class, which contains common settings for any application that is built with -the `GNU Autotools <https://en.wikipedia.org/wiki/GNU_Autotools>`__. +the :wikipedia:`GNU Autotools <GNU_Autotools>`. The ":ref:`ref-manual/classes:Classes`" chapter in the Yocto Project Reference Manual provides details about classes and how to use them. @@ -2061,7 +2061,7 @@ dependencies, you must manually declare the dependencies. located. For each shared library, the package that contains the shared library is registered as providing the shared library. More specifically, the package is registered as providing the - `soname <https://en.wikipedia.org/wiki/Soname>`__ of the library. The + :wikipedia:`soname <Soname>` of the library. The resulting shared-library-to-package mapping is saved globally in :term:`PKGDATA_DIR` by the :ref:`ref-tasks-packagedata` diff --git a/poky/documentation/overview-manual/development-environment.rst b/poky/documentation/overview-manual/development-environment.rst index 04aea1373c..7d5953db33 100644 --- a/poky/documentation/overview-manual/development-environment.rst +++ b/poky/documentation/overview-manual/development-environment.rst @@ -39,10 +39,9 @@ Linus Torvalds in 1991. Conversely, a good example of a non-open source project is the Windows family of operating systems developed by Microsoft Corporation. -Wikipedia has a good historical description of the Open Source -Philosophy `here <https://en.wikipedia.org/wiki/Open_source>`__. You can -also find helpful information on how to participate in the Linux -Community +Wikipedia has a good :wikipedia:`historical description of the Open Source +Philosophy <Open_source>`. You can also find helpful information on how +to participate in the Linux Community `here <https://www.kernel.org/doc/html/latest/process/index.html>`__. The Development Host @@ -608,18 +607,16 @@ licensing structures in place. License evolution for both Open Source and Free Software has an interesting history. If you are interested in this history, you can find basic information here: -- `Open source license - history <https://en.wikipedia.org/wiki/Open-source_license>`__ +- :wikipedia:`Open source license history <Open-source_license>` -- `Free software license - history <https://en.wikipedia.org/wiki/Free_software_license>`__ +- :wikipedia:`Free software license history <Free_software_license>` In general, the Yocto Project is broadly licensed under the Massachusetts Institute of Technology (MIT) License. MIT licensing permits the reuse of software within proprietary software as long as the license is distributed with that software. Patches to the Yocto Project follow the upstream licensing scheme. You can find information on the -MIT license `here <https://en.wikipedia.org/wiki/MIT_License>`__. +MIT license :wikipedia:`here <MIT_License>`. When you build an image using the Yocto Project, the build process uses a known list of licenses to ensure compliance. You can find this list in diff --git a/poky/documentation/poky.yaml.in b/poky/documentation/poky.yaml.in index 5639f3ca7a..ce67c4d3d3 100644 --- a/poky/documentation/poky.yaml.in +++ b/poky/documentation/poky.yaml.in @@ -13,16 +13,16 @@ YOCTO_RELEASE_DL_URL : "&YOCTO_DL_URL;/releases/yocto/yocto-&DISTRO;" UBUNTU_HOST_PACKAGES_ESSENTIAL : "gawk wget git diffstat unzip texinfo gcc \ build-essential chrpath socat cpio python3 python3-pip python3-pexpect \ xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \ - pylint3 xterm python3-subunit mesa-common-dev zstd liblz4-tool" + python3-subunit mesa-common-dev zstd liblz4-tool" FEDORA_HOST_PACKAGES_ESSENTIAL : "gawk make wget tar bzip2 gzip python3 unzip perl patch \ diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath \ ccache perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue perl-bignum socat \ python3-pexpect findutils which file cpio python python3-pip xz python3-GitPython \ - python3-jinja2 SDL-devel xterm rpcgen mesa-libGL-devel perl-FindBin perl-File-Compare \ + python3-jinja2 SDL-devel rpcgen mesa-libGL-devel perl-FindBin perl-File-Compare \ perl-File-Copy perl-locale zstd lz4" OPENSUSE_HOST_PACKAGES_ESSENTIAL : "python gcc gcc-c++ git chrpath make wget python-xml \ diffstat makeinfo python-curses patch socat python3 python3-curses tar python3-pip \ - python3-pexpect xz which python3-Jinja2 Mesa-libEGL1 libSDL-devel xterm rpcgen Mesa-dri-devel \ + python3-pexpect xz which python3-Jinja2 Mesa-libEGL1 libSDL-devel rpcgen Mesa-dri-devel \ zstd lz4 \n\ $ sudo pip3 install GitPython" CENTOS7_HOST_PACKAGES_ESSENTIAL : "-y epel-release @@ -30,7 +30,7 @@ CENTOS7_HOST_PACKAGES_ESSENTIAL : "-y epel-release \n\ $ sudo yum install gawk make wget tar bzip2 gzip python3 unzip perl patch \ diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath socat \ perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue python3-pip xz \ - which SDL-devel xterm mesa-libGL-devel zstd lz4 + which SDL-devel mesa-libGL-devel zstd lz4 \n\ $ sudo pip3 install GitPython jinja2" CENTOS8_HOST_PACKAGES_ESSENTIAL : "-y epel-release \n\ $ sudo dnf config-manager --set-enabled PowerTools @@ -38,7 +38,7 @@ CENTOS8_HOST_PACKAGES_ESSENTIAL : "-y epel-release \n\ $ sudo dnf install gawk make wget tar bzip2 gzip python3 unzip perl patch \ diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath ccache \ socat perl-Data-Dumper perl-Text-ParseWords perl-Thread-Queue python3-pip \ - python3-GitPython python3-jinja2 python3-pexpect xz which SDL-devel xterm \ + python3-GitPython python3-jinja2 python3-pexpect xz which SDL-devel \ rpcgen mesa-libGL-devel zstd lz4" PIP3_HOST_PACKAGES_DOC : "$ sudo pip3 install sphinx sphinx_rtd_theme pyyaml" MIN_PYTHON_VERSION : "3.6.0" diff --git a/poky/documentation/ref-manual/classes.rst b/poky/documentation/ref-manual/classes.rst index 3b33783c58..ffa3e50ab6 100644 --- a/poky/documentation/ref-manual/classes.rst +++ b/poky/documentation/ref-manual/classes.rst @@ -85,7 +85,7 @@ about the variable flags (varflags) that help control archive creation. ====================== The :ref:`autotools* <ref-classes-autotools>` classes support packages built with the -`GNU Autotools <https://en.wikipedia.org/wiki/GNU_Autotools>`__. +:wikipedia:`GNU Autotools <GNU_Autotools>`. The ``autoconf``, ``automake``, and ``libtool`` packages bring standardization. This class defines a set of tasks (e.g. ``configure``, @@ -373,8 +373,26 @@ support. ``create-spdx.bbclass`` ======================= -The :ref:`create-spdx <ref-classes-create-spdx>` class provides support for automatically creating -SPDX SBoM documents based upon image and SDK contents. +The :ref:`create-spdx <ref-classes-create-spdx>` class provides support for +automatically creating :term:`SPDX` :term:`SBOM` documents based upon image +and SDK contents. + +This class is meant to be inherited globally from a configuration file:: + + INHERIT += "create-spdx" + +The toplevel :term:`SPDX` output file is generated in JSON format as a +``IMAGE-MACHINE.spdx.json`` file in ``tmp/deploy/images/MACHINE/`` inside the +:term:`Build Directory`. There are other related files in the same directory, +as well as in ``tmp/deploy/spdx``. + +The exact behaviour of this class, and the amount of output can be controlled +by the :term:`SPDX_PRETTY`, :term:`SPDX_ARCHIVE_PACKAGED`, +:term:`SPDX_ARCHIVE_SOURCES` and :term:`SPDX_INCLUDE_SOURCES` variables. + +See the description of these variables and the +":ref:`dev-manual/common-tasks:creating a software bill of materials`" +section in the Yocto Project Development Manual for more details. .. _ref-classes-cross: @@ -723,8 +741,8 @@ class. .. _ref-classes-github-releases: -``github-releases`` -=================== +``github-releases.bbclass`` +=========================== For recipes that fetch release tarballs from github, the :ref:`github-releases <ref-classes-github-releases>` class sets up a standard way for checking available upstream versions @@ -959,7 +977,7 @@ Yocto Project Overview and Concepts Manual. The :ref:`image-buildinfo <ref-classes-image-buildinfo>` class writes a plain text file containing build information to the target filesystem at ``${sysconfdir}/buildinfo`` -by default (as specified by :term:`IMAGE_BUILDINFO_FILE`. +by default (as specified by :term:`IMAGE_BUILDINFO_FILE`). This can be useful for manually determining the origin of any given image. It writes out two sections: @@ -1586,6 +1604,27 @@ The :ref:`mime <ref-classes-mime>` class generates the proper post-install and p These scriptlets call ``update-mime-database`` to add the MIME types to the shared database. +.. _ref-classes-mime-xdg: + +``mime-xdg.bbclass`` +==================== + +The :ref:`mime-xdg <ref-classes-mime-xdg>` class generates the proper +post-install and post-remove (postinst/postrm) scriptlets for packages +that install ``.desktop`` files containing ``MimeType`` entries. +These scriptlets call ``update-desktop-database`` to add the MIME types +to the database of MIME types handled by desktop files. + +Thanks to this class, when users open a file through a file browser +on recently created images, they don't have to choose the application +to open the file from the pool of all known applications, even the ones +that cannot open the selected file. + +If you have recipes installing their ``.desktop`` files as absolute +symbolic links, the detection of such files cannot be done by the current +implementation of this class. In this case, you have to add the corresponding +package names to the :term:`MIME_XDG_PACKAGES` variable. + .. _ref-classes-mirrors: ``mirrors.bbclass`` @@ -1736,8 +1775,8 @@ is not needed. ``npm.bbclass`` =============== -Provides support for building Node.js software fetched using the `node -package manager (NPM) <https://en.wikipedia.org/wiki/Npm_(software)>`__. +Provides support for building Node.js software fetched using the +:wikipedia:`node package manager (NPM) <Npm_(software)>`. .. note:: diff --git a/poky/documentation/ref-manual/features.rst b/poky/documentation/ref-manual/features.rst index a5b01e8df7..71d3c5e2aa 100644 --- a/poky/documentation/ref-manual/features.rst +++ b/poky/documentation/ref-manual/features.rst @@ -126,10 +126,9 @@ metadata, as extra layers can define their own: - *3g:* Include support for cellular data. -- *acl:* Include - `Access Control List <https://en.wikipedia.org/wiki/Access-control_list>`__ support. +- *acl:* Include :wikipedia:`Access Control List <Access-control_list>` support. -- *alsa:* Include `Advanced Linux Sound Architecture <https://en.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture>`__ +- *alsa:* Include :wikipedia:`Advanced Linux Sound Architecture <Advanced_Linux_Sound_Architecture>` support (OSS compatibility kernel modules installed if available). - *api-documentation:* Enables generation of API documentation during @@ -167,7 +166,7 @@ metadata, as extra layers can define their own: - *multiarch:* Enable building applications with multiple architecture support. -- *ld-is-gold:* Use the `gold <https://en.wikipedia.org/wiki/Gold_(linker)>`__ +- *ld-is-gold:* Use the :wikipedia:`gold <Gold_(linker)>` linker instead of the standard GCC linker (bfd). - *ldconfig:* Include support for ldconfig and ``ld.so.conf`` on the @@ -190,14 +189,14 @@ metadata, as extra layers can define their own: - *overlayfs:* Include `OverlayFS <https://docs.kernel.org/filesystems/overlayfs.html>`__ support. -- *pam:* Include `Pluggable Authentication Module (PAM) <https://en.wikipedia.org/wiki/Pluggable_authentication_module>`__ +- *pam:* Include :wikipedia:`Pluggable Authentication Module (PAM) <Pluggable_authentication_module>` support. - *pci:* Include PCI bus support. - *pcmcia:* Include PCMCIA/CompactFlash support. -- *polkit:* Include `Polkit <https://en.wikipedia.org/wiki/Polkit>`__ support. +- *polkit:* Include :wikipedia:`Polkit <Polkit>` support. - *ppp:* Include PPP dialup support. @@ -210,11 +209,11 @@ metadata, as extra layers can define their own: `PulseAudio <https://www.freedesktop.org/wiki/Software/PulseAudio/>`__. - *selinux:* Include support for - `Security-Enhanced Linux (SELinux) <https://en.wikipedia.org/wiki/Security-Enhanced_Linux>`__ + :wikipedia:`Security-Enhanced Linux (SELinux) <Security-Enhanced_Linux>` (requires `meta-selinux <https://layers.openembedded.org/layerindex/layer/meta-selinux/>`__). - *seccomp:* Enables building applications with - `seccomp <https://en.wikipedia.org/wiki/Seccomp>`__ support, to + :wikipedia:`seccomp <Seccomp>` support, to allow them to strictly restrict the system calls that they are allowed to invoke. @@ -236,11 +235,10 @@ metadata, as extra layers can define their own: directories into their respective counterparts in the ``/usr`` directory to provide better package and application compatibility. -- *vfat:* Include `FAT filesystem <https://en.wikipedia.org/wiki/File_Allocation_Table>`__ +- *vfat:* Include :wikipedia:`FAT filesystem <File_Allocation_Table>` support. -- *vulkan:* Include support for the - `Vulkan API <https://en.wikipedia.org/wiki/Vulkan>`__. +- *vulkan:* Include support for the :wikipedia:`Vulkan API <Vulkan>`. - *wayland:* Include the Wayland display server protocol and the library that supports it. @@ -250,7 +248,7 @@ metadata, as extra layers can define their own: - *x11:* Include the X server and libraries. - *xattr:* Include support for - `extended file attributes <https://en.wikipedia.org/wiki/Extended_file_attributes>`__. + :wikipedia:`extended file attributes <Extended_file_attributes>`. - *zeroconf:* Include support for `zero configuration networking <https://en.wikipedia.org/wiki/Zero-configuration_networking>`__. diff --git a/poky/documentation/ref-manual/kickstart.rst b/poky/documentation/ref-manual/kickstart.rst index 48bba58995..11bc373b3c 100644 --- a/poky/documentation/ref-manual/kickstart.rst +++ b/poky/documentation/ref-manual/kickstart.rst @@ -177,7 +177,7 @@ the ``part`` and ``partition`` commands: - ``--part-type``: This option is a Wic-specific option that specifies the partition type globally unique identifier (GUID) for GPT partitions. You can find the list of partition type GUIDs at - https://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs. + :wikipedia:`GUID_Partition_Table#Partition_type_GUIDs`. - ``--use-uuid``: This option is a Wic-specific option that causes Wic to generate a random GUID for the partition. The generated diff --git a/poky/documentation/ref-manual/qa-checks.rst b/poky/documentation/ref-manual/qa-checks.rst index fb31dc16f9..3947dcfc17 100644 --- a/poky/documentation/ref-manual/qa-checks.rst +++ b/poky/documentation/ref-manual/qa-checks.rst @@ -590,10 +590,10 @@ Errors and Warnings - ``package contains desktop file with key 'MimeType' but does not inhert mime-xdg: <packagename> path '<file>' [mime-xdg]`` The specified package contains a .desktop file with a 'MimeType' key - present, but does not inherit the mime-xdg class that is required in - order for that to be activated. Either add ``inherit mime`` to the - recipe or remove the files at the :ref:`ref-tasks-install` step if they are not - needed. + present, but does not inherit the :ref:`mime-xdg <ref-classes-mime-xdg>` + class that is required in order for that to be activated. Either add + ``inherit mime`` to the recipe or remove the files at the + :ref:`ref-tasks-install` step if they are not needed. .. _qa-check-src-uri-bad: diff --git a/poky/documentation/ref-manual/terms.rst b/poky/documentation/ref-manual/terms.rst index 40209528ba..51f6e79200 100644 --- a/poky/documentation/ref-manual/terms.rst +++ b/poky/documentation/ref-manual/terms.rst @@ -321,6 +321,23 @@ universal, the list includes them just in case: :term:`build host<Build Host>` and other components, that can work on specific hardware. + :term:`SBOM` + This term means *Software Bill of Materials*. When you distribute + software, it offers a description of all the components you used, + their corresponding licenses, their dependencies, the changes that were + applied and the known vulnerabilities that were fixed. + + This can be used by the recipients of the software to assess + their exposure to license compliance and security vulnerability issues. + + See the :wikipedia:`Software Supply Chain <Software_supply_chain>` + article on Wikipedia for more details. + + The OpenEmbedded Build System can generate such documentation for your + project, in :term:`SPDX` format, based on all the metadata it used to + build the software images. See the ":ref:`dev-manual/common-tasks:creating + a software bill of materials`" section of the Development Tasks manual. + :term:`Source Directory` This term refers to the directory structure created as a result of creating a local copy of the ``poky`` Git @@ -381,6 +398,17 @@ universal, the list includes them just in case: ":ref:`overview-manual/development-environment:repositories, tags, and branches`" section in the Yocto Project Overview and Concepts Manual. + :term:`SPDX` + This term means *Software Package Data Exchange*, and is used as a open + standard for providing a *Software Bill of Materials* (:term:`SBOM`). + This standard is developed through a `Linux Foundation project + <https://spdx.dev/>`__ and is used by the OpenEmbedded Build System to + provide an :term:`SBOM` associated to each a software image. + + For details, see Wikipedia's :wikipedia:`SPDX page <Software_Package_Data_Exchange>` + and the ":ref:`dev-manual/common-tasks:creating a software bill of materials`" + section of the Development Tasks manual. + :term:`Sysroot` When cross-compiling, the target file system may be differently laid out and contain different things compared to the host system. The concept diff --git a/poky/documentation/ref-manual/variables.rst b/poky/documentation/ref-manual/variables.rst index dc6eccb314..d3aae63308 100644 --- a/poky/documentation/ref-manual/variables.rst +++ b/poky/documentation/ref-manual/variables.rst @@ -530,6 +530,33 @@ system and gives an overview of their function and contents. ":ref:`dev-manual/common-tasks:speeding up a build`" section in the Yocto Project Development Tasks Manual. + On the other hand, if your goal is to limit the amount of system + resources consumed by BitBake tasks, setting :term:`BB_NUMBER_THREADS` + to a number lower than the number of CPU threads in your machine + won't be sufficient. That's because each package will still be built + and installed through a number of parallel jobs specified by the + :term:`PARALLEL_MAKE` variable, which is by default the number of CPU + threads in your system, and is not impacted by the + :term:`BB_NUMBER_THREADS` value. + + So, if you set :term:`BB_NUMBER_THREADS` to "1" but don't set + :term:`PARALLEL_MAKE`, most of your system resources will be consumed + anyway. + + Therefore, if you intend to reduce the load of your build system by + setting :term:`BB_NUMBER_THREADS` to a relatively low value compared + to the number of CPU threads on your system, you should also set + :term:`PARALLEL_MAKE` to a similarly low value. + + An alternative to using :term:`BB_NUMBER_THREADS` to keep the usage + of build system resources under control is to use the smarter + :term:`BB_PRESSURE_MAX_CPU`, :term:`BB_PRESSURE_MAX_IO` or + :term:`BB_PRESSURE_MAX_MEMORY` controls. They will prevent BitBake + from starting new tasks as long as thresholds are exceeded. Anyway, + as with :term:`BB_NUMBER_THREADS`, such controls won't prevent the + tasks already being run from using all CPU threads on the system + if :term:`PARALLEL_MAKE` is not set to a low value. + :term:`BB_SERVER_TIMEOUT` Specifies the time (in seconds) after which to unload the BitBake server due to inactivity. Set :term:`BB_SERVER_TIMEOUT` to determine how @@ -3699,8 +3726,8 @@ system and gives an overview of their function and contents. :term:`Initramfs` An Initial RAM Filesystem (:term:`Initramfs`) is an optionally compressed - `cpio <https://en.wikipedia.org/wiki/Cpio>`__ archive which is extracted - by the Linux kernel into RAM in a special `tmpfs <https://en.wikipedia.org/wiki/Tmpfs>`__ + :wikipedia:`cpio <Cpio>` archive which is extracted + by the Linux kernel into RAM in a special :wikipedia:`tmpfs <Tmpfs>` instance, used as the initial root filesystem. This is a replacement for the legacy init RAM disk ("initrd") @@ -3756,7 +3783,7 @@ system and gives an overview of their function and contents. ``meta/conf/bitbake.conf`` configuration file in the :term:`Source Directory`, is "cpio.gz". The Linux kernel's :term:`Initramfs` mechanism, as opposed to the initial RAM filesystem - `initrd <https://en.wikipedia.org/wiki/Initrd>`__ mechanism, expects + :wikipedia:`initrd <Initrd>` mechanism, expects an optionally compressed cpio archive. :term:`INITRAMFS_IMAGE` @@ -4894,6 +4921,13 @@ system and gives an overview of their function and contents. The revision currently checked out for the OpenEmbedded-Core layer (path determined by :term:`COREBASE`). + :term:`MIME_XDG_PACKAGES` + The current implementation of the :ref:`mime-xdg <ref-classes-mime-xdg>` + class cannot detect ``.desktop`` files installed through absolute + symbolic links. Use this setting to make the class create post-install + and post-remove scripts for these packages anyway, to invoke the + ``update-destop-database`` command. + :term:`MIRRORS` Specifies additional paths from which the OpenEmbedded build system gets source code. When the build system searches for source code, it @@ -5784,17 +5818,20 @@ system and gives an overview of their function and contents. desired splitting. :term:`PARALLEL_MAKE` - Extra options passed to the ``make`` command during the - :ref:`ref-tasks-compile` task in order to specify - parallel compilation on the local build host. This variable is - usually in the form "-j x", where x represents the maximum number of - parallel threads ``make`` can run. + + Extra options passed to the build tool command (``make``, + ``ninja`` or more specific build engines, like the Go language one) + during the :ref:`ref-tasks-compile` task, to specify parallel compilation + on the local build host. This variable is usually in the form "-j x", + where x represents the maximum number of parallel threads such engines + can run. .. note:: - In order for :term:`PARALLEL_MAKE` to be effective, ``make`` must be - called with ``${``\ :term:`EXTRA_OEMAKE`\ ``}``. An easy way to ensure - this is to use the ``oe_runmake`` function. + For software compiled by ``make``, in order for :term:`PARALLEL_MAKE` + to be effective, ``make`` must be called with + ``${``\ :term:`EXTRA_OEMAKE`\ ``}``. An easy + way to ensure this is to use the ``oe_runmake`` function. By default, the OpenEmbedded build system automatically sets this variable to be equal to the number of cores the build system uses. @@ -5819,15 +5856,16 @@ system and gives an overview of their function and contents. section in the Yocto Project Development Tasks Manual. :term:`PARALLEL_MAKEINST` - Extra options passed to the ``make install`` command during the - :ref:`ref-tasks-install` task in order to specify + Extra options passed to the build tool install command + (``make install``, ``ninja install`` or more specific ones) + during the :ref:`ref-tasks-install` task in order to specify parallel installation. This variable defaults to the value of :term:`PARALLEL_MAKE`. .. note:: - In order for :term:`PARALLEL_MAKEINST` to be effective, ``make`` must - be called with + For software compiled by ``make``, in order for :term:`PARALLEL_MAKEINST` + to be effective, ``make`` must be called with ``${``\ :term:`EXTRA_OEMAKE`\ ``}``. An easy way to ensure this is to use the ``oe_runmake`` function. @@ -7284,6 +7322,88 @@ system and gives an overview of their function and contents. You can specify only a single URL in :term:`SOURCE_MIRROR_URL`. + :term:`SPDX_ARCHIVE_PACKAGED` + This option allows to add to :term:`SPDX` output compressed archives + of the files in the generated target packages. + + Such archives are available in + ``tmp/deploy/spdx/MACHINE/packages/packagename.tar.zst`` + under the :term:`Build Directory`. + + Enable this option as follows:: + + SPDX_ARCHIVE_PACKAGED = "1" + + According to our tests on release 4.1 "langdale", building + ``core-image-minimal`` for the ``qemux86-64`` machine, enabling this + option multiplied the size of the ``tmp/deploy/spdx`` directory by a + factor of 13 (+1.6 GiB for this image), compared to just using the + :ref:`create-spdx <ref-classes-create-spdx>` class with no option. + + Note that this option doesn't increase the size of :term:`SPDX` + files in ``tmp/deploy/images/MACHINE``. + + :term:`SPDX_ARCHIVE_SOURCES` + This option allows to add to :term:`SPDX` output compressed archives + of the sources for packages installed on the target. It currently + only works when :term:`SPDX_INCLUDE_SOURCES` is set. + + This is one way of fulfilling "source code access" license + requirements. + + Such source archives are available in + ``tmp/deploy/spdx/MACHINE/recipes/recipe-packagename.tar.zst`` + under the :term:`Build Directory`. + + Enable this option as follows:: + + SPDX_INCLUDE_SOURCES = "1" + SPDX_ARCHIVE_SOURCES = "1" + + According to our tests on release 4.1 "langdale", building + ``core-image-minimal`` for the ``qemux86-64`` machine, enabling + these options multiplied the size of the ``tmp/deploy/spdx`` + directory by a factor of 11 (+1.4 GiB for this image), + compared to just using the :ref:`create-spdx <ref-classes-create-spdx>` + class with no option. + + Note that using this option only marginally increases the size + of the :term:`SPDX` output in ``tmp/deploy/images/MACHINE/`` + (+ 0.07\% with the tested image), compared to just enabling + :term:`SPDX_INCLUDE_SOURCES`. + + :term:`SPDX_INCLUDE_SOURCES` + This option allows to add a description of the source files used to build + the host tools and the target packages, to the ``spdx.json`` files in + ``tmp/deploy/spdx/MACHINE/recipes/`` under the :term:`Build Directory`. + As a consequence, the ``spdx.json`` files under the ``by-namespace`` and + ``packages`` subdirectories in ``tmp/deploy/spdx/MACHINE`` are also + modified to include references to such source file descriptions. + + Enable this option as follows:: + + SPDX_INCLUDE_SOURCES = "1" + + According to our tests on release 4.1 "langdale", building + ``core-image-minimal`` for the ``qemux86-64`` machine, enabling + this option multiplied the total size of the ``tmp/deploy/spdx`` + directory by a factor of 3 (+291 MiB for this image), + and the size of the ``IMAGE-MACHINE.spdx.tar.zst`` in + ``tmp/deploy/images/MACHINE`` by a factor of 130 (+15 MiB for this + image), compared to just using the + :ref:`create-spdx <ref-classes-create-spdx>` class with no option. + + :term:`SPDX_PRETTY` + This option makes the SPDX output more human-readable, using + identation and newlines, instead of the default output in a + single line:: + + SPDX_PRETTY = "1" + + The generated SPDX files are approximately 20% bigger, but + this option is recommended if you want to inspect the SPDX + output files with a text editor. + :term:`SPDXLICENSEMAP` Maps commonly used license names to their SPDX counterparts found in ``meta/files/common-licenses/``. For the default :term:`SPDXLICENSEMAP` diff --git a/poky/documentation/sdk-manual/appendix-customizing.rst b/poky/documentation/sdk-manual/appendix-customizing.rst index d6bca44947..66218fccd6 100644 --- a/poky/documentation/sdk-manual/appendix-customizing.rst +++ b/poky/documentation/sdk-manual/appendix-customizing.rst @@ -176,9 +176,8 @@ the installed SDKs to update the installed SDKs by using the ``devtool sdk-update`` command: 1. Create a directory that can be shared over HTTP or HTTPS. You can do - this by setting up a web server such as an `Apache HTTP - Server <https://en.wikipedia.org/wiki/Apache_HTTP_Server>`__ or - `Nginx <https://en.wikipedia.org/wiki/Nginx>`__ server in the cloud + this by setting up a web server such as an :wikipedia:`Apache HTTP Server + <Apache_HTTP_Server>` or :wikipedia:`Nginx <Nginx>` server in the cloud to host the directory. This directory must contain the published SDK. 2. Set the @@ -262,9 +261,8 @@ source, you need to do a number of things: 2. Expose the ``sstate-cache`` directory produced by the build. Typically, you expose this directory by making it available through - an `Apache HTTP - Server <https://en.wikipedia.org/wiki/Apache_HTTP_Server>`__ or - `Nginx <https://en.wikipedia.org/wiki/Nginx>`__ server. + an :wikipedia:`Apache HTTP Server <Apache_HTTP_Server>` or + :wikipedia:`Nginx <Nginx>` server. 3. Set the appropriate configuration so that the produced SDK knows how to find the configuration. The variable you need to set is diff --git a/poky/documentation/sdk-manual/working-projects.rst b/poky/documentation/sdk-manual/working-projects.rst index 91d8d6ad93..0eddee08e3 100644 --- a/poky/documentation/sdk-manual/working-projects.rst +++ b/poky/documentation/sdk-manual/working-projects.rst @@ -11,9 +11,9 @@ Autotools-Based Projects ======================== Once you have a suitable :ref:`sdk-manual/intro:the cross-development toolchain` -installed, it is very easy to develop a project using the `GNU -Autotools-based <https://en.wikipedia.org/wiki/GNU_Build_System>`__ -workflow, which is outside of the :term:`OpenEmbedded Build System`. +installed, it is very easy to develop a project using the :wikipedia:`GNU +Autotools-based <GNU_Build_System>` workflow, which is outside of the +:term:`OpenEmbedded Build System`. The following figure presents a simple Autotools workflow. diff --git a/poky/documentation/test-manual/intro.rst b/poky/documentation/test-manual/intro.rst index 36958d00ad..0831f80466 100644 --- a/poky/documentation/test-manual/intro.rst +++ b/poky/documentation/test-manual/intro.rst @@ -74,8 +74,7 @@ simple JSON files. The project uses Buildbot for historical reasons but also because many of the project developers have knowledge of Python. It is possible to use the outer layers from another Continuous Integration - (CI) system such as - `Jenkins <https://en.wikipedia.org/wiki/Jenkins_(software)>`__ + (CI) system such as :wikipedia:`Jenkins <Jenkins_(software)>` instead of Buildbot. The following figure shows the Yocto Project Autobuilder stack with a diff --git a/poky/documentation/toaster-manual/reference.rst b/poky/documentation/toaster-manual/reference.rst index b181d12d86..f8aabeed04 100644 --- a/poky/documentation/toaster-manual/reference.rst +++ b/poky/documentation/toaster-manual/reference.rst @@ -28,8 +28,7 @@ at :oe_layerindex:`/`. You can find the code for this layer index's web application at :yocto_git:`/layerindex-web/`. When you tie a layer source into Toaster, it can query the layer source -through a -`REST <https://en.wikipedia.org/wiki/Representational_state_transfer>`__ +through a :wikipedia:`REST <Representational_state_transfer>` API, store the information about the layers in the Toaster database, and then show the information to users. Users are then able to view that information and build layers from Toaster itself without having to @@ -369,8 +368,8 @@ Remote Toaster Monitoring Toaster has an API that allows remote management applications to directly query the state of the Toaster server and its builds in a machine-to-machine manner. This API uses the -`REST <https://en.wikipedia.org/wiki/Representational_state_transfer>`__ -interface and the transfer of JSON files. For example, you might monitor +:wikipedia:`REST <Representational_state_transfer>` interface and the +transfer of JSON files. For example, you might monitor a build inside a container through well supported known HTTP ports in order to easily access a Toaster server inside the container. In this example, when you use this direct JSON API, you avoid having web page |