mirror of https://git.yoctoproject.org/poky synced 2026-02-07 09:16:36 +01:00

Go to file

Wang Mingyu f0f4ed9ba5 bind: upgrade 9.18.12 -> 9.18.13

Changelog:
==========
[bug] Use two pairs of dns_db_t and dns_dbversion_t in a
      catalog zone structure to avoid a race between the
      dns__catz_update_cb() and dns_catz_dbupdate_callback()
      functions. [GL #3907]

[bug] Make sure to revert the reconfigured zones to the
      previous version of the view, when the new view
      reconfiguration fails during the configuration of
      one of the configured zones. [GL #3911]

[bug] Fix error path cleanup issues in dns_catz_new_zones()
      and dns_catz_new_zone() functions. [GL #3900]

[bug] Unregister db update notify callback before detaching
      from the previous db inside the catz update notify
      callback. [GL #3777]

[func Run the catalog zone update process on the offload
      threads. [GL #3881]

[func Add shutdown signaling for catalog zones. [GL !7571]

[func Add reference count tracing for dns_catz_zone_t and
      dns_catz_zones_t. [GL !7570]

[bug] Detach 'rpzs' and 'catzs' from the previous view in
      configure_rpz() and configure_catz(), respectively,
      just after attaching it to the new view. [GL #3880]

[test Don't test HMAC-MD5 when not supported by libcrypto.
      [GL #3871]

[bug] Fix RPZ reference counting error on shutdown in
      dns__rpz_timer_cb(). [GL #3866]

[test Test various 'islands of trust' configurations when
      using managed keys. [GL #3662]

[bug] Building against (or running with) libuv versions
      1.35.0 and 1.36.0 is now a fatal error.  The rules for
      mixing and matching compile-time and run-time libuv
      versions have been tightened for libuv versions between
      1.35.0 and 1.40.0. [GL #3840]

[bug] dnssec-cds failed to cleanup properly. [GL #3831]

[bug] Source ports configured for query-source,
      transfer-source, etc, were being ignored. (This
      feature is deprecated, but it is not yet removed,
      so the bug still needed fixing.) [GL #3790]

(From OE-Core rev: 51ab191224aa1320d622bf79184940afa3910d60)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2023-04-13 11:56:07 +01:00

bitbake

bitbake: fetch2/crate: create versioned 'name' entries

2023-04-06 14:28:59 +01:00

contrib

contrib/git-hooks: add a sendemail-validate example hook that adds FROM: lines to outgoing patch emails

2020-12-30 14:01:07 +00:00

documentation

manuals: improve and fix target for supported distros

2023-04-06 14:35:18 +01:00

README.md

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

The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.

A guide to submitting patches to OpenEmbedded is available at:

https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

There is good documentation on how to write/format patches at:

https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

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.