12a62d57b3
0001-fix-compile-failure-with-musl.patch relocate.patch refreshed for 2.5.2 Changelog: ============ * gpg: Add option 16 to --full-gen-key to create ECC+Kyber. * gpg: For composite algos add the algo string to the colons listings. * gpg: Validate the trustdb after the import of a trusted key. * gpg: Exclude expired trusted keys from the key validation process. * gpg: Fix a wrong decryption failed status for signed and OCB encrypted messages without a signature verification key. * gpg: Retain binary representation for import->export with Ed25519 key signatures. * gpg: Fix comparing ed448 to ed25519 with --assert-pubkey-algo. * gpg: Avoid a failure exit code for expired ultimately trusted keys. * gpg: Emit status error for an invalid ADSK. * gpg: Allow the use of an ADSK subkey as ADSK subkey. * gpg: Fix --quick-set-expire for V5 subkey fingerprints. * gpg: Robust error handling for SCD READKEY. * gpg: Fix cv25519 v5 export regression. * gpgsm: Nearly fourfold speedup of validated certificate listings. * gpgsm: Improvement for some rare P12 files. * gpgsm: Terminate key listing on output write error. * agent: Add option --status to the LISTRUSTED command. * agent: Fix detection of the yet unused trustflag de-vs. * agent: Allow ssh to sign data larger than the Assuan line length. * keyboxd: Fix a race condition on the database handle. * dirmngr: A list of used URLs for loaded CRLs is printed first in the output of the LISTCRL command. * scd: More mitigations against lock ups with multiple cards or apps. * gpgtar: Use log-file from common.conf only in --batch mode. * gpgtar: Fix directory creation during extraction. * gpg-mail-tube: Minor fixes. * gpgconf: Add list flag to trusted-key et al. * Implement GNUPG_ASSUME_COMPLIANCE envvar and registry key for testing de-vs compliance mode. * Enable additional runtime protections in speedo builds for windows. * Fix a race condition in creating the socket directory. * Fix a build problem on macOS (missing unistd.h). (From OE-Core rev: 2ab817c434ac443e29d66105056675d6256e8a2c) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.