Re: [yocto] How to extrac rootfs.wic in Ubuntu?

[JH]

Good tips, Thanks Gabriele and Onur.

On 7/5/19, Gabriele Zampieri  wrote:
> Hi,
>
> in your machine conf add: (or just overload it, if you need only tar.gz
> images, this will speedup the image generation process)
> IMAGE_FSTYPES += " tar.gz"
>
> The list of (standard) available image types can be found here:
> https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-IMAGE_TYPES
>
> Gabriele
>
> Il giorno ven 5 lug 2019 alle ore 14:23 JH  ha
> scritto:
>
>> Hi,
>>
>> I know I can use dd to write wic to a device such as a SD card, but I
>> need to extract rootfs.wic then repack it by tar.gz in Ubuntu machine.
>> Is it possible? How can I do it.
>>
>> Thank you.
>>
>> - jupiter
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto dev day ELCE 2019 Lyon ?

[Philip Balister]

In 07/04/2019 06:38 AM, Peter Kjellerstedt wrote:
>> -Original Message-
>> From: yocto-boun...@yoctoproject.org 
>> On Behalf Of Nicolas Dechesne
>> Sent: den 4 juli 2019 08:45
>> To: Thomas Roos ; Volosincu, Andreea S
>> 
>> Cc: Yocto list discussion 
>> Subject: Re: [yocto] yocto dev day ELCE 2019 Lyon ?
>>
>> Hi Thomas,
>>
>> On Thu, Jul 4, 2019 at 8:18 AM Thomas Roos 
>> wrote:
>>>
>>> Hi,
>>> are there any plans to organize a yocto dev day in October 2019,
>>> Lyon. Embedded Linux Conference Europe?
>>> cheers, Thomas
>>
>> Yes, in fact we are trying something new for the first time at ELC-E
>> this year, see:
>> https://lists.yoctoproject.org/pipermail/yocto/2019-May/045088.html
>>
>> There will be a 2-day "Yocto Project Summit" with a mix of
>> presentations/talks, training classes and developers meetings,
>> including a social event in the evening.
>>
>> cc'ing Andreea if there are more questions.
> 
> Will this replace OEDEM too?

Yes. 5 days of conference sessions meetings is enough for anyone :)

Philip


> 
> //Peter
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.7.1.rc1)

[akuster808]

On 7/5/19 12:04 AM, Jain, Sangeeta wrote:
>
> QA cycle report for 2.7.1 RC1:
>
>  
>
>  1. No high milestone defects. 
>  2. Test results are available at following location:
>
>   • For results of all automated tests,
> please refer to results at public AB [1]
>
>   • For other test results, refer to git
> repo " yocto-testresults-contrib" [2]
>
>   • For test report for test cases run by
> Intel and WR team, refer to git repo " yocto-testresults-contrib" [2]
>
>  3. No new defects are found in this cycle. Hardware specific issues
> are observed (Parselog and Xorg failures), but no bugs are filed
> as these are not real Yocto failures.
>  4. ptest failing in this release which were passing in previous
> release – gstreamer[3]. Timeout issues observed in ptest - mdadm [4].
>  5. Summary of ptest in this build:
>
>    qemux86-64-ptest
>
>           Total : 44600
>
>       Pass : 42294
>
>    Fail :  290
>
>      Skip : 2016
>
>       Timeout issues in mdadm
>
> === Links 
>
>  
>
> [1] -
> https://autobuilder.yocto.io/pub/releases/yocto-2.7.1.rc1/testresults/
>
>  
>
> [2] -
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
>
>  
>
> [3] - [QA 2.7.1.rc1] gstreamer1.0.pipelines/seek ptest failure
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13429
>
Will have to investigate.
>
>  
>
> [4] - mdadm ptest times out
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13368
>
This is known issue and also affects master

Thanks for the report.

