Hi Steve and Anuj
I tested it on qemu, it works well.
- git package is installed by rpm command.
- git package is removed by rpm command.
Could you tell me what is needed to verify for RPM?
Thanks,
Minjae Kim.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Rep
Yes, I think so. This can be left out then.
Alex
On Fri, 25 Jun 2021 at 18:36, Ross Burton wrote:
> A ptest failed in perl with this upgrade in:
>
> gdbm_firstkey: Item not found at ../../t/lib/dbmt_common.pl line 52.
> Compilation failed in require at t/gdbm.t line 6.
>
> This might be related
A ptest failed in perl with this upgrade in:
gdbm_firstkey: Item not found at ../../t/lib/dbmt_common.pl line 52.
Compilation failed in require at t/gdbm.t line 6.
This might be related?
Ross
On Tue, 22 Jun 2021 at 12:21, Alexander Kanavin wrote:
>
> Signed-off-by: Alexander Kanavin
> ---
>
On Fri, 2021-06-25 at 17:45 +0200, Rasmus Villemoes wrote:
> On 25/06/2021 14.16, Richard Purdie wrote:
> > On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via
> > lists.openembedded.org wrote:
> > > I noticed that if I have an image recipe that says
> > >
> > > IMAGE_INSTALL += "kernel-modul
On 25/06/2021 14.16, Richard Purdie wrote:
> On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via
> lists.openembedded.org wrote:
>> I noticed that if I have an image recipe that says
>>
>> IMAGE_INSTALL += "kernel-module-foo"
>>
>> it fails as expected when the kernel hasn't been built with CO
On 6/24/21 11:10 PM, Andrej Valek wrote:
- Make mktemp applet compatible with --tmpdir option in ca-certificate
update script.
Signed-off-by: Andrej Valek
Signed-off-by: Peter Marko
---
.../busybox/0001-mktemp-add-tmpdir-option.patch| 81 ++
meta/recipes-core/busyb
Ignore this change.
When I release the next set of -stable kernels, this will be part of it.
As of now, those changes are not ready for release yet.
cheers,
Bruce
On Fri, Jun 25, 2021 at 11:10 AM Trevor Gamblin
wrote:
>
> yocto-kernel-cache/yocto-5.10 has been updated to support the latest
>
On 2021-06-25 11:10 a.m., Trevor Gamblin wrote:
yocto-kernel-cache/yocto-5.10 has been updated to support the latest
kernel netfilter/nf_tables configurations, so update the SRCREV to match.
Just ignore this one, didn't understand the workflow...
Signed-off-by: Trevor Gamblin
---
meta/reci
yocto-kernel-cache/yocto-5.10 has been updated to support the latest
kernel netfilter/nf_tables configurations, so update the SRCREV to match.
Signed-off-by: Trevor Gamblin
---
meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_5.10.bb| 2 +-
2 fil
On Thu, Jun 24, 2021 at 7:30 PM Minjae Kim wrote:
>
> In order to fix CVE-2021-3421, I added RPMSIGTAG_FILESIGNATURES and
> RPMSIGTAG_FILESIGNATURELENGTH in lib/rpmtag.h.
> So It is possible to build. but I cannot test on target yet.
FWIW, a-full test on the autobuilder passed with this patch in
This back-ports ARC support which was added after the most recent
tag 1.20.9 was cut. So on the next version bump this change to be
reverted.
Signed-off-by: Alexey Brodkin
---
.../dpkg/0014-arch-Add-support-for-ARCv2-CPU.patch | 68 ++
meta/recipes-devtools/dpkg/dpkg_1.20.9.b
Added readme to satisfy the readme file test.
Updated busybox bbappend to satisfy the signature test.
[YOCTO #13612]
Signed-off-by: Scott Weaver
---
meta-skeleton/README.skeleton | 4
meta-skeleton/recipes-core/busybox/busybox_%.bbappend | 3 ++-
2 files changed, 6
In sysbench version 0.4, the tmp variable used by the memory
test to execute requests is optimized by the compiler.
Caching mechanism reduces the direct accesses to the memory
increasing the transfer speed.
This leads to false timing estimations that considerably affect
read and also random write
On Fri, 2021-06-25 at 09:37 +0200, Rasmus Villemoes via lists.openembedded.org
wrote:
> I noticed that if I have an image recipe that says
>
> IMAGE_INSTALL += "kernel-module-foo"
>
> it fails as expected when the kernel hasn't been built with CONFIG_FOO=m.
>
> However, if at the same time some
On 2021-06-24 3:42 a.m., Anuj Mittal wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
Backport upstream patches to fix issues introduced by a backported CVE
patch. Fixes:
| ../../curl-7.75.0/lib/vtls/vtls.c: In function ‘Curl_ssl_addsessionid’:
| ../../curl-7.75.0/lib/vtls/
Add SSTATETASKS to package_prepare_pkgdata[vardepsexclude] since otherwise
the task hashes vary depending upon which packaging backends are enabled
and likely other changes which add/remove unrelated sstate tasks.
Signed-off-by: Richard Purdie
---
meta/classes/package_pkgdata.bbclass | 2 +-
1 f
From: Alexander Kanavin
License-Update: added terms for cipher/cipher-gcm-ppc.c, still under GPL
(From OE-Core rev: d28c1f67c447f99313890e68083da61adcc66f74 )
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
Signed-off-by: Lee Chee Yang
---
.../libgcrypt/{libgcrypt_1.9.2.bb =>
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Michael Ho
> Sent: den 24 juni 2021 12:40
> To: openembedded-core@lists.openembedded.org
> Cc: Michael Ho
> Subject: [OE-core] [PATCH] sstate.bbclass: fix errors about read-only
I noticed that if I have an image recipe that says
IMAGE_INSTALL += "kernel-module-foo"
it fails as expected when the kernel hasn't been built with CONFIG_FOO=m.
However, if at the same time some other package which happens to get
installed in the same image says
RRECOMMENDS_${PN} += "kernel-mo
19 matches
Mail list logo
