Check if the module object has attribute '__file__' to fix and
avoid errors like:
AttributeError: module '_abc' has no attribute '__file__'. Did you mean: '__name__'?
(From OE-Core rev: 8acce12c1a4cf37ac312c92d62a6ae93a349dddf)
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes in this update includes:
* The option "--vgdb-stop-at=event1,event2,..." accepts the new value
abexit. This indicates to invoke gdbserver when your program exits
abnormally (i.e. with a non zero exit code).
* Fix Rust v0 name demangling.
* The Linux rseq syscall is now implemented as (silently) returning
ENOSYS.
* Add FreeBSD syscall wrappers for __specialfd and __realpathat.
* Remove FreeBSD dependencies on COMPAT10, which fixes compatibility
with HardenedBSD
* The option --enable-debuginfod=<no|yes> [default: yes] has been added
on Linux.
* More DWARF5 support as generated by clang14.
Drop the patch 0001-Fix-drd-tests-shared_timed_mutex.cpp.patch which was
merged upstream.
ptest result:
System Pass Fail Skip
x86-64 717 0 20
(From OE-Core rev: 51e3d2ecef6a031105c04eb730580c17411eaf46)
Signed-off-by: Zheng Qiu <zheng.qiu@windriver.com>
Signed-off-by: Randy MacLeod <randy.macleod@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Highlights for this release:
- Continued work on color management infrastructure:
In Weston 11, if you enable the tentative, experimental and WIP color
management option, Weston will not only blend in linear light, but
you can also set up a monitor ICC profile and Weston will do some
kind of color mapping from sRGB to that profile. Furthermore, you can
configure a monitor into HDR mode and deliver HDR characteristics from
weston.ini to the monitor, but Weston will *not* produce proper HDR
content yet, meaning the display is incorrect.
- Various RDP improvements.
- Performance improvements in the DRM backend.
- Support for the wp_single_pixel_buffer_v1 protocol.
- weston_buffer refactoring.
- Groundwork for running multiple backends at the same time (e.g. KMS + RDP)
and for multi-GPU support in the DRM backend. This is not supported
yet, but may be in a future release.
Breaking changes for users:
- The cms-static and cms-colord plugins are now deprecated.
- A number of features have been removed from desktop-shell: multiple
workspaces, zoom, exposay.
- wl_shell support has been removed (superseded by xdg-shell).
- The fbdev backend has been removed (superseded by KMS).
- weston-launch and launcher-direct have been removed (superseded by libseat).
- The weston-info and weston-gears clients have been removed (weston-info is
superseded by wayland-info).
- The KMS max-bpc property is now set by default. If you experience black
screens with (faulty) monitors, try lowering it in weston.ini.
- Weston will now abort when running out of memory. Weston is not suitable
for memory constrained environments.
(From OE-Core rev: eb00d50e5da97a726eb6290317a3ef7d8e1b90a3)
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* use 4 spaces
* avoid trailing space
* add CARGO_LOCK_SRC_DIR to allow searching outside ${S}
* use BPN in output filename
* First I've used CARGO_LOCK_SRC_DIR as relative to ${S}, because that's what CARGO_SRC_DIR
in cargo.bbclass is using:
meta/classes-recipe/cargo.bbclass:CARGO_SRC_DIR ??= ""
meta/classes-recipe/cargo.bbclass:MANIFEST_PATH ??= "${S}/${CARGO_SRC_DIR}/Cargo.toml"
but change to absolute path (defaulting to ${S}) as requested by Alex:
11:44 < kanavin> JaMa, would prefer CARGO_LOCK_SRC_DIR ??= "${S}"
11:46 < kanavin> otherwise looks good
* I've resolved my usecase for CARGO_LOCK_SRC_DIR by changing
S back to ${WORKDIR}/git and using CARGO_SRC_DIR to select
the right subdirectory to be built, because the Cargo.toml
in this subdirectory was also referencing other subdirectories
with relative path:
88b147506d/token/cli/Cargo.toml (L30)
so including all Cargo.lock files in whole ${WORKDIR}/git
seems like reasonable approach
(From OE-Core rev: 7636a2b8080521ed2ad54b0edce47a8742a12d58)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
https://www.sphinx-doc.org/en/master/changes.html#release-5-3-0-released-oct-16-2022
Release 5.3.0 (released Oct 16, 2022)
* #10759: LaTeX: add latex_table_style and support the 'booktabs',
'borderless', and 'colorrows' styles. (thanks to Stefan
Wiehler for initial pull requests #6666, #6671)
* #10840: One can cross-reference including an option value like
`--module=foobar`, `--module[=foobar]` or `--module foobar`.
Patch by Martin Liska.
* #10881: autosectionlabel: Record the generated section label to the
debug log.
* #10268: Correctly URI-escape image filenames.
* #10887: domains: Allow sections in all the content of all object
description directives (e.g. py:function). Patch by Adam
Turner
(From OE-Core rev: 35d65248c2a46f4966ded2e95e530f25a2869ce9)
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://github.com/more-itertools/more-itertools/blob/master/docs/versions.rst#900
9.0.0
* Potentially breaking changes
- `grouper` no longer accepts an integer as its first
argument. Previously this raised a DeprecationWarning.
- `collate` has been removed. Use the built-in
`heapq.merge` instead.
- `windowed` now yields nothing when its iterable is
empty.
* This library now advertises support for Python 3.7+.
* New functions
- `constrained_batches`
- `batched` (from the Python itertools docs)
- `polynomial_from_roots` (from the Python itertools
docs)
-`sieve` (from the Python itertools docs)
* Other changes
- Some documentation issues were fixed (thanks to nanouasyn)
(From OE-Core rev: f31ea2784428114acae33522a80208aa35d133bc)
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://hypothesis.readthedocs.io/en/latest/changes.html#v6-56-4
6.56.4 - 2022-10-28
* This patch updates some docs, and depends on exceptiongroup 1.0.0 final
to avoid a bug in the previous version.
6.56.3 - 2022-10-17
* This patch teaches text() to rewrite a few more filter predicates (issue
#3134). You’re unlikely to notice any change.
6.56.2 - 2022-10-10
* This patch updates our vendored list of top-level domains, which is used
by the provisional domains() strategy, and fixes some incorrect examples
in the docs for mutually_broadcastable_shapes().
(From OE-Core rev: 1071b68375819d9faa607ae1179720500157d932)
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://docs.pytest.org/en/stable/changelog.html#pytest-7-2-0-2022-10-23
Excerpt from upstream release notes:
Deprecations
* #10012: Update pytest.PytestUnhandledCoroutineWarning to a
deprecation; it will raise an error in pytest 8.
* #10396: pytest no longer depends on the py library. pytest provides
a vendored copy of py.error and py.path modules but will use
the py library if it is installed. If you need other py.* modules,
continue to install the deprecated py library separately, otherwise it
can usually be removed as a dependency.
* #4562: Deprecate configuring hook specs/impls using
attributes/marks.
Instead use pytest.hookimpl() and pytest.hookspec(). For more
details, see the docs.
* #9886: The functionality for running tests written for nose has been
officially deprecated.
This includes:
Plain setup and teardown functions and methods: this might catch
users by surprise, as setup() and teardown() are not pytest idioms, but
part of the nose support.
Setup/teardown using the @with_setup decorator.
For more details, consult the deprecation docs.
(From OE-Core rev: 8ae3b896b0e1a77bcbd5b98b4b983e4f34746a94)
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://github.com/giampaolo/psutil/blob/master/HISTORY.rst#593
2022-10-18
Enhancements
* 2040, [macOS]: provide wheels for arm64 architecture. (patch by
Matthieu Darbois)
Bug fixes
* 2116, [macOS], [critical]: `psutil.net_connections`_ fails with
RuntimeError.
* 2135, [macOS]: Process.environ() may contain garbage data. Fix
out-of-bounds read around sysctl_procargs. (patch by Bernhard
Urban-Forster)
* 2138, [Linux], [critical]: can't compile psutil on Android due to
undefined ethtool_cmd_speed symbol.
* 2142, [POSIX]: net_if_stats() 's flags on Python 2 returned unicode
instead of str. (patch by Matthieu Darbois)
* 2147, [macOS] Fix disk usage report on macOS 12+. (patch by Matthieu
Darbois)
* 2150, [Linux] Process.threads() may raise NoSuchProcess. Fix race
condition. (patch by Daniel Li)
* 2153, [macOS] Fix race condition in
test_posix.TestProcess.test_cmdline. (patch by Matthieu Darbois)
(From OE-Core rev: 893fc6a99f1ad3417fec43eb9b7fdb641e7d1e6d)
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>
38.0.3 - 2022-11-01
* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL
3.0.7, which resolves CVE-2022-3602 and CVE-2022-3786.
38.0.2 - 2022-10-11 (YANKED)
Attention!
This release was subsequently yanked from PyPI due to a regression in
OpenSSL.
* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL
3.0.6.
https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst#3803---2022-11-01
(From OE-Core rev: 3c0c03312724de85e3209e6e5a5aa20c094eae45)
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>
* Refresh python3-bcrypt-crates.inc
Upstream release notes[1]:
* We now build PyPy manylinux wheels.
* Fixed a bug where passing an invalid salt to checkpw could result in
a pyo3_runtime.PanicException. It now correctly raises a ValueError.
[1] https://github.com/pyca/bcrypt/#401
(From OE-Core rev: 509a684b748af92e0b657433da85550de72ecbe0)
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>
qemuarmv5 passes testimage on with the linux-yocto-dev kernel. Add it
to the compatible machines list for that recipe.
(From OE-Core rev: e1587fbac4d3ee8092d5e858f1b423faa512c559)
Signed-off-by: Jon Mason <jdmason@kudzu.us>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently the hciattach bcm43xx firmware loader looks up the firmware
blob in /etc/firmware . Change this to /lib/firmware instead, so that
the path is consistent with Linux kernel which also looks up firmware
for the WiFi part in /lib/firmware .
(From OE-Core rev: 72b3b79ad8b980e8dd9470d16b72c2c70072bbc0)
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
STAGING_KERNEL_DIR uses the MACHINE name so it breaks the multiconfig
and in this cases it will run the shared recipes twice, one for each
machine.
STAGING_KERNEL_DIR it's been introduced in commit 5487dee2e1
(From OE-Core rev: 6050d1f74c02495490d982ead2993b6b3c9cc04a)
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Test that the shared recipes in original mode with diff enabled works in multiconfig,
otherwise it will not build when using the same TMP dir.
The test can be run with:
oe-selftest -r archiver.Archiver.test_archiver_multiconfig_shared_unpack_and_patch
| oe-selftest - INFO - test_archiver_multiconfig_shared_unpack_and_patch (archiver.Archiver)
| oe-selftest - INFO - ... ok
| oe-selftest - INFO - ----------------------------------------------------------------------
| oe-selftest - INFO - Ran 1 test in 52.948s
| oe-selftest - INFO - OK
| oe-selftest - INFO - RESULTS:
| oe-selftest - INFO - RESULTS - archiver.Archiver.test_archiver_multiconfig_shared_unpack_and_patch: PASSED (49.98s)
| oe-selftest - INFO - SUMMARY:
| oe-selftest - INFO - oe-selftest () - Ran 1 test in 52.948s
| oe-selftest - INFO - oe-selftest - OK - All required tests passed (successes=1, skipped=0, failures=0, errors=0)
(From OE-Core rev: 0059a5c9c0116dcc24d03a946703c0cd2ee23d16)
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add ptest for OSS 'bc' by using 'bc' in the system to do calculation jobs according to the .b files from the source file.
Test example as below:
......
.00673400673400673400
“PASS: bc/div.b”
99836408603283573660347145562829683495827909199408566065153345558783\
9427595471.89114392327665123852
“PASS: bc/exp.b”
length(b)= 1406
“PASS: bc/fact.b”
......
If bc runs the .b files and does not crash, it would 'PASS', otherwise 'FAIL'.
Tested in qemux86-64, with kvm enabled, test cost 12 secs, so it should be a fast test.
Thanks to Ross Burton and Alexander Kanavin for the professional guidance.
(From OE-Core rev: 98b058a039ae8a49437c306f684f919c93df55fd)
Signed-off-by: Yan Xinkuan <yanxk.fnst@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Rust targets have the form of 'arch-unknown-linux-gnu' while
oe's native targets are 'arch-linux-gnu', e.g. omit the vendor.
The effect this has on rust-native builds is that rust first builds
itself as stage0 for arch-unknown-linux-gnu, then builds itself
again for arch-unknown-linux-gnu, then finally uses the compiler
from second step to 'cross-compile' a compiler for 'arch-linux-gnu'.
This last step is really not necessary, and we could save 4 minutes
out of 12 if it is eliminated. Which is what this patch does
by setting the target directly to 'arch-unknown-linux-gnu'; rust's
build system then shortcuts the build process after the second step.
Given a working rust-native will be needed as early as possible in a
typical yocto build (e.g. when in a not too distant future making a
useful kernel will not be possible without rust), producing it faster
is important.
(From OE-Core rev: a918ea5645d8a67cedaf3ecf6c382520bbcad85b)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This test doesn't get exercised on the autobuilder and so it was broken:
specifically some of the ln commands silently fail and the chroot isn't
usable.
Rewrite the test case to correctly construct a chroot so the test can
pass.
(From OE-Core rev: bb6ebb9956a42df3ed8681aec9aedf340b12f934)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The underlying _run() method has an ignore_status argument and can
either return the exit code or raise an exception if it is non-zero.
Add the same argument to the run() method so that test cases can change
this value. It currently defaults to True as that is the existing
behaviour, but a follow-up patch will change this to False as test cases
should fail on errors unless told otherwise.
(From OE-Core rev: e244228730178d15a066a1428956de328cc09671)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Released: Thu Sep 22 2022
* bug
- [bug] [lexer]
* Fixed issue in lexer in the same category as that of #366 where the regexp
used to match an end tag didn’t correctly organize for matching characters
surrounded by whitespace, leading to high memory / interpreter hang if a
closing tag incorrectly had a large amount of unterminated space in it.
Credit to Sebastian Chnelik for locating the issue.
As Mako templates inherently render and directly invoke arbitrary Python
code from the template source, it is never appropriate to create templates
that contain untrusted input.
References: #367
[1] https://docs.makotemplates.org/en/latest/changelog.html#change-1.2.3
[2] https://github.com/sqlalchemy/mako/issues/366
[3] https://github.com/sqlalchemy/mako/issues/367
(From OE-Core rev: 49ad6f031458e1f48f24547dc88e41abc4ec41a6)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A recent change in libuuid made warning when running
sgdisk. Backport patch from upstream to silent warning.
The warning:
"Warning! Unable to generate a proper UUID! Creating an improper one as a last
resort! Windows 7 may crash if you save this partition table!"
(From OE-Core rev: ce6491b900e509a776eddaf6bd57251628393fa3)
Signed-off-by: Peter Bergin <peter@berginkonsult.se>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove two patches as issues fixed upstream,
submit the third one.
License-Update: argp.h is an import from glibc and
has been refreshed to the latest version. It's still
lgpl 2.1.
(From OE-Core rev: 6ecd02e4aff8222b55cd94d5214ccd76c96b7387)
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 allows semi-automated updates to the list of crates, which
is far too awkward to maintain by hand, particularly on version updates.
(From OE-Core rev: 1071e2fdd23271bf5df60712263838fe70276c67)
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 component has been reimplemented in rust, and comes
with a large list of dependencies in Cargo.toml/Cargo.lock.
Rather than list them by hand, use a file generated with
cargo-update-recipe-crates class.
(From OE-Core rev: f1ebc71d9c35ba3ff58851efe2fae4e193f481f1)
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>
For better or worse, more and more rust components are appearing that do
not include their dependencies in tarballs (or git trees), and rely on cargo
to fetch them. On the other hand, bitbake does not use cargo (and quite possible
won't ever be able to), and relies on having each item explicitly listed in SRC_URI
with a crate:// prefix. This however creates a problem of both making such lists in
the first place and updating them when a recipe is updated to a newer version.
So this class can be used to perform such updates by implementing a task that does it;
the next commit shows the outcome for python3-bcrypt (which has been tested to work
and produce a successful build).
Note: the python script relies on tomllib library, which appears in Python 3.11 and
does not exist in earlier versions - I've tested this by first updating python to 3.11-rc2
in oe-core.
(From OE-Core rev: 9eee3631124d64574b18a70a2fc42f446d58bfd2)
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>
[YOCTO #7852]
Fixes 'bitbake-layers layerindex-fetch --branch kirkstone meta-arm'
not checking out the branch if the repo is already cloned and on a
different branch.
If a clone of a layer being added already exists check what branch it
is on and if necessary attempt to switch to the given branch. If the
switch fails to happen the git error will be reported. We also warn if
there are uncommitted changes as the changes might go unnoticed and
result in unexpected behaviors.
(Bitbake rev: d2cb388f58a37db2149fad34e4572d954e6e5441)
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