- armin
>
>  
>
>  
>
>  
>
> Thanks & Regards,
>
> Sangeeta Jain
>
>  
>
>  Forwarded Message 
>
> *Subject: *
>
>   
>
> QA notification for completed autobuilder build (yocto-2.7.1.rc1)
>
> *Date: *
>
>   
>
> Mon, 1 Jul 2019 03:08:44 +
>
> *From: *
>
>   
>
> Poky Build User 
> 
>
> *To: *
>
>   
>
> yocto@yoctoproject.org 
>
> *CC: *
>
>   
>
> ota...@ossystems.com.br ,
> yi.z...@windriver.com ,
> apoorv.san...@intel.com ,
> ee.peng.y...@intel.com ,
> aaron.chun.yew.c...@intel.com ,
> chin.huat@intel.com ,
> richard.pur...@linuxfoundation.org
> , akuster...@gmail.com
> , sjolley.yp...@gmail.com
> , sangeeta.j...@intel.com
> 
>
>
>
>
> A build flagged for QA (yocto-2.7.1.rc1) was completed on the
> autobuilder and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-2.7.1.rc1
>
>
> Build hash information:
> bitbake: 34ed28a412af642a993642c14bd8b95d5ef22cd8
> meta-gplv2: 460ba027fd79b99151f95c826446f3aead5d17ff
> meta-intel: e84c763090f91196a5d234f62ee39bcf296c7f2e
> meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
> oecore: 886deb4d0919c7a81036ea14fb8fd0f1619dd3a3
> poky: 38d5c8ea98cfa49825c473eba8984c12edf062be
>
>
>
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
>
>

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

Re: [yocto] How to extrac rootfs.wic in Ubuntu?

[Gabriele Zampieri]

Hi,

in your machine conf add: (or just overload it, if you need only tar.gz
images, this will speedup the image generation process)
IMAGE_FSTYPES += " tar.gz"

The list of (standard) available image types can be found here:
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-IMAGE_TYPES

Gabriele

Il giorno ven 5 lug 2019 alle ore 14:23 JH  ha
scritto:

> Hi,
>
> I know I can use dd to write wic to a device such as a SD card, but I
> need to extract rootfs.wic then repack it by tar.gz in Ubuntu machine.
> Is it possible? How can I do it.
>
> Thank you.
>
> - jupiter
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to extrac rootfs.wic in Ubuntu?

[Onur Eser]

Hello Jupiter,
I guess you can directly use archieve manager of ubuntu to extract it. And then 
you can tar the files from terminal. Or there should be another image ends with 
.wic (not .rootfs.wic) inside /build/tmp/deploy/image-name
Onur



Kimden: JH  adına yocto-boun...@yoctoproject.org
Gönderme tarihi: Cuma, Temmuz 5, 2019 3:23 ÖS
Kime: Yocto discussion list
Konu: [yocto] How to extrac rootfs.wic in Ubuntu?

Hi,

I know I can use dd to write wic to a device such as a SD card, but I
need to extract rootfs.wic then repack it by tar.gz in Ubuntu machine.
Is it possible? How can I do it.

Thank you.

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

[yocto] How to extrac rootfs.wic in Ubuntu?

[JH]

Hi,

I know I can use dd to write wic to a device such as a SD card, but I
need to extract rootfs.wic then repack it by tar.gz in Ubuntu machine.
Is it possible? How can I do it.

Thank you.

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

Re: [yocto] dev_pkgs feature caused conflict

[Zoran Stojsavljevic]

Hello Onur,

It was quite a while (almost two years) I experimented with IMX6
Colibri from Toradex. Here is what I have used to build tools using
the following Toradex pointer (from one of my private Github
specimens):

OpenEmbedded (core):
http://developer.toradex.com/knowledge-base/board-support-package/openembedded-(core)

How to set up Qt Creator to cross compile for embedded Linux:
http://developer.toradex.com/knowledge-base/how-to-set-up-qt-creator-to-cross-compile-for-embedded-linux

