Re: [yocto] QA notification for completed autobuilder build (yocto-3.0.rc2)

[Jain, Sangeeta]

Hello All,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.0.rc2.
We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
3. BSP-Qemu

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. MPC8315e-rdb
7. Beaglebone

ETA for completion is next Tuesday, October 15.


Thanks & Regards,
Sangeeta Jain


>-Original Message-
>From: pokybu...@fedora30-ty-2.yocto.io 
>Sent: Thursday, October 10, 2019 12:11 PM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; richard.pur...@linuxfoundation.org;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
>
>Subject: QA notification for completed autobuilder build (yocto-3.0.rc2)
>
>
>A build flagged for QA (yocto-3.0.rc2) was completed on the autobuilder and is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-3.0.rc2
>
>
>Build hash information:
>
>bitbake: 5d83d828cacb58ccb7c464e799c85fd2d2a50ccc
>meta-gplv2: 9ca96786fd851150b518388bcb166efa0b4dfff9
>meta-intel: 13fcf624491cdd0d9b3eb78a4f0cd1781b482b51
>meta-mingw: 756963cc28ebc163df7d7f4b4ee004c18d3d3260
>oecore: 59938780e7e776d87146002ea939b185f8704408
>poky: 94f6b31befda5c496f65e863a6f8152b42d7ebf0
>
>
>
>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

[yocto] buildhistory revert

[Mauro Ziliani]

Hi all

I need to change the build number of a package.

That is: i have the package 
kernel-4.1.15-2.0.1_4.1.15-r0.*17*_armhf.deb, but in need to turn back 
to kernel-4.1.15-2.0.1_4.1.15-r0.*13*_armhf.deb



Can I setup manually the 17 value to 13?


Mauro

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

Re: [yocto] Where to get kconfig-frontends package?

[Peter Kjellerstedt]

I have been in contact with Yann E Morin, the maintainer of the 
kconfig-frontends repository, and it turns out his server did not survive their 
last move of house. However, he pointed out that he has published the code to 
GitLab and recommended to use that repository instead: 
https://gitlab.com/ymorin/kconfig-frontends

I will send a patch to the openembedded-devel list to update the recipe to use 
the GitLab repository.

//Peter

From: yocto-boun...@yoctoproject.org  On Behalf 
Of Matouš Pokorný
Sent: den 26 september 2019 14:02
To: yocto@yoctoproject.org
Subject: [yocto] Where to get kconfig-frontends package?

Hello!

I come from NuttX RTOS project (nuttx.org), and we use 
Kconfig tool for configuration. The toolchain build script gets 
kconfig-frontends source code from the same server as Yocto 
(http://ymorin.is-a-geek.org). The server is down 
for approx. one week and it caused the fail during the toolchain building. Have 
you met this problem as well? We would like to switch to another more reliable 
repository, but I read, the server's owner is one of the Linux core developers. 
So the server is a kind of primary source. Do you have a suggestion on how to 
solve this problem? I would like to ask you for help because you know the Linux 
ecosystem and are in the same situation as we are.

Thank you.

Matous Pokorny
Embedded System Developer

DataVision s.r.o.
Ukrajinska 2a
101 00 Praha 10
Czech Republic

GSM: (+420) 723 280 471
matous.poko...@datavision.cz
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH 1/2] apparmor: add PRIVATE_LIBS for ptest package

[Alexander Kanavin]

Otherwise, the following occurs:
ERROR: apparmor-2.13.3-r0 do_package: apparmor: Multiple shlib providers for 
libapparmor.so.1: apparmor, apparmor-ptest (used by files: 
/home/alexander/development/poky/build-metaoe/tmp/work/core2-32-poky-linux/apparmor/2.13.3-r0/packages-split/apparmor/usr/lib/perl5/vendor_perl/5.30.0/i686-linux/auto/LibAppArmor/LibAppArmor.so)
ERROR: apparmor-2.13.3-r0 do_package: apparmor: Multiple shlib providers for 
libapparmor.so.1: apparmor, apparmor-ptest (used by files: 
/home/alexander/development/poky/build-metaoe/tmp/work/core2-32-poky-linux/apparmor/2.13.3-r0/packages-split/apparmor/usr/lib/python3.7/site-packages/LibAppArmor/_LibAppArmor.cpython-37m-i686-linux-gnu.so)

