Date   

Re: [meta-security][PATCH 2/2] sssd: add DISTRO_FEATURE sssd

Adrian Bunk
 

On Fri, Apr 05, 2019 at 03:47:46AM +0530, Armin Kuster wrote:
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 34bc8c8..d6a308c 100644
--- a/recipes-security/sssd/sssd_1.16.4.bb
+++ b/recipes-security/sssd/sssd_1.16.4.bb
@@ -16,7 +16,7 @@ SRC_URI[sha256sum] = "6bb212cd6b75b918e945c24e7c3f95a486fb54d7f7d489a9334cfa1a1f

inherit autotools pkgconfig gettext python-dir distro_features_check

-REQUIRED_DISTRO_FEATURES = "pam"
+REQUIRED_DISTRO_FEATURES = "pam sssd"
...
Adding a distro feature for a leaf package is wrong.

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed


Re: QA notification for completed autobuilder build (yocto-2.6.2.rc3)

Armin Kuster
 



On 4/5/19 6:28 AM, Tim Orling wrote:
Just curious: all Perl modules in oe-core have ptest enabled, but only libxml-parser-perl is included in these test reports. Is it simply the only module in that image or is something else afoot?

Is this what you are looking for ?

<snipped>
pango              | 12          | 0        | 0        | -
perl               | 2282        | 3        | 120      | -
python             | 8331        | 45       | 69       | -


On Thu, Apr 4, 2019 at 3:29 PM <richard.purdie@...> wrote:
On Fri, 2019-04-05 at 03:46 +0530, akuster808 wrote:
>
> On 4/5/19 3:25 AM, richard.purdie@... wrote:
> > On Thu, 2019-04-04 at 02:19 +0000, Jain, Sangeeta wrote:
> > > Also, I don't see any ptest results for 2.6.2.rc3 on public
> > > autobuilder. Do you have any plans to run them and share the
> > > results
> > > on autobuilder?
> > These were run separately but will run as part of any new stable
> > release builds. The results are here:
> >
> > https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/
> > https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/
> >
> > (for 2.6.2 and 2.5.4)
> >
> > I'll merge these into the main release output in due course.
> Did I miss something in order to create:
> https://autobuilder.yocto.io/pub/non-release/20190326-8/testresults/testresult-report.txt

Right now only a-quick or a-full builds get those.

You can get one with:

$ wget https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/testresults.json
$ resulttool report .

which gives:

==============================================================================================================
PTest Result Summary
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
Recipe             | Passed      | Failed   | Skipped  | Time(s)   
--------------------------------------------------------------------------------------------------------------
acl                | 221         | 0        | 0        | -
attr               | 109         | 0        | 0        | -
bash               | 75          | 4        | 0        | -
bluez5             | 25          | 0        | 0        | -
busybox            | 528         | 15       | 45       | -
bzip2              | 6           | 0        | 0        | -
dbus-test          | 18          | 3        | 2        | -
diffstat           | 439         | 0        | 0        | -
diffutils          | 20          | 0        | 0        | -
e2fsprogs          | 315         | 6        | 27       | -
flex               | 114         | 0        | 0        | -
gawk               | 342         | 0        | 0        | -
gdbm               | 24          | 0        | 0        | -
gdk-pixbuf         | 20          | 0        | 0        | -
glib-2.0           | 259         | 3        | 0        | -
gstreamer1.0       | 101         | 3        | 0        | -
gzip               | 21          | 0        | 0        | -
libpcre            | 3           | 0        | 0        | -
libusb1            | 4           | 0        | 0        | -
libxml-parser-perl | 15          | 0        | 0        | -
libxml2            | 134         | 0        | 0        | -
lttng-tools        | 1087        | 0        | 0        | - T
lzo                | 39          | 6        | 0        | -
nettle             | 158         | 0        | 2        | -
openssh            | 832         | 72       | 367      | - T
openssl            | 0           | 0        | 0        | -
pango              | 12          | 0        | 0        | -
perl               | 2298        | 1        | 120      | -
python             | 5444        | 15       | 53       | -
python3            | 7466        | 0        | 198      | -
quilt              | 57          | 0        | 0        | -
sed                | 86          | 0        | 0        | -
slang              | 97          | 0        | 0        | -
strace             | 213         | 272      | 97       | - T
tcl                | 148         | 0        | 0        | -
util-linux         | 0           | 395      | 55       | -
--------------------------------------------------------------------------------------------------------------

and

$ wget https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/testresults.json
$ resulttool report .

which gives:

