Remove 0002-sepdebugcrcfix.c-do-not-use-64bit-variants.patch
as the issues were fixed upstream.
(From OE-Core rev: d4cbc3fe8354ce2bbcee90c5bd9e6b821b488900)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was prompted by working on librsvg update: the new meson-driven
version wants to query values from .pc files residing in its own
build directory, and modifies PKG_CONFIG_PATH accordingly.
When using the pkg-config-native wrapper such modifications
have no effect, and we have to pass them in manually
from the recipe via EXTRA_NATIVE_PKGCONFIG_PATH variable.
This variable is already defined (with an empty value) and
appended to PKG_CONFIG_PATH export in the native class, so this
simply extends its use to the wrapper.
(Appending to PKG_CONFIG_PATH in the wrapper, instead of resetting it,
is not an option as that can lead to contamination with the cross values).
(From OE-Core rev: 2bc050146d47b14d890a1b0db2b55f9057a08b65)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed:
bitbake automake-native failed with error:
| :; HELP2MAN_NAME="Generate Makefile.in files for configure from Makefile.am"; export HELP2MAN_NAME; LONGPATH/tmp/hosttools/mkdir -p doc && AUTOMAKE_HELP2MAN=true ./pre-inst-env LONGPATH/tmp/hosttools/perl ../automake-1.17/doc/help2man --output=doc/automake-1.17.1 --info-page=automake --name="${HELP2MAN_NAME}" bin/automake-1.17
| help2man: can't get `--help' info from bin/aclocal-1.17
| Try `--no-discard-stderr' if option outputs to stderr
| make: *** [Makefile:3818: doc/aclocal-1.17.1] Error 2
In above command, `bin/aclocal-1.17 --help` will be runned, since
@PERL@ is replaced as the full path of perl, it is possible that the
shebang line exceeds the max limit and causes above error, because the
kernel imposes a maximum length on the text that follows the "#!"
characters at the start of a script; characters beyond the limit are
ignored. Before Linux 5.1, the limit is 127 characters. Since Linux
5.1, the limit is 255 characters.
Add back the forced perl settings and add a patch for workaround the
fatal error caused by space in perl path
(From OE-Core rev: 0061f441501be923ddf326dcc5b3f25b59ac86d4)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1.26.3:
- Support an old import path that is still used by some consumers like
Hatch
1.26.2:
- Back-populate string license fields (License-Expression) for core
metadata versions prior to 2.4
- Remove the License-Expression and License-Files core metadata from
version 2.2 that was missed in the previous minor release
1.26.1:
- Add backward compatibility for the old license-files metadata field
- Support an old import path that is still used by some consumers like
Hatch
1.26.0:
- The license-files metadata field has been updated to the latest spec
and is now just an array of glob patterns
- Support version 2.4 of core metadata for the wheel and sdist targets
- Add HATCH_METADATA_CLASSIFIERS_NO_VERIFY environment variable to
disable trove classifier verification
- Add .pixi to the list of directories that cannot be traversed
- Bump the minimum supported version of packaging to 24.2
- No longer write package metadata for license expressions and files for
versions of core metadata prior to 2.4
- Properly enable Zip64 support for the wheel target
- Properly ignore parent .gitingore files when the project root matches
one of the patterns
(From OE-Core rev: 2c09f03e62f96016c2a3713362f83a7591bd0f9b)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
RISC-V offers several virtual memory address schemes (Sv39, Sv48, and Sv57),
but ASan currently supports only Sv39 on RISC-V64.
For RISC-V64 Sv39, ASan uses custom allocator configurations
tuned to manage large allocations efficiently.
These tunings are incompatible with larger address spaces like
Sv48/Sv57 due to differences in region sizes and alignment.
For riscv64, Asan's tuning for Sv39 can be enabled in qemu
by using the appropriate flag in the command line as shown below:
runqemu nographic qemuparams="-cpu rv64,sv39=true"
Additionally, the COMPATIBLE_HOST list in gcc-sanitizers has been
updated to include riscv64. All necessary tests were successfully
conducted on both hardware(Microchip PolarFire SoC)
and the qemurisv64 environment, with ASan effectively
detecting memory errors in both scenarios.
(From OE-Core rev: 4b4450ff695ef73bf7a2437e142d2e0730d6a547)
Signed-off-by: Deepthi Hemraj <Deepthi.Hemraj@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* The package now requires python3-hatch-vcs-native at build-time
* Updated HOMEPAGE to point to the correct Github repository. The old link re-directs to the same link.
2.2.3 (2024-09-12)
==================
Features
--------
- Added support for Python 3.13.
Bugfixes
--------
- Fixed the default encoding of chunked request bodies to be UTF-8 instead of ISO-8859-1. All other methods of supplying a request body already use UTF-8 starting in urllib3 v2.0.
- Fixed ResourceWarning on CONNECT with Python < 3.11.4 by backporting https://github.com/python/cpython/issues/103472
- Adjust tolerance for floating-point comparison on Windows to avoid flakiness in CI
- Fixed a crash where certain standard library hash functions were absent in restricted environments.
- Fixed mypy error when adding to ``HTTPConnection.default_socket_options``.
HTTP/2 (experimental)
---------------------
See details: https://github.com/urllib3/urllib3/releases/tag/2.2.3
Deprecations and Removals
-------------------------
- Note for downstream distributors: the ``_version.py`` file has been removed and is now created at build time by hatch-vcs.
- Drop support for end-of-life PyPy3.8 and PyPy3.9
(From OE-Core rev: 61331e291a2f96c7ac7efccd7d95de68432ea992)
Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
python3-iniparse dependency was dropped 2019, see the
following commit as reference:
d7d0e0e2f9
When looking at the Git history, this happened around tag 4.2.1
(From OE-Core rev: 05220b4907ab654e829d97ab68d48f76330937dd)
Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Looking at the history, python3-six was removed as a dependency
in the poetry.lock file in v1.5.2
Even before v1.5.2 and until now (v1.9.1) there is no code in
the package which imports the six module. So it can be safely
dropped from the recipe.
(From OE-Core rev: 1ed30cd9426e1f8a6caf31277f0349343a06f2d4)
Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As commit 81551871b183 (gcc: Remove Java support variables) correctly
stated
Java support was removed in upstream gcc 7.
but this line snuck back in with commit bbf32e24608c (gcc-9: Add
recipes for gcc 9.1 release).
(From OE-Core rev: 136619477f0ce7c9da0762bbbeb1227a1ad6c0c7)
Signed-off-by: Rasmus Villemoes <ravi@prevas.dk>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Change the suffix from 'tcl' to 'tcl9' and from 'tcl8' to avoid
conflicts with the man pages provided by the tcl packages.
file /usr/share/man/mann/vwait.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64
file /usr/share/man/mann/while.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64
file /usr/share/man/mann/yield.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64
file /usr/share/man/mann/yieldto.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64
file /usr/share/man/mann/zlib.ntcl conflicts between attempted installs of tcl-doc-9.0.0-r0.riscv64 and tcl8-doc-8.6.15-r0.riscv64
[...]
(From OE-Core rev: b961021cc47c53ddd602e6038f5faf02416455b3)
Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Seems every time python is updated this gets removed. That's likely
because the tk option can't be enabled in python3-native without
creating a dependency loop.
Instead of manually editing the manifest every time, explicitly
add it in the recipe as suggested by Alexander Kanavin.
(From OE-Core rev: d2e82fc12509950ea30fa20fcbe9fc148b6cff1c)
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of relying completely on the python packaging manifest,
allow some default values. This is useful for the edge cases that
can't be found automatically by the create_manifest step.
In particular, tkinter can't be built for python3-native, so its
consistently missed in manifest updates.
(From OE-Core rev: cc5ec75b50618ce42d5b19d0aad0b44611bf8fbe)
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Summary of changes:
- The ``--python`` option can now take the path of a virtualenv folder, as an
alternative to a Python executable.
- The metadata in packages now has the names of optional dependency groups
("extras") normalised, complying with version 2.3 of the metadata standard.
- Fix potential substitution of environment variables into passwords read from
``.pypirc`` files.
- A warning is now shown when building packages which specify the old
``flit.buildapi`` backend, which should be replaced by
``flit_core.buildapi``. It's a good idea to always set a maximum
version for the build requirement, to protect against changes in
future major versions of Flit.
- Avoid using the deprecated ``datetime.utcfromtimestamp()``.
- The tests for ``flit_core`` are no longer part of the installed package,
reducing the size of the wheels.
Remove the -tests package, as the tests are no longer installed.
(From OE-Core rev: 102e3524361d7d07f0dee09b1b12346b1184268f)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was supposed to be added in oe-core commit fd656aaf7fbe
("python3-numpy: upgrade 1.26.4 -> 2.1.3"), but it somehow got missed in
the final version of that patch. Add it now to fix possible do_compile
errors on some systems, due to host paths sneaking into the meson build
options, e.g.:
| Build machine cpu family: x86_64
| Build machine cpu: x86_64
| Host machine cpu family: x86_64
| Host machine cpu: x86_64
| Target machine cpu family: x86_64
| Target machine cpu: x86_64
| Program python3 found: YES (/home/tgamblin/workspace/yocto/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/recipe-sysroot-native/usr/bin/nativepython3)
| Did not find pkg-config by name 'pkg-config'
| Found pkg-config: NO
| Run-time dependency python found: NO (tried pkgconfig, pkgconfig and sysconfig)
|
| ../numpy-2.1.3/meson.build:41:12: ERROR: Python dependency not found
|
| A full log can be found at /home/tgamblin/workspace/yocto/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/build/meson-logs/meson-log.txt
and notably (meson-log.txt snippet):
|x86_64-poky-linux-musl-g++ -m64 -march=core2 -mtune=core2 -msse3 -mfpmath=sse -fstack protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/media/build/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/recipe-sysroot -I/media/build/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/recipe-sysroot/usr/include/python3.13 -I/usr/include/python3.13
A bug has been filed about this and the related gcc issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15672
With pkgconfig on the inherit line, all include directives in
meson-log.txt end up looking something like:
|-I/home/tgamblin/workspace/yocto/poky/build/tmp/work/core2-64-poky-linux-musl/python3-numpy/2.1.3/recipe-sysroot/usr/include/python3.13
(From OE-Core rev: b8503a2c5000262a400375321de75161357111fb)
Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
python3-rdflib was the last consumer of this recipe in oe-core.
(From OE-Core rev: 72cc499429b0869385223ba21fe03849c6145b89)
Signed-off-by: Guðni Már Gilbert <gudni.m.g@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
==========
Fixed pure Python wheels converted from eggs and wininst files having the ABI tag in the file name
(From OE-Core rev: 06fcf1f8ae763eee996294e8636aedbdbf388491)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
============
- Supported max_queue=None in the asyncio and threading implementations for
consistency with the legacy implementation, even though this is never a good idea.
- Added close_code and close_reason attributes in the asyncio and threading
implementations for consistency with the legacy implementation.
- Once the connection is closed, messages previously received and buffered can
be read in the asyncio and threading implementations, just like in the legacy implementation.
(From OE-Core rev: b36742c5153873832fbf5fb1788d5c333286a583)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0005-Do-not-prepend-installroot-to-logdir.patch
refreshed for 4.22.0
Changelog:
=============
- doc: Naming of source and debug repos
- Fix /var/cache/dnf and /etc/yum packaging
- Allow --installroot on read-only bootc system
- spec: If DNF5 obsoletes DNF, do not build dnf and yum packages
- Print rpm unpack errors to the user (RhBug:2312906)
- package: remote_location() takes basedir into account
- spec: If DNF5 obsoletes DNF, do not build dnf-automatic
- Allow --downloadonly on read-only bootc system
- Add kernel-core to reboot_needed list
- Update need_reboot for dnf-automatic
- doc: Example send_error_messages in /etc/dnf/automatic.conf
- automatic: Check availability of config file
- Updated conf_ref to reflect change in fastestmirror behavior
- doc: Fix display issue of a code snippet
(From OE-Core rev: 7a97281b65f1cd0268217e44819a0b55faa20178)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: MIT changed to X11 (which is MIT plus advertising clause)
(From OE-Core rev: dee8f3552cbe1194f97481df4270ca8e9b5113d5)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: copyright years
(From OE-Core rev: eda9c9b556c6671e009bc637acb151580796223b)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed Ross' comments:
* Add -n to gzip to make the resulting files reproducible, so we don't need to
decompress them.
* Makefile: Let bootchartd.conf use EARLY_PREFIX, so that bootchartd.conf can
install to correct location.
* Set MANDIR and DOCDIR to make the files install to correct location for
bootchart2-native.
(From OE-Core rev: 5354966a92cd522a3312c870aefa239d5c564a9f)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is an issue in the std::chrono::tzdb parser that causes problems
since the tzdata-2024b release started using %z in the main format.
As a real world problem I encounter an issue with the waybar clock module,
which ignores the timezone setting and only shows system time.
(From OE-Core rev: 39018429f05511053ab12e23e7f4487ea25ee529)
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