Signed-off-by: Alexander Kanavin 
---
 recipes-mac/AppArmor/apparmor_2.13.3.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb 
b/recipes-mac/AppArmor/apparmor_2.13.3.bb
index 2e5d221..990d870 100644
--- a/recipes-mac/AppArmor/apparmor_2.13.3.bb
+++ b/recipes-mac/AppArmor/apparmor_2.13.3.bb
@@ -165,3 +165,5 @@ RDEPENDS_${PN} += "bash"
 RDEPENDS_${PN} += "${@bb.utils.contains('PACKAGECONFIG','python','python3-core 
python3-modules','', d)}"
 RDEPENDS_${PN}_remove += 
"${@bb.utils.contains('PACKAGECONFIG','perl','','perl', d)}"
 RDEPENDS_${PN}-ptest += "perl coreutils dbus-lib bash"
+
+PRIVATE_LIBS_${PN}-ptest = "libapparmor.so*"
-- 
2.17.1

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

[yocto] [meta-security][PATCH 2/2] apparmor: make bash dependency optional

[Alexander Kanavin]

Bash is only needed by one not particularly important script,
so not requiring bash is a useful option for builds that
cannot have gpl3 components.

Signed-off-by: Alexander Kanavin 
---
 recipes-mac/AppArmor/apparmor_2.13.3.bb | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb 
b/recipes-mac/AppArmor/apparmor_2.13.3.bb
index 990d870..6183064 100644
--- a/recipes-mac/AppArmor/apparmor_2.13.3.bb
+++ b/recipes-mac/AppArmor/apparmor_2.13.3.bb
@@ -32,11 +32,12 @@ PARALLEL_MAKE = ""
 
 inherit pkgconfig autotools-brokensep update-rc.d python3native perlnative 
ptest cpan manpages systemd
 
-PACKAGECONFIG ??= "python perl"
+PACKAGECONFIG ??= "python perl aa-decode"
 PACKAGECONFIG[manpages] = "--enable-man-pages, --disable-man-pages"
 PACKAGECONFIG[python] = "--with-python, --without-python, python3 swig-native"
 PACKAGECONFIG[perl] = "--with-perl, --without-perl, perl perl-native 
swig-native"
 PACKAGECONFIG[apache2] = ",,apache2,"
+PACKAGECONFIG[aa-decode] = ",,,bash"
 
 PAMLIB="${@bb.utils.contains('DISTRO_FEATURES', 'pam', '1', '0', d)}"
 HTTPD="${@bb.utils.contains('PACKAGECONFIG', 'apache2', '1', '0', d)}"
@@ -97,6 +98,10 @@ do_install () {
rm -f ${D}${sbindir}/aa-notify
fi
 
+   if ! ${@bb.utils.contains('PACKAGECONFIG','aa-decode','true','false', 
d)}; then
+   rm -f ${D}${sbindir}/aa-decode
+   fi
+
if test -z "${HTTPD}" ; then
oe_runmake -C ${B}/changehat/mod_apparmor DESTDIR="${D}" install
fi
@@ -161,7 +166,6 @@ PACKAGES += "mod-${PN}"
 FILES_${PN} += "/lib/apparmor/ ${sysconfdir}/apparmor 
${PYTHON_SITEPACKAGES_DIR}"
 FILES_mod-${PN} = "${libdir}/apache2/modules/*"
 
-RDEPENDS_${PN} += "bash"
 RDEPENDS_${PN} += "${@bb.utils.contains('PACKAGECONFIG','python','python3-core 
python3-modules','', d)}"
 RDEPENDS_${PN}_remove += 
"${@bb.utils.contains('PACKAGECONFIG','perl','','perl', d)}"
 RDEPENDS_${PN}-ptest += "perl coreutils dbus-lib bash"
-- 
2.17.1

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

Re: [yocto] QA notification for completed autobuilder build (yocto-3.0.rc2)

[richard . purdie]

On Thu, 2019-10-10 at 07:37 +, Jain, Sangeeta wrote:
> Hello All,
> 
> Intel and WR YP QA is planning for QA execution for YP build yocto-
> 3.0.rc2.
> We are planning to execute following tests for this cycle:
> 
> OEQA-manual tests for following module:
> 1. OE-Core
> 2. BSP-hw
> 3. BSP-Qemu
> 
> Runtime auto test for following platforms:
> 1. MinnowTurbot 32-bit
> 2. Coffee Lake
> 3. NUC 7
> 4. NUC 6
> 5. Edgerouter
> 6. MPC8315e-rdb
> 7. Beaglebone
> 
> ETA for completion is next Tuesday, October 15.

Thanks Sangeeta!

There were some failures in the build, specifically the build
performance results didn't merge to the repo correct and an oe-selftest 
failed.

I fixed the performance results manually and pushed them. The oe-
selftest in the reproducibility test is a known issue with perl from
the host system.

I don't believe either issue should affect the release.

Cheers,

Richard



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

Re: [yocto] buildhistory revert

[Yann Dirson]

The PR server takes care not to reuse those versions.
Apart from making sure your recipe's signature matches the one for
0.13, you probably can't (assuming you don't want to mess with your
PR's database).


2019-10-10 10:27 UTC+02:00, Mauro Ziliani :
> Hi all
>
> I need to change the build number of a package.
>
> That is: i have the package
> kernel-4.1.15-2.0.1_4.1.15-r0.*17*_armhf.deb, but in need to turn back
> to kernel-4.1.15-2.0.1_4.1.15-r0.*13*_armhf.deb
>
>
> Can I setup manually the 17 value to 13?
>
>
> Mauro
>
>


-- 
Yann Dirson 
Blade / Shadow -- http://shadow.tech
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] buildhistory revert

