Date   

Getting kernel patch to work

Greg Wilson-Lindberg
 

I'm using a boot2qt version of a warrior Yocto build for a raspberry pi4.

I'm trying to apply a patch to a driver in the linux kernel. I'm following the procedures laid out in the
book "Embedded Linux Systems with the Yocto Project".

I already have a kernel .bbappend file that I'm using to modify the kernel config and that is working correctly.

I started with a patch file that I found on the internet that addressed the problem that I have and I added
support for it to my .bbappend file. I know that it has been found correctly because I initially specified the
file path incorrectly and received an error.

After building my image I go to look at the STAGING_KERNEL_DIR and I do not see my changes applied to the
file. I even added an error to the patch to see if it was compiling and it didn't trigger the error.


At this point I went back fully to "Embedded Linux Systems with the Yocto Project" and created my own
patch. I still don't see it being applied.

Can somebody please tell me where I should see the patch applied?

Here is how I modified my .bbappend:


# additions to Kernel configuration

SRC_URi += "file://0001-drm-vc4-Keep-the-binner-BO-through-suspend-GWL.patch"

do_configure_append() {
.
.
.
}


And here is the patch:


From d95e6ead8d25165014f8746082656da6345889b0 Mon Sep 17 00:00:00 2001
From: Greg Wilson-Lindberg <gwilson@sakuraus.com>
Date: Tue, 10 Mar 2020 16:29:08 -0700
Subject: [PATCH 1/1] drm-vc4-Keep-the-binner-BO-through-suspend-GWL

---
 drivers/gpu/drm/vc4/vc4_v3d.c | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/drivers/gpu/drm/vc4/vc4_v3d.c b/drivers/gpu/drm/vc4/vc4_v3d.c
index e47e29426078..ff7812066668 100644
--- a/drivers/gpu/drm/vc4/vc4_v3d.c
+++ b/drivers/gpu/drm/vc4/vc4_v3d.c
@@ -303,9 +303,6 @@ static int vc4_v3d_runtime_suspend(struct device *dev)
 
     vc4_irq_uninstall(vc4->dev);
 
-    drm_gem_object_put_unlocked(&vc4->bin_bo->base.base);
-    vc4->bin_bo = NULL;
-
     clk_disable_unprepare(v3d->clk);
 
     return 0;
@@ -317,10 +314,6 @@ static int vc4_v3d_runtime_resume(struct device *dev)
     struct vc4_dev *vc4 = v3d->vc4;
     int ret;
 
-    ret = vc4_allocate_bin_bo(vc4->dev);
-    if (ret)
-        return ret;
-
     ret = clk_prepare_enable(v3d->clk);
     if (ret != 0)
         return ret;
--
2.17.1


Thanks in advance,
Greg Wilson-Lindberg


Yocto Project Status WW10'20

Stephen Jolley
 

Current Dev Position: YP 3.1 M3 - At Feature Freeze, build pending

Next Deadline: YP 3.1 M3 build date 2/24/2020

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We are now past M3 feature freeze. The blocking issues continue to reduce, thanks to everyone who has contributed fixes. The remaining issues are:
    • continued minor bugs with buildtools tarball integration
    • coreutils ptest blocked on reproducibility issues with gcc-plugins
    • SystemExit() intermittent selftest failure
    • pseudo sysroot high priority bug
  • There are significant changes proposed to bitbake’s logging structure to address concerns raised by hashequiv changes. These are currently in testing and are likely to become part of M3 given the timing, wider review is welcome.
  • Recipe upgrades are now unlikely to be merged into 3.1 as we focus on stabilizing and bug fixing for the release
  • Autobuilder build results continue to be a concern as we’re not getting green builds very often due to multiple varied issues.

 

YP 3.1 Milestone Dates:

  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date  3/30/2020
  • YP 3.1 M4 release date  4/24/2020

 

Planned upcoming dot releases:

  • YP 3.0.3 build date  5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date  5/18/2020
  • YP 2.7.4 release date 5/29/2020

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: Should changing a task in the .bb file cause the task to be rerun?

