[yocto] [poky][PATCH] kernel.bbclass: Fix kernel size checking
From 4d542a5a37210b4fc8c8e894554a75ba6b9be0af Mon Sep 17 00:00:00 2001
From: Jaap de Jong
Date: Fri, 15 Dec 2017 08:58:09 +0100
Subject: [poky][PATCH] kernel.bbclass: Fix kernel size checking
To: yocto@yoctoproject.org
---
meta/classes/kernel.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 7ef4f47..f41c3e4 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -601,12 +601,12 @@ do_sizecheck() {
if [ ! -z "${KERNEL_IMAGE_MAXSIZE}" ]; then
invalid=`echo ${KERNEL_IMAGE_MAXSIZE} | sed 's/[0-9]//g'`
if [ -n "$invalid" ]; then
- die "Invalid KERNEL_IMAGE_MAXSIZE: ${KERNEL_IMAGE_MAXSIZE}, should
be an integerx (The unit is Kbytes)"
+ die "Invalid KERNEL_IMAGE_MAXSIZE: ${KERNEL_IMAGE_MAXSIZE}, should
be an integer (The unit is Kbytes)"
fi
for type in ${KERNEL_IMAGETYPES} ; do
size=`du -ks ${B}/${KERNEL_OUTPUT_DIR}/$type | awk
'{print $1}'`
if [ $size -ge ${KERNEL_IMAGE_MAXSIZE} ]; then
-warn "This kernel $type (size=$size(K) >
${KERNEL_IMAGE_MAXSIZE}(K)) is too big for your device. Please reduce
the size of the kernel by making more of it modular."
+die "This kernel $type (size=$size(K) > ${KERNEL_IMAGE_MAXSIZE}(K))
is too big for your device. Please reduce the size of the kernel by
making more of it modular."
fi
done
fi
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [poky][PATCH] kernel.bbclass: Fix kernel size checking
On Fri, Dec 15, 2017 at 9:16 AM, Jaap de Jong wrote:
> From 4d542a5a37210b4fc8c8e894554a75ba6b9be0af Mon Sep 17 00:00:00 2001
> From: Jaap de Jong
> Date: Fri, 15 Dec 2017 08:58:09 +0100
> Subject: [poky][PATCH] kernel.bbclass: Fix kernel size checking
> To: yocto@yoctoproject.org
>
> ---
> meta/classes/kernel.bbclass | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 7ef4f47..f41c3e4 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -601,12 +601,12 @@ do_sizecheck() {
> if [ ! -z "${KERNEL_IMAGE_MAXSIZE}" ]; then
> invalid=`echo ${KERNEL_IMAGE_MAXSIZE} | sed 's/[0-9]//g'`
> if [ -n "$invalid" ]; then
> - die "Invalid KERNEL_IMAGE_MAXSIZE:
> ${KERNEL_IMAGE_MAXSIZE}, should be an integerx (The unit is Kbytes)"
> + die "Invalid KERNEL_IMAGE_MAXSIZE:
> ${KERNEL_IMAGE_MAXSIZE}, should be an integer (The unit is Kbytes)"
> fi
> for type in ${KERNEL_IMAGETYPES} ; do
> size=`du -ks ${B}/${KERNEL_OUTPUT_DIR}/$type | awk
> '{print $1}'`
> if [ $size -ge ${KERNEL_IMAGE_MAXSIZE} ]; then
> - warn "This kernel $type (size=$size(K) >
> ${KERNEL_IMAGE_MAXSIZE}(K)) is too big for your device. Please reduce the
> size of the kernel by making more of it modular."
> + die "This kernel $type (size=$size(K) >
> ${KERNEL_IMAGE_MAXSIZE}(K)) is too big for your device. Please reduce the
> size of the kernel by making more of it modular."
> fi
> done
> fi
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
Hi,
there has been a discussion about do_sizecheck and there is already a
pending patch:
http://lists.openembedded.org/pipermail/openembedded-core/2017-December/145376.html
thanks
Andrea
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] error executing python function in linux-raspberrypi-dev
On Fri, Dec 15, 2017 at 5:00 AM, Sherif Omran wrote: > By testing the latest update of meta-raspberry pi with the Rocko or the > morty branch, i get ERROR executing a python function in code (see > attachment). > Please send error messages in plain text not as an image. The image doesn't show the full output as well, we'd need to also see the earlier bitbake output including the build configuration to determine what's gone wrong here. -- Paul Barker Togán Labs Ltd -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [poky][PATCH] kernel.bbclass: Fix kernel size checking
there has been a discussion about do_sizecheck and there is already a pending patch: http://lists.openembedded.org/pipermail/openembedded-core/2017-December/145376.html Ah! Apologies, totally missed that one -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-2.5_M1.rc1 now available.
A release candidate build for yocto-2.5_M1.rc1 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.5_M1.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 0f266744f7d542a960a78226af35403f871ba5a6 meta-qt4 : f313dbee2ac3d5fcc9801407947d3cb6cfb90b5d refkit : f24883b7d360de3eed89badce4b7fdaf7d6492c1 meta-mingw : a2c5fb82e5595d5bb56b579b7c93147c4fb065a5 meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f meta-gplv2 : c7f97f199a6dd54d3f369f0465a6bfd2cfa739b9 poky : b73e96e7f3f5d1ba3a221d99792a7a3c7ef42c21 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: joshua.g.l...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] CROPS status?
+ joshua. I am no longer working on the YP, but Joshua is looking after CROPS. It is actually a family of containers, so some parts have been updated more recently. -brian On 12/13/17, 10:26 AM, "Martin Kelly" wrote: Hi, I recently discovered the CROPS project at https://github.com/crops/crops. It looks like a great idea, but I see it hasn't had a commit since June 23, 2016. Is the project still active? Thanks, Martin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] xmlsec1: fix invalid paths in target xmlsec1Conf.sh
Remove build host paths from target xmlsec1Conf.sh script.
Signed-off-by: Catalin Enache
Signed-off-by: Ovidiu Panait
---
recipes-security/xmlsec1/xmlsec1_1.2.24.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-security/xmlsec1/xmlsec1_1.2.24.bb
b/recipes-security/xmlsec1/xmlsec1_1.2.24.bb
index 9798ce2..1f7fbd3 100644
--- a/recipes-security/xmlsec1/xmlsec1_1.2.24.bb
+++ b/recipes-security/xmlsec1/xmlsec1_1.2.24.bb
@@ -46,6 +46,7 @@ do_compile_ptest () {
do_install_append() {
sed -i -e "s@${STAGING_DIR_HOST}@@g" ${D}${bindir}/xmlsec1-config
+sed -e "s@${STAGING_DIR_HOST}@@g" -i ${D}${libdir}/xmlsec1Conf.sh
}
do_install_ptest () {
--
2.10.2
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-2.2.3.rc2 now available.
A release candidate build for yocto-2.2.3.rc2 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.2.3.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-intel : c781510a5a6b45e60cc32b6614ddcce3f1452121 meta-qt4 : f389368dc86e745df14cab9eeb9a94bc02bd273e refkit : f24883b7d360de3eed89badce4b7fdaf7d6492c1 meta-mingw : 58dda8440c1943c15ee750eb40f0fc651e316f51 meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f meta-gplv2 : c7f97f199a6dd54d3f369f0465a6bfd2cfa739b9 poky : e6626951501cdf8c5516ad42fd585894f19c2327 \nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: git://git.yoctoproject.org/yocto-autobuilder\nEmail: joshua.g.l...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail
On Thu, 2017-12-14 at 06:31 +0100, Zoran Stojsavljevic wrote:
> > Also is worth noting that I'm running Fedora 27 which wasn't tested...
>
> You should start from here your investigation, since you are on not tested
> YOCTO host distribution. And Fedoras are
> different from release to release, certainly!
>
> So either you should downgrade your fedora 27 to 26 (which I doubt it is
> possible), better to build brand new Fedora 26 using exactly the same
> packages.
Oh no, don't downgrade your distro. :-)
Docker is your friend for a repeatable and tested Yocto build environment
(In Fedora of course systemd-nspawn and other esoteric choices may exist).
We usually use & recommend easy-build project [1] (except for the CI system
build agents that needed a little bit more, and when I set that up I was
also more accustomed with using phusion/baseimage docker image over standard
Ubuntu).
If you find anything lacking, I'm sure it will accept pull requests - just
fork & extend in the meantime. Honestly, it's quite trivial for anyone to
reproduce such Docker files, but Gianpaolo set up a structure and a project
here. IMHO, we just need ANY canonical source for a base distro with an
official list of yocto/poky required packages ready to go, so why not use
this one & support it with any needed update?
HTH
- Gunnar
[1] https://github.com/gmacario/easy-build
--
Gunnar Andersson
Development Lead
GENIVI Alliance
> Here is a bit of help: to port all the packages to fresh installed Fedora
> 26, use the following command to retrieve
> packages from Fedora 27: rpm -qa --qf "%{name}.%{arch}\n" > packages-
> list.txt
>
> Zoran
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified
On 12/14/2017 06:38 PM, Alexander Kanavin wrote: Got it, thanks. I just sent the patches to yocto@ ML and published them on github - please do try them out, and rebase your patchset on top (some of it may no longer be relevant). I did the rebase myself, and pushed the result here - please check and feel free to add anything else that you deem useful: http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/log/?h=devel Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Using a poky recipe's files in a custom recipe
The current Poky I'm using (krogoth) has a recipe for dropbear, but I want to upgrade to use the latest version of dropbear. For source control reasons, I don't want to modify what's in meta/recipes-core/dropbear and therefore want to have my own recipe in my own layer. Yet for cleanliness I'd also prefer not to have to replicate all its .inc file etc in my own layer. Is there a clean way to be able to include meta's files within my own recipe? Is it a case of some sort of FILESEXTRAPATHS entry, and what would be the best way to cross reference to the poky layer? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using a poky recipe's files in a custom recipe
On 12/15/2017 08:36 AM, colin.helliw...@ln-systems.com wrote: > The current Poky I'm using (krogoth) has a recipe for dropbear, but I want > to upgrade to use the latest version of dropbear. > For source control reasons, I don't want to modify what's in > meta/recipes-core/dropbear and therefore want to have my own recipe in my > own layer. Yet for cleanliness I'd also prefer not to have to replicate all > its .inc file etc in my own layer. > Is there a clean way to be able to include meta's files within my own > recipe? Is it a case of some sort of FILESEXTRAPATHS entry, and what would > be the best way to cross reference to the poky layer? > I'm thinking if you require recipes-core/dropbear/dropbear.inc it uses BBPATH to search for the inc file, so it will pick up the one in meta. Philip -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Using a poky recipe's files in a custom recipe
> On 15 December 2017 at 14:35 Philip Balister wrote: > > > On 12/15/2017 08:36 AM, colin.helliw...@ln-systems.com wrote: > > The current Poky I'm using (krogoth) has a recipe for dropbear, but I want > > to upgrade to use the latest version of dropbear. > > For source control reasons, I don't want to modify what's in > > meta/recipes-core/dropbear and therefore want to have my own recipe in my > > own layer. Yet for cleanliness I'd also prefer not to have to replicate all > > its .inc file etc in my own layer. > > Is there a clean way to be able to include meta's files within my own > > recipe? Is it a case of some sort of FILESEXTRAPATHS entry, and what would > > be the best way to cross reference to the poky layer? > > I'm thinking if you > > require recipes-core/dropbear/dropbear.inc > > it uses BBPATH to search for the inc file, so it will pick up the one in > meta. > Excellent. Many thanks, Philip - that's got it. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail
As I told before, by pass this is a simple matter of running devshell,
creating the folder and running running the build again,
Paul ask me for more information and so I did, I'll remove that duplicated
layer and fire `bitbake -fc cleanall linux-raspberry && bitbake
linux-rapsberry` again, if I hit this I may try some digging. I don't think
this has to do with Fedora version, anyway, sooner or latter this version
will be tested, so this same error may arise, and at that time we'll be
doing the same questions, so, why to wait?
Regards,
2017-12-15 11:09 GMT-02:00 Gunnar Andersson :
>
> On Thu, 2017-12-14 at 06:31 +0100, Zoran Stojsavljevic wrote:
> > > Also is worth noting that I'm running Fedora 27 which wasn't tested...
> >
> > You should start from here your investigation, since you are on not
> tested
> > YOCTO host distribution. And Fedoras are
> > different from release to release, certainly!
> >
> > So either you should downgrade your fedora 27 to 26 (which I doubt it is
> > possible), better to build brand new Fedora 26 using exactly the same
> > packages.
>
> Oh no, don't downgrade your distro. :-)
>
> Docker is your friend for a repeatable and tested Yocto build environment
> (In Fedora of course systemd-nspawn and other esoteric choices may exist).
>
> We usually use & recommend easy-build project [1] (except for the CI system
> build agents that needed a little bit more, and when I set that up I was
> also more accustomed with using phusion/baseimage docker image over
> standard
> Ubuntu).
>
> If you find anything lacking, I'm sure it will accept pull requests - just
> fork & extend in the meantime. Honestly, it's quite trivial for anyone to
> reproduce such Docker files, but Gianpaolo set up a structure and a project
> here. IMHO, we just need ANY canonical source for a base distro with an
> official list of yocto/poky required packages ready to go, so why not use
> this one & support it with any needed update?
>
> HTH
> - Gunnar
>
> [1] https://github.com/gmacario/easy-build
>
> --
> Gunnar Andersson
> Development Lead
> GENIVI Alliance
>
>
> > Here is a bit of help: to port all the packages to fresh installed Fedora
> > 26, use the following command to retrieve
> > packages from Fedora 27: rpm -qa --qf "%{name}.%{arch}\n" > packages-
> > list.txt
> >
> > Zoran
> >
>
>
>
>
--
“If you're going to try, go all the way. Otherwise, don't even start. ..."
Charles Bukowski
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail
On Fri, 2017-12-15 at 12:50 -0200, Daniel. wrote: > As I told before, by pass this is a simple matter of running devshell, > creating the folder and running running the build again, > > Paul ask me for more information and so I did, I'll remove that duplicated > layer and fire `bitbake -fc cleanall linux-raspberry && bitbake linux- > rapsberry` again, if I hit this I may try some digging. I don't think this > has to do with Fedora version, anyway, sooner or latter this version will > be tested, so this same error may arise, and at that time we'll be doing > the same questions, so, why to wait? Agreed! It would seem strange if it's a host problem, and even if it were, it's better to get to the bottom of it, so that the latest popular distros work as intended. I just reacted to Zoran's suggestion, with what I find to at least be a better alternative for controlling the build host. Good luck! - Gunnar > > Regards, -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] x11 and gstreamer compete on same display ?
Hello, I use yocto x11 distro, and it works well with various application including qt5. On trying to use gstreamer, it seems that it does not function OK, I first suspected that it only has to do with high resolution, but now it seems that various distortions happens only in low resolution. I suspect that x11 output compete with gstreamer output. I think that maybe most of embedded applications which use gstreamer probably used fb disro instead of x11 distro, and maybe that can explain why I did not find any information of this issue in internet. I also see that when I stop the gstreamer pipeline , then x11 always pop in. I tried to disable x11 with: systemctl set-default multi-user.target It seems to work find, but the xterm terminal show on the hdmi, and trying to kill it won't help. So, I guess that I better move to distro fb instead of distro x11. I would like to ask if my suspicion sound reasonable, and if both x11 and gstreamer compete on the same display ? I use yocto morti with imx6. Best Regards. Ran -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail
> I just reacted to Zoran's suggestion, with what I find to at least be a better alternative for controlling the build host. Gunnar, You (probably) did not read Martin's (Jansa) comment on my initial, and my reply. I already reverted my decision on downgrading Fedora and other distros. Zoran On Fri, Dec 15, 2017 at 3:55 PM, Gunnar Andersson wrote: > On Fri, 2017-12-15 at 12:50 -0200, Daniel. wrote: > > As I told before, by pass this is a simple matter of running devshell, > > creating the folder and running running the build again, > > > > Paul ask me for more information and so I did, I'll remove that > duplicated > > layer and fire `bitbake -fc cleanall linux-raspberry && bitbake linux- > > rapsberry` again, if I hit this I may try some digging. I don't think > this > > has to do with Fedora version, anyway, sooner or latter this version will > > be tested, so this same error may arise, and at that time we'll be doing > > the same questions, so, why to wait? > > Agreed! It would seem strange if it's a host problem, and even if it were, > it's better to get to the bottom of it, so that the latest popular distros > work as intended. I just reacted to Zoran's suggestion, with what I find > to > at least be a better alternative for controlling the build host. > > Good luck! > > - Gunnar > > > > > Regards, > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] error executing python function in linux-raspberrypi-dev
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
sherif@sherif-virtual-machine:~/yocto-rocko/poky/build$ bitbake
rpi-basic-image >a.txt
ERROR: /home/sherif/yocto/poky/meta-openembedded/meta-networking/
recipes-support/nis/ypbind-mt_1.38.bb: Error executing a python function in
:
The stack trace of python calls that resulted in this exception/failure was:
File: '', lineno: 13, function:
0009:__anon_35__home_sherif_yocto_rocko_poky_meta_classes_
devshell_bbclass(d)
0010:__anon_101__home_sherif_yocto_rocko_poky_meta_classes_
sstate_bbclass(d)
0011:__anon_20__home_sherif_yocto_rocko_poky_meta_classes_
blacklist_bbclass(d)
0012:__anon_154__home_sherif_yocto_rocko_poky_meta_classes_
siteinfo_bbclass(d)
*** 0013:__anon_31__home_sherif_yocto_poky_meta_openembedded_
meta_networking_recipes_support_nis_nis_inc(d)
0014:__anon_23__home_sherif_yocto_rocko_poky_meta_classes_
systemd_bbclass(d)
0015:__anon_81__home_sherif_yocto_rocko_poky_meta_classes_
update_rc_d_bbclass(d)
File:
'/home/sherif/yocto/poky/meta-openembedded/meta-networking/recipes-support/nis/nis.inc',
lineno: 29, function: __anon_31__home_sherif_yocto_
poky_meta_openembedded_meta_networking_recipes_support_nis_nis_inc
0025:# so force the package to be skipped here (this will cause a
0026:# 'nothing provides' error)
0027:python () {
0028:os = bb.data.getVar("TARGET_OS", d, 1)
*** 0029:if os == "linux-uclibc":
0030:raise bb.parse.SkipPackage("NIS functionality requires
rpcsvc/yp.h, uClibC does not provide this")
0031:}
Exception: AttributeError: module 'bb.data' has no attribute 'getVar'
ERROR: /home/sherif/yocto/poky/meta-openembedded/meta-networking/
recipes-support/nis/yp-tools_2.14.bb: Error executing a python function in
:
The stack trace of python calls that resulted in this exception/failure was:
File: '', lineno: 13, function:
0009:__anon_35__home_sherif_yocto_rocko_poky_meta_classes_
devshell_bbclass(d)
0010:__anon_101__home_sherif_yocto_rocko_poky_meta_classes_
sstate_bbclass(d)
0011:__anon_20__home_sherif_yocto_rocko_poky_meta_classes_
blacklist_bbclass(d)
0012:__anon_154__home_sherif_yocto_rocko_poky_meta_classes_
siteinfo_bbclass(d)
*** 0013:__anon_31__home_sherif_yocto_poky_meta_openembedded_
meta_networking_recipes_support_nis_nis_inc(d)
0014:__anon_23__home_sherif_yocto_rocko_poky_meta_classes_
systemd_bbclass(d)
File:
'/home/sherif/yocto/poky/meta-openembedded/meta-networking/recipes-support/nis/nis.inc',
lineno: 29, function: __anon_31__home_sherif_yocto_
poky_meta_openembedded_meta_networking_recipes_support_nis_nis_inc
0025:# so force the package to be skipped here (this will cause a
0026:# 'nothing provides' error)
0027:python () {
0028:os = bb.data.getVar("TARGET_OS", d, 1)
*** 0029:if os == "linux-uclibc":
0030:raise bb.parse.SkipPackage("NIS functionality requires
rpcsvc/yp.h, uClibC does not provide this")
0031:}
Exception: AttributeError: module 'bb.data' has no attribute 'getVar'
ERROR: Failed to parse recipe: /home/sherif/yocto/poky/meta-
openembedded/meta-networking/recipes-support/nis/ypbind-mt_1.38.bb
sherif@sherif-virtual-machine:~/yocto-rocko/poky/build$ ls
note that i am not mixing branches
On Fri, Dec 15, 2017 at 10:32 AM, Paul Barker wrote:
> On Fri, Dec 15, 2017 at 5:00 AM, Sherif Omran
> wrote:
> > By testing the latest update of meta-raspberry pi with the Rocko or the
> > morty branch, i get ERROR executing a python function in code (see
> > attachment).
> >
>
> Please send error messages in plain text not as an image. The image
> doesn't show the full output as well, we'd need to also see the
> earlier bitbake output including the build configuration to determine
> what's gone wrong here.
>
> --
> Paul Barker
> Togán Labs Ltd
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [layerindex-web][PATCH v3 0/1] update_layer.py: Save and show recipe dependencies
In v3, fix bug that breaks search if keyword doesn't match one or both of the dependency items. Add a note about how dependencies may very. Activate tooltips so we don't have to wait for them to show. Only display PACKAGECONFIG names. The following changes since commit a64bfed81b3827503ff825090f1fb4b94e1cd9bd: recipes.html: Require keyword for recipe search (2017-12-05 10:01:10 +1300) are available in the git repository at: git://git.yoctoproject.org/layerindex-web abrindle/dependencies http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=abrindle/dependencies Amanda Brindle (1): update_layer.py: Save and show recipe dependencies layerindex/admin.py| 20 ++- layerindex/migrations/0010_add_dependencies.py | 50 ++ layerindex/models.py | 24 + layerindex/update_layer.py | 38 layerindex/views.py| 17 - templates/layerindex/recipedetail.html | 41 + 6 files changed, 188 insertions(+), 2 deletions(-) create mode 100644 layerindex/migrations/0010_add_dependencies.py -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [layerindex-web][PATCH v3 1/1] update_layer.py: Save and show recipe dependencies
Added a model for the PACKAGECONFIG variable, which has a one to
many relationship with the Recipe model.
Added models for static build dependencies and dynamic build
dependenices, both of which have a many to many relationship with
the Recipe model.
These objects are created in update_layer.py and are displayed on the
Recipe detail page.
Added a depends search option for recipes, allowing users to search for
recipes based on the recipe's build dependencies.
Fixes [YOCTO #12129]
Fixes [YOCTO #11415]
Signed-off-by: Amanda Brindle
---
layerindex/admin.py| 20 ++-
layerindex/migrations/0010_add_dependencies.py | 50 ++
layerindex/models.py | 24 +
layerindex/update_layer.py | 38
layerindex/views.py| 17 -
templates/layerindex/recipedetail.html | 41 +
6 files changed, 188 insertions(+), 2 deletions(-)
create mode 100644 layerindex/migrations/0010_add_dependencies.py
diff --git a/layerindex/admin.py b/layerindex/admin.py
index a7d024b..ed0307c 100644
--- a/layerindex/admin.py
+++ b/layerindex/admin.py
@@ -89,12 +89,27 @@ class LayerUpdateAdmin(admin.ModelAdmin):
class RecipeAdmin(admin.ModelAdmin):
search_fields = ['filename', 'pn']
list_filter = ['layerbranch__layer__name', 'layerbranch__branch__name']
-readonly_fields = [fieldname for fieldname in
Recipe._meta.get_all_field_names() if fieldname not in
['recipefiledependency', 'classicrecipe']]
+readonly_fields = [fieldname for fieldname in
Recipe._meta.get_all_field_names() if fieldname not in
['recipefiledependency', 'classicrecipe', 'packageconfig']]
def has_add_permission(self, request, obj=None):
return False
def has_delete_permission(self, request, obj=None):
return False
+class PackageConfigAdmin(admin.ModelAdmin):
+search_fields = ['feature']
+list_display = ('feature',)
+ordering = ('feature',)
+
+class StaticBuildDepAdmin(admin.ModelAdmin):
+search_fields = ['name']
+list_display = ('name',)
+filter_horizontal = ('recipes',)
+
+class DynamicBuildDepAdmin(admin.ModelAdmin):
+search_fields = ['name']
+list_display = ('name',)
+filter_horizontal = ('package_configs',)
+
class ClassicRecipeAdmin(admin.ModelAdmin):
search_fields = ['filename', 'pn']
list_filter = ['layerbranch__layer__name', 'layerbranch__branch__name']
@@ -159,6 +174,9 @@ admin.site.register(LayerDependency, LayerDependencyAdmin)
admin.site.register(LayerNote, LayerNoteAdmin)
admin.site.register(Update, UpdateAdmin)
admin.site.register(LayerUpdate, LayerUpdateAdmin)
+admin.site.register(PackageConfig, PackageConfigAdmin)
+admin.site.register(StaticBuildDep, StaticBuildDepAdmin)
+admin.site.register(DynamicBuildDep, DynamicBuildDepAdmin)
admin.site.register(Recipe, RecipeAdmin)
admin.site.register(RecipeFileDependency)
admin.site.register(Machine, MachineAdmin)
diff --git a/layerindex/migrations/0010_add_dependencies.py
b/layerindex/migrations/0010_add_dependencies.py
new file mode 100644
index 000..16cd776
--- /dev/null
+++ b/layerindex/migrations/0010_add_dependencies.py
@@ -0,0 +1,50 @@
+# -*- coding: utf-8 -*-
+from __future__ import unicode_literals
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+
+dependencies = [
+('layerindex', '0009_layerbranch_collection'),
+]
+
+operations = [
+migrations.CreateModel(
+name='DynamicBuildDep',
+fields=[
+('id', models.AutoField(primary_key=True, serialize=False,
verbose_name='ID', auto_created=True)),
+('name', models.CharField(max_length=255)),
+],
+),
+migrations.CreateModel(
+name='PackageConfig',
+fields=[
+('id', models.AutoField(primary_key=True, serialize=False,
verbose_name='ID', auto_created=True)),
+('feature', models.CharField(max_length=255)),
+('with_option', models.CharField(max_length=255, blank=True)),
+('without_option', models.CharField(max_length=255,
blank=True)),
+('build_deps', models.CharField(max_length=255, blank=True)),
+('recipe', models.ForeignKey(to='layerindex.Recipe')),
+],
+),
+migrations.CreateModel(
+name='StaticBuildDep',
+fields=[
+('id', models.AutoField(primary_key=True, serialize=False,
verbose_name='ID', auto_created=True)),
+('name', models.CharField(max_length=255)),
+('recipes', models.ManyToManyField(to='layerindex.Recipe')),
+],
+),
+migrations.AddField(
+model_name='dynamicbuilddep',
+name='package_configs',
+field=models.ManyToManyField(to='layer
Re: [yocto] [meta-raspberrypi] error executing python function in linux-raspberrypi-dev
On Fri, Dec 15, 2017 at 11:24 AM, Sherif Omran wrote: > > note that i am not mixing branches Yes you are. You have somehow setup a rocko build (path ~/yocto-rocko/...), which is using recipes from the morty branch of meta-oe (/home/sherif/yocto/poky/meta-openembedded/meta-networking/recipes-support/nis/ypbind-mt_1.38.bb). -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