[Mauro Ziliani]

I find the solution.

I know that I have not modified the packages rebuilded (i.e the kernel)

So I see in prserv.sqlite3.

The table PRMAIN_nohist contains the history of buildhistory for each 
pkg/recipe.


I deleted the  line which the field value i bigger or equal the value I need

The package kernel-4.1.15-2.0.1_4.1.15-r0.17_armhf.deb is built from 
recipe linux-imx


Inside PRMAIN_nohist table there a record with the field "value=18".

I make this from sqlite3 tool

DELETE FROM PRMAIN_nohist WHERE version LIKE 'linux-imx-%' AND value>=13

I rebuild the linux-imx with bitbake linux-imx and magically the package 
kernel-4.1.15-2.0.1_4.1.15-r0.13_armhf.deb is build.



MZ


Il 10/10/19 14:40, Yann Dirson ha scritto:

The PR server takes care not to reuse those versions.
Apart from making sure your recipe's signature matches the one for
0.13, you probably can't (assuming you don't want to mess with your
PR's database).


2019-10-10 10:27 UTC+02:00, Mauro Ziliani :

Hi all

I need to change the build number of a package.

That is: i have the package
kernel-4.1.15-2.0.1_4.1.15-r0.*17*_armhf.deb, but in need to turn back
to kernel-4.1.15-2.0.1_4.1.15-r0.*13*_armhf.deb


Can I setup manually the 17 value to 13?


Mauro




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

[yocto] Force do_package_index

[Mauro Ziliani]

Goodmorning.

How to force the execuction o do_package_index over an image recipe?


MZ

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

Re: [yocto] buildhistory revert

[Yann Dirson]

If you see a spurious rebuild, you should investigate with
bitbake-diffsigs, rather that trying to outsmart the build system,
else you're likely to shoot yourself in the foot :)

2019-10-10 17:32 UTC+02:00, Mauro Ziliani :
> I find the solution.
>
> I know that I have not modified the packages rebuilded (i.e the kernel)
>
> So I see in prserv.sqlite3.
>
> The table PRMAIN_nohist contains the history of buildhistory for each
> pkg/recipe.
>
> I deleted the  line which the field value i bigger or equal the value I
> need
>
> The package kernel-4.1.15-2.0.1_4.1.15-r0.17_armhf.deb is built from
> recipe linux-imx
>
> Inside PRMAIN_nohist table there a record with the field "value=18".
>
> I make this from sqlite3 tool
>
> DELETE FROM PRMAIN_nohist WHERE version LIKE 'linux-imx-%' AND value>=13
>
> I rebuild the linux-imx with bitbake linux-imx and magically the package
> kernel-4.1.15-2.0.1_4.1.15-r0.13_armhf.deb is build.
>
>
> MZ
>
>
> Il 10/10/19 14:40, Yann Dirson ha scritto:
>> The PR server takes care not to reuse those versions.
>> Apart from making sure your recipe's signature matches the one for
>> 0.13, you probably can't (assuming you don't want to mess with your
>> PR's database).
>>
>>
>> 2019-10-10 10:27 UTC+02:00, Mauro Ziliani :
>>> Hi all
>>>
>>> I need to change the build number of a package.
>>>
>>> That is: i have the package
>>> kernel-4.1.15-2.0.1_4.1.15-r0.*17*_armhf.deb, but in need to turn back
>>> to kernel-4.1.15-2.0.1_4.1.15-r0.*13*_armhf.deb
>>>
>>>
>>> Can I setup manually the 17 value to 13?
>>>
>>>
>>> Mauro
>>>
>>>
>>
>