Richard Purdie
 

On Tue, 2020-03-10 at 11:33 +0000, Mikko.Rapeli@bmw.de wrote:
On Fri, Feb 28, 2020 at 11:25:59PM +0000, Richard Purdie wrote:
On Fri, 2020-02-28 at 22:51 +0000, Sean McKay wrote:
This is probably a fairly short question (I hope):
I’m working on a branch based on zeus. I found a bug in the way that
one of our recipes was handling something during do_configure (which
caused an error to pop up in a do_compile task). When I modified the
do_configure task (do_configure_append, actually) to behave properly
(which involved changing the actual commands run in that function)
and reran bitbake -c compile <recipe>, the do_configure task wasn’t
rerun despite the change to the function’s code.

Is it safe to assume this means we’ve done something to mess up the
way our system is processing things? Or is that expected behavior
Its not expected behaviour and yes, it sounds like something is messed
up...
This is what I've come to expect with yocto 2.0 jethro, 2.5 sumo and
3.0 zeus.

That's why I always write:

$ bitbake -c clean recipe && bitbake -c cleansstate && bitbake -c compile recipe

when debugging changes in recipes to_compile and other dependent tasks.
I'm also cleaning up sstate to be sure it's not corrupt or filled with
somehow bad data.
This is bad and shouldn't be happening. Can anyone provide some
examples I can look at?

You shouldn't ever need to run cleansstate in particular. If you have
to, there is another underlying bug that should get fixed.

Cheers,

Richard


Re: Should changing a task in the .bb file cause the task to be rerun?

Mikko Rapeli
 

On Fri, Feb 28, 2020 at 11:25:59PM +0000, Richard Purdie wrote:
On Fri, 2020-02-28 at 22:51 +0000, Sean McKay wrote:
This is probably a fairly short question (I hope):
I’m working on a branch based on zeus. I found a bug in the way that
one of our recipes was handling something during do_configure (which
caused an error to pop up in a do_compile task). When I modified the
do_configure task (do_configure_append, actually) to behave properly
(which involved changing the actual commands run in that function)
and reran bitbake -c compile <recipe>, the do_configure task wasn’t
rerun despite the change to the function’s code.

Is it safe to assume this means we’ve done something to mess up the
way our system is processing things? Or is that expected behavior
Its not expected behaviour and yes, it sounds like something is messed
up...
This is what I've come to expect with yocto 2.0 jethro, 2.5 sumo and
3.0 zeus.

That's why I always write:

$ bitbake -c clean recipe && bitbake -c cleansstate && bitbake -c compile recipe

when debugging changes in recipes to_compile and other dependent tasks.
I'm also cleaning up sstate to be sure it's not corrupt or filled with
somehow bad data.

-Mikko


Re: What is the Yocto / OE recipe for u-boot-fw-utils how can append it?

Quentin Schulz
 

Hi JH,

On Tue, Mar 10, 2020 at 08:23:37PM +1100, JH wrote:
Hi,

I could not find u-boot-fw-utils recipe from OE git repository, when I
added it to build package, it did build u-boot-fw-utils/1_2019.07-r0
from git://git.denx.de/u-boot.git, but I could not make a bbapend to
it as I don't know what is the bb name.
It was recently changed to libubootenv IIRC. Are you sure it was taken
from u-boot git repo?

In zeus you have both available if you have meta-swupdate layer but
u-boot-fw-utils is still present in openembedded-core.

In master, only libubootenv exists in openembedded-core.

Are you using master for poky/openembedded?

FWIW, what a recipe provides either at runtime or at buildtime is
(R)PROVIDES, c.f.:
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-bsp/u-boot/libubootenv_0.2.bb?h=master

Quentin


What is the Yocto / OE recipe for u-boot-fw-utils how can append it?

JH
 

Hi,

I could not find u-boot-fw-utils recipe from OE git repository, when I
added it to build package, it did build u-boot-fw-utils/1_2019.07-r0
from git://git.denx.de/u-boot.git, but I could not make a bbapend to
it as I don't know what is the bb name.

