From a119299be6b18c273e802382c506ce49b77b4b40 Mon Sep 17 00:00:00 2001 From: "riseproject-dev[bot]" <330740410+riseproject-dev[bot]@users.noreply.github.com> Date: Thu, 1 Oct 2026 08:33:54 +0000 Subject: [PATCH 1/2] pylibjpeg-openjpeg: Add version 2.6.0 Signed-off-by: riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com> --- docs/packages/pylibjpeg-openjpeg.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/packages/pylibjpeg-openjpeg.yaml b/docs/packages/pylibjpeg-openjpeg.yaml index 4a06f9eba703..be4d72fa899a 100644 --- a/docs/packages/pylibjpeg-openjpeg.yaml +++ b/docs/packages/pylibjpeg-openjpeg.yaml @@ -15,3 +15,4 @@ versions: - filename: pylibjpeg_openjpeg-2.5.0-cp314-cp314-manylinux_2_31_riscv64.manylinux_2_39_riscv64.whl sha256: 4a6b5725b6258de0d63f4f6278764b1ea406878834f75f6a73e237febd061863 requires-python: '>=3.9,<4.0' +- version: 2.6.0 From 96d8bb425205da441e1b093ad99d0d229b6f7e5d Mon Sep 17 00:00:00 2001 From: Ludovic Henry Date: Fri, 9 Oct 2026 16:31:08 +0000 Subject: [PATCH 2/2] pylibjpeg-openjpeg: carry forward riscv64 patches to 2.6.0 Nightly version bump omitted the patches/pylibjpeg-openjpeg/ directory for 2.6.0, so the build's unconditional `git apply .../*.patch` step failed with "No such file or directory" before any build/test ran. Copied forward the same patch set from 2.5.0 (unchanged since then). --- ...ittle-CMS-licence-in-the-built-wheel.patch | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 patches/pylibjpeg-openjpeg/2.6.0/0001-package-the-Little-CMS-licence-in-the-built-wheel.patch diff --git a/patches/pylibjpeg-openjpeg/2.6.0/0001-package-the-Little-CMS-licence-in-the-built-wheel.patch b/patches/pylibjpeg-openjpeg/2.6.0/0001-package-the-Little-CMS-licence-in-the-built-wheel.patch new file mode 100644 index 000000000000..0fea1a895382 --- /dev/null +++ b/patches/pylibjpeg-openjpeg/2.6.0/0001-package-the-Little-CMS-licence-in-the-built-wheel.patch @@ -0,0 +1,38 @@ +From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 +From: Ludovic Henry +Date: Wed, 30 Sep 2026 12:00:00 +0200 +Subject: [PATCH] package the Little CMS licence in the built wheel + +Upstream-Status: To upstream [not yet submitted; every pylibjpeg-openjpeg wheel on PyPI has the same gap, so it needs a maintainer discussion rather than a drive-by PR] + +build_package.py compiles every lib/openjpeg/thirdparty/liblcms2/src/*.c +file (Little CMS 2.8, vendored by the openjpeg v2.5.3 submodule) into +the _openjpeg extension, so every wheel redistributes Little CMS in +binary form. Its MIT licence requires the copyright notice to travel +with the binary, but the root LICENSE only carries pylibjpeg-openjpeg's +own MIT text and openjpeg's BSD-2-Clause text. + +Add the vendored copy's COPYING verbatim as LICENSE.lcms2 at the project +root: poetry-core copies every root LICENSE* file into the wheel's +dist-info, so no packaging change is needed. +--- + LICENSE.lcms2 | 8 ++++++++ + 1 file changed, 8 insertions(+) + create mode 100644 LICENSE.lcms2 + +diff --git a/LICENSE.lcms2 b/LICENSE.lcms2 +new file mode 100644 +--- /dev/null ++++ b/LICENSE.lcms2 +@@ -0,0 +1,8 @@ ++Little CMS ++Copyright (c) 1998-2011 Marti Maria Saguer ++ ++Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: ++ ++The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. ++ ++THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. +-- +2.43.0 +