Wang Mingyu 0dbf873a5c bind: upgrade 9.18.25 -> 9.18.26
Changelog:
============
- Add RESOLVER.ARPA to the built in empty zones.
- dig/mdig +ednsflags=<non-zero-value> did not re-enable
  EDNS if it had been disabled.
- Some invalid ISO 8601 durations were accepted
  erroneously.
- Don't return static-stub synthesised NS RRset.
- Fix bug in Depends (keymgr_dep) function.
- Support for the RESINFO record type has been added.
- Cleaned up several minor bugs in the RBTDB dbiterator
  implementation.
- Added missing dns_rdataset_disassociate calls in
 validator.c:findnsec3proofs.
- Fix incorrectly reported errors when running tests
 with `make test` on platforms with older pytest.
- Optimize slabheader placement, so the infrastructure
 records are put in the beginning of the slabheader
 linked list.
- Improve ARM parental-agents definition.
- Fix the DNS_GETDB_STALEFIRST flag, which was defined
 incorrectly in lib/ns/query.c.
- Update ZSK minimum lifetime documentation in ARM, also
 depends on signing delay.
- Add workaround to enforce dynamic linker to pull
 jemalloc earlier than libc to ensure all memory
 allocations are done via jemalloc.
- Changes to "listen-on" statements were ignored on
 reconfiguration unless the port or interface address was
 changed, making it impossible to change a related
 listener transport type. Thanks to Thomas Amgarten.
- Expose the TCP client count in statistics channel.
- Fix a possible crash in 'dig +nssearch +nofail' and
 'host -C' commands when one of the name servers returns
 SERVFAIL.
- When dnssec-policy is in effect the DNSKEY's TTLs in
 the zone where not being updated to match the policy.
 This lead to failures when DNSKEYs where updated as the
 TTLs mismatched.

(From OE-Core rev: 9dc097f240c5ab7703179f480f538be8e21defce)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-04-25 10:06:02 +01:00
2024-04-25 10:06:02 +01:00
2024-02-19 11:34:33 +00:00
2021-07-19 18:07:21 +01:00
2023-10-19 11:31:13 +01:00

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/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

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.

CII Best Practices

Description
No description provided
Readme 249 MiB