Changes from 1.9.2 to 1.9.3:
----------------------------
* Fix a bunch of minor code issues pointed out using Clang static analyzer.
* New API: pkgconf_solution_free(), which frees a compiled solution graph.
* Fix behavior when overriding global variables with '--define-variable'.
(From OE-Core rev: a48dc992ebf8e664bde4de61ba937a87fc142533)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
==========
New features:
context: Support (NEVRA forms, provides, file provides) including globs in the dnf_context_remove func
Bug fixes:
dnf-context: Disconnect signal handler before dropping file monitor ref
Filter out advisory pkgs with different arch during advisory upgrade, fixes possible problems in dependency resulution
Gracefully handle failure to open repo primary file
Fix listing a repository without cpeid
(From OE-Core rev: 57893d38c2725c07b29d974e184be37b3d265d9b)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0001-device-utils.c-Use-linux-mount.h-instead-of-sys-moun.patch
removed since it's included in 5.19
Changelog:
==========
* send: support protocol version 2
* fi show: print all missing devices
* device stats: add tabular output
* replace: add alias to device group (device replace)
* check: validate free space tree items
* fixes:
* convert: support large filesystems (block count > 32bit)
* recognize filesystems with verity enabled
* mkfs and DUP could write out of order, fix it for zoned mode
* build:
* optional support for LZO and ZSTD in receive
* compatibility with glibc 2.36 (mount.h)
* add fallbacks for new GCC builtins
* other:
* corrupt-block: target specific items, offsets
* documentation updates, new pages from wiki
* new tests
(From OE-Core rev: 53ead3fb0e51e71207dfd62f43f0ec4304524dcc)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
python3-requests makes use of 'zipfile' module, so we need to add
python3-compression as a dependency, otherwise 'import requests'
errors out.
(From OE-Core rev: 6cfe2ed2234a76a3f9da194097781e8d6ce1353b)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Make unique shell variable names for cargo and rust
setup scripts. This change will make it easier to append to the
scripts in a bbappend file by using the variable for the script.
Before this change it was only possible for the last script as
they shared the same variable name.
(From OE-Core rev: 74307f57ad0b3c538be0add11028e4e6199a7662)
Signed-off-by: Peter Bergin <peter@berginkonsult.se>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This package was broken since it was upgraded to 6.48, because
it started using 'exceptiongroup' since then, which is missing
in any meta layer. On target, when importing hypothesis, we meet
the following error:
Traceback (most recent call last):
File "/usr/lib64/python3.10/site-packages/hypothesis/internal/compat.py", line 18, in <module>
BaseExceptionGroup = BaseExceptionGroup
NameError: name 'BaseExceptionGroup' is not defined. Did you mean: 'BaseException'?
ModuleNotFoundError: No module named 'exceptiongroup'
The related codes as below:
try:
BaseExceptionGroup = BaseExceptionGroup
ExceptionGroup = ExceptionGroup # pragma: no cover
except NameError:
from exceptiongroup import (
BaseExceptionGroup as BaseExceptionGroup,
ExceptionGroup as ExceptionGroup,
)
We can see that it tries to use ExceptionGroup and falls back to
use an import from exceptiongroup module.
Looking at the https://github.com/agronholm/exceptiongroup, it says:
"""
This is a backport of the BaseExceptionGroup and ExceptionGroup classes from Python 3.11.
"""
So instead of adding a new recipe for exception group, it might be
better to revert to a working version and wait for python 3.11 to release.
(From OE-Core rev: 37c5b171d7de25b131e77b80d37f8481308bd6fe)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It does not yet compile with clang it comes with __ builtin___snprintf_chk Not Supported
formatted output of built-in functions check is failing with clang
somehow it seems to be compiler limitation. Therefore disable building
this component with clang for now
(From OE-Core rev: 5f4b6afb030fe75247cc2da09cdf0ec5259673df)
(From OE-Core rev: 0b3cff906c469bb9d6dfc7fafe385243d00f1c2b)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the recpie to match the recent debug files layout change.
(From OE-Core rev: 7d191fc547a817f453496f2f48901ff384e34875)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After improvements to debug sources handling I suspect that extra debug
information became available and is confusing this test. Disable it
for now until someone with more knowledge can resolve the issue.
(From OE-Core rev: 2d52b590f4f254ba6ff310af1f68780a0f329673)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Tweak the powerpc code to just include filenames rather than full paths
to avoid build reproducibility issues.
(From OE-Core rev: a71832a14b6944da10c1916861545577f2f2de2c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a patch to gcc so that relative paths are handled by -fdebug-prefix-map
and friends. In OE we use relative paths in autotools and removing that
creates a lot of issues we'd have to fix. This alternative allows us to
fix the paths within gcc and improve our debug file coverage (and SPDX
manifests) accordingly.
(From OE-Core rev: 591cbe7140f01470b5799bc51e5b23f58bf95ffa)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Now that we're using absolute paths to run configure, there are absolute
path symlinks within gcc's output. Use our script that fixes these so
that the sstate objects work correctly.
(From OE-Core rev: 78f0bb21ae4337fdf628b2436c6182c32ed4fa9d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Match the changes to debug prefixes in bitbake.conf.
(From OE-Core rev: ccbbed323b5a96bbdaec4411fdd26cb9dca583e8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We don't really need to keep S and B separate for debug source purposes
and there shouldn't be source references in WORKDIR that isn't S and B
either.
Separating these out simplifies the shared-work directory handling for
gcc and should also help fix external source usage. Therefore handle
S and B in DEBUG_PREFIX_MAP separately and clean up other code.
Indentation is reduced here as it is introduced on every compiler
commandline so minimising it is helpful.
(From OE-Core rev: c39b5020b8705d17e3745c41e38d0f99a1ac94cf)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This code was some of the earliest reproducible build work we did. To
correctly handle the encoding of file paths, we used relative build
paths to run configure which resulted in relative build paths in the
binaries.
We now have more modern approaches used elsewhere with the prefix remapping
options. These work best with absolute paths, not relative ones. As such,
drop the relative path mangling and switch to using prefix mapping
exclusively on absolute paths.
This makes the code matc the rest of the system and triggers the correct
code to be added in /usr/src/debug.
We have to include both file-prefix and debug-prefix since the assembler
only looks at debug-prefix.
(From OE-Core rev: 309e5d8bb56eb8599d756831f0bd38e6a50cfb05)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
