114c0a6c37
Changelog: =========== -Fixed issue where "InsecureRequestWarning" was emitted for HTTPS connections when using Emscripten. -Fixed "HTTPConnectionPool.urlopen" to stop automatically casting non-proxy headers to "HTTPHeaderDict". -Changed "InvalidChunkLength" to "ProtocolError" when response terminates before the chunk length is sent. -Changed "ProtocolError" to be more verbose on incomplete reads with excess content. -Added support for 'Emscripten and Pyodide -Added support for "HTTPResponse.read1()" method. -Added rudimentary support for HTTP/2. -Fixed issue where requests against urls with trailing dots were failing due to SSL errors when using proxy. -Fixed "HTTPConnection.proxy_is_verified" and "HTTPSConnection.proxy_is_verified" to be always set to a boolean after connecting to a proxy. It could be "None" in some cases previously. -Fixed an issue where "headers" passed in a request with "json=" would be mutated -Fixed "HTTPSConnection.is_verified" to be set to "False" when connecting from a HTTPS proxy to an HTTP target. It was set to "True" previously. -Fixed handling of new error message from OpenSSL 3.2.0 when configuring an HTTP proxy as HTTPS -Fixed TLS 1.3 post-handshake auth when the server certificate validation is disabled -Note for downstream distributors: To run integration tests, you now need to run the tests a second time with the "--integration" pytest flag. (From OE-Core rev: c1968ceeddbad57bc86aaa23a705093c353d3bc9) Signed-off-by: Wang Mingyu <wangmy@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.