==============================================================================================================
PTest Result Summary
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
Recipe             | Passed      | Failed   | Skipped  | Time(s)   
--------------------------------------------------------------------------------------------------------------
acl                | 221         | 0        | 0        | -
attr               | 109         | 0        | 0        | -
bash               | 75          | 4        | 0        | -
bluez5             | 7           | 0        | 0        | -
busybox            | 509         | 14       | 36       | -
bzip2              | 6           | 0        | 0        | -
dbus-test          | 18          | 3        | 2        | -
diffstat           | 439         | 0        | 0        | -
diffutils          | 20          | 0        | 0        | -
e2fsprogs          | 304         | 5        | 27       | -
flex               | 114         | 0        | 0        | -
gawk               | 342         | 0        | 0        | -
gdbm               | 19          | 0        | 0        | -
gdk-pixbuf         | 20          | 0        | 0        | -
glib-2             | 252         | 1        | 0        | -
gzip               | 21          | 0        | 0        | -
libevent           | 1           | 0        | 0        | -
libpcre            | 3           | 0        | 0        | -
libxml-parser-perl | 15          | 0        | 0        | -
libxml2            | 134         | 0        | 0        | -
lttng-tools        | 1087        | 0        | 0        | -
lzo                | 39          | 6        | 0        | -
nettle             | 158         | 0        | 2        | -
openssh            | 840         | 72       | 367      | -
openssl            | 54          | 0        | 0        | -
pango              | 12          | 0        | 0        | -
perl               | 2282        | 3        | 120      | -
python             | 8331        | 45       | 69       | -
quilt              | 57          | 0        | 0        | -
sed                | 86          | 0        | 0        | -
slang              | 97          | 0        | 0        | -
strace             | 160         | 233      | 80       | -
tcl                | 148         | 0        | 0        | -
util-linux         | 0           | 389      | 52       | -
--------------------------------------------------------------------------------------------------------------

Knowing what I do about master, there is the same image  space issue
here triggered in the strace ptest by the looks of it which then breaks
other tests like util-linux.

Cheers,

Richard






--
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto



[meta-security][PATCH 2/2] libmspack: update to 0.10.1

Armin Kuster
 

For details see: https://github.com/kyz/libmspack/blob/master/libmspack/ChangeLog

