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 L
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
--
___
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
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/pe
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 --g
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
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 o
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
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
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 rebu
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@y
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
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,
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
14 matches
Mail list logo
