This helps in fending off the build time QA error
WARNING: /mnt/b/yoe/master/sources/meta-openembedded/meta-oe/recipes-core/opencl/opencl-icd-loader_2023.12.14.bb: RPROVIDES is set to v
irtual/opencl-icd, the substring 'virtual/' holds no meaning in this context. It is suggested to use the 'virtual-' instead.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Zoltán Böszörményi <zboszor@gmail.com>
Since gnome classes are using it in core, they are now appearing after
native resulting in QA errors
ERROR: /mnt/b/yoe/master/sources/meta-openembedded/meta-gnome/recipes-gnome/evolution-data-server/evolution-data-server-native.bb: QA Issue: evolution-data-server-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: pkgconfig.bbclass
siteconfig.bbclass siteinfo.bbclass autotools.bbclass [native-last]
secondly, use 'cmake' for GNOMEBASEBUILDCLASS
default is set to meson (legacy is autotools) since most of gnome recipes are using meson
these days. This recipe however uses neither autotools nor meson to
build, it uses cmake, to this effect it inherits cmake bbclass
and things worked so far, however with inherit_defer things changed because
meta/classes-recipe/gnomebase.bbclass has switched to using
inherit_defer, this unearths this issue where its not overriding
exported functions as desired. Therefore this fixes that issue
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Nothing in oe-core depends on rng-tools anymore:
e7e1bc43ca rng-tools: splitting the rng-tools systemd/sysvinit serivce as a package
so move it to meta-oe for people who still want to run rngd
as a service for some reason or for those who want to run rng-test.
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Khem Raj <raj.khem@gmail.com>
GRPC depends on protobuf, not protobuf-c
Additionally zlib is missing in dependencies
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The gnome-keyring functionality is nowadays provided by libsecret and gnome-keyring
has been deprecated. This will prevent from getting it installed/running it twice.
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Updated license checksum for copyright year and verified MIT still applies
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Convert recipe to pypi
Update license checksum for copyright year and verify MIT still applies
Signed-off-by: Derek Straka <derek@asterius.io>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
Also, clean up FILES:
Don't package all of ${datadir} in PN, as this means the locale
information isn't split into the appropriate packages.
.la files are deleted globally so there's no need to package them in
PN-dev.
Debug files are managed automatically so there's no need to package them
at all.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Recent changes to oe-core[1] mean that if a configure.ac uses gtk-doc
then gtkdocize will be called. This means that recipes that don't
inherit gtk-doc (to depend on gtk-doc-native) but don't explicitly
disable the use of gtkdocize will fail to configure.
Inheriting gtk-doc both solves the configure failure, and allows us to
build the API documentation.
[1] oe-core 891ec38d4c5cc5ac7bc34938276261ebd6f6d54e
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Building the recipe with MUSL fails, because it uses error.h which isn't
supported by MUSL. Because the usage is only in one expression, it's easy to
rewrite this.
Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Packages that use gtk-doc want to find a native gtk-doc not a target
gtk-doc, so remove the pointless check for a target gtk-doc package.
This only worked before as it was being pulled in via DEPENDS in
glib-2.0, but as of oe-core f91694f this no longer happens.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Now that autotools uses autopoint to call gtkdocize, this variable is no
longer needed.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update the GTK_DOC_CHECK invocation to specify where the
documentation will be built (as the default is ./docs).
This is needed so that gtkdocize as run by autopoint knows where the
documentation will be built. At the moment we manually call gtkdocize
but this will change to autopoint in the future.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update to 1.26.1.
Remove the Makefile.am patches as they no longer apply due to
the switch to Meson.
Backport a fix that prevents installing 50-rc_keymap.conf in systems
without systemd.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Error: Transaction test error:
file /usr/share/yang/ietf-interfaces.yang conflicts between attempted installs of libsmi-yang-0.5.0-r0.cortexa57 and frr-9.1-r1.cortexa57
frr also uses the doc 'ietf-interfaces.yang'.
frr has a priority of 100.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Error: Transaction test error:
file /usr/share/yang/ietf-interfaces.yang conflicts between attempted installs of libsmi-yang-0.5.0-r0.cortexa57 and frr-9.1-r1.cortexa57
libsmi also uses the doc 'ietf-interfaces.yang'.
libsmi has a priority of 50.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fixes installed-vs-shipped e.g. in multilib builds with libdir set to /usr/lib32:
ERROR: QA Issue: lib32-libpwquality: Files/directories were installed but not shipped in any package:
/usr/lib/python3.11/site-packages/pwquality.cpython-311-arm-linux-gnueabi.so
/usr/lib/python3.11/site-packages/pwquality-1.4.5-py3.11.egg-info
/usr/lib/python3.11/site-packages/pwquality-1.4.5-py3.11.egg-info/SOURCES.txt
/usr/lib/python3.11/site-packages/pwquality-1.4.5-py3.11.egg-info/PKG-INFO
/usr/lib/python3.11/site-packages/pwquality-1.4.5-py3.11.egg-info/dependency_links.txt
/usr/lib/python3.11/site-packages/pwquality-1.4.5-py3.11.egg-info/top_level.txt
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
lib32-libpwquality: 6 installed and not shipped files. [installed-vs-shipped]
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
0001-cmake-Link-with-libatomic-on-rv32-rv64.patch refreshed
Changelog:
Core
Implemented dualstack IPv4 and IPv6 backend support, as per draft gRFC A61. xDS support currently guarded by GRPC_EXPERIMENTAL_XDS_DUALSTACK_ENDPOINTS env var.
Dropped Bazel 5 support. (#34813)
[deps] Upgrade protobuf version to v25.0. (#34513)
[Security - Revocation] Crl Directory Watcher Implementation. (#34749)
[server] Cap size of pending request queue with RealRequestMatcher. (#34782)
[chttp2] Fix outgoing data stats. (#34693)
[EventEngine] Enable Posix EventEngine Listener on all builds. (#34748)
[EventEngine] Enable Windows EventEngine Listener on all builds. (#34436)
[chttp2] Alternative protection for too many streams in the system. (#34697)
[Proxy] Support for setting proxy for addresses. (#34617)
[client idleness] client channels go idle after 30 minutes by default. (#34653)
[chttp2] Add an experiment to separate liveness checks from ping timeouts. (#34647)
[chttp2] Tarpit invalid requests. (#34641)
[chttp2] Enforce settings acks. (#34640)
[chttp2] Limit work per read cycle. (#34639)
[chttp2] Limit request count before receiving settings ack. (#34638)
[chttp2] Randomly ping on RST_STREAM. (#34637)
C++
[xds] C++ XdsServerBuilder Remove src/... header dependency from public header. (#34790)
[reflection] Add v1 reflection. (#34535)
C#
[csharp] Grpc.Tools documentation for sharing proto files between projects and nuget packages. (#34521)
Ruby
[ruby] create debug symbol packages. (#34632)
Python
[Bug Fix] Change return of grpc.aio.ServicerContext.code() from integer to grpc.StatusCode. (#34292)
Signed-off-by: alperak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
6.6+ kernel has the warning options moved to dedicated include file
under scripts called Makefile.extrawarn, therefore search for this
file as well to remove this unrecognized option by clang
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Version 45.3
Released: 2024-01-05
This is a stable release with the following changes:
Recognize links in package update descriptions
Increase speed of load of the category pages
Fix deadlock when cancelling app update
This release also updates translations:
Chinese (Taiwan) (Andre Klapper)
Persian (Danial Behzadi)
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
============
Version 45.2
============
Apps
- Fix status page glitch on initialization
- Fix "File and Link Association" interface not reflecting changes
Background
- Improve background preview and chooser performance
Default Apps
- Fix undesired resetting of default apps during startup
Mouse
- Fix interference issue with scroll event in Mouse Test window
Network
- Close network editor when using non-native nm-connection-editor
- Show decoration buttons on empty-state (no network device found page)
- Share WPA3 (SAE) networks with QR Code
- Hide QR Code icon when connection is not successful
- Remove deprecated 'wpa-none'
- Fix route label alignments
Privacy
- Fix crash from free bug in the Camera page
- Fix potential crash on Bolt page visibility
Region
- Show preview measurement format in current locale
Sound
- Update mute state when setting mixer control for a stream
Users
- Show tooltip information for the Avatar widget
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changelog:
* Multiple registers can now be dumped at once, via the generic dump
operation.
* Relax the driver matching to accept the strings used in kernels 6.2
and newer.
Signed-off-by: Michael Haener <michael.haener@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The git revison info is added [1] to make the version more descriptive
to produce an incremental revision number like 1.8.18.13 or 1.8.18.14
and etc and more clear in terms of "what codebase was used" like
`1.8.18.13.gee01aa5`. But it also introduces the version inconsistence.
Note as stated in [1]
For cases when .git directory is missing (Release compilation?) the suffix
part will be omitted completely yielding a version like `1.8.18`.
Considering the version we acutally used in oe is a release version,
the git revision info as [1] is meaningness. So drop the git revsion
info to make the version consistent.
Before the patch:
root@qemux86-64:~# ipmitool -V
ipmitool version 1.8.19.19.gab5ce5b
root@qemux86-64:~# rpm -qa | grep ipmitool
ipmitool-1.8.19-r0.core2_64
After the patch:
root@qemux86-64:~# ipmitool -V
ipmitool version 1.8.19
root@qemux86-64:~# rpm -qa | grep ipmitool
ipmitool-1.8.19-r0.core2_64
[1] https://github.com/ipmitool/ipmitool/commit/ba01dc84b4e225c86eac3f562e629662d752040f
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Keep nvme-cli in sync with libnvme which was upgraded from 1.6 to
1.7.1 by the following commit:
* 7a6ca59ab libnvme: upgrade 1.6 -> 1.7.1
Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Khem Raj
Randy MacLeod
Peter Marko
alperak
Markus Volk
Derek Straka
Ross Burton
Jörg Sommer
Alex Kiernan
Wang Mingyu
Fabio Estevam
Martin Jansa
Michael Haener
Mingli Yu
Christophe Vu-Brugier