Hi everybody,
Let me throw in my 2 cents ;)
We have 2 cases (and combinations)
1) .scc, .cfg, .patch files just lying around not being used
2) .scc, .cfg, .patch files actually somehow being included in the
kernel recipe and hence being used
Say, the kernel recipe includes something like
We could just always install libxml2 into the SDK...
On Fri, 5 Jul 2019 at 02:18, Chen Qi wrote:
>
> For build-sysroots.bb, the xmlcatalog would not be in its
> staging directory. Causing the following error for eSDK.
>
> ERROR: build-sysroots-1.0-r0 do_build_native_sysroot: Command
>
Change the default configuration so that it doesn't need GTK+ 2 to build, as
GTK+ 2 is obsolete.
Signed-off-by: Ross Burton
---
meta/recipes-multimedia/alsa/alsa-tools_1.1.7.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-multimedia/alsa/alsa-tools_1.1.7.bb
This is the Adwaita theme for GTK+ 2, which we don't include in oe-core anymore.
Signed-off-by: Ross Burton
---
.../gnome/gnome-themes-standard_3.22.3.bb | 46 --
1 file changed, 46 deletions(-)
delete mode 100644
GTK+ 2 is being removed from oe-core, so remove it from the oe-core LSB
packagegroup.
Also document the fact that GTK+ 2 is no longer part of the LSB packagegroup,
and point to meta-oe for the recipe if required.
Signed-off-by: Ross Burton
---
README.LSB
GTK+ 2 is ancient, and shouldn't be used. It will be moved to meta-oe for
people who do need it, but it shouldn't in oe-core.
[ YOCTO #12673 ]
Signed-off-by: Ross Burton
---
meta/recipes-gnome/gtk+/gtk+.inc | 107 -
From: Bruce Ashfield
Updating the linux-yocto 4.19 recipe to the latest -stable and -rt
releases.
We also integrate a configuration change to support ptests on scsci
targets:
scsi-debug: include core scsi support for standalone inclusion
The -stable changes comprise the following commits:
From: Bruce Ashfield
If a package uses PKG_ variables to map package names to version specific
variants, on target postinstall functionality will be broken.
i.e. something like the following casuses rootfs assembly errors:
d.setVar('pkg_postinst_ontarget_linux-source', 'cd /usr/src/; ln -sf
From: Bruce Ashfield
Hi all,
Here's the next round of updates I've been testing. The 4.19 update is pretty
standard, and is both a -stable and -rt refresh. Boot testing shows no issues
on either kernel type.
We also have a configuration tweak to allow the beaglebone reference to be
booted in
From: Bruce Ashfield
While we don't normally do a dual h/w and virt BSP (since they
tend to have conflicting requirements over time). A minimal overhead
option to do this was submitted to linux-yocto. Since it has no
impact on the h/w reference, has SDK testing value and can serve
as a template
On Fri, 2019-07-05 at 09:30 +0800, Chen Qi wrote:
> For build-sysroots.bb, the xmlcatalog would not be in its
> staging directory. Causing the following error for eSDK.
>
> ERROR: build-sysroots-1.0-r0 do_build_native_sysroot: Command
>
== Series Details ==
Series: "[v2] cve-check: Depends on cve..." and 2 more
Revision: 1
URL : https://patchwork.openembedded.org/series/18539/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
From: Pierre Le Magourou
Instead of using expanded list of affected versions that is not
reliable, use the 'cpe_match' node in the 'configurations' json node.
For cve-check to correctly match affected CVE, the sqlite database need to
contain operator_start, operator_end and the corresponding
From: Pierre Le Magourou
do_populate_cve_db is a native task.
Signed-off-by: Pierre Le Magourou
---
meta/classes/cve-check.bbclass | 2 +-
meta/recipes-core/meta/{cve-update-db.bb => cve-update-db-native.bb} | 0
2 files changed, 1 insertion(+), 1
From: Pierre Le Magourou
Now that cve-update-db added CPE information to NVD database. We can
check for unpatched versions with operators '<', '<=', '>', and '>='.
Signed-off-by: Pierre Le Magourou
---
meta/classes/cve-check.bbclass | 54 +++---
1 file
Hello,
> > From: Pierre Le Magourou
> >
> > do_populate_cve_db is a native task.
> >
> > Signed-off-by: Pierre Le Magourou <
> > pierre.lemagou...@softbankrobotics.com>
> > ---
> > meta/classes/cve-check.bbclass | 2 +-
> > meta/recipes-core/meta/cve-update-db.bb | 1 +
> > 2 files
From: Mingli Yu
The current go class includes ptest logic by default
and will make the recipe which inherits go class
to support ptest automatically though maybe the
recipe which inherits go class doesn't plan to
support the ptest.
So separate the ptest logic to another specified
class go-ptest
-Upgrade from util-linux_2.33.2.bb to util-linux_2.34.bb.
-util-linux/check-for-_HAVE_STRUCT_TERMIOS_C_OSPEED.patch
Removed since this is included in 2.34.
Signed-off-by: Zang Ruochen
---
.../check-for-_HAVE_STRUCT_TERMIOS_C_OSPEED.patch| 16
.../{util-linux_2.33.2.bb
At 2019-07-05 00:42:53, "Bruce Ashfield" wrote:
>On Thu, Jul 4, 2019 at 12:36 PM wrote:
>>
>> On Thu, 2019-07-04 at 12:29 -0400, Bruce Ashfield wrote:
>> > On Thu, Jul 4, 2019 at 11:18 AM Richard Purdie
>> > wrote:
>> > > On Thu, 2019-07-04 at 08:48 -0400, Bruce Ashfield wrote:
>> > > > On Thu,
19 matches
Mail list logo