Adding the Qt5 Layer:
http://developer.toradex.com/knowledge-base/board-support-package/openembedded-(core)#Adding_the_Qt5_Layer

Please, could you inspect these pointers (Toradex ones)?

I used Toradex repos (not ones you are using) to build Qt5 on the top of X11.

I attached a local.conf I used to build Rocko at the time (September
2017., IIRC), and to build the first step: tools!

I built google repo Toradex image for tools using the command: bitbake
-k meta-toolchain-qt5 . I remember, worked as a charm.

Zoran
___




On Fri, Jul 5, 2019 at 11:40 AM Onur Eser  wrote:
>
> Hello everyone,
>
> I am trying to build a toolchain for my image. Added line
> IMAGE_FEATURES += "dev-pkgs"
> to my local.conf file and rebuilt everything from zero.
> It gives two conflict errors.
>
> Check my error log:
> https://paste.ee/p/HbC5r#zh4fQsZhX9vAQEXQiwIqc7c2VkK82i2d
>
> Note: If I exclude the line
> IMAGE_FEATURES += "dev-pkgs"
> image is being builded and booted successfully.
> But I need it to cross compile if I am not wrong.
> If I include this line, following error shows up.
>
> Note2: My base image is core-image-weston.
> My device is SolidRun Humming Board 2 i.MX6 ARMv7
>
> Cheers,
> Onur
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
WARN_QA_remove = "host-user-contaminated"

# meta-freescale otherwise defaults to wayland
DISTRO_FEATURES_remove = "wayland"

# This file is your local configuration file and is where all local user 
settings
# are placed. The comments in this file give some guide to the options a new 
user
# to the system might want to change but pretty much any configuration option 
can
# be set in this file. More adventurous users can look at local.conf.extended 
# which contains other examples of configuration which can be placed in this 
file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the 
# default values are provided as comments to show people example syntax. 
Enabling
# the option is a question of removing the # character and making any change to 
the
# variable as required.

#
# Parallelism Options
#
# These two options control how much parallelism BitBake should use. The first 
# option determines how many tasks bitbake should run in parallel:
#
#BB_NUMBER_THREADS ?= "4"
#
# Default to setting automatically based on cpu count
BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
# 
# The second option controls how many processes make should run in parallel when
# running compile tasks:
#
#PARALLEL_MAKE ?= "-j 4"
#
# Default to setting automatically based on cpu count
PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
#
# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate for example.

BB_NUMBER_THREADS = "4"
PARALLEL_MAKE = "-j 4"

#
# Machine Selection
#
# You need to select a specific machine to target the build with. These are the
# machines which for the Toradex Colibri and Apalis computer on module families
#
#MACHINE ?= "apalis-imx6"
#MACHINE ?= "apalis-t30"
#MACHINE ?= "apalis-tk1"
#MACHINE ?= "apalis-tk1-mainline"
#
#MACHINE ?= "colibri-imx6"
#MACHINE ?= "colibri-imx7"
#MACHINE ?= "colibri-t20"
#MACHINE ?= "colibri-t30"
#MACHINE ?= "colibri-vf"

MACHINE ?= "colibri-imx6"

#
# There are also a selection of emulated machines available which can boot and 
run
# in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"

#
# Where to place downloads
#
# During a first build the system will download many different source code 
tarballs
# from various upstream projects. This can take a while, particularly if your 
network
# connection is slow. These are all stored in DL_DIR. When wiping and 
rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This 
directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build 
directory.
#
DL_DIR ?= "${TOPDIR}/downloads"

#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built 
output.
# This is done using "shared state" files which can be thought of as cache 
objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory inta

Re: [yocto] dev_pkgs feature caused conflict

[Burton, Ross]

