As a bunch of other assignments did, let this cover all riscv32 architectures,
not just qemuriscv32.
Signed-off-by: He Zhe
---
meta/recipes-kernel/lttng/lttng-platforms.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/lttng/lttng-platforms.inc
b/meta/r
On 9/26/22 23:58, Khem Raj wrote:
> On 9/26/22 1:08 AM, He Zhe wrote:
>> lttng-tools requires SYS_ppoll and SYS_pselect6 which are not supported on
>> riscv32. This has been confirmed by lttng-tools upstream.
>> https://github.com/lttng/lttng-tools/pull/162
>>
>> It's also turned off for riscv32
> I still can't send the resulting two files via git send-email (the final
step), as I would have to do a significant amount of configuration in my
_personal_ gmail account in order to use git send-email to send the final
patch.
FWIW: I'm also using my gmail account and the configuration was quit
I have confirmed your patch worked for me. Perhaps the documentation should
also be updated to indicate that remotes need to be cloned/added using the
https protocol?
I still can't send the resulting two files via git send-email (the final step),
as I would have to do a significant amount of co
On 9/26/22 22:05, Steve Sakoman wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
On Sun, Sep 25, 2022 at 4:29 PM Xiangyu Chen wrote:
Backport patch from upstream to handle negative time and offset from Epoch[1]
and fix the yocto autobuilder ptest failures for both qemux86-
Backport patch from upstream to handle negative time and offset from Epoch[1]
and fix the yocto autobuilder ptest failures for both qemux86-64 and qemuarm64
when
applied this backport patch[2].
[1] 0001-Handle-negative-time-and-offset-from-Epoch.patch backport from
https://git.efficios.com/?p=bab
All,
Below is the list as of top 35 bug owners as of the end of WW39 of who have
open medium or higher bugs and enhancements against YP 4.1. There are 23
possible work days left until the final release candidates for YP 4.1 needs
to be released.
Who
Count
michael.opdenac...@bootlin.com
33
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc
Fix telnetd crash if the first two bytes of a new connection
are 0xff 0xf7 (IAC EC) or 0xff 0xf8 (IAC EL).
CVE: CVE-2022-39028
Signed-off-by:Minjae Kim
---
.../inetutils/inetutils/CVE-2022-39028.patch | 54 +++
.../inetutils/inetutils_1.9.4.bb | 1 +
2 files chang
see the REMOTE_URL changes shown in set -x, relevant context is in:
https://git.openembedded.org/openembedded-core/commit/?id=675e88e6e0bbd5ab2dcd4bdf97b0de59925a1be6
We forgot to update it after:
https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git
an
Many git repos prefer https:// nowadays and many removed support
for git://.
This breaks the script when using github.com even when selected remote
is ssh (g...@github.com:openembedded/...), it will re-write it to git://
before calling git pull-request causing:
openembedded-core $ scripts/create-
I think I'm missing some context. Not really understanding what this script is
trying to accomplish I don't know what "remote branch" is vs "local branch".
Should "remote branch" be "master" and the local branch be the branch with the
change I want to make? Here's that script running with "set -
Looks like your badger remote is still using git:// protocol which isn't
supported by github.com anymore, you need to change it to https://.
On Mon, Sep 26, 2022 at 5:49 PM Robert Henz via lists.openembedded.org
wrote:
> On Tue, Sep 20, 2022 at 05:19 PM, Alexandre Belloni wrote:
>
> Hello,
>
> O
I've just written and sent a sort of 'introduction' to the official
layer setup tooling:
https://lists.openembedded.org/g/openembedded-core/message/171070
Build configuration management is a separate concern, I have an
introduction to that too, but not sending it yet, as particularly
oe-setup-bui
TL;DR version
=
If you want to get everything needed to run a yocto build:
- clone the bootstrap repository (ask your distribution maintainer where it is):
$ git clone bootstrap_repo_uri
- run 'setup-layers' from that repo:
$ /path/to/bootstrap_repo/setup-layers
If you want
On 9/26/22 1:08 AM, He Zhe wrote:
lttng-tools requires SYS_ppoll and SYS_pselect6 which are not supported on
riscv32. This has been confirmed by lttng-tools upstream.
https://github.com/lttng/lttng-tools/pull/162
It's also turned off for riscv32 in meta-riscv.
https://github.com/riscv/meta-riscv
On Tue, Sep 20, 2022 at 05:19 PM, Alexandre Belloni wrote:
>
> Hello,
>
> On 20/09/2022 17:55:42+, Robert Henz via lists.openembedded.org wrote:
>
>
>> Hi everyone,
>>
>> I have a PR to fix the WantedBy parsing of the systemctl script. I
>> tried to follow the process described in your wi
On Sun, Sep 25, 2022 at 4:34 AM Steve Sakoman via
lists.openembedded.org
wrote:
>
> Branch: dunfell
>
> New this week: 7 CVEs
> CVE-2022-2795 (CVSS3: 7.5 HIGH): bind
> https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2795 *
> CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-
On Sun, Sep 25, 2022 at 4:29 PM Xiangyu Chen wrote:
>
> Backport patch from upstream to handle negative time and offset from Epoch[1]
> and fix the yocto autobuilder ptest failures for both qemux86-64 and
> qemuarm64 when
> applied this backport patch[2].
Since master babeltrace is also at versi
On 26/09/2022 14:21, Richard Purdie wrote:
>
> I'm old school and have used quilt for patching kernels for a couple of
> decades and have used it before devtool (or even git) existed! There
> are
> probably better ways now but quilt is muscle memory.
>
>
>> Then another (dirtier?) option woul
Thanks Martin. Yes, it does, just tried it on the latest master. When I
cross-checked this before, I must have done it on an older project, with quilt
0.66 (and applying c9d36882044 there doesn't help, either).
On 26/09/2022 13:21, Martin Jansa wrote:
>
> > I am aware of the "force-unpack + pa
On Mon, 2022-09-26 at 04:46 -0700, Andriy Danylovskyy wrote:
> On 26/09/2022 12:23, Richard Purdie wrote:
> > On Mon, 2022-09-26 at 11:06 +0200, Andriy Danylovskyy wrote:
> > > This will move the quilt cache from the default location '$S/.pc'
> > > to
> > > '$S/patches/.pc', to ensure source invali
On 26/09/2022 12:23, Richard Purdie wrote:
>
> On Mon, 2022-09-26 at 11:06 +0200, Andriy Danylovskyy wrote:
>
>> This will move the quilt cache from the default location '$S/.pc' to
>> '$S/patches/.pc', to ensure source invalidation always wipes it out,
>> together with all patches.
>>
>> Recip
> I am aware of the "force-unpack + patch" scenario, discussed in
https://lists.yoctoproject.org/g/yocto/topic/89948013#56602, and this
patch, sadly, doesn't fix that.
Wasn't this scenario fixed by: c9d36882044b1c633d8611a77df54cd68c9bee25 ?
It was for me.
On Mon, Sep 26, 2022 at 11:13 AM Andriy
Instead of installing run-postinsts with it's postinst scripts causing
systemd restarts, use the new dnf-test-* packages instead.
Remove from the installroot tests entirely as they're exercised enough
using just busybox.
Rewrite the exclude test to be simplier now these packages are not going
to
oeqa/runtime needs packages which are always built, but we don't want to
use packages which have large side effects (unlike the current test recipe,
run-postinsts).
As finding a package that is both of these things isn't easy, for now
dnf can generate its own. Moving forward this should be genera
On Mon, 2022-09-26 at 11:06 +0200, Andriy Danylovskyy wrote:
> This will move the quilt cache from the default location '$S/.pc' to
> '$S/patches/.pc', to ensure source invalidation always wipes it out,
> together with all patches.
>
> Recipes which set $S to $WORKDIR are susceptible to a weird is
On Mon, 2022-09-26 at 09:22 +, Teoh, Jay Shen wrote:
> Hi All,
>
> QA for yocto-4.0.4.rc1 is completed. This is the full report for this
> release:
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
>
> === Summary
> No high
Hi All,
QA for yocto-4.0.4.rc1 is completed. This is the full report for this release:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=== Summary
No high milestone defects.
No new issue found.
Thanks,
Jay
> -Original Mes
I am aware of the "force-unpack + patch" scenario, discussed in
https://lists.yoctoproject.org/g/yocto/topic/89948013#56602 ,
and this patch, sadly, doesn't fix that.
But it does fix another face of it, which IMO is even worse than a failing
build - a false positive, where updates to a source are
This will move the quilt cache from the default location '$S/.pc' to
'$S/patches/.pc', to ensure source invalidation always wipes it out,
together with all patches.
Recipes which set $S to $WORKDIR are susceptible to a weird issue: if
a source file is patched by quilt (a .bbappend adds a patch), u
On 9/23/22 23:30, Ross Burton wrote:
Hi Ross,
This is making our CI explode, I suspect the trigger is having meta-clang
present and enabled:
WARNING: binutils-2.39-r0 do_package: binutils: NOT adding alternative provide
/usr/bin/gp-archive: /usr/bin/aarch64-poky-linux-gp-archive does not ex
lttng-tools requires SYS_ppoll and SYS_pselect6 which are not supported on
riscv32. This has been confirmed by lttng-tools upstream.
https://github.com/lttng/lttng-tools/pull/162
It's also turned off for riscv32 in meta-riscv.
https://github.com/riscv/meta-riscv/blob/master/conf/layer.conf
Signed
33 matches
Mail list logo