-- 
Yann Dirson 
Blade / Shadow -- http://shadow.tech
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Force do_package_index

[Ross Burton]

On 10/10/2019 16:35, Mauro Ziliani wrote:

How to force the execuction o do_package_index over an image recipe?


Are you intending to use the deploy directory as a package feed? 
"bitbake package-index" for that.


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

Re: [yocto] Force do_package_index

[Mauro Ziliani]

I use the deploy/deb as Debian repository for internal upgrade.

So I export over an internal ftp the 4 folders under tmp/deply/deb, and 
I integrate package-management with package_deb.


I need to restore the old buildhistory, because I rebuild some package 
but I have not change anything.



I try bitbake package-index, maybe is what I need


Thanks


Mauro



Il 10/10/19 18:45, Ross Burton ha scritto:

On 10/10/2019 16:35, Mauro Ziliani wrote:

How to force the execuction o do_package_index over an image recipe?


Are you intending to use the deploy directory as a package feed? 
"bitbake package-index" for that.


Ross

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

Re: [yocto] [meta-openssl102-fips][PATCH] README.build/image.inc: add missing openssl-fips to image

[Mark Hatle]

merged.

--Mark

On 10/9/19 3:28 AM, Hongxu Jia wrote:
> For Yocto and WRLinux, openssl fips works only if installing
> package openssl-fips
> 
> Signed-off-by: Hongxu Jia 
> ---
>  README.build | 1 +
>  templates/feature/openssl-fips/image.inc | 1 +
>  2 files changed, 2 insertions(+)
>  create mode 100644 templates/feature/openssl-fips/image.inc
> 
> diff --git a/README.build b/README.build
> index c6e..50bd9a5 100644
> --- a/README.build
> +++ b/README.build
> @@ -132,6 +132,7 @@ Building Steps (based on section 4 of the 
> UsersGuide-2.0.pdf):
>  prebuilt tar archive.
>  
>  For Yocto, in your build directory, edit conf/local.conf, add:
> +  IMAGE_INSTALL_append = " openssl-fips"
>OPENSSL_FIPS_ENABLED = "1"
>OPENSSL_FIPS_PREBUILT = ""
>  
> diff --git a/templates/feature/openssl-fips/image.inc 
> b/templates/feature/openssl-fips/image.inc
> new file mode 100644
> index 000..0d62e44
> --- /dev/null
> +++ b/templates/feature/openssl-fips/image.inc
> @@ -0,0 +1 @@
> +IMAGE_INSTALL += "openssl-fips"
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] fix typo: openssl-fips -> openssl-fips-dev

[Hongxu Jia]

The working fips package is openssl-fips-dev rather than openssl-fips.

Signed-off-by: Hongxu Jia 
---
 README.build | 2 +-
 templates/feature/openssl-fips/image.inc | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.build b/README.build
index 50bd9a5..b4e8f2e 100644
--- a/README.build
+++ b/README.build
@@ -132,7 +132,7 @@ Building Steps (based on section 4 of the 
UsersGuide-2.0.pdf):
 prebuilt tar archive.
 
 For Yocto, in your build directory, edit conf/local.conf, add:
-  IMAGE_INSTALL_append = " openssl-fips"
+  IMAGE_INSTALL_append = " openssl-fips-dev"
   OPENSSL_FIPS_ENABLED = "1"
   OPENSSL_FIPS_PREBUILT = ""
 
diff --git a/templates/feature/openssl-fips/image.inc 
b/templates/feature/openssl-fips/image.inc
index 0d62e44..3616432 100644
--- a/templates/feature/openssl-fips/image.inc
+++ b/templates/feature/openssl-fips/image.inc
@@ -1 +1 @@
-IMAGE_INSTALL += "openssl-fips"
+IMAGE_INSTALL += "openssl-fips-dev"
-- 
2.7.4

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