Vala 0.52.4
===========
* Various improvements and bug fixes:
- codegen:
+ GArray, GByteArray and GPtrArray are reference counted
+ Replace wrongly hard coded usage of G_OBJECT_GET_CLASS
+ Don't add errornous cast for unknown type_symbol
+ Mark entry point method implementation "_vala_main" as static
+ Improve check for GLib.Source derived classes
- vala: Parameter following params-array parameter is not allowed
- doc: Update man page to include more information on profiles
* Bindings:
- glib-2.0: Add missing has_typedef attributes on SourceFuncs delegates
- gstreamer: Update from 1.19.0+ git master
- gtk+-3.0: Update to 3.24.29+f9fe28ce
- gtk4: Update to 4.3.0+24f0ae1d
- pango: Mark language parameter of AttrIterator.get_font() as out
- vapi: Update GIR-based bindings
(From OE-Core rev: 9f0f6ef0daf913057af69a834f3607e567d2e54d)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Feed signature checking with OpenSSL will be deprecated in the next
release of opkg.
Upstream ML Announcement:
https://groups.google.com/g/opkg-devel/c/drqw5_HuXuU
The opkg-0.4.5 configure.ac already throws a warning when
`--enable-openssl` is requested.
Add a temporary QA check to the opkg recipe, which will throw a warning
to the builder when they have `openssl` enabled in their opkg
PACKAGECONFIG. This will give builders some time to either change their
feed verification mechanism, or raise their use-case with upstream.
(From OE-Core rev: 0ccd4149881113f5c8344ab0cefcf984ade50b1c)
Signed-off-by: Alex Stewart <alex.stewart@ni.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop patches which have been accepted upstream.
(From OE-Core rev: 9fed64cca20e98ab8df874a172cfe17fb3f77142)
Signed-off-by: Alex Stewart <alex.stewart@ni.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pass --enable-standard-branch-protection. This is an aarch64-specific
option (currently) which does nothing on other targets. On aarch64 this
generates code uses BTI/PAC instructions to mitigate Return Orientated
Programming attacks. This approach is backwards compatible and the code
size/performance impact is typically negliable.
More details can be found at
https://events.static.linuxfound.org/sites/events/files/slides/slides_23.pdf
(From OE-Core rev: 84e6064cde02b463066d7b63fcf8baf392491327)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream release notes:
v4.5.0
Issue 319: Remove SelectableGroups deprecation exception for flake8.
Previous upgrade release notes:
v4.4.0
Issue 300: Restore compatibility in the result from Distribution.entry_points
(EntryPoints) to honor expectations in older implementations and issuing
deprecation warnings for these cases: EntryPoints objects are once again
mutable, allowing for sort() and other list-based mutation operations. Avoid
deprecation warnings by casting to a mutable sequence (e.g.
list(dist.entry_points).sort()). EntryPoints results once again allow for
access by index. To avoid deprecation warnings, cast the result to a Sequence
first (e.g. tuple(dist.entry_points)[0]).
v4.3.1
Issue 320: Fix issue where normalized name for eggs was incorrectly solicited,
leading to metadata being unavailable for eggs.
(From OE-Core rev: 1d60ba1bc4eafc9cc232d61d2746f272fc966442)
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add RDEPENDS on python3-unittest
Upstream release notes:
6.13.14
This patch improves the :func:`~hypothesis.strategies.tuples` strategy
type annotations, to preserve the element types for up to length-five
tuples (:issue:`3005`).
As for :func:`~hypothesis.strategies.one_of`, this is the best we can do
before a `planned extension <https://mail.python.org/archives/list/typing-sigpython.org/thread/LOQFV3IIWGFDB7F5BDX746EZJG4VVBI3/>`__
to :pep:`646` is released, hopefully in Python 3.11.
6.13.13
This patch teaches :doc:`the Ghostwriter <ghostwriter>` how to find
:np-ref:`custom ufuncs <ufuncs.html>` from *any* module that defines them,
and that ``yaml.unsafe_load()`` does not undo ``yaml.safe_load()``.
6.13.12
This patch reduces the amount of internal code excluded from our test suite's
code coverage checks.
There is no user-visible change.
6.13.11
This patch removes some old internal helper code that previously existed
to make Python 2 compatibility easier.
There is no user-visible change.
6.13.10
This release adjusts some internal code to help make our test suite more
reliable.
There is no user-visible change.
6.13.9
This patch cleans up some internal code related to filtering strategies.
There is no user-visible change.
6.13.8
This patch slightly improves the performance of some internal code for
generating integers.
(From OE-Core rev: 545b062e6816ad0c97a91e3cdbc486fc381f6263)
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Several of the valgrind tests (particulaly helgrind) are unreliable and
can fail with a different output.
Particularly, there is a higher chance of failure on QEMU instances with
SMP enabled and on systems with more interrupts such as laptops on powersave.
The tests have been reported upstream as being unreliable dating back
over 5 years, due in part to the ordering of threads during
an "unwinding" process in helgrind.
https://bugs.kde.org/show_bug.cgi?id=345121https://bugs.kde.org/show_bug.cgi?id=430321
A workaround to improve the reliability of such tests is to force them
to run on a single CPU core using taskset. This greatly reduces the
chance of a failure.
>From my testing, I have found it can help reduce the rate of failures
on both a laptop and QEMU by over 5x. Stress-testing in QEMU for several
hours did not result in a failure while running the test normally did.
The flaky or undeterministic thread-based tests are defined in the
taskset_nondeterministic_tests file. These test cases will be run with
taskset 0x00000001 to run on a single CPU core rather then the regular
test.
The edited run-ptest executes the flaky tests first, then ignores them
to not duplicate the results from the main tests. Everything modified is
restored when testing is complete.
The drawback is that this isn't a foolproof solution. It helps the tests
fail much less frequently, and considering how this issue has been documented
for a long time, a workaround such as this is needed.
(From OE-Core rev: b318944dd72ca7b0408e955f3599381ab3ac3ba8)
Signed-off-by: Tony Tascioglu <tony.tascioglu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add runtime dependency to resolve errors that occurred when import libarchive.
(From OE-Core rev: 5d29a4f036a81076b9ddd98dd93d885f8d2b9f74)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As perl and perl-cross need to be updated (and patches rebased)
in lockstep, devtool upgrade (and therefore AUH) can't cope with it.
Manually updating is still possible, but painful.
Split determinism.patch into perl and perl-cross parts, move the
rest of the perl-cross patches.
(From OE-Core rev: 60dcb230f65fb1a0f23341c379676f82213d6240)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since commit [1] applied, PYTHON_INSTALL_DIR is not right
on nativesdk build which caused [installed-vs-shipped] QA issue
...
|Building for python3
|-- Python install dir is
|tmp-glibc/work/x86_64-nativesdk-wrlinuxsdk-linux/nativesdk-libdnf/0.63.0-r0/
recipe-sysroot-native/usr/lib/python3.9/site-packages
...
Yocto manually set PYTHON_INSTALL_DIR from recipe, it is not
necessary to call FindPythonInstDir.cmake which will override
Yocto setting
[1] f1cffbfb9f
(From OE-Core rev: d6b62b5a9d6c64971b9f981a4732791658150e43)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a patch to fix a reproducibility issue in the new version.
(From OE-Core rev: ea6fffe4f07cfd105f861ad0d2dc7c7605bf9e64)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The git repo for pkg-config was changed, so update the
SRC_URI accordingly with the new link.
(From OE-Core rev: 9fd1b9b8282d68213b187ab42fae27e6a3c95b2e)
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since Linux 5.4 a new read-only filesystem is available, erofs.
Compared to squashfs it offers much better read performance with and
without compression enabled.
It suppports two optional compressors, lz4 and lz4hc.
>From the mkfs.erofs man page:
EROFS is a new enhanced lightweight linux read-only filesystem with
modern designs (eg. no buffer head, reduced metadata, inline
xattrs/data, etc.) for scenarios which need high-performance read-only
requirements, e.g. Android OS for smartphones and LIVECDs.
It also provides fixed-sized output compression support, which improves
storage density, keeps relatively higher compression ratios, which is
more useful to achieve high performance for embedded devices with
limited memory since it has unnoticable memory overhead and page cache
thrashing.
This commit adds support for three new filesystem targets:
erofs: erofs without compression
erofs-lz4: erofs with lz4 compresssion enabled
erofs-lz4hc: erofs with lz4hc compression enabled
(From OE-Core rev: 41dead1ff8ccc49e6cd6e6f5d41a59d164693e0d)
Signed-off-by: Richard Weinberger <richard@nod.at>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update: Corrected license information
flex package is under two licenses:
- "BSD-3-Clause" is provided in top-level COPYING file; the license
actually include third obligation (without the actual "3" numbering)
- "LGPL-2.0+" is explained by src/gettext.h
(From OE-Core rev: 7beaae812f55a43797a459f3ad25f1be121bdbe1)
Signed-off-by: Dmitry Kisil <d.kisil@inango-systems.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add runtime dependency to resolve errors that occurred when import more_itertools.
(From OE-Core rev: 2165dc8b7f8448d5053ce25d676039430db25203)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This issue is seen with clang/libc++
(From OE-Core rev: 65e9606bae6bcd849e3e30f3ce093ee64838b774)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Making ptest images based on core-image-minimal uncovered quite a
few missing depenendcies from various recipes, here they are.
(From OE-Core rev: 2cda6242f2f0f6f9c6bdef72bbb271eab7e5e1f5)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Commit dbb87d in the GCC 11 branch was intended to make the installation of
this Python module more robust, but for unknown reasons the library_name
in libstdc++.la in baremetal builds (for example, Zephyr) is unset, so the
module is just installed as "-gdb.py".
This may be a GCC bug, or a bug in our build. Until that is resolved,
revert the commit to fix the packaging.
(From OE-Core rev: 61947fc024bf18b42547d2ea4cad90184132994d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
CMake depends on having all formats supported and build issues can
arise when zstd is not available:
https://gitlab.kitware.com/cmake/cmake/-/issues/21552
Quote from a CMake dev:
"As far as CMake's design is concerned, we have no optional formats.
All should be supported. That's why we bundle sufficiently new versions
of libarchive and libzstd. If a distro builds with an older libarchive
that doesn't have zstd support, then that is not a proper packaging of CMake."
(From OE-Core rev: 897d3695e11484cb5e62d63e4d6b0b4893605c56)
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream has never published the 2.0.1 tarball.
(From OE-Core rev: 00f3ebbab50182ad5b948f266480cf30f9eb1d33)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop patch as upstream has fixed the issue.
(From OE-Core rev: 656894bc388bc5c65e2b7cc4a34642bf17db89bf)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
