First, it sets a weak default value for IMAGE_ROOTFS_MAXSIZE.
This helps the recipe linter oelint-adv from meta-sca to be aware
of the existence of this variable.
See https://github.com/priv-kweihmann/oelint-adv/issues/695 for details.
Note: The chosen weak default value actually imposes no limit
First, it sets a weak default value for IMAGE_ROOTFS_MAXSIZE.
This helps the recipe linter oelint-adv from meta-sca to be aware
of the existence of this variable.
See https://github.com/priv-kweihmann/oelint-adv/issues/695 for details.
Note: The chosen weak default value actually imposes no limit
First, it takes into account that the initramfs might
be built with another multiconfig.
Second, an unnecessary dependency is dropped in case the
initramfs is already bundled into the kernel.
Weisser, Pascal (2):
kernel-fitImage: Take possible multiconfig into account.
kernel-fitImage: Remove
Currently, Yocto only supports FIT setups in extlinux for providing and
applying Device Tree Overlays. It even has an additional requirement of
needing the base FDT image node to have a load property outside of the
DRAM location where the FIT data is stored. This is being fixed in
U-Boot, c.f.
http
Step-wise upgrade as the first step required the most effort
and it was already submitted (skipped due to regressions).
Peter Marko (2):
curl: upgrade 8.10.1 -> 8.11.0
cure: upgrade 8.11.0 -> 8.11.1
meta/recipes-support/curl/curl/no-test-timeout.patch | 2 +-
.../curl/{curl_8.10.1.bb =>
From: Hiago De Franco
This series aims to upgrade weston from version 13.0.3 to 14.0.1.
Since commit a16598b038b2 ("backend-drm: make libdisplay-info
mandatory") from Weston, libdisplay-info is now a build dependency,
therefore I am also adding libdisplay-info recipe into this series.
In order
Guðni Már Gilbert (2):
bluez5: add PACKAGECONFIG for library
python3: add bluez5-native to DEPENDS conditionally
meta/recipes-connectivity/bluez5/bluez5.inc| 8 +++-
meta/recipes-devtools/python/python3_3.13.0.bb | 3 +++
2 files changed, 10 insertions(+), 1 deletion(-)
--
2.43.0
On 20 Sep 2024, at 09:53, Robert Yang via lists.openembedded.org
wrote:
> The VENDOR_REVISION is for cve scanners to know the CVEs have been fixed in a
> lower version, CVE scanners such as Trivy can know the CVEs have been fixed in
> a higher version, but it can't know the CVE is fixed in a lowe
Hi,
On Tue, Sep 24, 2024 at 04:21:49PM +0800, Robert Yang wrote:
> On 9/24/24 15:52, Mikko Rapeli wrote:
> > Hi,
> >
> > On Fri, Sep 20, 2024 at 01:53:13AM -0700, Robert Yang via
> > lists.openembedded.org wrote:
> > > From: Robert Yang
> > >
> > > The VENDOR_REVISION is for cve scanners to kn
On Tue, 24 Sept 2024 at 10:18, Robert Yang wrote:
> > done by users in local installations? This does appear hack-ish to me,
> > the better thing to do would be to actually include the list of fixed
> > CVEs into package metadata.
>
> The problem is that Trivy can't work in this way AFAIK.
You do
On 9/24/24 15:52, Mikko Rapeli wrote:
Hi,
On Fri, Sep 20, 2024 at 01:53:13AM -0700, Robert Yang via
lists.openembedded.org wrote:
From: Robert Yang
The VENDOR_REVISION is for cve scanners to know the CVEs have been fixed in a
lower version, CVE scanners such as Trivy can know the CVEs have b
On 9/24/24 12:47, Alexander Kanavin wrote:
On Tue, 24 Sept 2024 at 06:24, Robert Yang wrote:
Thanks for looking into this, the problem is that the metadata (CVE patch info)
is not in the binary packages such as RPMs, so the cve scanners such as Trivy
doesn't know that. For example, CentOS and
Hi,
On Fri, Sep 20, 2024 at 01:53:13AM -0700, Robert Yang via
lists.openembedded.org wrote:
> From: Robert Yang
>
> The VENDOR_REVISION is for cve scanners to know the CVEs have been fixed in a
> lower version, CVE scanners such as Trivy can know the CVEs have been fixed in
> a higher version,
On Tue, 24 Sept 2024 at 06:24, Robert Yang wrote:
> Thanks for looking into this, the problem is that the metadata (CVE patch
> info)
> is not in the binary packages such as RPMs, so the cve scanners such as Trivy
> doesn't know that. For example, CentOS and Ubuntu also has the similar issues,
>
Hi Alexander,
On 9/24/24 01:19, Alexander Kanavin wrote:
I don't understand. If we fix a CVE with a backport, then there's
metadata in the backported patch to indicate that even though the
overall version doesn't change to the one that isn't vulnerable, the
patch addresses the vulnerability. Why
I don't understand. If we fix a CVE with a backport, then there's
metadata in the backported patch to indicate that even though the
overall version doesn't change to the one that isn't vulnerable, the
patch addresses the vulnerability. Why is a whole separate mechanism
still needed?
Alex
On Fri,
From: Robert Yang
The VENDOR_REVISION is for cve scanners to know the CVEs have been fixed in a
lower version, CVE scanners such as Trivy can know the CVEs have been fixed in
a higher version, but it can't know the CVE is fixed in a lower version without
a helper, we have the following ways to se
Hello,
on any ptest failure, testimage build a list of artifacts to retrieve from
the target under test, create an archive and pull the corresponding raw
stream onto the controlling host (eg: autobuilder), which uncompresses it
immediately.
This small series follows a request to keep those artifac
From: Mark Hatle
This resolves problems when building an SDK that includes multilibs.
It also adds the isfile change that was previou put in for spdx 2.2.
Introduce a new multilib SSTATE_ARCHs, as an optimization this just
defaults to SSTATE_ARCHs in most cases. If building an SDK we do
expand
From: Ricardo Simoes
The recipe `volatile-binds` relies on the `mount-copybind` script
to create volatile mount points. In commit [1], the script was modified
to use OverlayFS as the primary mount strategy. If OverlayFS fails, it
falls back to an old-school bind mount.
To meet the requirements o
AMD (Xilinx) toolchain building for our 'vitis' product line seems to trigger
two issues with the SPDX processing. Specifically:
*) Baremetal toolchain elements may have directories listed in them, which
triggers a hashing failure
*) The toolchains are built of multilib packages, which trigge
Doesn't this cause:
ERROR: hdparm-9.65-r0 do_populate_lic: QA Issue: hdparm: hdparm is a
generic license, please don't use NO_GENERIC_LICENSE for it.
[license-no-generic]
?
On Mon, Jul 1, 2024 at 4:33 PM Joshua Watt via lists.openembedded.org
wrote:
>
> Ah, right, I should have known that would h
Hello,
this small series aims to fix Bugzilla issue 15536 [1], which results in a
big disk storage consumption and/or inode max count issue. The main root
cause is that in its current form, the artifacts retriever convert symlinks
to the targeted files. This series changes the way those files are
r
Ah, right, I should have known that would happen. I'll send the fix
On Mon, Jul 1, 2024 at 12:56 AM Richard Purdie
wrote:
>
> On Thu, 2024-06-27 at 16:16 -0600, Joshua Watt via lists.openembedded.org
> wrote:
> > Adds a script to read the released SPDX license JSON data, and uses it
> > to updat
Thanks, these look good.
Alex
On Mon, 1 Jul 2024 at 07:56, Primoz Fiser via lists.openembedded.org
wrote:
>
> Hi,
>
> these 2 patches fix pulseaudio issues with Y2038 compatibility. And in
> turn solve run-time issue with "Stack smashing" as described here [1].
>
> Explanation:
>
> Patch #1: Add
On Thu, 2024-06-27 at 16:16 -0600, Joshua Watt via lists.openembedded.org wrote:
> Adds a script to read the released SPDX license JSON data, and uses it
> to update the common license files
>
> Joshua Watt (2):
> scripts/pull-spdx-licenses.py: Add script
> licenses: Update to SPDX license ver
Hi,
these 2 patches fix pulseaudio issues with Y2038 compatibility. And in
turn solve run-time issue with "Stack smashing" as described here [1].
Explanation:
Patch #1: Adds PACKAGECONFIG[oss-output] and hence adds configure flag
"-Doss-output=disabled" by default to pulseaudio. This in turn dis
Adds a script to read the released SPDX license JSON data, and uses it
to update the common license files
Joshua Watt (2):
scripts/pull-spdx-licenses.py: Add script
licenses: Update to SPDX license version 3.24.0
meta/files/common-licenses/3D-Slicer-1.0 | 190 +
meta/files/common-lice
From: Robert Yang
The fmt is from meta-oe, will send a patch to remove it from meta-oe after this
patch is merged.
// Robert
The following changes since commit 07b4c7a2bd23f8645810e13439e814caaaf9cd94:
linuxloader: add -armhf on arm only for TARGET_FPU 'hard' (2024-06-11
11:41:09 +0100)
ar
On Thu, Apr 11, 2024 at 12:47 PM Justin Bronder
wrote:
> Removing a couple of remaining ${PYTHON_PN} uses that were missed in the
> prior scrubs.
>
Thank you. I thought we had already caught everything.
We really do not need to be carrying such obfuscation and abstraction
anymore. Let python2 go
Removing a couple of remaining ${PYTHON_PN} uses that were missed in the prior
scrubs.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#198143):
https://lists.openembedded.org/g/openembedded-core/message/198143
Mute This Topic: https://lists.openem
While going down the rabbit hole of UPSTREAM_CHECK, I came across this
package needing updates. I found the switch to github on the webpage
and updated, etc. With the first patch, I get:
acpica2023062820240322Ross Burton
170fc3076a86777077637f10b05c32ac21ac13
*** BLURB HERE ***
lixiaoyong (2):
utils.bbclass: enhance readelf command call with llvm
oe/package.py: enhance objdump command call with llvm
meta/classes-global/utils.bbclass | 4 ++--
meta/lib/oe/package.py| 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.34.1
This perl package has not seen any updates since 2020.
The upstream author of Error has deprecated it for quite some time.
https://metacpan.org/pod/Error#WARNING
'Using the "Error" module is no longer recommended due to the
black-magical nature of its syntactic sugar, which often tends
A feature in vscode-cpptools was just added that allow us to pass the absolute
compiler path through the devtool ide-sdk generated configuration. We can
revert the meson.bbclass modification to avoid any potential issues with using
absolute paths in meson.cross.
-=-=-=-=-=-=-=-=-=-=-=-
Links: Yo
The python3-pytest upgrade to 8.0.0 caused a failure in python3-attrs.
https://github.com/python-attrs/attrs/issues/1233
Tim Orling (1):
python3-attrs: skip test failing with pytest-8
Wang Mingyu (1):
python3-pytest: upgrade 7.4.4 -> 8.0.0
...funcs-skip-test_unknown-for-pytest-8.patch | 30
Hello,
this small series is a very late follow-up to my initial artifacts
retrieval series (sorry for the delay).
The initial series can be found in [1]. The goal is to retrieve some
specific files from target whenever some tests fail, to ease debugging. The
feature relies on a new TESTIMAGE_FAILED
From: Robert Yang
The following changes since commit d2c4e8cb85c6a5ca37c7990f879c3b650df5770b:
vte: Separate out gtk4 pieces of vte into individual packages (2023-12-04
12:45:20 +)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/upgrade
https://githu
The following changes since commit 212affe748e2f628ecf11f26485b07dd303fe6e3:
Revert "binutils: Fix CVE-2022-47007" (2023-11-23 14:58:06 +)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/upgrade
https://github.com/robertlinux/yocto/tree/rbt/upgrade
Rob
Not sure if there is a better way to enable the cmake-qemu.bbclass for
all recipes inheriting also the cmake.bbclass globaly.
Adrian Freihofer (2):
cmake-qemu.bbclass: support qemu for cmake
cmake.bbclass: optionally support qemu
meta/classes-recipe/cmake-qemu.bbclass | 28 ++
From: Lukas Funke
The patch series aims to reduce the noise in patches created by devtools. Some
diffs are just introduced due to an update in the hash or in the diffstats.
These changes are not important to a reviewer.
Stefan Herbrechtsmeier (2):
patch: extract patches without diffstats
pat
Hello Alexandre,
On 10/20/23 08:05, Alexandre Belloni via lists.openembedded.org wrote:
> Hello Alexis,>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/5886/steps/14/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5935/steps/14/logs/stdio
> http
Hello Alexis,
On 19/10/2023 11:53:50+0200, Alexis Lothoré via lists.openembedded.org wrote:
> It has been observed that useful information in regression report can be
> drowned in huge regression lists which are often false-positives (for
> example, a whole set of tests has been temporarily disabl
From: Eero Aaltonen
Enable DNS resolution features from systemd-resolved, such as Multicast DNS for
distros using systemd.
The first commit enables systemd-resolved via glibc nsswitch.conf, which is one
of the interfaces recommended by systemd upstream.
The second commit enables mDNS resolutio
It has been observed that useful information in regression report can be
drowned in huge regression lists which are often false-positives (for
example, a whole set of tests has been temporarily disabled).
This series brings a default limit to how many changes are displayed per
base/target comparis
On 10/10/23 11:30, Alexis Lothoré via lists.openembedded.org wrote:
> With those two patches, I have been able to properly generate the
> regression report from [1] with the following command:
It looks like I forgot to paste the relevant command. Here it is, for
documentation purpose:
yocto_testre
There are still issues in Autobuilder when trying to generate regression
reports on master-next branch, as visible in [1]. This issue makes build
status as failed
After being finally able to replicate the issue locally (which is quite
difficult since master-next is a force-pushed branch), I observ
This is the first step toward better handling of empty packages and bogus
dependencies (e.g. ${PN}-dev -> ${PN}, ${PN}, being empty).
See: https://lists.openembedded.org/g/openembedded-architecture/message/1701
> a) Add warnings for dependencies (RDEPENDS or RRECOMMENDS) on packages
> which don't
Drop the backports
Fix patch-fuzz
Khem Raj (2):
systemd: Drop two upstreamed musl patches
systemd: Refresh patches to avoid patch-fuzz
...14-Use-uintmax_t-for-handling-rlim_t.patch | 23 ++---
...-not-disable-buffer-in-writing-files.patch | 89 +
.../0022-Handle-__cpu_mask-us
This patch series ensures that do_populate_sdk knows about
nativesdk-intercepts. It also ensures that debian builds work with
update_mandb.
Eilís 'pidge' Ní Fhlannagáin (2):
lib/oe/package_managegment: Add nativesdk-intercept PATH
update_mandb: deb fails due to missing man cache
meta/lib/oe/
The project changed its dependency for rfc3339 validation from package
"python3-strict-rfc3339" to package "python3-rfc3339-validation" after
v3.2.0.
But the v4.4.0 recipe in #kirkstone does not reflect this change and
still depends on package "python3-strict-rfc3339" when "format" is set
in PACKAG
This set of patches started out with fixing #15023 where building the sdk with
api-documentation set would fail out. This patch series fixes both of the main
underlying issues.
First, populate_sdk did not the nativesdk chown/chgrp intercepts in $PATH.
The second issue was within the chown/chgrp
On 2023-08-23 12:08, Khem Raj wrote:
On Wed, Aug 23, 2023 at 12:27 AM Luca Ceresoli
wrote:
On Wed, 23 Aug 2023 09:24:42 +0200
"Luca Ceresoli via lists.openembedded.org"
wrote:
Hello Trevor,
On Mon, 21 Aug 2023 13:38:38 -0400
"Trevor Gamblin" wrote:
The Cython 3.0.0 release contains many
On Wed, Aug 23, 2023 at 12:27 AM Luca Ceresoli
wrote:
>
> On Wed, 23 Aug 2023 09:24:42 +0200
> "Luca Ceresoli via lists.openembedded.org"
> wrote:
>
> > Hello Trevor,
> >
> > On Mon, 21 Aug 2023 13:38:38 -0400
> > "Trevor Gamblin" wrote:
> >
> > > The Cython 3.0.0 release contains many changes.
Hello,
this is another attempt to properly fix tag computation in Autobuilder.
First attempt ([1]) completely replaced "git tag" with "git ls-remote" to
make sure to know about all tags when computing new tag name. It raised
some issue because oe-git-archive works with local repositories with no
r
On Wed, 23 Aug 2023 09:24:42 +0200
"Luca Ceresoli via lists.openembedded.org"
wrote:
> Hello Trevor,
>
> On Mon, 21 Aug 2023 13:38:38 -0400
> "Trevor Gamblin" wrote:
>
> > The Cython 3.0.0 release contains many changes. Since there are a large
> > number of recipes that depend on it, there wil
Hello Trevor,
On Mon, 21 Aug 2023 13:38:38 -0400
"Trevor Gamblin" wrote:
> The Cython 3.0.0 release contains many changes. Since there are a large
> number of recipes that depend on it, there will potentially be build
> issues with recipes in meta-python and elsewhere. I performed a world
> buil
The Cython 3.0.0 release contains many changes. Since there are a large
number of recipes that depend on it, there will potentially be build
issues with recipes in meta-python and elsewhere. I performed a world
build on poky alone with the python3-cython upgrade and the only recipe
to fail was pyth
Hello,
this series brings a fix to a sporadic tag push issue observed in
autobuilder. The bug is documented in bugzilla #15140 ([1]). Basically,
whenever the autobuilder creates a new tag on test results, it is only
aware of "local" tags, which is kind of faulty since used repository is a
shallow c
From: Alexis Lothoré
Hello,
this very small series intend to eliminate confusion about regressions
reported by resulttool whenever a test result is present in "base test
result" but absent from "target test result". This scenario leads to many
"XXX -> None" lines. The series allows to define cust
On 5/12/23 10:06, Alexandre Belloni wrote:
Hello,
This caused the following failures on the AB:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/3986/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5176/steps/15/logs/stdio
https://autobuil
Hello,
This caused the following failures on the AB:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/3986/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5176/steps/15/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/bu
From: Randolph Sapp
Fix a few of the oddities introduced by the previous patch that allowed
specification of the DTB install directory and specification of vendor
directories in that directory.
Add a recursive search for dtb and dtbo files to make sure
upstream dtb directory standards don't brea
On Thu, 2023-04-13 at 18:31 +0800, Jamin Lin wrote:
> v1:
> kernel-fitimage.bbclass: allow users to change address-cells
> to support 64bits address
> uboot-sign.bbclass: allow users to change address-cells
> to support 64bits address.
>
> Jamin Lin (2):
> kernel-fitimage: support 64 bits addres
v1:
kernel-fitimage.bbclass: allow users to change address-cells
to support 64bits address
uboot-sign.bbclass: allow users to change address-cells
to support 64bits address.
Jamin Lin (2):
kernel-fitimage: support 64 bits address
uboot-sign: support 64bits address
meta/classes-recipe/kernel-
v1:
kernel-fitimage.bbclass: allow users to change address-cells
to support 64bits address
uboot-sign.bbclass: allow users to change address-cells
to support 64bits address.
Jamin Lin (2):
kernel-fitimage: support 64 bits address
uboot-sign: support 64bits address
meta/classes-recipe/kernel-
From: Alexis Lothoré
Hello,
this series is a small follow-up to [1]
- add explicit error when running yocto_testresults_query.py from
oe-core instead of poky. Since the tool is working with git references
from poky, it will not manage to resolve SHA-1 in oe-core
- add tests for new resulttoo
Per feedback from users, remove the top level image SPDX file and the
JSON index file from DEPLOYDIR. Having these files here is confusing to
end users because these files are not very useful by themselves, and
having them in DEPLOYDIR makes it unclear which they should be using.
Joshua Watt (2):
On Thu, Jan 26, 2023 at 10:06 AM Bruce Ashfield
wrote:
>
> On Thu, Jan 26, 2023 at 12:58 PM Khem Raj wrote:
> >
> > we need to define
> >
> > KBUILD_BUILD_USER="yocto"
> > KBUILD_BUILD_HOST="yocto"
> >
> > in linux-yocto defconfigs
> >
>
> No, we really don't want to do that.
>
> There's an envir
On Thu, Jan 26, 2023 at 12:58 PM Khem Raj wrote:
>
> we need to define
>
> KBUILD_BUILD_USER="yocto"
> KBUILD_BUILD_HOST="yocto"
>
> in linux-yocto defconfigs
>
No, we really don't want to do that.
There's an environment variable that is supposed to be reflected in
the build. Which we already se
we need to define
KBUILD_BUILD_USER="yocto"
KBUILD_BUILD_HOST="yocto"
in linux-yocto defconfigs
You can use my name too :)
On Thu, Jan 26, 2023 at 9:34 AM Richard Purdie
wrote:
>
> On Thu, 2023-01-26 at 12:07 -0500, Bruce Ashfield wrote:
> > On Thu, Jan 26, 2023 at 11:36 AM Richard Purdie
> >
On Thu, 2023-01-26 at 12:07 -0500, Bruce Ashfield wrote:
> On Thu, Jan 26, 2023 at 11:36 AM Richard Purdie
> wrote:
> >
> > On Thu, 2023-01-26 at 17:21 +0100, Alexandre Belloni wrote:
> > > On 26/01/2023 12:39:02+, Richard Purdie wrote:
> > > > On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi..
On Thu, Jan 26, 2023 at 11:36 AM Richard Purdie
wrote:
>
> On Thu, 2023-01-26 at 17:21 +0100, Alexandre Belloni wrote:
> > On 26/01/2023 12:39:02+, Richard Purdie wrote:
> > > On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> > > > From: Bruce Ashfield
> > > >
> > > > Richa
On Thu, Jan 26, 2023 at 11:36 AM Richard Purdie
wrote:
>
> On Thu, 2023-01-26 at 17:21 +0100, Alexandre Belloni wrote:
> > On 26/01/2023 12:39:02+, Richard Purdie wrote:
> > > On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> > > > From: Bruce Ashfield
> > > >
> > > > Richa
On Thu, 2023-01-26 at 17:21 +0100, Alexandre Belloni wrote:
> On 26/01/2023 12:39:02+, Richard Purdie wrote:
> > On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> > > From: Bruce Ashfield
> > >
> > > Richard,
> > >
> > > As promised, here are the commits to switch us over
On 26/01/2023 12:39:02+, Richard Purdie wrote:
> On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > Richard,
> >
> > As promised, here are the commits to switch us over to 6.1 as the
> > default.
> >
> > I'll also send a series for poky to bu
On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Richard,
>
> As promised, here are the commits to switch us over to 6.1 as the
> default.
>
> I'll also send a series for poky to bump things there as well.
>
> Also, if there are any significant prob
From: Bruce Ashfield
Richard,
As promised, here are the commits to switch us over to 6.1 as the
default.
I'll also send a series for poky to bump things there as well.
Also, if there are any significant problems, we'll just shelve this
while I look at any issues. But at this point, it is worth
On 05.01.23 14:22, Henning Schild via lists.openembedded.org wrote:
> Am Thu, 5 Jan 2023 12:52:21 +
> schrieb Felix Moessbauer :
>
>> For comparison, here the fstab files for the ext4 and the wic version
>> of the core-image-minimal (see below).
>
> In fact one probably really wants no fstab
Hi Richard,
On Wed, Jan 4, 2023 at 6:42 PM Richard Purdie
wrote:
>
> On Wed, 2023-01-04 at 13:18 +0100, toer...@gmail.com wrote:
> > From: Mark Jonas
> >
> > The patch series fixes a regression where images built for QEMU x86 and
> > x86-64 did not contain sound drivers matching the QEMU device
Am Thu, 5 Jan 2023 12:52:21 +
schrieb Felix Moessbauer :
> For comparison, here the fstab files for the ext4 and the wic version
> of the core-image-minimal (see below).
In fact one probably really wants no fstab / line at all, unless it is
ever somehow explicitly asked for.
The bootloader a
For comparison, here the fstab files for the ext4 and the wic version
of the core-image-minimal (see below).
Putting all persons in CC who have been involved in the first try and in
the revert.
Best regards,
Felix Moessbauer
Siemens AG
.ext4
```
# stock fstab - you probably want to override this
On Wed, 2023-01-04 at 13:18 +0100, toer...@gmail.com wrote:
> From: Mark Jonas
>
> The patch series fixes a regression where images built for QEMU x86 and
> x86-64 did not contain sound drivers matching the QEMU device emulation
> configuration. Additionally, the right drivers are now also auto-l
From: Mark Jonas
The patch series fixes a regression where images built for QEMU x86 and
x86-64 did not contain sound drivers matching the QEMU device emulation
configuration. Additionally, the right drivers are now also auto-loaded
when starting the image.
root@qemux86:~# uname -a
Linux qemux86
On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote:
> On Fri, Nov 18, 2022 at 03:04:29PM +, Richard Purdie wrote:
>
> > My concern is having multiple different file formats and data streams.
> > It means we no longer have one definitive data mechanism but two, then
> > the argument for peop
Hi,
On Fri, Nov 18, 2022 at 04:04:01PM +, Richard Purdie wrote:
> On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote:
> > Additionally I'm currently interested in kirkstone LTS branch so would like
> > any changes to be there too...
>
> The idea is that we develop things in master, then th
On Fri, 2022-11-18 at 17:57 +0200, Mikko Rapeli wrote:
> Additionally I'm currently interested in kirkstone LTS branch so would like
> any changes to be there too...
The idea is that we develop things in master, then they become
available in the next LTS release, not the previous one.
People some
On Fri, Nov 18, 2022 at 03:04:29PM +, Richard Purdie wrote:
> On Fri, 2022-11-18 at 16:32 +0200, Mikko Rapeli wrote:
> > Hi,
> >
> > On Thu, Nov 17, 2022 at 04:57:36PM +, Richard Purdie wrote:
> > > On Thu, 2022-11-17 at 17:39 +0200, Mikko Rapeli wrote:
> > > > Hi,
> > > >
> > > > On Thu,
On Fri, 2022-11-18 at 16:32 +0200, Mikko Rapeli wrote:
> Hi,
>
> On Thu, Nov 17, 2022 at 04:57:36PM +, Richard Purdie wrote:
> > On Thu, 2022-11-17 at 17:39 +0200, Mikko Rapeli wrote:
> > > Hi,
> > >
> > > On Thu, Nov 17, 2022 at 03:17:43PM +, Richard Purdie wrote:
> > > > On Thu, 2022-11
Hi,
On Thu, Nov 17, 2022 at 04:57:36PM +, Richard Purdie wrote:
> On Thu, 2022-11-17 at 17:39 +0200, Mikko Rapeli wrote:
> > Hi,
> >
> > On Thu, Nov 17, 2022 at 03:17:43PM +, Richard Purdie wrote:
> > > On Thu, 2022-11-17 at 09:12 +0200, Mikko Rapeli wrote:
> > > > Many runtime tests woul
On Thu, 2022-11-17 at 17:39 +0200, Mikko Rapeli wrote:
> Hi,
>
> On Thu, Nov 17, 2022 at 03:17:43PM +, Richard Purdie wrote:
> > On Thu, 2022-11-17 at 09:12 +0200, Mikko Rapeli wrote:
> > > Many runtime tests would need customization for different
> > > machines and images. Currently some test
Hi,
On Thu, Nov 17, 2022 at 03:17:43PM +, Richard Purdie wrote:
> On Thu, 2022-11-17 at 09:12 +0200, Mikko Rapeli wrote:
> > Many runtime tests would need customization for different
> > machines and images. Currently some tests like parselogs.py are hard
> > coding machine specific exceptions
On Thu, 2022-11-17 at 09:12 +0200, Mikko Rapeli wrote:
> Many runtime tests would need customization for different
> machines and images. Currently some tests like parselogs.py are hard
> coding machine specific exceptions into the test itself. I think these
> machine specific exceptions fit better
Hi,
On Thu, Nov 17, 2022 at 03:22:20PM +0100, Alexandre Belloni wrote:
> Hello,
>
> With this two patches, I have multiple new warnings on the autobuilders
> for qemuarm and qemuarm-alt
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/6185/steps/13/logs/stdio
> https://autob
Hello,
With this two patches, I have multiple new warnings on the autobuilders
for qemuarm and qemuarm-alt
https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/6185/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/5064/steps/12/logs/stdio
On 17/
Many runtime tests would need customization for different
machines and images. Currently some tests like parselogs.py are hard
coding machine specific exceptions into the test itself. I think these
machine specific exceptions fit better as image specific ones, since a
single machine config can gene
When we use externalsrc.bbclass with devtool, it is not possible to
fetch crates via bb/fetch2/crate.py even though crate:// is defined in
SRC_URI. To be working with externalsrc, we should not remove from
externalsrc and remove "-z ${EXTERNALSRC}" check from
cargo_common.bbclass.
Chanho Park (2):
From: Ming Liu
Ming Liu (2):
kernel-fitimage.bbclass: change 'echo' to 'bbnote'
kernel-fitimage.bbclass: introduce FIT_SUPPORTED_INITRAMFS_FSTYPES
meta/classes/kernel-fitimage.bbclass | 35 +---
1 file changed, 21 insertions(+), 14 deletions(-)
--
2.25.1
-=-=-=-=
These changes allow the package bbclass to process the kernel and
kernel modules so that they that extended packaging info can be used
by the create-spdx bbclass.
Tested with qemux86-64
Saul Wold (2):
kernel: add -dbg package
package.bbclass: don't skip kernel and kernel modules
meta/clas
But you can use externalsrc to simply point to a custom source checkout, no?
Alex
On Mon, 13 Dec 2021 at 18:34, Max Krummenacher wrote:
> On Fri, Dec 10, 2021 at 4:57 PM Richard Purdie
> wrote:
> >
> > On Fri, 2021-12-10 at 14:04 +0100, Max Krummenacher wrote:
> > > The current developer manua
1 - 100 of 1925 matches
Mail list logo