change compression to match that now being used from source

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
.../libmspack/{libmspack_0.9.1.bb => libmspack_0.10.1.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename recipes-security/libmspack/{libmspack_0.9.1.bb => libmspack_0.10.1.bb} (71%)

diff --git a/recipes-security/libmspack/libmspack_0.9.1.bb b/recipes-security/libmspack/libmspack_0.10.1.bb
similarity index 71%
rename from recipes-security/libmspack/libmspack_0.9.1.bb
rename to recipes-security/libmspack/libmspack_0.10.1.bb
index 56a8a07..b46159f 100644
--- a/recipes-security/libmspack/libmspack_0.9.1.bb
+++ b/recipes-security/libmspack/libmspack_0.10.1.bb
@@ -6,10 +6,10 @@ DEPENDS = ""

LIC_FILES_CHKSUM = "file://COPYING.LIB;beginline=1;endline=2;md5=5b1fd1f66ef926b3c8a5bb00a72a28dd"

-SRC_URI = "${DEBIAN_MIRROR}/main/libm/${BPN}/${BPN}_${PV}.orig.tar.gz"
+SRC_URI = "${DEBIAN_MIRROR}/main/libm/${BPN}/${BPN}_${PV}.orig.tar.xz"

-SRC_URI[md5sum] = "9602ae4a6b0468d9aaef6359c1e90657"
-SRC_URI[sha256sum] = "62a336d9c798638aaf3dceb43843320061544bbf35547c316b075b99112f2e40"
+SRC_URI[md5sum] = "d894d91eba4d2c6f76695fc9566d5387"
+SRC_URI[sha256sum] = "850c57442b850bf1bc0fc4ea8880903ebf2bed063c3c80782ee4626fbcb0e67d"

inherit autotools

--
2.7.4


[meta-security][PATCH 1/2] ccs-tools: move to reciped-mac

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
{recipes-security => recipes-mac}/ccs-tools/README | 0
{recipes-security => recipes-mac}/ccs-tools/ccs-tools_1.8.4.bb | 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename {recipes-security => recipes-mac}/ccs-tools/README (100%)
rename {recipes-security => recipes-mac}/ccs-tools/ccs-tools_1.8.4.bb (100%)

diff --git a/recipes-security/ccs-tools/README b/recipes-mac/ccs-tools/README
similarity index 100%
rename from recipes-security/ccs-tools/README
rename to recipes-mac/ccs-tools/README
diff --git a/recipes-security/ccs-tools/ccs-tools_1.8.4.bb b/recipes-mac/ccs-tools/ccs-tools_1.8.4.bb
similarity index 100%
rename from recipes-security/ccs-tools/ccs-tools_1.8.4.bb
rename to recipes-mac/ccs-tools/ccs-tools_1.8.4.bb
--
2.7.4


Re: QA notification for completed autobuilder build (yocto-2.6.2.rc3)

Tim Orling
 

Just curious: all Perl modules in oe-core have ptest enabled, but only libxml-parser-perl is included in these test reports. Is it simply the only module in that image or is something else afoot?

On Thu, Apr 4, 2019 at 3:29 PM <richard.purdie@...> wrote:
On Fri, 2019-04-05 at 03:46 +0530, akuster808 wrote:
>
> On 4/5/19 3:25 AM, richard.purdie@... wrote:
> > On Thu, 2019-04-04 at 02:19 +0000, Jain, Sangeeta wrote:
> > > Also, I don't see any ptest results for 2.6.2.rc3 on public
> > > autobuilder. Do you have any plans to run them and share the
> > > results
> > > on autobuilder?
> > These were run separately but will run as part of any new stable
> > release builds. The results are here:
> >
> > https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/
> > https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/
> >
> > (for 2.6.2 and 2.5.4)
> >
> > I'll merge these into the main release output in due course.
> Did I miss something in order to create:
> https://autobuilder.yocto.io/pub/non-release/20190326-8/testresults/testresult-report.txt

Right now only a-quick or a-full builds get those.

You can get one with:

$ wget https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/testresults.json
$ resulttool report .

which gives:

==============================================================================================================
PTest Result Summary
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
Recipe             | Passed      | Failed   | Skipped  | Time(s)   
--------------------------------------------------------------------------------------------------------------
acl                | 221         | 0        | 0        | -
attr               | 109         | 0        | 0        | -
bash               | 75          | 4        | 0        | -
bluez5             | 25          | 0        | 0        | -
busybox            | 528         | 15       | 45       | -
bzip2              | 6           | 0        | 0        | -
dbus-test          | 18          | 3        | 2        | -
diffstat           | 439         | 0        | 0        | -
diffutils          | 20          | 0        | 0        | -
e2fsprogs          | 315         | 6        | 27       | -
flex               | 114         | 0        | 0        | -
gawk               | 342         | 0        | 0        | -
gdbm               | 24          | 0        | 0        | -
gdk-pixbuf         | 20          | 0        | 0        | -
glib-2.0           | 259         | 3        | 0        | -
gstreamer1.0       | 101         | 3        | 0        | -
gzip               | 21          | 0        | 0        | -
libpcre            | 3           | 0        | 0        | -
libusb1            | 4           | 0        | 0        | -
libxml-parser-perl | 15          | 0        | 0        | -
libxml2            | 134         | 0        | 0        | -
lttng-tools        | 1087        | 0        | 0        | - T
lzo                | 39          | 6        | 0        | -
nettle             | 158         | 0        | 2        | -
openssh            | 832         | 72       | 367      | - T
openssl            | 0           | 0        | 0        | -
pango              | 12          | 0        | 0        | -
perl               | 2298        | 1        | 120      | -
python             | 5444        | 15       | 53       | -
python3            | 7466        | 0        | 198      | -
quilt              | 57          | 0        | 0        | -
sed                | 86          | 0        | 0        | -
slang              | 97          | 0        | 0        | -
strace             | 213         | 272      | 97       | - T
tcl                | 148         | 0        | 0        | -
util-linux         | 0           | 395      | 55       | -
--------------------------------------------------------------------------------------------------------------

and

$ wget https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/testresults.json
$ resulttool report .

which gives:

==============================================================================================================
PTest Result Summary
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
Recipe             | Passed      | Failed   | Skipped  | Time(s)   
--------------------------------------------------------------------------------------------------------------
acl                | 221         | 0        | 0        | -
attr               | 109         | 0        | 0        | -
bash               | 75          | 4        | 0        | -
bluez5             | 7           | 0        | 0        | -
busybox            | 509         | 14       | 36       | -
bzip2              | 6           | 0        | 0        | -
dbus-test          | 18          | 3        | 2        | -
diffstat           | 439         | 0        | 0        | -
diffutils          | 20          | 0        | 0        | -
e2fsprogs          | 304         | 5        | 27       | -
flex               | 114         | 0        | 0        | -
gawk               | 342         | 0        | 0        | -
gdbm               | 19          | 0        | 0        | -
gdk-pixbuf         | 20          | 0        | 0        | -
glib-2             | 252         | 1        | 0        | -
gzip               | 21          | 0        | 0        | -
libevent           | 1           | 0        | 0        | -
libpcre            | 3           | 0        | 0        | -
libxml-parser-perl | 15          | 0        | 0        | -
libxml2            | 134         | 0        | 0        | -
lttng-tools        | 1087        | 0        | 0        | -
lzo                | 39          | 6        | 0        | -
nettle             | 158         | 0        | 2        | -
openssh            | 840         | 72       | 367      | -
openssl            | 54          | 0        | 0        | -
pango              | 12          | 0        | 0        | -
perl               | 2282        | 3        | 120      | -
python             | 8331        | 45       | 69       | -
quilt              | 57          | 0        | 0        | -
sed                | 86          | 0        | 0        | -
slang              | 97          | 0        | 0        | -
strace             | 160         | 233      | 80       | -
tcl                | 148         | 0        | 0        | -
util-linux         | 0           | 389      | 52       | -
--------------------------------------------------------------------------------------------------------------

Knowing what I do about master, there is the same image  space issue
here triggered in the strace ptest by the looks of it which then breaks
other tests like util-linux.

Cheers,

Richard






--
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: QA notification for completed autobuilder build (yocto-2.6.2.rc3)

Richard Purdie
 

On Fri, 2019-04-05 at 03:46 +0530, akuster808 wrote:

On 4/5/19 3:25 AM, richard.purdie@linuxfoundation.org wrote:
On Thu, 2019-04-04 at 02:19 +0000, Jain, Sangeeta wrote:
Also, I don't see any ptest results for 2.6.2.rc3 on public
autobuilder. Do you have any plans to run them and share the
results
on autobuilder?
These were run separately but will run as part of any new stable
release builds. The results are here:

https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/
https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/

(for 2.6.2 and 2.5.4)

I'll merge these into the main release output in due course.
Did I miss something in order to create:
https://autobuilder.yocto.io/pub/non-release/20190326-8/testresults/testresult-report.txt
Right now only a-quick or a-full builds get those.

You can get one with:

$ wget https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/testresults.json
$ resulttool report .

which gives:

==============================================================================================================
PTest Result Summary
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
Recipe | Passed | Failed | Skipped | Time(s)
--------------------------------------------------------------------------------------------------------------
acl | 221 | 0 | 0 | -
attr | 109 | 0 | 0 | -
bash | 75 | 4 | 0 | -
bluez5 | 25 | 0 | 0 | -
busybox | 528 | 15 | 45 | -
bzip2 | 6 | 0 | 0 | -
dbus-test | 18 | 3 | 2 | -
diffstat | 439 | 0 | 0 | -
diffutils | 20 | 0 | 0 | -
e2fsprogs | 315 | 6 | 27 | -
flex | 114 | 0 | 0 | -
gawk | 342 | 0 | 0 | -
gdbm | 24 | 0 | 0 | -
gdk-pixbuf | 20 | 0 | 0 | -
glib-2.0 | 259 | 3 | 0 | -
gstreamer1.0 | 101 | 3 | 0 | -
gzip | 21 | 0 | 0 | -
libpcre | 3 | 0 | 0 | -
libusb1 | 4 | 0 | 0 | -
libxml-parser-perl | 15 | 0 | 0 | -
libxml2 | 134 | 0 | 0 | -
lttng-tools | 1087 | 0 | 0 | - T
lzo | 39 | 6 | 0 | -
nettle | 158 | 0 | 2 | -
openssh | 832 | 72 | 367 | - T
openssl | 0 | 0 | 0 | -
pango | 12 | 0 | 0 | -
perl | 2298 | 1 | 120 | -
python | 5444 | 15 | 53 | -
python3 | 7466 | 0 | 198 | -
quilt | 57 | 0 | 0 | -
sed | 86 | 0 | 0 | -
slang | 97 | 0 | 0 | -
strace | 213 | 272 | 97 | - T
tcl | 148 | 0 | 0 | -
util-linux | 0 | 395 | 55 | -
--------------------------------------------------------------------------------------------------------------

and

$ wget https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/testresults.json
$ resulttool report .

which gives:

==============================================================================================================
PTest Result Summary
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
Recipe | Passed | Failed | Skipped | Time(s)
--------------------------------------------------------------------------------------------------------------
acl | 221 | 0 | 0 | -
attr | 109 | 0 | 0 | -
bash | 75 | 4 | 0 | -
bluez5 | 7 | 0 | 0 | -
busybox | 509 | 14 | 36 | -
bzip2 | 6 | 0 | 0 | -
dbus-test | 18 | 3 | 2 | -
diffstat | 439 | 0 | 0 | -
diffutils | 20 | 0 | 0 | -
e2fsprogs | 304 | 5 | 27 | -
flex | 114 | 0 | 0 | -
gawk | 342 | 0 | 0 | -
gdbm | 19 | 0 | 0 | -
gdk-pixbuf | 20 | 0 | 0 | -
glib-2 | 252 | 1 | 0 | -
gzip | 21 | 0 | 0 | -
libevent | 1 | 0 | 0 | -
libpcre | 3 | 0 | 0 | -
libxml-parser-perl | 15 | 0 | 0 | -
libxml2 | 134 | 0 | 0 | -
lttng-tools | 1087 | 0 | 0 | -
lzo | 39 | 6 | 0 | -
nettle | 158 | 0 | 2 | -
openssh | 840 | 72 | 367 | -
openssl | 54 | 0 | 0 | -
pango | 12 | 0 | 0 | -
perl | 2282 | 3 | 120 | -
python | 8331 | 45 | 69 | -
quilt | 57 | 0 | 0 | -
sed | 86 | 0 | 0 | -
slang | 97 | 0 | 0 | -
strace | 160 | 233 | 80 | -
tcl | 148 | 0 | 0 | -
util-linux | 0 | 389 | 52 | -
--------------------------------------------------------------------------------------------------------------

Knowing what I do about master, there is the same image space issue
here triggered in the strace ptest by the looks of it which then breaks
other tests like util-linux.

Cheers,

Richard


[meta-security][PATCH 2/2] sssd: add DISTRO_FEATURE sssd

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 34bc8c8..d6a308c 100644
--- a/recipes-security/sssd/sssd_1.16.4.bb
+++ b/recipes-security/sssd/sssd_1.16.4.bb
@@ -16,7 +16,7 @@ SRC_URI[sha256sum] = "6bb212cd6b75b918e945c24e7c3f95a486fb54d7f7d489a9334cfa1a1f

inherit autotools pkgconfig gettext python-dir distro_features_check

-REQUIRED_DISTRO_FEATURES = "pam"
+REQUIRED_DISTRO_FEATURES = "pam sssd"

SSSD_UID ?= "root"
SSSD_GID ?= "root"
--
2.7.4


[meta-security][PATCH 1/2] libldb: work around samba libldb packaging issues

Armin Kuster
 

Samba and libldb overlap in a few places. This is the simplest fix for
now.

Use "sssd" DISTRO_FEATUE to test and enable changes

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-support/libldb/libldb_%.bbappend | 1 +
recipes-support/libldb/libldb_sssd.inc | 22 ++++++++++++++++++++++
2 files changed, 23 insertions(+)
create mode 100644 recipes-support/libldb/libldb_%.bbappend
create mode 100644 recipes-support/libldb/libldb_sssd.inc

diff --git a/recipes-support/libldb/libldb_%.bbappend b/recipes-support/libldb/libldb_%.bbappend
new file mode 100644
index 0000000..bb81700
--- /dev/null
+++ b/recipes-support/libldb/libldb_%.bbappend
@@ -0,0 +1 @@
+require ${@bb.utils.contains('DISTRO_FEATURES', 'sssd', '${BPN}_sssd.inc', '', d)}
diff --git a/recipes-support/libldb/libldb_sssd.inc b/recipes-support/libldb/libldb_sssd.inc
new file mode 100644
index 0000000..2633a1e
--- /dev/null
+++ b/recipes-support/libldb/libldb_sssd.inc
@@ -0,0 +1,22 @@
+# This fixes this issue:
+#ERROR: sssd-1.16.3-r0 do_prepare_recipe_sysroot: The file /usr/lib/python2.7/site-packages/_ldb_text.py is installed by both libldb and samba, aborting
+
+EXTRA_OECONF += "--disable-python"
+
+#Error: Transaction check error:
+# file /usr/bin/ldbadd conflicts between attempted installs of samba-4.8.4-r0.cortexa15t2hf_neon_vfpv4 and libldb-1.4.1-r0.cortexa15t2hf_neon_vfpv4
+# file /usr/bin/ldbdel conflicts between attempted installs of samba-4.8.4-r0.cortexa15t2hf_neon_vfpv4 and libldb-1.4.1-r0.cortexa15t2hf_neon_vfpv4
+# file /usr/bin/ldbedit conflicts between attempted installs of samba-4.8.4-r0.cortexa15t2hf_neon_vfpv4 and libldb-1.4.1-r0.cortexa15t2hf_neon_vfpv4
+# file /usr/bin/ldbmodify conflicts between attempted installs of samba-4.8.4-r0.cortexa15t2hf_neon_vfpv4 and libldb-1.4.1-r0.cortexa15t2hf_neon_vfpv4
+# file /usr/bin/ldbrename conflicts between attempted installs of samba-4.8.4-r0.cortexa15t2hf_neon_vfpv4 and libldb-1.4.1-r0.cortexa15t2hf_neon_vfpv4
+# file /usr/bin/ldbsearch conflicts between attempted installs of samba-4.8.4-r0.cortexa15t2hf_neon_vfpv4 and libldb-1.4.1-r0.cortexa15t2hf_neon_vfpv4
+
+do_install_append() {
+ rm -f ${D}${bindir}/ldbadd
+ rm -f ${D}${bindir}/ldbdel
+ rm -f ${D}${bindir}/ldbedit
+ rm -f ${D}${bindir}/ldbmodify
+ rm -f ${D}${bindir}/ldbrename
+ rm -f ${D}${bindir}/ldbsearch
+ rmdir ${D}${bindir}
+}
--
2.7.4


Re: QA notification for completed autobuilder build (yocto-2.6.2.rc3)

Armin Kuster
 

On 4/5/19 3:25 AM, richard.purdie@linuxfoundation.org wrote:
On Thu, 2019-04-04 at 02:19 +0000, Jain, Sangeeta wrote:
Also, I don't see any ptest results for 2.6.2.rc3 on public
autobuilder. Do you have any plans to run them and share the results
on autobuilder?
These were run separately but will run as part of any new stable
release builds. The results are here:

https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/
https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/

(for 2.6.2 and 2.5.4)

I'll merge these into the main release output in due course.
Did I miss something in order to create:
https://autobuilder.yocto.io/pub/non-release/20190326-8/testresults/testresult-report.txt

- Armin

Cheers,

Richard


Re: QA notification for completed autobuilder build (yocto-2.6.2.rc3)

Richard Purdie
 

On Thu, 2019-04-04 at 02:19 +0000, Jain, Sangeeta wrote:
Also, I don't see any ptest results for 2.6.2.rc3 on public
autobuilder. Do you have any plans to run them and share the results
on autobuilder?
These were run separately but will run as part of any new stable
release builds. The results are here:

https://autobuilder.yocto.io/pub/non-release/20190328-8/testresults/qemux86-64-ptest/
https://autobuilder.yocto.io/pub/non-release/20190328-7/testresults/qemux86-64-ptest/

(for 2.6.2 and 2.5.4)

I'll merge these into the main release output in due course.

Cheers,

Richard


Re: [ptest-runner] Run ptests via stdbuf configured to line-buffering

Richard Purdie
 

On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote:
As ptest-runner communicates with child processes via pipe2(),
the corresponding channels are not attached to a pty. In that
situation stdio facilities like printf() or fwrite() are fully
buffered. If a ptest would use them, without bothering
to fflush() the output, ptest-runner will only receive what
was written by the child ptest process after a buffer gets filled.
If the unit tests are proceeding slowly, this may mean that
ptest-runner will erroneously timeout due to an apparent lack of
'signs of life' from the child process.

stdbuf utility from coreutils adjusts the buffering to a line-
buffered
one, and so ptest-runner will get the lines as soon as they are
written.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
utils.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
I'm a little torn on this. I noticed some of the run-ptest scripts use
"| sed -u" whilst the one you were seeing problems with uses "| sed"
without -u.

We may want to consider strongly recommending -u. I'm testing a patch
with some tweaks like that in it...

Cheers,

Richard


Worries kernels supported

Armin Kuster
 

Hello,

I noticed there are 3 kernels in Warrior. 4.18, 4.19 an 5.0. Do we
really need 4.18?
I see its the default version for poky-tiny. 4.18 is EOL but maintained
by Windriver.

regards,
Armin


Do you use ISO images generated by bitbake?

Ross Burton
 

Hi,

I'm looking for some users that use the ISO images generated by
Bitbake (IMAGE_FSTYPE live or iso). Anyone out there?

Ross


Re: [ptest-runner] Run ptests via stdbuf configured to line-buffering

Joshua Watt
 

On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote:
As ptest-runner communicates with child processes via pipe2(),
the corresponding channels are not attached to a pty. In that
situation stdio facilities like printf() or fwrite() are fully
buffered. If a ptest would use them, without bothering
to fflush() the output, ptest-runner will only receive what
was written by the child ptest process after a buffer gets filled.
If the unit tests are proceeding slowly, this may mean that
ptest-runner will erroneously timeout due to an apparent lack of
'signs of life' from the child process.

stdbuf utility from coreutils adjusts the buffering to a line-
buffered
one, and so ptest-runner will get the lines as soon as they are
written.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
utils.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/utils.c b/utils.c
index 504df0b..1376e39 100644
--- a/utils.c
+++ b/utils.c
@@ -243,16 +243,13 @@ filter_ptests(struct ptest_list *head, char
**ptests, int ptest_num)
static inline void
run_child(char *run_ptest, int fd_stdout, int fd_stderr)
{
- char **argv = malloc(sizeof(char) * 2);
+ char* argv[] = {"stdbuf", "-oL", "-eL", "./run-ptest", NULL};
Should be run_ptest the from the function argument, not the string
literal "./run-ptest" ?


chdir(dirname(strdup(run_ptest)));

- argv[0] = run_ptest;
- argv[1] = NULL;
-
dup2(fd_stdout, STDOUT_FILENO);
// XXX: Redirect stderr to stdout to avoid buffer ordering
problems.
dup2(fd_stdout, STDERR_FILENO);
- execv(run_ptest, argv);
+ execvp(argv[0], argv);

exit(1);
}
--
2.17.1
--
Joshua Watt <JPEWhacker@gmail.com>


[ptest-runner] Run ptests via stdbuf configured to line-buffering

Alexander Kanavin
 

As ptest-runner communicates with child processes via pipe2(),
the corresponding channels are not attached to a pty. In that
situation stdio facilities like printf() or fwrite() are fully
buffered. If a ptest would use them, without bothering
to fflush() the output, ptest-runner will only receive what
was written by the child ptest process after a buffer gets filled.
If the unit tests are proceeding slowly, this may mean that
ptest-runner will erroneously timeout due to an apparent lack of
'signs of life' from the child process.

stdbuf utility from coreutils adjusts the buffering to a line-buffered
one, and so ptest-runner will get the lines as soon as they are
written.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
utils.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/utils.c b/utils.c
index 504df0b..1376e39 100644
--- a/utils.c
+++ b/utils.c
@@ -243,16 +243,13 @@ filter_ptests(struct ptest_list *head, char **ptests, int ptest_num)
static inline void
run_child(char *run_ptest, int fd_stdout, int fd_stderr)
{
- char **argv = malloc(sizeof(char) * 2);
+ char* argv[] = {"stdbuf", "-oL", "-eL", "./run-ptest", NULL};
chdir(dirname(strdup(run_ptest)));

- argv[0] = run_ptest;
- argv[1] = NULL;
-
dup2(fd_stdout, STDOUT_FILENO);
// XXX: Redirect stderr to stdout to avoid buffer ordering problems.
dup2(fd_stdout, STDERR_FILENO);
- execv(run_ptest, argv);
+ execvp(argv[0], argv);

exit(1);
}
--
2.17.1


Re: [ptest-runner] Run ptests via stdbuf configured to line-buffering

Alexander Kanavin
 

Bah, sorry, debugging got into the patch.

Will resend.

Alex

On Thu, 4 Apr 2019 at 17:34, Alexander Kanavin <alex.kanavin@gmail.com> wrote:

As ptest-runner communicates with child processes via pipe2(),
the corresponding channels are not attached to a pty. In that
situation stdio facilities like printf() or fwrite() are fully
buffered. If a ptest would use them, without bothering
to fflush() the output, ptest-runner will only receive what
was written by the child ptest process after a buffer gets filled.
If the unit tests are proceeding slowly, this may mean that
ptest-runner will erroneously timeout due to an apparent lack of
'signs of life' from the child process.

stdbuf utility from coreutils adjusts the buffering to a line-buffered
one, and so ptest-runner will get the lines as soon as they are
written.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
utils.c | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/utils.c b/utils.c
index 504df0b..c130fbd 100644
--- a/utils.c
+++ b/utils.c
@@ -243,16 +243,13 @@ filter_ptests(struct ptest_list *head, char **ptests, int ptest_num)
static inline void
run_child(char *run_ptest, int fd_stdout, int fd_stderr)
{
- char **argv = malloc(sizeof(char) * 2);
+ char* argv[] = {"stdbuf", "-oL", "-eL", "./run-ptest", NULL};
chdir(dirname(strdup(run_ptest)));

- argv[0] = run_ptest;
- argv[1] = NULL;
-
dup2(fd_stdout, STDOUT_FILENO);
// XXX: Redirect stderr to stdout to avoid buffer ordering problems.
dup2(fd_stdout, STDERR_FILENO);
- execv(run_ptest, argv);
+ execvp(argv[0], argv);

exit(1);
}
@@ -291,12 +288,12 @@ wait_child(const char *ptest_dir, const char *run_ptest, pid_t pid,

if (pfds[0].revents != 0) {
while ((n = read(fds[0], buf, WAIT_CHILD_BUF_MAX_SIZE)) > 0)
- fwrite(buf, n, 1, fps[0]);
+ fwrite(buf, n, 1, fps[0]); fwrite("hallo", 5 ,1 ,fps[0]); fflush(fps[0]);
}

if (pfds[1].revents != 0) {
while ((n = read(fds[1], buf, WAIT_CHILD_BUF_MAX_SIZE)) > 0)
- fwrite(buf, n, 1, fps[1]);
+ fwrite(buf, n, 1, fps[1]); fwrite("hallo-err", 9 ,1 ,fps[0]); fflush(fps[1]);
}

clock_gettime(clock, &sentinel);
--
2.17.1


[ptest-runner] Run ptests via stdbuf configured to line-buffering

Alexander Kanavin
 

As ptest-runner communicates with child processes via pipe2(),
the corresponding channels are not attached to a pty. In that
situation stdio facilities like printf() or fwrite() are fully
buffered. If a ptest would use them, without bothering
to fflush() the output, ptest-runner will only receive what
was written by the child ptest process after a buffer gets filled.
If the unit tests are proceeding slowly, this may mean that
ptest-runner will erroneously timeout due to an apparent lack of
'signs of life' from the child process.

stdbuf utility from coreutils adjusts the buffering to a line-buffered
one, and so ptest-runner will get the lines as soon as they are
written.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
utils.c | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/utils.c b/utils.c
index 504df0b..c130fbd 100644
--- a/utils.c
+++ b/utils.c
@@ -243,16 +243,13 @@ filter_ptests(struct ptest_list *head, char **ptests, int ptest_num)
static inline void
run_child(char *run_ptest, int fd_stdout, int fd_stderr)
{
- char **argv = malloc(sizeof(char) * 2);
+ char* argv[] = {"stdbuf", "-oL", "-eL", "./run-ptest", NULL};
chdir(dirname(strdup(run_ptest)));

- argv[0] = run_ptest;
- argv[1] = NULL;
-
dup2(fd_stdout, STDOUT_FILENO);
// XXX: Redirect stderr to stdout to avoid buffer ordering problems.
dup2(fd_stdout, STDERR_FILENO);
- execv(run_ptest, argv);
+ execvp(argv[0], argv);

exit(1);
}
@@ -291,12 +288,12 @@ wait_child(const char *ptest_dir, const char *run_ptest, pid_t pid,

if (pfds[0].revents != 0) {
while ((n = read(fds[0], buf, WAIT_CHILD_BUF_MAX_SIZE)) > 0)
- fwrite(buf, n, 1, fps[0]);
+ fwrite(buf, n, 1, fps[0]); fwrite("hallo", 5 ,1 ,fps[0]); fflush(fps[0]);
}

if (pfds[1].revents != 0) {
while ((n = read(fds[1], buf, WAIT_CHILD_BUF_MAX_SIZE)) > 0)
- fwrite(buf, n, 1, fps[1]);
+ fwrite(buf, n, 1, fps[1]); fwrite("hallo-err", 9 ,1 ,fps[0]); fflush(fps[1]);
}

clock_gettime(clock, &sentinel);
--
2.17.1


Re: require and image.bbappend

Stefano Babic
 

Hi Matteo,

On 04/04/19 15:35, Matteo Facchinetti wrote:
Hi,

I encountered a problem when try to add packages in my image recipe, but
I don't understernd if I wrong something or I have to do it in another way.

In detail, in my common_layer there are:
   - image_base.bb <http://image_base.bb> : yocto base image 
   - image_with_graphicsupport.bb <http://image_with_graphicsupport.bb>
: where include image_base.bb <http://image_base.bb> (require
image_base.bb <http://image_base.bb>)

Now, in my BSP layer, I want to add some packages to the image_base.bb
<http://image_base.bb>, so I create here the image_base.bbappend file.
But when I try to compile image_with_graphicsupport.bb
<http://image_with_graphicsupport.bb> the result is not how expected.
Image_with_graphicsupport.bb doesn't add packages contained in
image_base.bbappend but only the packages contained in image_base.bb
<http://image_base.bb>.

Is true that when include an image to another with require statement,
you can't extend the base image with a bbappend?
Yes, it is true, because the file is included and it is not anymore like
a recipe that can be extend. It will be searched for a
image_with_graphicsupport.bb append, not image_base.bbappend.

IMHO you can easy reach your goal if you write a packagegroup recipe
where you put all packages you have in the IMAGE_INSTALL of your
image_base.bb. You can then have a .bbappend for the packagegroup in
your BSP layer (and this then works) and you put the packagegroup in the
IMAGE_INSTALL directive of both image_base.bb and
Image_with_graphicsupport.bb.

or I wrong something else?
Best regards,
Stefano Babic


--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================


require and image.bbappend

Matteo Facchinetti
 

Hi,

I encountered a problem when try to add packages in my image recipe, but I don't understernd if I wrong something or I have to do it in another way.

In detail, in my common_layer there are:
   - image_base.bb : yocto base image 

Now, in my BSP layer, I want to add some packages to the image_base.bb, so I create here the image_base.bbappend file.
But when I try to compile image_with_graphicsupport.bb the result is not how expected.
Image_with_graphicsupport.bb doesn't add packages contained in image_base.bbappend but only the packages contained in image_base.bb.

Is true that when include an image to another with require statement, you can't extend the base image with a bbappend? or I wrong something else?

Regards,

Matteo Facchinetti,
Sirius Electronic Systems


Re: gdb built with musl libc segfault

Lluis Campos
 

Hi again,

On 04.04.2019 12:58, Lluis Campos wrote:

On 03.04.2019 18:59, Khem Raj wrote:
On Tue, Apr 2, 2019 at 4:51 AM Lluis Campos <lluis.campos@northern.tech> wrote:
Hi all,

This is my very first question in the Yocto mailing list. Very exited!
Please let me know if I should use other list for this.


I am building an image using musl libc instead of gnu libc. I am not
using yocto-tiny distro, instead I achieve this by setting on my local.conf:

TCLIBC = "musl"


My app (mender) got a segfault just starting. See output from strace:

root@raspberrypi3:~# strace mender
execve("/usr/bin/mender", ["mender"], 0x7ee65e10 /* 13 vars */) = 0
set_tls(0x76f1bffc)                     = 0
set_tid_address(0x76f1bfa0)             = 3020
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x530bc8} ---
+++ killed by SIGSEGV +++
Segmentation fault


To be able to debug the process, I added gdb to my image adding to my
local.conf:

CORE_IMAGE_EXTRA_INSTALL += "packagegroup-core-buildessential
packagegroup-core-tools-debug"


Then, ironically, gdb itself also segfaults:

root@raspberrypi3:~# strace gdb 2>&1 | tail
fcntl64(3, F_SETFD, FD_CLOEXEC)         = 0
getdents64(3, /* 6 entries */, 2048)    = 144
getdents64(3, /* 0 entries */, 2048)    = 0
close(3)                                = 0
ioctl(0, TIOCGWINSZ, {ws_row=25, ws_col=74, ws_xpixel=0, ws_ypixel=0}) = 0
getcwd("/home/root", 4096)              = 11
access("/usr/local/bin/gdb", X_OK)      = -1 ENOENT (No such file or
directory)
access("/usr/bin/gdb", X_OK)            = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7e35aff0} ---
+++ killed by SIGSEGV +++


So, what is going on here? My guess is that some recipes are being
wrongly linked with gnu libc instead of musl, and then cannot run in my
device.

Any ideas on how to debug the issue?
We have switched to using PIE by default in last few releases, can you
try master but comment out
require conf/distro/include/security_flags.inc
in your distro conf file.
Hi Khem,

Thanks for your help.

Commenting out this line seems to work!

FYI,

Enabling back the require of security_flags.in, and instead applying no security flags only to my recipe is enough.

I have added to my conf/local.conf:

SECURITY_CFLAGS_pn-mender = "${SECURITY_NOPIE_CFLAGS}"
SECURITY_LDFLAGS_pn-mender = ""

So I will continue this way until I find the root cause on my CGO code.

Thanks again for your help.




I will try to figure out exactly which exact option is causing the issue.



Thanks!


Lluís Campos
mender.io
Northen Tech

--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

8821 - 8840 of 53484