Thanks Steve,
We'll give it a try.
On 10/18/2018 11:46 AM, Steve Scott wrote:
You may also need
PREFERRED_PROVIDER_virtual/refpolicy = "refpolicy-standard"
in local.conf.
-steve
-Original Message-----
From: Sinan Kaya [mailto:ok...@kernel.org]
Sent: Thursday, October 18,
to create the sumo branch?
On 10/18/2018 9:48 AM, Steve Scott wrote:
I did not try it on sumo.
From: Stefano Cappa [mailto:stefano.cappa.k...@gmail.com]
Sent: Wednesday, October 17, 2018 11:15 PM
To: ssc...@san.rr.com
Cc: Sinan Kaya ; yocto@yoctoproject.org
Subject: Re: [yocto] [selinux
Sorry for confusing names, not enough coffee yet...
I was trying to say that Steve's suggestion to use
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
didn't work on sumo branch.
On 10/18/2018 10:49 AM, Sinan Kaya wrote:
CC'ing the selinux maintainers:
I was told that using
On 10/18/2018 3:08 PM, Joe MacDonald wrote:
Sorry, I thought it had been created. I'm going to be traveling the
next few days to ELC-E, but I will try to get to it if someone else
does not first.
Yeah, Mark and I are both going to be at ELC-E this week, we'll get it
sorted out.
thanks.
--
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707
On 10/24/2018 7:49 PM, Joe MacDonald wrote:
Hey all,
I just thought I should quickly follow up on this. I have a change set
ready that includes tagging and a minor tweak for sumo, integration of
the current outstanding patch list and a tag for thud and a couple of
additional things (possibly)
On 9/21/2018 4:35 PM, akuster808 wrote:
I already have in my sumo-next
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=stable/sumo-next
libcroco: patch for CVE-2017-7960
rom=1774f1c3baf0bc3d=d75e67654aa9620b=1]
CVE: CVE-2018-8740
Ref: https://access.redhat.com/security/cve/cve-2018-8740
Signed-off-by: Sinan Kaya
---
.../sqlite/files/CVE-2018-8740.patch | 52 +++
meta/recipes-support/sqlite/sqlite3_3.22.0.bb | 1 +
2 files changed, 53 insertions(+)
cre
8a05766cb74af05c04c53e6c9d60c13fc4d59bf2)
Affects libpng <= 1.6.34
CVE: CVE-2018-13785
Upstream-Status: Backport
[https://github.com/glennrp/libpng/commit/8a05766cb74af05c04c53e6c9d60c13fc4d59bf2]
Ref: https://access.redhat.com/security/cve/cve-2018-13785
Signed-off-by: Sinan Kaya
---
.../libpng/files/CVE-2018-13
CVE: CVE-2017-15874
Ref: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-15874
Signed-off-by: Sinan Kaya
---
.../busybox/busybox/CVE-2017-15874.patch | 28 +++
meta/recipes-core/busybox/busybox_1.27.2.bb | 1 +
2 files changed, 29 insertions(+)
create mode 100644 m
/libarchive.org/downloads/libarchive-${PV}.tar.gz \
file://CVE-2017-14502.patch \
file://non-recursive-extract-and-list.patch \
file://CVE-2017-14503.patch \
+ file://CVE-2017-14501.patch \
"
SRC_URI[md5sum] = "4583bd6b2ebf7e0e8963d9
On 9/21/2018 4:35 PM, akuster808 wrote:
For the rest can you sent them to the proper mailing list
openembedded-c...@lists.openembedded.org via git send-patch.
I noticed a few of the patches for recipes need some addition information:
please review
On 9/22/2018 10:46 AM, akuster wrote:
Signed-off-by: Zheng Ruoqin
Signed-off-by: Richard Purdie
What does it take to move this in the right direction?
bring it to my attention like you have.
backported it for the next build round.
Here is another one.
On 9/24/2018 10:27 AM, Sinan Kaya wrote:
Here is another one.
https://patches.openembedded.org/patch/154290/
I see you pulled this into rucko-nmut. It is also needed for the sumo
branch.
--
___
yocto mailing list
yocto@yoctoproject.org
https
On Sun, Jan 13, 2019 at 12:17 PM Sinan Kaya wrote:
>
> On Sat, Jan 12, 2019 at 2:41 PM Joshua Watt wrote:
> >
> > CC'ing yocto@yoctoproject.org
> >
> > On Sat, Jan 12, 2019 at 1:02 PM Sinan Kaya wrote:
> > >
> > > Hi Joshua,
> > >
> &
On Sat, Jan 12, 2019 at 2:41 PM Joshua Watt wrote:
>
> CC'ing yocto@yoctoproject.org
>
> On Sat, Jan 12, 2019 at 1:02 PM Sinan Kaya wrote:
> >
> > Hi Joshua,
> >
> > I have this instruction to build cmake as part of the SDK.
> >
> > +# Add the
musl compilation has been broken since systemd: fix CVE-2018-6954. Fixing this
by placing #ifdef for glob definition.
Signed-off-by: Sinan Kaya
---
.../systemd/0036-Fix-musl-compilation.patch | 27 +++
meta/recipes-core/systemd/systemd_237.bb | 1 +
2 files changed, 28
lipcre-native is trying to create symbolic links to so files
when used with meta-mingw. Remove this condition for mingw builds.
Signed-off-by: Sinan Kaya
---
recipes-support/libpcre/libpcre_selinux.inc | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git
+akuster
On 4/10/2019 3:38 PM, Sinan Kaya wrote:
musl compilation has been broken since systemd: fix CVE-2018-6954. Fixing this
by placing #ifdef for glob definition.
Signed-off-by: Sinan Kaya
---
.../systemd/0002-Make-tmpfiles-safe.patch | 88 +++
1 file changed, 51
On 3/29/2019 10:42 AM, Sinan Kaya wrote:
musl compilation has been broken since systemd: fix CVE-2018-6954. Fixing this
by placing #ifdef for glob definition.
Signed-off-by: Sinan Kaya
I didn't see any comments here but I wanted to let everyone know that
sumo-next branch is currently broken
On 4/11/2019 1:34 AM, Sinan Kaya wrote:
+akuster
On 4/10/2019 3:38 PM, Sinan Kaya wrote:
musl compilation has been broken since systemd: fix CVE-2018-6954.
Fixing this
by placing #ifdef for glob definition.
Signed-off-by: Sinan Kaya
---
.../systemd/0002-Make-tmpfiles-safe.patch | 88
musl compilation has been broken since systemd: fix CVE-2018-6954. Fixing this
by placing #ifdef for glob definition.
Signed-off-by: Sinan Kaya
---
.../systemd/0002-Make-tmpfiles-safe.patch | 88 +++
1 file changed, 51 insertions(+), 37 deletions(-)
diff --git a/meta
On 4/9/2019 7:49 AM, akuster wrote:
After closer look, I don't the "Upstream-Status:" nor a signoff in the
patch being added in the bb file.
Does this issue affect later branches ?
I can fix this. The issue was introduced while backporting a CVE patch
from debian.
So, we are fixing a problem
I noticed last week that qemu packaged into mingw sdk is broken while
the qemu in linux sdk works fine.
Qemu crashes very early while launching the kernel boot.
This used to work fine on sumo.
Does anybody see this problem too?
--
___
yocto
On 8/26/2019 5:33 PM, Joshua Watt wrote:
> On 8/19/19 7:30 AM, Sinan Kaya wrote:
>> I noticed last week that qemu packaged into mingw sdk is broken while
>> the qemu in linux sdk works fine.
>>
>> Qemu crashes very early while launching the kernel boot.
>&g
On 8/26/2019 9:47 PM, Joshua Watt wrote:
> No, I don't think that is supported. Just to make sure, did you try
> building with
>
> SDKMACHINE = "x86_64-mingw32"
>
> to try building the entire SDK as 64-bit?
Yup, that's what I have been using.
SDKMACHINE = "x86_64-mingw32"
--
26 matches
Mail list logo
