This is a test for an issue seen long ago, to avoid regressions, where a
reference to a def'd function in the metadata would return the string
value from the metadata rather than the function in inline python.
(Bitbake rev: 9f7cb22febd557817c164e25a93f5660e9c06358)
Signed-off-by: Christopher Larson <kergoth@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This has been around without being properly documented since 2019 (!!!),
and is nowadays the preferred method for enforcing license restrictions,
especially since meta-gplv2 is officially obsolete.
(From yocto-docs rev: efa1c57ecec934998792b7851b4a162be92c8b23)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- Kirkstone is now a 4 year LTS
- Add future Scarthgap LTS
- Update document metadata: license, title
(From yocto-docs rev: 12d40f56edc755db9724b7382e30082874f29699)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Restore the error message as it is supposed to be issued.
The literal block renders its content verbatim so a term role (`:term:`)
would appear as :term: string in there and `---` as --- string instead
of the expected hyphen.
Fixes: e319b3bf4eb6 ("manuals: add missing references to SDKMACHINE and SDK_ARCH")
Cc: Quentin Schulz <foss+yocto@0leil.net>
(From yocto-docs rev: 95158beba0aea7539024688c71b54fed5267faec)
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
`login` from busybox has explicit heuristics to handle CONFIG_MULTIUSER
unset (i.e. a kernel without non-root users, groups or capabilities),
bringing in the shadow version of `login` causes obscure failures at
runtime ("setgid: Function not implemented"), instead exclude it here so
anyone who includes it (likely accidentally) will at least get a build
time failure.
(From meta-yocto rev: be22c2923a0cdf60ab60012668382e55a3618f2b)
Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
https://wheel.readthedocs.io/en/stable/news.html
0.41.0 (2023-07-22)
* Added full support of the build tag syntax to wheel tags (you can now
set a build tag like 123mytag)
* Fixed warning on Python 3.12 about onerror deprecation. (PR by Henry
Schreiner)
* Support testing on Python 3.12 betas (PR by Ewout ter Hoeven)
(From OE-Core rev: 81e7e3b9059840fd749b5b50fc75588d7c4b7593)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
https://more-itertools.readthedocs.io/en/stable/versions.html
10.0.0
* Potentially breaking changes
- Python 3.7 support was dropped, since it went EOL on 2023-06-27
- batched() no longer issues a DeprecationWarning; it is now an alias
for itertools.batched for Python 3.12+
- batched() and matmul() now yield tuples instead of lists
* New functions
- combination_with_replacement_index() (thanks to Schoyen)
- nth_combination_with_replacement() (thanks to Schoyen)
- polynomial_eval() (from the Python itertools docs)
- polynomial_derivative() (from the Python itertools docs)
- sum_of_squares() (from the Python itertools docs)
* Changes to existing functions
- seekable() now has relative_seek method (thanks to karlb)
- chunked_even() was optimized (thanks to elliotwutingfeng)
- numeric_range() was optimized (thanks to eltoder)
- duplicates_justseen(), pairwise(), partial_product(), and partition()
were updated and optimized (thanks to pochmann)
- unique_in_window() had its implementation updated (thanks to
elliotwutingfeng)
- iterate() now breaks when its func argument raises StopIteration (thanks
to jrebiffe)
* Other changes
- Some documentation and testing issues were fixed (thanks to lonnen and
XuehaiPan)
(From OE-Core rev: 9351489f3fd9a01f1e74b4f209df01aeffe55c8f)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rewrite of CVE_CHECK_IGNORE to CVE_STATUS contained copy+paste
problem changing CVE numbers.
CVE-2020-12352 -> CVE-2022-3563
CVE-2020-24490 -> CVE-2022-3637
CVE-2020-12352 is now for kernel only in NVD BD, so remove it.
CVE-2020-24490 is corrected in this commit.
(From OE-Core rev: 150f81b764ccf1abfc69bd573d1fb997a6115884)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This will remove 6 CVEs which were already excluded before.
(From OE-Core rev: 8fbf7ec2b98395d87fed1360e362dc1e91e6d400)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This issue was reported and discusses under [1] which is linked in NVD CVE report.
It was already documented that some parts or libarchive are thread safe and some not.
[2] was now merged to document that also reported function is not thread safe.
So this CVE *now* reports thread race condition for non-thread-safe function.
And as such the CVE report is now invalid.
The issue is still not closed for 2 reasons:
* better document what is and what is not thread safe
* request to public if someone could make these functions thread safe
This should however not invalidate above statment about ignoring this CVE.
[1] https://github.com/libarchive/libarchive/issues/1876
[2] https://github.com/libarchive/libarchive/pull/1875
(From OE-Core rev: 9b5b850d6a6982bb8ff14dcfbb6769b293638293)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For newest Qualcomm platforms the firmware for the Adreno GPU consists
of two parts: platform-independent SQE/GMU/GPMU/PFP/PM4 and
platform-specific ZAP shader, which is used during the boot process. As
the platform-independent parts can be shared between different
platforms, split the platform-specific part to the separate package.
(From OE-Core rev: bf00a042d2fa2eb4b20d8c5982926758821bf990)
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
RTL8822 is a serie of wireless modules that need firmwares to function correctly.
The linux firmware recipe does not have a package of these firmwares, and this commit add them.
(From OE-Core rev: 6459959beeb91c0b694f5f17b6587a12c6dcb087)
Signed-off-by: BELOUARGA Mohamed <m.belouarga@technologyandstrategy.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The specific set was written to ensure vim builds reproducibly; this is
however prone to silent regressions (if vim adds more usage of iconv with
different encodings). Installing the full set also matches what standard
desktop distributions do, and thus meets expectations of upstream projects in general.
(From OE-Core rev: 2685c497c14bc325500053e551d97e8cbda97252)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This resolves two issues:
1. metapackages were depending on themselves (except -binaries which wouldn't match against 'glibc-binary').
2. for the nativesdk variant, due to a non-empty dependency list at parsing time caused by
issue 1, map_depends_variable() from meta/lib/oe/classextend.py was forcibly setting PACKAGES
to the initial parse-time value (e.g. missing the dynamically created packages). This meant that
three out of four nativesdk- metapackages were entireyly missing the dependencies on the
respective dynamic package sets.
(From OE-Core rev: a90fd3afe9184aa1870b34a826e3ba0563477d4b)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With this version, epiphany has transitioned to gtk4,
and requires webkit built with gtk4 support (there is no choice,
it's a hard break). Adjust the webkit recipe accordingly.
There's also a new requirement for gcr 4.x and libadwaita.
(From OE-Core rev: 6a300f48e783ee95ccad52fd47ad4e7d88279e4e)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
None of the files are generated, and so there is no need to carry them
in oe-core (which greatly complicates gettext version updates, for one thing).
Let's simply copy them over directly from the tarball; as the set of installed .m4
files can and does change over time, obtain them with a python scriptlet from Makefile.am
where they are listed.
(From OE-Core rev: d06cfaadb6d4bd93982f82ad8b93b89e9bceea16)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Unset LDFLAGS as the standard ones do not work when linking EFI binaries
(the new version of gnu-efi adds various apps).
(From OE-Core rev: b4b94acef1e2c5e5f1185ae165969c8a66038b17)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Absent maintainer entries are as well a frequent source of friction, as they are checked
only in selftest, and so aren't revealed until autobuilder runs.
The selftest is retained as it also checks for obsolete entries in maintainers.inc
(not possible to do in insane class).
(From OE-Core rev: 675dff0e37666c1cffa10a83f6f1f67d5fadd204)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was done in a selftest, but that is too late and creates
friction in integration as errors are not seen until autobuilder fails.
Bonus fix: SUMMARY check wasn't even working, as in the absence
of one set in the recipe there is a default value set from bitbake.conf.
I left DESCRIPTION check out for now, as many recipes don't actually
have it, and it's set from SUMMARY (plus a dot) if absent.
(From OE-Core rev: 4144c2f43da39336b03cfd612cbe1694cbf8c7bd)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The immediate reason is that the task is sstate enabled, and due
to the way devtool sets up source extraction this causes bogus
values to appear in tmp/sstate-control/index-* files.
Also, recipe_qa may contain hard failures in the future, and it
would be counterproductive for the failures to prevent devtool
workflows (which may perhaps be about fixing the failure).
An alternative would have been to not insert recipe_qa task before
fetch task, but that would greatly delay the checks in larger
bitbake builds, and it's better to run them as early as possible.
(From OE-Core rev: 6f9db3f8de3dca9b0c87382561c70857d5b39e0f)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a need to run QA checks that can operate entirely from
recipe metadata and do not need any of the build artefacts or
source code. After some deliberation it was concluded that such
checks are best collected in their own task that runs as early as possible,
and so this commit adds the task.
Like package_qa, the task is sstate enabled, but doesn't (yet)
register the qa results into sstate.
(From OE-Core rev: e0c71367ab59021fc430ef215bbfc3b525036ba4)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To match the other tests, round the test duration to an intger value
so the test reports are consistent.
(From OE-Core rev: c5be3b22a7d5b3f211080ecdf05a077f8b413ef2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
