Re: [OE-core] [PATCH v2] sstate: another fix for touching files inside pseudo

2021-11-06 Thread Steve Sakoman
On Sat, Nov 6, 2021 at 8:09 AM Jose Quaresma wrote: > > Hi Steve, > > Can this patch be backported to dunfell branch to land in the next release > 3.1.12? This patch won't apply due to the zstd related changes in master. Could you submit a dunfell version of the patch? Steve > > Jose > > Jose

Re: [OE-core] [dunfell][PATCH] piglit: upgrade to latest revision

2021-11-06 Thread Steve Sakoman
On Sat, Nov 6, 2021 at 6:24 AM Marek Vasut wrote: > > On 11/6/21 5:01 PM, Steve Sakoman wrote: > > On Sat, Nov 6, 2021 at 2:59 AM Marek Vasut wrote: > >> > >> Update piglit to latest git revision and update the branch name, > >> since the original one is no longer updated. Make sure the VK > >>

Re: [OE-core] cargo-native do_fetch error

2021-11-06 Thread Zoltan Boszormenyi via lists.openembedded.org
2021. 11. 06. 14:02 keltezéssel, Konrad Weihmann írta: On 06.11.21 13:49, Zoltan Boszormenyi via lists.openembedded.org wrote: I tried building my custom OS rebased on current master. I got this error: ERROR: cargo-native-1.56.0-r0 do_fetch: No checksum specified for

Re: [OE-core] [PATCH v2] sstate: another fix for touching files inside pseudo

2021-11-06 Thread Jose Quaresma
Hi Steve, Can this patch be backported to dunfell branch to land in the next release 3.1.12? Jose Jose Quaresma via lists.openembedded.org escreveu no dia quinta, 4/11/2021 à(s) 19:14: > This patch is a fixup for 676757f "sstate: fix touching files inside > pseudo" > > running the 'id'

Re: [OE-core] [dunfell][PATCH] piglit: upgrade to latest revision

2021-11-06 Thread Marek Vasut
On 11/6/21 5:01 PM, Steve Sakoman wrote: On Sat, Nov 6, 2021 at 2:59 AM Marek Vasut wrote: Update piglit to latest git revision and update the branch name, since the original one is no longer updated. Make sure the VK tests are only enabled if VK is also enabled in PACKAGECONFIG, and that

Re: [OE-core] [dunfell][PATCH] piglit: upgrade to latest revision

2021-11-06 Thread Steve Sakoman
On Sat, Nov 6, 2021 at 2:59 AM Marek Vasut wrote: > > Update piglit to latest git revision and update the branch name, > since the original one is no longer updated. Make sure the VK > tests are only enabled if VK is also enabled in PACKAGECONFIG, > and that this is opt-in, otherwise older

[OE-core] [master-next][PATCH] librsvg: Disable 64bit atomics on riscv32/mipsel in crossbeam

2021-11-06 Thread Khem Raj
Signed-off-by: Khem Raj --- meta/recipes-gnome/librsvg/librsvg_2.52.3.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-gnome/librsvg/librsvg_2.52.3.bb b/meta/recipes-gnome/librsvg/librsvg_2.52.3.bb index 6c4850271de..f1d1a8f9f49 100644 ---

Re: [OE-core] cargo-native do_fetch error

2021-11-06 Thread Konrad Weihmann
On 06.11.21 13:49, Zoltan Boszormenyi via lists.openembedded.org wrote: I tried building my custom OS rebased on current master. I got this error: ERROR: cargo-native-1.56.0-r0 do_fetch: No checksum specified for '/data/genericx86-64-yocto-3.5/downloads/rustc-1.56.0-src.tar.xz', please add

[OE-core] [dunfell][PATCH] piglit: upgrade to latest revision

2021-11-06 Thread Marek Vasut
Update piglit to latest git revision and update the branch name, since the original one is no longer updated. Make sure the VK tests are only enabled if VK is also enabled in PACKAGECONFIG, and that this is opt-in, otherwise older systems fail to build. Cherry picked from squashed commits:

[OE-core] cargo-native do_fetch error

2021-11-06 Thread Zoltan Boszormenyi via lists.openembedded.org
I tried building my custom OS rebased on current master. I got this error: ERROR: cargo-native-1.56.0-r0 do_fetch: No checksum specified for '/data/genericx86-64-yocto-3.5/downloads/rustc-1.56.0-src.tar.xz', please add at least one to the recipe: SRC_URI[rust.sha256sum] =

Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3

2021-11-06 Thread Richard Purdie
On Fri, 2021-11-05 at 14:09 +, Jasper Orschulko wrote: > Actually, I don't believe this to be an issue for the following > reasons: > > [...] > > 2. When using repo within the yocto build itself (with the repo > fetcher), the repo binary is only ever called during the do_fetch step, > which

Re: [OE-core] [V3][PATCH] ruby: workaround ptest hang problem

2021-11-06 Thread Richard Purdie
On Fri, 2021-11-05 at 10:18 +0800, Changqing Li wrote: > From: Changqing Li > > since openssl 3 not compatible problem, ruby have disable openssl > extention. But disable openssl extention make test_smtp.rs hang at > test case "test_start". > > Net::TestSMTP#test_start: > NameError:

Re: [OE-core] [PATCH 5/7] librsvg: set the needed atomic configuration flags directly per-target

2021-11-06 Thread Khem Raj
On Fri, Nov 5, 2021 at 1:48 AM Alexander Kanavin wrote: > > Do not try to mangle the upstream list of targets; > after discussion with upstream it turns out it's neither > necessary nor upstreamable: > https://github.com/crossbeam-rs/crossbeam/pull/751 > > Signed-off-by: Alexander Kanavin > ---

Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3

2021-11-06 Thread Alexander Kanavin
On Fri, 5 Nov 2021 at 21:32, Jasper Orschulko < jasper.orschu...@iris-sensing.com> wrote: > So yeah... as far as I can tell, there are multiple ways to approach > this issue, but none of them seem straight forward nor pretty. Bitbake > as it is is just fundamentally not good at handling highly