file /lib/firmware/ti-connectivity/wl18xx-fw-4.bin from install of
linux-firmware-wl12xx-1:0.0+git0+d114732723-r0.noarch conflicts with
file from package firmware-wireless-wilink8-1.0-r0.cortexa9hf_neon
file /lib/firmware/brcm/brcmfmac4330-sdio.bin from install of
linux-firmware-bcm4330-1:0.0+git0+d114732723-r0.noarch conflicts with
file from package firmware-wireless-brcm-1.0-r0.cortexa9hf_neon


Looks like your BSP is shipping its own firmware (firmware-wireless-*)
that ships the same files as linux-firmware.  Speak to your BSP
provider to detemine what one of those needs to be removed.

Ross

On Fri, 5 Jul 2019 at 10:40, Onur Eser  wrote:
>
> Hello everyone,
>
> I am trying to build a toolchain for my image. Added line
> IMAGE_FEATURES += "dev-pkgs"
> to my local.conf file and rebuilt everything from zero.
> It gives two conflict errors.
>
> Check my error log:
> https://paste.ee/p/HbC5r#zh4fQsZhX9vAQEXQiwIqc7c2VkK82i2d
>
> Note: If I exclude the line
> IMAGE_FEATURES += "dev-pkgs"
> image is being builded and booted successfully.
> But I need it to cross compile if I am not wrong.
> If I include this line, following error shows up.
>
> Note2: My base image is core-image-weston.
> My device is SolidRun Humming Board 2 i.MX6 ARMv7
>
> Cheers,
> Onur
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] dev_pkgs feature caused conflict

[Onur Eser]

Hello everyone,

I am trying to build a toolchain for my image. Added line
IMAGE_FEATURES += "dev-pkgs"
to my local.conf file and rebuilt everything from zero.
It gives two conflict errors.

Check my error log:
https://paste.ee/p/HbC5r#zh4fQsZhX9vAQEXQiwIqc7c2VkK82i2d

Note: If I exclude the line
IMAGE_FEATURES += "dev-pkgs"
image is being builded and booted successfully.
But I need it to cross compile if I am not wrong.
If I include this line, following error shows up.

Note2: My base image is core-image-weston.
My device is SolidRun Humming Board 2 i.MX6 ARMv7

Cheers,
Onur
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-cgl][PATCH] cluster-glue: use git fetcher instead of the tarball source

[mingli.yu]

From: Mingli Yu 

Per http://hg.linux-ha.org/, the repo moves to
https://github.com/ClusterLabs/cluster-glue and since
commit [21f84fc insane: add sanity checks to SRC_URI]
applied in oe-core, do not use unstable github archive
tarballs, so use git instead.

Signed-off-by: Mingli Yu 
---
 meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb | 7 +++
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb 
b/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
index 0673482..e0aa2b1 100644
--- a/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
+++ b/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
 DEPENDS = "libxml2 libtool glib-2.0 bzip2 util-linux net-snmp openhpi"
 
 SRC_URI = " \
-http://hg.linux-ha.org/glue/archive/glue-${PV}.tar.bz2 \
+git://github.com/ClusterLabs/${BPN}.git \
 file://0001-don-t-compile-doc-and-Error-Fix.patch \
 file://0001-ribcl.py.in-Warning-Fix.patch \
 file://volatiles \
@@ -19,8 +19,7 @@ SRC_URI = " \
 "
 SRC_URI_append_libc-uclibc = " file://kill-stack-protector.patch"
 
-SRC_URI[md5sum] = "ec620466d6f23affa3b074b72bca7870"
-SRC_URI[sha256sum] = 
"feba102fa1e24b6be2005089ebe362b82d6567af60005cf371679b1b44ec503f"
+SRCREV = "1bc77825c0cfb0c80f9c82a061af7ede68676cb4"
 
 inherit autotools useradd pkgconfig systemd
 
@@ -30,7 +29,7 @@ SYSTEMD_AUTO_ENABLE = "disable"
 HA_USER = "hacluster"
 HA_GROUP = "haclient"
 