Appreciate your help and advice.

Thank you.

Kind regards,

- jh


Re: do_rootfs task took long time to finish

Marek Belisko
 

On Wed, Feb 19, 2020 at 11:01 PM Khem Raj <raj.khem@gmail.com> wrote:



On 2/17/20 11:55 PM, Marek Belisko wrote:
Hi,

I'm debugging strange issue that do_rootfs task took ~50 minutes. I
enabled buildstats and from that I learned it's quite long. Any ideas
how to debug this issue? My idea was to add timestamp to do_rootfs
tasks but I'm not sure if it's even possible. Thanks.
how big is the image its creating, might affect the time. Secondly
use some system perf monitor to see which tool is taking so long.
Image is ~1GB so I would say quite
I can see that python3 took ~75-100% cpu when doing do_rootfs. We
tested on 16.04 + 18.04 Ubuntu server it's same.
Which perf monitor you had in mind? Thanks.

BR,

marek



BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Re: Building xen-image-minmal for raspberrypi3-64: kernel-module-xen-* not being built

Aljoscha Lautenbach
 

Hi,

You'd be better off asking these questions on the meta-virtualization
mailing list. That's where you'll find the Xen folks.
Thanks, I'll direct any follow-up questions regarding Xen there.

But as for the kernel options, it depends on what kernel you are
using, release, etc. Last I checked, the raspberrypi wouldn't
directly use the fragments from meta-virt, so yes, you'd need to
ensure they are set in your own layer/defconfig.
Ahh, thank you, you managed to switch on the light bulb! :)
Checking the kernel recipes I see now that meta-virt has a
linux-yocto_4.19.bbappend file, whereas meta-raspberrypi uses
linux-raspberrypi_4.19.bb; so as you said, the meta-virt configuration
is never applied due to different versions. Being new to yocto I did
not make that connection immediately, I guess I did miss the obvious.
;)

If I understand you correctly, I need to add a
linux-raspberrypi_4.19.bbappend file in my own layer that applies the
Xen configuration fragments.
That makes sense, thanks again!

Best regards,
Aljoscha


Enhancements/Bugs closed WW10!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

richard.purdie@...

4

chee.yang.lee@...

1

matthew.zeng@...

1

akuster@...

1

zoran.stojsavljevic@...

1

Grand Total

8

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current Top developers on Yocto Project 3.1

Stephen Jolley
 

All,

Below is the list as of top 50 developers as of the end of WW10 of who have open medium or higher bugs and enhancements against YP 3.1.   There are 33 possible work days left until the final release candidates for YP 3.1 needs to be released.

Who

Count

richard.purdie@...

34

liezhi.yang@...

27

david.reyna@...

25

akuster808@...

14

bluelightning@...

13

mark.morton@...

12

Qi.Chen@...

12

bruce.ashfield@...

10

kai.kang@...

10

timothy.t.orling@...

10

randy.macleod@...

9

ross@...

7

hongxu.jia@...

5

jon.mason@...

5

kexin.hao@...

5

michael@...

5

changqing.li@...

5

alejandro@...

4

pbarker@...

4

JPEWhacker@...

4

srifenbark@...

4

mingli.yu@...

4

trevor.gamblin@...

3

matthew.zeng@...

2

ycnakajsph@...

2

anuj.mittal@...

2

chee.yang.lee@...

2

alex.kanavin@...

2

mark.hatle@...

2

raj.khem@...

2

kergoth@...

2

jaewon@...

2

seebs@...

2

yang.wang@...

2

sakib.sajal@...

2

zhe.he@...

1

anon2313@...

1

mshah@...

1

maxime.roussinbelanger@...

1

Martin.Jansa@...

1

akuster@...

1

limon.anibal@...

1

daisuke.yamane@...

1

yi.zhao@...

1

kai.ruhnau@...

1

peter.kjellerstedt@...

1

apoorv.sangal@...

1

scott.branden@...

1

jonathan.yong@...

