On Tue, Mar 3, 2020 at 10:42 PM Khem Raj wrote:
>
> Hi Scott
>
> I am getting a textrel issue reported on musl builds see
> https://errors.yoctoproject.org/Errors/Details/393681/
>
> this recipe is already applied but would be good to root cause this issue
> and find appropriate fix
>
>
Hi Scott
I am getting a textrel issue reported on musl builds see
https://errors.yoctoproject.org/Errors/Details/393681/
this recipe is already applied but would be good to root cause this issue
and find appropriate fix
https://errors.yoctoproject.org/Errors/Details/393681/
On Fri, Feb 14,
Backport the CVE patch from the upstream to fix the heap-based buffer
over-read in tiffWriter.
Signed-off-by: Haiqing Bai
---
meta-oe/recipes-support/gd/gd/CVE-2017-6363.patch | 35 +++
meta-oe/recipes-support/gd/gd_2.2.5.bb| 1 +
2 files changed, 36
On 3/3/20 7:20 PM, Haiqing Bai wrote:
> Backport the CVE patch from the upstream to fix the heap-based buffer
> over-read in tiffWriter.
Did I miss the patch for master?
- armin
>
> Signed-off-by: Haiqing Bai
> ---
> .../recipes-support/gd/gd/CVE-2017-6363.patch | 35 +++
>
On Tue, Mar 3, 2020 at 8:43 PM Martin Jansa wrote:
>
> You can use something like:
> 2.0.99+2.1.0-beta3
> to make sure it doesn't go backwards.
>
> 2.1.0+beta3 seems wrong, because it would sort higher than final 2.1.0
> (without the +git${SRCPV} suffix).
>
> 2.1.0~beta3 might work, but it's not
You can use something like:
2.0.99+2.1.0-beta3
to make sure it doesn't go backwards.
2.1.0+beta3 seems wrong, because it would sort higher than final 2.1.0
(without the +git${SRCPV} suffix).
2.1.0~beta3 might work, but it's not used by many recipes.
On Wed, Mar 4, 2020 at 4:01 AM Leo Yan
On Tue, Mar 03, 2020 at 07:25:07PM -0800, Khem Raj wrote:
> I have pushed a fix with ~
Ah, I see that: PV = "2.1.0~beta3". Thanks a lot!
Leo
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
I have pushed a fix with ~
On Tue, Mar 3, 2020 at 7:00 PM Leo Yan wrote:
> Hi Khem,
>
> On Thu, Feb 27, 2020 at 07:27:21AM -0800, Khem Raj wrote:
> > I am seeing version going backward errors still
> >
> > luajit-2.0.5+2.1.0-beta3: Package version for package luajit-src went
> > backwards which
Backport the CVE patch from the upstream to fix the heap-based buffer
over-read in tiffWriter.
Signed-off-by: Haiqing Bai
---
.../recipes-support/gd/gd/CVE-2017-6363.patch | 35 +++
meta-oe/recipes-support/gd/gd_2.2.5.bb| 1 +
2 files changed, 36 insertions(+)
create
Hi Khem,
On Thu, Feb 27, 2020 at 07:27:21AM -0800, Khem Raj wrote:
> I am seeing version going backward errors still
>
> luajit-2.0.5+2.1.0-beta3: Package version for package luajit-src went
> backwards which would break package feeds (from
> 0:2.0.5+git0+02b521981a-r0.7 to
- Drop unused 0001-dlm-fix-package-qa-error.patch
- Merge appends into main task
- remove explicitly mentioning systemd in deps, systemd bbclass will add it
- Add a patch to fix install using cp cmd to preserve file permissions
Fixes
dlm: /usr/lib/libdlmcontrol.so.3 is owned by uid 1000, which is
On Tue, 2020-03-03 at 10:00 -0800, Khem Raj wrote:
>
> On 3/3/20 9:28 AM, André Draszik wrote:
> > From: André Draszik
> >
> > During the python3 / nodejs update, the dependencies weren't updated, so
> > using system-gyp ends up trying to use the python2 version of system-
> > gyp, which will
From: André Draszik
During the python3 / nodejs update, the dependencies weren't updated, so
using system-gyp ends up trying to use the python2 version of system-
gyp, which will of course fail.
Fixing this to depend on the python3 version of gyp still doesn't
doesn't make things work, though:
On 3/3/20 9:28 AM, André Draszik wrote:
From: André Draszik
During the python3 / nodejs update, the dependencies weren't updated, so
using system-gyp ends up trying to use the python2 version of system-
gyp, which will of course fail.
Fixing this to depend on the python3 version of gyp still
From: André Draszik
During the python3 / nodejs update, the dependencies weren't updated, so
using system-gyp ends up trying to use the python2 version of system-
gyp, which will of course fail.
Fixing this to depend on the python3 version of gyp still doesn't
doesn't make things work, though:
From: André Draszik
Use system brotli via PACKAGECONFIG by default. So far,
nodejs had been built using its embedded copy of brotli,
which we generally try to avoid, for the known reasons
(independent updates, cve & license checks, etc).
The nodejs patches to enable this have been submitted.
can you rebase it on top of master-next and resend
On Tue, Mar 3, 2020 at 5:46 AM André Draszik wrote:
>
> From: André Draszik
>
> Use system brotli via PACKAGECONFIG by default. So far,
> nodejs had been built using its embedded copy of brotli,
> which we generally try to avoid, for the known
can you rebase it on top of master-next and resend
On Tue, Mar 3, 2020 at 5:45 AM André Draszik wrote:
>
> From: André Draszik
>
> During the python3 / nodejs update, the dependencies weren't updated, so
> using system-gyp ends up trying to use the python2 version of system-
> gyp, which will
* because sysdig from meta-oe depends on it now, since:
commit ed798c764319d83ad9eb1b963bfc99b1fa1a791a
Author: Khem Raj
Date: Wed Jan 2 17:59:20 2019 -0800
sysdig: Upgrade to 0.26.5
Signed-off-by: Martin Jansa
---
.../recipes-core/packagegroups/packagegroup-meta-networking.bb |
On Tue, Mar 3, 2020 at 5:53 AM Martin Jansa wrote:
> Should I send the patch to move grpc from meta-networking to meta-oe to
> fix this or do you have it already?
>
Please send I don’t have it ready
>
> On Mon, Mar 2, 2020 at 6:22 PM Khem Raj wrote:
>
>> On Mon, Mar 2, 2020 at 4:27 AM Martin
pon., 2 mar 2020 o 19:25 Khem Raj napisał(a):
>
> >
> > Khem, Armin: any thoughts?
>
> there are many ota layers on OE, most of them are self-contained, so a
> question arises, how is this different, somethings here say it could be
> a base layer for all OTAs, which actually seems quite valuable,
Should I send the patch to move grpc from meta-networking to meta-oe to fix
this or do you have it already?
On Mon, Mar 2, 2020 at 6:22 PM Khem Raj wrote:
> On Mon, Mar 2, 2020 at 4:27 AM Martin Jansa
> wrote:
> >
> > Hi,
> >
> > added dependency on grpc exists only in meta-networking, so this
From: André Draszik
nodejs (-native) can be built against a system-installed version of
the brotli libraries. Allow doing that by provide a -native version
of brotli.
Signed-off-by: André Draszik
---
meta-oe/recipes-extended/brotli/brotli_1.0.7.bb | 2 ++
1 file changed, 2 insertions(+)
diff
From: André Draszik
Use system brotli via PACKAGECONFIG by default. So far,
nodejs had been built using its embedded copy of brotli,
which we generally try to avoid, for the known reasons
(independent updates, cve & license checks, etc).
The nodejs patches to enable this have been submitted.
From: André Draszik
During the python3 / nodejs update, the dependencies weren't updated, so
using system-gyp ends up trying to use the python2 version of system-
gyp, which will of course fail.
Fixing this to depend on the python3 version of gyp still doesn't
doesn't make things work, though:
> -Original Message-
> From: openembedded-devel-boun...@lists.openembedded.org devel-boun...@lists.openembedded.org> On Behalf Of Peter Kjellerstedt
> Sent: den 3 mars 2020 12:03
> To: André Draszik ; openembedded-
> de...@lists.openembedded.org
> Subject: Re: [oe]
> -Original Message-
> From: André Draszik
> Sent: den 29 februari 2020 08:08
> To: Peter Kjellerstedt ; openembedded-
> de...@lists.openembedded.org
> Subject: Re: [oe] [meta-networking][PATCH] meta-networking:
> s|${COREBASE}/meta/files/common-licenses|${COMMON_LICENSE_DIR}
>
> On Fri,
27 matches
Mail list logo