-S = "${WORKDIR}/Reusable-Cluster-Components-glue--glue-${PV}"
+S = "${WORKDIR}/git"
 
 PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}"
 PACKAGECONFIG[systemd] = 
"--with-systemdsystemunitdir=${systemd_system_unitdir},--without-systemdsystemunitdir,systemd"
-- 
2.7.4

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

[yocto] [meta-selinux][PATCH v2 1/2] audit: upgrade 2.8.4 -> 2.8.5

[mingli.yu]

From: Yi Zhao 

* Drop backport patch:
  0001-Remove-strdupa-as-suggested-in-pull-request-25.patch

* Refresh all patches.

Signed-off-by: Yi Zhao 
---
 ...e-strdupa-as-suggested-in-pull-request-25.patch | 47 --
 ...bstitue-functions-for-strndupa-rawmemchr.patch} | 23 +--
 .../audit/audit/audit-python-configure.patch   | 10 ++---
 recipes-security/audit/audit/audit-python.patch|  8 ++--
 recipes-security/audit/audit/auditd|  2 +-
 .../audit/audit/fix-swig-host-contamination.patch  | 22 +-
 .../audit/{audit_2.8.4.bb => audit_2.8.5.bb}   |  7 ++--
 7 files changed, 35 insertions(+), 84 deletions(-)
 delete mode 100644 
recipes-security/audit/audit/0001-Remove-strdupa-as-suggested-in-pull-request-25.patch
 rename 
recipes-security/audit/audit/{0002-Add-substitue-functions-for-strndupa-rawmemchr.patch
 => Add-substitue-functions-for-strndupa-rawmemchr.patch} (88%)
 rename recipes-security/audit/{audit_2.8.4.bb => audit_2.8.5.bb} (92%)

diff --git 
a/recipes-security/audit/audit/0001-Remove-strdupa-as-suggested-in-pull-request-25.patch
 
b/recipes-security/audit/audit/0001-Remove-strdupa-as-suggested-in-pull-request-25.patch
deleted file mode 100644
index 38029aa..000
--- 
a/recipes-security/audit/audit/0001-Remove-strdupa-as-suggested-in-pull-request-25.patch
+++ /dev/null
@@ -1,47 +0,0 @@
-From a1782b58b687b74249dc8b2411a3f646b821ebd6 Mon Sep 17 00:00:00 2001
-From: Steve Grubb 
-Date: Thu, 4 Oct 2018 08:45:47 -0400
-Subject: [PATCH] Remove strdupa as suggested in pull request #25
-

- src/auditd.c | 11 ++-
- 1 file changed, 6 insertions(+), 5 deletions(-)
-
-Origin: 
https://github.com/linux-audit/audit-userspace/commit/a1782b58b687b74249dc8b2411a3f646b821ebd6
-Applied-Upstream: yes
-
-diff --git a/src/auditd.c b/src/auditd.c
-index b0952db..c826ec0 100644
 a/src/auditd.c