1

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

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#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 292 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.1”, “3.2, "3.99" and "Future", the more pressing/urgent issues being in "3.1" and then “3.2”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


[meta-security][PATCH] openscap-daemon: add missing runtime dependencies

Yi Zhao
 

Add missing runtime dependencies otherwise /usr/bin/oscapd can not
startup.

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
---
.../openscap-daemon/openscap-daemon_0.1.10.bb | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta-security-compliance/recipes-openscap/openscap-daemon/openscap-daemon_0.1.10.bb b/meta-security-compliance/recipes-openscap/openscap-daemon/openscap-daemon_0.1.10.bb
index ca6e030..a775021 100644
--- a/meta-security-compliance/recipes-openscap/openscap-daemon/openscap-daemon_0.1.10.bb
+++ b/meta-security-compliance/recipes-openscap/openscap-daemon/openscap-daemon_0.1.10.bb
@@ -17,4 +17,7 @@ inherit setuptools3

S = "${WORKDIR}/git"

-RDEPENDS_${PN} = "python"
+RDEPENDS_${PN} = "openscap scap-security-guide \
+ python3-core python3-dbus \
+ python3-pygobject \
+ "
--
2.17.1


Re: [meta-cgl][PATCH 1/2] core-image-cgl/core-image-cgl-initramfs: remove them

Changqing Li
 

ping

On 9/17/19 4:04 PM, changqing.li@windriver.com wrote:
From: Changqing Li <changqing.li@windriver.com>

remove core-image-cgl.bb and core-image-cgl-initramfs.bb

* They require core-image-lsb.bb which has been removed by oe-core

* Even before LSB support is dropped by oe-core, core-image-cgl
and core-image-cgl-initramfs cannot build success, failed during
do_rootfs with below error, so I suppose that no one use these
2 recipes, so remove it

Error:
Problem: package logcheck-1.3.20-r0.core2_64 requires rsyslog, but none of the providers can be installed
- package rsyslog-8.1907.0-r0.core2_64 conflicts with sysklogd provided by sysklogd-1.5.1-r0.core2_64
- package sysklogd-1.5.1-r0.core2_64 conflicts with rsyslog provided by rsyslog-8.1907.0-r0.core2_64
- package packagegroup-cgl-applications-1.0-r0.noarch requires logcheck, but none of the providers can be installed
- package packagegroup-core-full-cmdline-initscripts-1.0-r6.noarch requires sysklogd, but none of the providers can be installed
- package packagegroup-cgl-1.0-r0.noarch requires packagegroup-cgl-applications, but none of the providers can be installed
- package packagegroup-core-full-cmdline-1.0-r6.noarch requires packagegroup-core-full-cmdline-initscripts, but none of the providers can be installed

Signed-off-by: Changqing Li <changqing.li@windriver.com>
---
meta-cgl-common/images/core-image-cgl-initramfs.bb | 19 ---------------
meta-cgl-common/images/core-image-cgl.bb | 28 ----------------------
2 files changed, 47 deletions(-)
delete mode 100644 meta-cgl-common/images/core-image-cgl-initramfs.bb
delete mode 100644 meta-cgl-common/images/core-image-cgl.bb

diff --git a/meta-cgl-common/images/core-image-cgl-initramfs.bb b/meta-cgl-common/images/core-image-cgl-initramfs.bb
deleted file mode 100644
index 67cb4c1..0000000
--- a/meta-cgl-common/images/core-image-cgl-initramfs.bb
+++ /dev/null
@@ -1,19 +0,0 @@
-require core-image-cgl.bb
-
-# Recipe is based on core-image-minimal.bb
-DESCRIPTION = "Initramfs used to mount multipath device as root file system"
-
-PACKAGE_INSTALL = "initramfs-cgl-boot busybox base-passwd udev"
-
-# Do not pollute the initrd image with rootfs features
-IMAGE_FEATURES = ""
-
-export IMAGE_BASENAME = "core-image-cgl-initramfs"
-IMAGE_LINGUAS = ""
-
-LICENSE = "MIT"
-IMAGE_FSTYPES ??= "cpio.gz.u-boot"
-
-IMAGE_ROOTFS_SIZE = "8192"
-
-BAD_RECOMMENDATIONS += "busybox-syslog"
diff --git a/meta-cgl-common/images/core-image-cgl.bb b/meta-cgl-common/images/core-image-cgl.bb
deleted file mode 100644
index 86bf7d4..0000000
--- a/meta-cgl-common/images/core-image-cgl.bb
+++ /dev/null
@@ -1,28 +0,0 @@
-require recipes-extended/images/core-image-lsb.bb
-
-
-VALGRIND ?= ""
-VALGRIND_powerpc ?= "valgrind"
-VALGRIND_e500v2 ?= ""
-VALGRIND_x86 ?= "valgrind"
-VALGRIND_x86_64 ?= "valgrind"
-VALGRIND_armv7a ?= "valgrind"
-
-# Include modules in rootfs
-IMAGE_INSTALL += "\
- packagegroup-core-buildessential \
- packagegroup-core-selinux \
- packagegroup-cgl \
- kexec-tools \
- lttng-tools \
- lttng-modules \
- ${VALGRIND} \
- "
-
-IMAGE_FSTYPES += " ext3.gz"
-
-# kexec-tools doesn't work on Mips
-KEXECTOOLS_mips ?= ""
-KEXECTOOLS_mipsel ?= ""
-
-IMAGE_FEATURES += "tools-debug tools-profile"


Stable life cycle status

Armin Kuster
 

Hello,

Thud has moved to "Community supported" today.

The older releases have moved to EOL as no one has stepped up to take on
the maintenance of those older branches.


regards,
Armin


[meta-security][v2][PATCH] libseccomp: update to 2.4.3

Armin Kuster
 

dropped patch now included in update

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
...SNR_xxx-instead-of-__NR_xxx-for-sysc.patch | 45 -------------------
...ibseccomp_2.4.2.bb => libseccomp_2.4.3.bb} | 3 +-
2 files changed, 1 insertion(+), 47 deletions(-)
delete mode 100644 recipes-security/libseccomp/files/0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch
rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} (90%)

diff --git a/recipes-security/libseccomp/files/0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch b/recipes-security/libseccomp/files/0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch
deleted file mode 100644
index a53433f..0000000
--- a/recipes-security/libseccomp/files/0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch
+++ /dev/null
@@ -1,45 +0,0 @@
-From 1ecdddb2a5b61cf527d1f238f88a9d129239f87a Mon Sep 17 00:00:00 2001
-From: Paul Moore <paul@paul-moore.com>
-Date: Tue, 5 Nov 2019 15:11:11 -0500
-Subject: [PATCH] tests: rely on __SNR_xxx instead of __NR_xxx for syscalls
-
-We recently changed how libseccomp handles syscall numbers that are
-not defined natively, but we missed test #15.
-
-Acked-by: Tom Hromatka <tom.hromatka@oracle.com>
-Signed-off-by: Paul Moore <paul@paul-moore.com>
-
-Upstream-Status: Backport
-[https://github.com/seccomp/libseccomp/commit/1ecdddb2a5b61cf527d1f238f88a9d129239f87a]
-
-Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
----
- tests/15-basic-resolver.c | 6 +++---
- 1 file changed, 3 insertions(+), 3 deletions(-)
-
-diff --git a/tests/15-basic-resolver.c b/tests/15-basic-resolver.c
-index 6badef1..0c1eefe 100644
---- a/tests/15-basic-resolver.c
-+++ b/tests/15-basic-resolver.c
-@@ -55,15 +55,15 @@ int main(int argc, char *argv[])
- unsigned int arch;
- char *name = NULL;
-
-- if (seccomp_syscall_resolve_name("open") != __NR_open)
-+ if (seccomp_syscall_resolve_name("open") != __SNR_open)
- goto fail;
-- if (seccomp_syscall_resolve_name("read") != __NR_read)
-+ if (seccomp_syscall_resolve_name("read") != __SNR_read)
- goto fail;
- if (seccomp_syscall_resolve_name("INVALID") != __NR_SCMP_ERROR)
- goto fail;
-
- rc = seccomp_syscall_resolve_name_rewrite(SCMP_ARCH_NATIVE, "openat");
-- if (rc != __NR_openat)
-+ if (rc != __SNR_openat)
- goto fail;
-
- while ((arch = arch_list[iter++]) != -1) {
---
-2.17.1
-
diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb b/recipes-security/libseccomp/libseccomp_2.4.3.bb
similarity index 90%
rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
index 07db82a..9ca41e6 100644
--- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
+++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
@@ -4,10 +4,9 @@ SECTION = "security"
LICENSE = "LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"

-SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
+SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"

SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
- file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
file://run-ptest \
"

--
2.17.1


Re: [meta-security][PATCH] libseccomp: update to 2.4.3

Armin Kuster
 



On 3/7/20 2:18 PM, Denys Dmytriyenko wrote:
On Sat, Mar 07, 2020 at 08:38:49PM +0000, akuster wrote:
dropped patch now included in update
Do you want to remove the patch?
yeah.. I should.

v2 shortly

thanks,
Armin


Signed-off-by: Armin Kuster <akuster808@...>
---
 .../libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb}    | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} (90%)

diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb b/recipes-security/libseccomp/libseccomp_2.4.3.bb
similarity index 90%
rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
index 07db82a..9ca41e6 100644
--- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
+++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
@@ -4,10 +4,9 @@ SECTION = "security"
 LICENSE = "LGPL-2.1"
 LIC_FILES_CHKSUM = "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"
 
-SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
+SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"
 
 SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
-           file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
            file://run-ptest \
 "
 
-- 
2.17.1


      

      

      

    


Re: [meta-security][PATCH] libseccomp: update to 2.4.3

Denys Dmytriyenko
 

On Sat, Mar 07, 2020 at 08:38:49PM +0000, akuster wrote:
dropped patch now included in update
Do you want to remove the patch?


Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
.../libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} (90%)

diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb b/recipes-security/libseccomp/libseccomp_2.4.3.bb
similarity index 90%
rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
index 07db82a..9ca41e6 100644
--- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
+++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
@@ -4,10 +4,9 @@ SECTION = "security"
LICENSE = "LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"

-SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
+SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"

SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
- file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
file://run-ptest \
"

--
2.17.1


[meta-security][PATCH] sssd: python2 not supported

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-security/sssd/sssd_1.16.4.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/sssd/sssd_1.16.4.bb b/recipes-security/sssd/sssd_1.16.4.bb
index d42a455..c5ddd5c 100644
--- a/recipes-security/sssd/sssd_1.16.4.bb
+++ b/recipes-security/sssd/sssd_1.16.4.bb
@@ -41,7 +41,6 @@ PACKAGECONFIG[ssh] = "--with-ssh, --with-ssh=no, "
PACKAGECONFIG[samba] = "--with-samba, --with-samba=no, samba"
PACKAGECONFIG[selinux] = "--with-selinux, --with-selinux=no --with-semanage=no, libselinux"
PACKAGECONFIG[manpages] = "--with-manpages, --with-manpages=no"
-PACKAGECONFIG[python2] = "--with-python2-bindings, --without-python2-bindings, python, python"
PACKAGECONFIG[python3] = "--with-python3-bindings, --without-python3-bindings"
PACKAGECONFIG[nss] = "--with-crypto=nss, ,nss,"
PACKAGECONFIG[crypto] = "--with-crypto=libcrypto, , libcrypto"
@@ -57,6 +56,7 @@ EXTRA_OECONF += " \
--without-ipa-getkeytab \
--without-python2-bindings \
--enable-pammoddir=${base_libdir}/security \
+ --without-python2-bindings \
"

do_configure_prepend() {
--
2.17.1


[meta-security][PATCH] libseccomp: update to 2.4.3

Armin Kuster
 

dropped patch now included in update

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
.../libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb} (90%)

diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb b/recipes-security/libseccomp/libseccomp_2.4.3.bb
similarity index 90%
rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
index 07db82a..9ca41e6 100644
--- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
+++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
@@ -4,10 +4,9 @@ SECTION = "security"
LICENSE = "LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"

-SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
+SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"

SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
- file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
file://run-ptest \
"

--
2.17.1


Re: [OE-core] Yocto Project Status WW09'20

Richard Purdie
 

On Sat, 2020-03-07 at 16:58 +0000, Richard Purdie wrote:
On Fri, 2020-03-06 at 22:53 +0100, Alexander Kanavin wrote:
On Wed, 4 Mar 2020 at 23:42, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
Just FYI I think there may also be a couple of other packages
coreutils
pulls in and they may also have reproducibility issues (gettext-
ptest,
glibc-locale-* and procps*).
Patch for gettext also sent :) glibc-locale and procps I could not
reproduce :-/
Thanks for that fix, it helps!

FWIW, what I'm seeing with glibc-locale is that these files
"disappear"
from the packages in one of my builds:

./usr/share/locale/vi/LC_MESSAGES/libc.mo
./usr/share/locale/ko/LC_MESSAGES/libc.mo
./usr/share/locale/en_GB/LC_MESSAGES/libc.mo
./usr/share/locale/ca/LC_MESSAGES/libc.mo
./usr/share/locale/fr/LC_MESSAGES/libc.mo
./usr/share/locale/pl/LC_MESSAGES/libc.mo
./usr/share/locale/id/LC_MESSAGES/libc.mo
./usr/share/locale/hr/LC_MESSAGES/libc.mo
./usr/share/locale/uk/LC_MESSAGES/libc.mo
./usr/share/locale/ja/LC_MESSAGES/libc.mo
./usr/share/locale/gl/LC_MESSAGES/libc.mo
./usr/share/locale/es/LC_MESSAGES/libc.mo
./usr/share/locale/el/LC_MESSAGES/libc.mo
./usr/share/locale/pt_BR/LC_MESSAGES/libc.mo
./usr/share/locale/sl/LC_MESSAGES/libc.mo
./usr/share/locale/lt/LC_MESSAGES/libc.mo
./usr/share/locale/rw/LC_MESSAGES/libc.mo
./usr/share/locale/sv/LC_MESSAGES/libc.mo
./usr/share/locale/cs/LC_MESSAGES/libc.mo
./usr/share/locale/nl/LC_MESSAGES/libc.mo
./usr/share/locale/zh_CN/LC_MESSAGES/libc.mo
./usr/share/locale/ia/LC_MESSAGES/libc.mo
./usr/share/locale/fi/LC_MESSAGES/libc.mo
./usr/share/locale/be/LC_MESSAGES/libc.mo
./usr/share/locale/ru/LC_MESSAGES/libc.mo
./usr/share/locale/nb/LC_MESSAGES/libc.mo
./usr/share/locale/zh_TW/LC_MESSAGES/libc.mo
./usr/share/locale/tr/LC_MESSAGES/libc.mo
./usr/share/locale/de/LC_MESSAGES/libc.mo
./usr/share/locale/da/LC_MESSAGES/libc.mo
./usr/share/locale/pt/LC_MESSAGES/libc.mo
./usr/share/locale/hu/LC_MESSAGES/libc.mo
./usr/share/locale/eo/LC_MESSAGES/libc.mo
./usr/share/locale/it/LC_MESSAGES/libc.mo
./usr/share/locale/bg/LC_MESSAGES/libc.mo
./usr/share/locale/sk/LC_MESSAGES/libc.mo

I can conform they're not in the glibc stashed-locale sstate object
so
they disappear somewhere before that in the glibc recipe itself.

Quite where/why I don't know as yet.
Just to save anyone digging, the difference is in configure, one has
msgfmt in the sysroot, one does not. It is there later in the build so
its probably task dependencies not being right.

Cheers,

Richard

8381 - 8400 of 57104