Yogita Urade 4e24d7f64b ruby: upgrade 3.3.4 -> 3.3.5
Includes fix for CVE-2024-41123 & CVE-2024-41946

Changelog
=========
d3ab7be8ca merge revision(s) 657f4b99f61: [Backport #20667]
c69d59e9b2 Sync tool/lib/core_assertions.rb from master
cf9a6c2b63 merge revision(s) a3562c2a0abf1c2bdd1d50377b4f929580782594: [Backport #20701]
d83b5633b1 merge revision(s) 992596fb7af18a7f472589a607d0eb3fbb03b49a: [Backport #20344]
b210c86a02 merge revision(s) 97449338d6cb42d9dd7c9ca61550616e7e6b6ef6: [Backport #20649]
6a4e79533b merge revision(s) 1870505f478cc75993b296b7144a45137ace6937: [Backport #20651]
e0e23e7d5e merge revision(s) 29500e30346: [Backport #20667]
7b954e7bc6 Allow failures in Travis ppc64le and s390x
937964f346 Merge URI-0.13.1 for Ruby 3.3 (#11466)
ac8d50e52e [Backport 3.3] [Bug #20691] Fix use-after-free in WeakKeyMap#clear (#11443)
8657de70aa [Backport 3.3] [Bug #20688] Fix use-after-free for WeakMap and WeakKeyMap (#11439)
9ae91eb2aa Backport warning feature for bundled gems from master (#11420)
66312ad913 Re-initialize vm->ractor.sched.lock after fork (#11372)
4d11a0960d Added bootstrap job for release workflow
65cca99b30 parse.y: const_decl_path don't replace destination node by a literal (#11314)
f85c7deacc Update RubyGems 3.5.16 and Bundler 2.5.16 for Ruby 3.3 (#11252)
0922afa95b [Bug #20654] Fix floor and ceil when ndigits is large (#11277)
ce565cd4b8 [Bug #20653] Fix memory leak in String#start_with? when regexp times out (#11255)
6d744837ab [Bug #20088] Fix ARCH_FLAG for cross compiling
7571ad42f4 [Bug #20650] Fix memory leak in Regexp capture group when timeout (#11244)
4667f8ec10 bundled_gems.rb: Add a fast path (#11221)
425e468d25 [Backport #20633] Fix the condition for `atomic_signal_fence` (#11166)
3427a1679a retry on cancelling of `getaddrinfo` (#11131)

(From OE-Core rev: 0291e93cc1457aa4e214c2bf730447178eb07c04)

Signed-off-by: Yogita Urade <yogita.urade@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2024-09-30 17:00:50 +01:00
2024-09-30 17:00:50 +01:00
2024-09-30 17:00:50 +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 251 MiB