Running, e.g., `devtool reset sdbus-c++` would result in the following
error:
re.error: multiple repeat at position 35
This was due to the ++ in the recipe name, which would be treated as an
incorrect regular expression in _reset().
Use re.escape() to make sure all characters in the recipe name are
treated literally.
(From OE-Core rev: 6e73bd9b3e6d529752db93879f2c0ed53873dd1a)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The demo uses some SVG icons, so depend on the SVG pixbuf loader so that
they are visible.
(From OE-Core rev: 77e18e640c42ee3992464fddc1a16760cea9bc4f)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since Ubuntu 20.04 is heading to EoL and that we're having other issues
on that platform needing buildtools anyway, we're about to lose the
last python 3.8 platform we were supporting.
Bump the minimum version to 3.9 since there are many developers wanting
access to newer python features.
This likely won't be seen since the bitbake minimum has also been
increased but helps for documentation purposes.
(From OE-Core rev: c3db241c6e97420ca0705d1535a7cdd0c273b761)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard managed to reproduce a pseudo bug that pciutils in a minimal
test case[1] which confirmed that it was the symlink creation causing
issues.
The pciutils Makefile has several installation targets:
- install: binaries, manpages, shared library
- install-lib: headers, library symlinks, shared library
We need to run both targets to install the full set of files we want to
be installed, but notably they both create the .so symlink and as they're
running in parallel this is what triggers the bug in pseudo.
Until the bug has been resolved (or the Makefiles don't duplicate rules),
just run the two targets separately.
[ YOCTO #14957 ]
[1] https://lore.kernel.org/openembedded-core/20250319133457.806384-1-richard.purdie@linuxfoundation.org/T/#u
(From OE-Core rev: a5fc49fafe910a25be7372c82bfbd7876871ce3f)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This includes fixes for gcc 15.
License fixes were also made in the repository. The license being referred to
as MIT was in fact HPND so fix the LICENSE on the recipe accordingly.
Use the new bitbake tag functionality to verify the commit matches the tagged
version.
Trim the license checksums to the top level COPYING files now everything
is accurate.
(From OE-Core rev: c9d3a47a19babfe88f0174233729394292a31726)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The new version is in a location that isn't discoverable
by upstream version checks, and so has been overlooked for a while.
Drop patches:
0001-mesa-demos-Add-missing-data-files.patch
(backport)
0004-Use-DEMOS_DATA_DIR-to-locate-data-files.patch
(very old patch rejected by upstream as not necessary and not making sense:
https://gitlab.freedesktop.org/mesa/demos/-/issues/9 )
Disably wayland for now due to libdecor dependency,
adjust other feature dependencies as needed.
(From OE-Core rev: 59a9e96fa43e18af932cec7c2f1a36d9fcafff94)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pull in upstream changes for fix the build with gcc 15 and README tweaks.
(From OE-Core rev: 0ba624f30d482c0c7d86202d46abdab9d148c9b0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are conflict of config files between kea and lib32-kea:
| Error: Transaction test error:
| file /etc/kea/kea-dhcp6.conf conflicts between attempted installs of lib32-kea-2.6.1-r0.core2_32 and kea-2.6. 1-r0.core2_64
Similar to:
| 8cc65e7eb0 kea: fix conflict between multilibs
(From OE-Core rev: 0fe8ec57f19d79e94f02e3c710a1b76c04b34143)
Signed-off-by: Lei Maohui <leimaohui@fujitsu.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix function prototypes for C23 to work
(From OE-Core rev: 2bdb276345b4b40be53d818116f71851e45cd1b1)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fix gcc-15 compiling error: too many arguments to function eppic_init
(From OE-Core rev: 3bd6bbd77e8ceb068baeffd7670eb51efd52d917)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is in conflict with signature from system time.h
extern time_t mktime (struct tm *__tp) __THROW;
GCC-15 with C23 on, this is treated at error
posixtm.c:45:8: error: conflicting types for 'mktime'; have 'time_t(void)' {aka 'long int(void)'}
| 45 | time_t mktime ();
| | ^~~~~~
|
config.h is local include file to use quotes to include it
(From OE-Core rev: afc888d87fbf268c43bbcc81aa378eb9d58397a8)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Stick to C17 standard as GCC 15 switches to C23
(From OE-Core rev: 4ae08da819d1bc5fee382651c3fe074e9be9d86e)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If tag.gpgSign is configured in Git's configuration, then creating the
build-minus-X tags will fail (if Git's core.editor is not configured) or
it will hang (when trying to open the editor). This is beacause
tag.gpgSign causes git tag to create annotated tags. To avoid this,
specify --no-sign as argument to git tag.
(From OE-Core rev: 7595a0a63a933af9dd9d1e458dc34a4ba80d9eae)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If tag.gpgSign is configured in Git's configuration, then creating the
devtool-patched tag will fail (if Git's core.editor is not configured)
or it will hang (when trying to open the editor). This is beacause
tag.gpgSign causes git tag to create annotated tags. To avoid this,
specify --no-sign as argument to git tag.
(From OE-Core rev: 5dba8d0b6c940934375eea9af37e7c4856b51c96)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If tag.gpgSign is configured in Git's configuration, then creating the
devtool-base tag will fail (if Git's core.editor is not configured) or
it will hang (when trying to open the editor). This is beacause
tag.gpgSign causes git tag to create annotated tags. To avoid this,
specify --no-sign as argument to git tag.
(From OE-Core rev: f96e955b29aad6a9e0b20f8e9a4987ace3808c91)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1.84.0 - 2025-03-15
-------------------
* No changes
1.83.4 - 2025-03-08
-------------------
* Revert support for "static" virtual functions [!526]
1.83.2 - 2025-03-01
-------------------
* Improve GType inspection helper [!494]
* Parse C11's _Alignas [#520]
* Respect custom Python binary [!503]
* Fix build on the latest Windows SDK [!498]
* Small performance improvement when looking up a signal information [!504]
* Use standard imports in the JavaScript templates for g-ir-doctool [!501]
* Ensure that enumeration members can be marked as deprecated [!512]
* Add more test coverage for structured union types [!348]
* Add an option to skip tests when building [!507]
* Fix various MSVC compatibility issues [!511]
* Add support for "static" virtual functions [!361]
* Allow specifying the format of the documentation inside doc blocks [!401]
* Handle C99's _Complex [!515]
* Consider UCRT64 and CLANG64 as mingw32 compilers [!516]
* Handle static NSString syntax [!518]
* Add instance parameter checks to strict validation [!506, !521]
* Documentation improvements [!481, !483, !485, !500]
(From OE-Core rev: cc3bfd7547d88ac0ae11c11812aafb89965a659a)
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ppp-2.5.2 tarball ships a generated header with various
configuration settigns that takes precedence over the same
header generated into the build directory during the actual build.
This resulted in various linking fails that were worked around
by enabling multilink in 2.5.2 version update. The correct fix
that removes all contamination is to remove the bogus header first.
(From OE-Core rev: 87863ce4530cf08fd28b1bde13e3f7142001b54d)
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>
License-Update: Upstream added SPDX tags and more license information. The
main license is AFL-2.1 | GPL-2.0-or-later however some files are
LGPL-2.1-or-later or MIT licensed. The bash completiion plugin is
GPL-2.0-or-later only.
Therefore:
* Add checksums for the separated license files
* Update the main LICENSE
* Specify the correct license for the bash completion plugin
(From OE-Core rev: 82f2675ad3821398a849ced303b6f637f14723d1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This isn't a common license as it's the DocBook v4 XML DTD license, and
that is now part of the recipe itself.
(From OE-Core rev: 11c366ebff98dad34d95aac0cfee571f78b87252)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Don't use the common 'OASIS' license, as this isn't a SPDX license and
is in fact specifically the DocBook XML v4 license text.
Instead, use NO_GENERIC_LICENSE to ship a custom license file. We still
need to ship a copy of it in-tree because the license code needs a bare
copy of the license text. Reference the in-tree license text in the
license checksum to show that we've verified they match.
Also, clean up some comments.
Thanks to hongxu.jia@eng.windriver.com for a previous iteration of this.
(From OE-Core rev: d04db152a512f564566a4205db6fe788fcbadde2)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add tests for git tag verification in both standard and shallow clones.
(Bitbake rev: f47127066d67e2ad80974fa1e7c0fcc7409161af)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we want to validate a tag when using shallow clones, we need to ensure
the tag is imported to the clone. Adding to extra_refs allows this to happen
ensuring tag validation in shallow clones works.
(Bitbake rev: 03945475886b8d31c7eccc80fe594ab5306bcf5d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently bitbake disallows tag parameters along with revision parameters.
This isn't great since quite often, we'd like to verify that a given revision
does match some tag. At the same time we don't want to or need to access
the network to verify this, which normally a tag would require.
Rework the code so that tag and revisions can both be specified together.
Verify that any tag specified matches the revision in use at unpack time.
This means we can start requiring people to put tags in git SRC_URIs
when revisions are used, making review a little easier that it isn't
some random revision.
The test that is dropped looks like a different test but the comment
is a copy and paste error. The SRCREV/rev mismatch test remains, this
removes the rev and tag set test.
(Bitbake rev: d591d7633fe8d739ec00395920e44910b0b77e27)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Move to the FKIE feed by default, as it is showing better stability
than NVD2. Content of the feed should be the same.
(From OE-Core rev: 10580a6d36aa1366732f9c030345bd4590eb9f74)
Signed-off-by: Marta Rybczynska <marta.rybczynska@ygreky.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Replace the UTF8 character for non-breaking space with regular
(ASCII) space in RDEPENDS:${PN}-utils variable.
(From OE-Core rev: ee772df90dfc0eb1c973282e3bfac7357d42b0db)
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Newer snapshots of ncurses have the fixes but they are many needed to get
C23 going. Until next release lets stick with C17 even while GCC 15 switches
to C23 defaults.
(From OE-Core rev: f3081700d931fc8f7d5cb13494e11100cb28b19f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes build with GCC-15 which is defaulting to C23
(From OE-Core rev: c4978268a4714466ecdec14d865a61adc47f3b3b)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GCC 15 has switched to C23 by default and tcp-wrappers is old code
pre-c99 and would need to be fixed all around to get to work in C23
(From OE-Core rev: 0a532f07eb54b7f66be25a0f9584581ab693b21c)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GCC 15 defaults to C23 and bash is not yet ready for that
so keep using C17 like GCC 14 for now
(From OE-Core rev: aa9ac09aa7b8d4bd4427dbb26ae595b97b60da2f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GCC15 is switching defaults to C23 and gdbm is not yet ready to
compile using C23 std.
(From OE-Core rev: e0f13f9bc96a0dd4c5f6750a8106422a6d015359)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It removes the installation of ptest cases when upgrade libpam to 1.7.0.
Add them back to make ptest work. And 2 more cases in libpam 1.7.0.
(From OE-Core rev: ba8266267b4a89285bba0fceeaa1507957d318fb)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
