linux/meta-virtualization.git/recipes-devtools/python, branch kirkstone

python3-docker: Fix for requests 2.32.0: CVE-2024-35195 backport

2025-04-19T22:49:36+00:00

After backporting the CVE-2024-35195 in poky, parts of python3-requests got updated to 2.32.0 which is incompatible with the current docker-compose command. This patch will fix the following error message: During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/docker-compose", line 8, in sys.exit(main()) File "/usr/lib/python3.10/site-packages/compose/cli/main.py", line 81, in main command_func() File "/usr/lib/python3.10/site-packages/compose/cli/main.py", line 200, in perform_command project = project_from_options('.', options) File "/usr/lib/python3.10/site-packages/compose/cli/command.py", line 60, in project_from_options return get_project( File "/usr/lib/python3.10/site-packages/compose/cli/command.py", line 152, in get_project client = get_client( File "/usr/lib/python3.10/site-packages/compose/cli/docker_client.py", line 41, in get_client client = docker_client( File "/usr/lib/python3.10/site-packages/compose/cli/docker_client.py", line 170, in docker_client client = APIClient(use_ssh_client=not use_paramiko_ssh, **kwargs) File "/usr/lib/python3.10/site-packages/docker/api/client.py", line 197, in __init__ self._version = self._retrieve_server_version() File "/usr/lib/python3.10/site-packages/docker/api/client.py", line 221, in _retrieve_server_version raise DockerException( docker.errors.DockerException: Error while fetching server API version: Not supported URL scheme http+docker Signed-off-by: Christian Ege Reference: https://github.com/graugans/meta-virtualization/commit/4149812ca9581a313de27c45a0f2dfa7bd8f53df Signed-off-by: Libo Chen Signed-off-by: Bruce Ashfield

python3-colorama: drop recipe

2024-10-10T13:06:14+00:00

We no longer need our own pinned version of this recipe, and it causes us issues with meta-python. Signed-off-by: Bruce Ashfield

python3-sphinx: make a 4.2.0 specific recipe

2022-03-24T12:10:59+00:00

OEcore has pulled in python3-sphinx, and bumped the version. Our recipe is causing failures. We still have a version dependency on 4.2.x, so we create a specific recipe to keep things working. Hopefully this can be deleted shortly, and this is only being created as a transition project. Signed-off-by: Bruce Ashfield

python3-sphinx: add specific Licenses

2021-09-16T22:01:55+00:00

The LICENSE field for python3-sphinx is not specific enough, and doesn't contain all the integrated package licenses. Signed-off-by: Bruce Ashfield

python3-sphinx: update to 4.2.0

2021-09-16T22:01:55+00:00

Signed-off-by: Bruce Ashfield

python-cached: synchronize with meta-python

2021-09-02T02:52:12+00:00

python3-cached-property was recently added to meta-python, with the same version, but slightly different variable definitions. This is breaking reprodicibility tests. We've had some issues with python packages upgrading in meta-python and causing runtime issues, so we temporarily want to hold onto a copy of this recipe until that can be ruled out. We'll either pin the version in meta-virt or remove the recipe once that is determined. But for now, if we synchronize the recipe variables, the reprodicibility checks should stop failing. Signed-off-by: Bruce Ashfield

global: overrides syntax conversion

2021-08-02T21:17:53+00:00

OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie Signed-off-by: Bruce Ashfield

python3: remove the no-longer required bbappend

2021-07-29T14:56:47+00:00

It has been carried over from python2 and is no longer required. More importantly it breaks the python3-native build due to ${STAGING_DIR_TARGET} being "" for native recipes. Signed-off-by: Ruslan Babayev Signed-off-by: Bruce Ashfield

python3-bugsnag: Upgrade 4.0.2 -> 4.1.0

2021-07-21T02:51:29+00:00

Upgrade to release 4.1.0: - Add support for breadcrumbs. These are short log statements that are attached to error reports to help diagnose what events led to the error. - Apply filtering with params_filters to bytes, not just strings Signed-off-by: Leon Anavi Signed-off-by: Bruce Ashfield

python3-paramiko: drop in favour of meta-python recipe

2021-04-26T15:17:27+00:00

meta-python has the exact same version of this recipe, with only minor differences. Our copy is no longer needed, and in fact, is taking precedence over a base build, changing signatures and breaking yocto compatibility. Signed-off-by: Bruce Ashfield