-+++ b/src/auditd.c
-@@ -209,21 +209,22 @@ static void cont_handler(struct ev_loop *loop, struct 
ev_signal *sig,
- 
- static int extract_type(const char *str)
- {
--  const char *tptr, *ptr2, *ptr = str;
-+  const char *ptr2, *ptr = str;
-   if (*str == 'n') {
-   ptr = strchr(str+1, ' ');
-   if (ptr == NULL)
-   return -1; // Malformed - bomb out
-   ptr++;
-   }
-+
-   // ptr should be at 't'
-   ptr2 = strchr(ptr, ' ');
--  // get type=xxx in a buffer
--  tptr = strndupa(ptr, ptr2 - ptr);
-+
-   // find =
--  str = strchr(tptr, '=');
--  if (str == NULL)
-+  str = strchr(ptr, '=');
-+  if (str == NULL || str >= ptr2)
-   return -1; // Malformed - bomb out
-+
-   // name is 1 past
-   str++;
-   return audit_name_to_msg_type(str);
--- 
-2.20.1
-
diff --git 
a/recipes-security/audit/audit/0002-Add-substitue-functions-for-strndupa-rawmemchr.patch
 
b/recipes-security/audit/audit/Add-substitue-functions-for-strndupa-rawmemchr.patch
similarity index 88%
rename from 
recipes-security/audit/audit/0002-Add-substitue-functions-for-strndupa-rawmemchr.patch
rename to 
recipes-security/audit/audit/Add-substitue-functions-for-strndupa-rawmemchr.patch
index c948aa3..bb6c61e 100644
--- 
a/recipes-security/audit/audit/0002-Add-substitue-functions-for-strndupa-rawmemchr.patch
+++ 
b/recipes-security/audit/audit/Add-substitue-functions-for-strndupa-rawmemchr.patch
@@ -1,12 +1,11 @@
-From 5346b6af0ca67a2965ca5846ae150f3021a2aa17 Mon Sep 17 00:00:00 2001
+From bdcdc3dff4469aac88e718bd15958d5ed4b9392a Mon Sep 17 00:00:00 2001
 From: Steve Grubb 
 Date: Tue, 26 Feb 2019 18:33:33 -0500
 Subject: [PATCH] Add substitue functions for strndupa & rawmemchr
 
+Upstream-Status: Backport
+[https://github.com/linux-audit/audit-userspace/commit/d579a08bb1cde71f939c13ac6b2261052ae9f77e]
 ---
-Origin: 
https://github.com/linux-audit/audit-userspace/commit/d579a08bb1cde71f939c13ac6b2261052ae9f77e
-Applied-Upstream: yes
-
  auparse/auparse.c   | 12 +++-
  auparse/interpret.c |  9 -
  configure.ac| 14 +-
@@ -14,7 +13,7 @@ Applied-Upstream: yes
  4 files changed, 43 insertions(+), 4 deletions(-)
 
 diff --git a/auparse/auparse.c b/auparse/auparse.c
-index f84712e..3764046 100644
+index 650db02..2e1c737 100644
 --- a/auparse/auparse.c
 +++ b/auparse/auparse.c
 @@ -1,5 +1,5 @@
@@ -24,7 +23,7 @@ index f84712e..3764046 100644
   * All Rights Reserved.
   *
   * This library is free software; you can redistribute it and/or
-@@ -1100,6 +1100,16 @@ static int str2event(char *s, au_event_t *e)
+@@ -1118,6 +1118,16 @@ static int str2event(char *s, au_event_t *e)
return 0;
  }
  
@@ -42,7 +41,7 @@ index f84712e..3764046 100644
  static int extract_timestamp(const char *b, au_event_t *e)
  {
 diff --git a/auparse/interpret.c b/auparse/interpret.c
-index 1846f9d..8540bd1 100644
+index 51c4a5e..67b7b77 100644
 --- a/auparse/interpret.c
 +++ b/auparse/interpret.c
 @@ -853,6 +853,13 @@ err_out:
@@ -69,7 +68,7 @@ index 1846f9d..8540bd

[yocto] [meta-selinux][PATCH 2/2] audit: use git fetcher instead of the tarball source

[mingli.yu]

From: Mingli Yu 

Per http://people.redhat.com/sgrubb/audit/, the
tarball source moves to https://github.com/linux-audit/audit-userspace,
and since commit [21f84fc insane: add sanity checks to SRC_URI]
applied in oe-core, do not use unstable github archive
tarballs, so use git instead.

Signed-off-by: Mingli Yu 
---
 recipes-security/audit/audit_2.8.5.bb | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/recipes-security/audit/audit_2.8.5.bb 
b/recipes-security/audit/audit_2.8.5.bb
index bd09873..d3b9b51 100644
--- a/recipes-security/audit/audit_2.8.5.bb
+++ b/recipes-security/audit/audit_2.8.5.bb
@@ -7,7 +7,7 @@ SECTION = "base"
 LICENSE = "GPLv2+ & LGPLv2+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
 
-SRC_URI = "http://people.redhat.com/sgrubb/${BPN}/${BPN}-${PV}.tar.gz \
+SRC_URI = 
"git://github.com/linux-audit/${BPN}-userspace.git;branch=2.8_maintenance \
file://audit-python-configure.patch \
file://audit-python.patch \
file://fix-swig-host-contamination.patch \
@@ -16,8 +16,9 @@ SRC_URI = 
"http://people.redhat.com/sgrubb/${BPN}/${BPN}-${PV}.tar.gz \
file://auditd.service \
file://audit-volatile.conf \
 "
-SRC_URI[md5sum] = "9455e5773670afdbccaeb92681b2e97d"
-SRC_URI[sha256sum] = 
"0e5d4103646e00f8d1981e1cd2faea7a2ae28e854c31a803e907a383c5e2ecb7"
+
+S = "${WORKDIR}/git"
+SRCREV = "5fae55c1ad15b3cefe6890eba7311af163e9133c"
 
 inherit autotools pythonnative update-rc.d systemd
 
-- 
2.7.4

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

Re: [yocto] QA notification for completed autobuilder build (yocto-2.7.1.rc1)

[Jain, Sangeeta]

QA cycle report for 2.7.1 RC1:


  1.  No high milestone defects.
  2.  Test results are available at following location:

  • For results of all automated tests, please 
refer to results at public AB [1]

  • For other test results, refer to git repo " 
yocto-testresults-contrib" [2]

  • For test report for test cases run by Intel and 
WR team, refer to git repo " yocto-testresults-contrib" [2]

  1.  No new defects are found in this cycle. Hardware specific issues are 
observed (Parselog and Xorg failures), but no bugs are filed as these are not 
real Yocto failures.
  2.  ptest failing in this release which were passing in previous release – 
gstreamer[3]. Timeout issues observed in ptest - mdadm [4].
  3.  Summary of ptest in this build:

   qemux86-64-ptest

  Total : 44600

  Pass : 42294

   Fail :  290

 Skip : 2016

  Timeout issues in mdadm

=== Links 



[1] - https://autobuilder.yocto.io/pub/releases/yocto-2.7.1.rc1/testresults/



[2] - 
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults



[3] - [QA 2.7.1.rc1] gstreamer1.0.pipelines/seek ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13429



[4] - mdadm ptest times out

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13368




Thanks & Regards,
Sangeeta Jain

 Forwarded Message 
Subject:

QA notification for completed autobuilder build (yocto-2.7.1.rc1)

Date:

Mon, 1 Jul 2019 03:08:44 +

From:

Poky Build User 


To:

yocto@yoctoproject.org

CC:

ota...@ossystems.com.br, 
yi.z...@windriver.com, 
apoorv.san...@intel.com, 
ee.peng.y...@intel.com, 
aaron.chun.yew.c...@intel.com, 
chin.huat@intel.com, 
richard.pur...@linuxfoundation.org, 
akuster...@gmail.com, 
sjolley.yp...@gmail.com, 
sangeeta.j...@intel.com




A build flagged for QA (yocto-2.7.1.rc1) was completed on the autobuilder and 
is available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.7.1.rc1


Build hash information:
bitbake: 34ed28a412af642a993642c14bd8b95d5ef22cd8
meta-gplv2: 460ba027fd79b99151f95c826446f3aead5d17ff
meta-intel: e84c763090f91196a5d234f62ee39bcf296c7f2e
meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
oecore: 886deb4d0919c7a81036ea14fb8fd0f1619dd3a3
poky: 38d5c8ea98cfa49825c473eba8984c12edf062be



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: 
richard.pur...@linuxfoundation.org
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto