Re: [yocto] [autobuilder][PATCH 1/2] yocto-autobuilder2: add missing __init__.py to top level
On Sun, 2018-06-03 at 17:22 -0700, Armin Kuster wrote: > This fixes the import of modules when starting buildbot > as master.cfg has: > from yoctoabb import builders, config, schedulers, workers, services, > www > > Signed-off-by: Armin Kuster > --- > __init__.py | 0 > 1 file changed, 0 insertions(+), 0 deletions(-) > create mode 100644 __init__.py > > diff --git a/__init__.py b/__init__.py > new file mode 100644 > index 000..e69de29 I've merged the other patch (2/2). I've now realised this issue is due to the use of python2 when we've been testing with python3. Rather than trying to support both, I'd prefer to simply suggest people use python3 at this point. Fancy sending a patch to document this? :) It'd be useful to me to be cc'd on patches for the autobuilder stuff too if that isn't too much trouble as I sometimes don't get though all the mailing lists as often as I'd like. Cheers, Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Target CPU architectures that Yocto Project Support
Hi, Naive question from a newbie. How can this be achieved? I'd appreciate if you could please shed some light on what steps need to be followed? Thanks in advance, -R -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Target CPU architectures that Yocto Project Support
Hi Ricardo, If you are asking about the list of MACHINE types that Yocto Project supports, then the best place to look is in the Layer Index: https://layers.openembedded.org/layerindex/branch/master/layers/ Click on the “Machines” tab, click on the “Search” tab with or without a search value, and see the glorious list. The same goes for supported layers, recipes, classes, and distro values. You can change the “Branch” value to see the MACHINE’s per release. - David Reyna From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Ricardo Ramirez Sent: Sunday, June 10, 2018 5:07 PM To: yocto@yoctoproject.org Subject: Re: [yocto] Target CPU architectures that Yocto Project Support Hi, Naive question from a newbie. How can this be achieved? I'd appreciate if you could please shed some light on what steps need to be followed? Thanks in advance, -R -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Gratitude
Hi Jefro, I am very happy for you in your moving forward, thought I will very much miss your being part of our community. Thank you for all your years of work and guidance and enthusiasm, and thank you for your generous support of the team as a whole and myself in particular! I hope to get a chance to say hello next time I am in Portland (and if you end up in Canada, I am happy to meet up with you there as well :-). - David -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Khem Raj Sent: Wednesday, June 06, 2018 10:49 AM To: OSIER-MIXON, JEFFREY Cc: yocto@yoctoproject.org Subject: Re: [yocto] Gratitude Jefro you have been very helpful all along has been great working with you. Your contributions have been significant for project, thanks for all your contributions. Small world I am sure I will see you around :) -Khem On Tue, Jun 5, 2018 at 11:42 PM, Osier-mixon, Jeffrey wrote: > I have been the Yocto Project community manager for over 7 years now, and > have had the pleasure of knowing or conversing individually with several > hundred of you. It is with mixed feelings that I must announce that I am > stepping down from my position as the YP community manager and the Advisory > Board chair after 7 years, as I am taking on a new role in my job. > > I am very proud of the progress that the project has made, growing from a > small set of build tools into an industry standard for building and working > with embedded Linux-based operating systems, supporting upstream projects > including the Linux kernel, hosting projects like opkg, and inspiring many > very successful downstream projects, including AGL and OpenBMC among many > others, and also supporting countless configurations of hardware among seven > different architectures. We have also seen the community of users grow from > fewer than 1000 in 2010 to a large city-sized community, estimated in the > tens of thousands of developers. > > Please continue to participate, collaborate, and come together as a > community! The Yocto Project is a success because every one of you > participates. > > Jeffrey "Jefro" Osier-Mixon, Intel Corporation > Open Source Community Ecosystem Strategist > > > -- > ___ > 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 mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Target CPU architectures that Yocto Project Support
Hi David, Thanks for the prompt reply! My question was a follow up of Khem's inquire (posted on 2014-05-02) https://lists.yoctoproject.org/pipermail/yocto/2014-May/019387.html Using the links you sent me, I found that the old OE-Classic branch supports sparc32 but didn't see any sparc64 http://layers.openembedded.org/layerindex/oe-classic/recipes/ As such, I'd like to know what steps I need to follow in order to enable a SPARCv9 machine in Yocto. I appreciate your answer. -R On Sun, Jun 10, 2018 at 7:17 PM, Reyna, David wrote: > Hi Ricardo, > > > > If you are asking about the list of MACHINE types that Yocto Project > supports, then the best place to look is in the Layer Index: > > > >https://layers.openembedded.org/layerindex/branch/master/layers/ > > > > Click on the “Machines” tab, click on the “Search” tab with or without a > search value, and see the glorious list. > > > > The same goes for supported layers, recipes, classes, and distro values. > > > > You can change the “Branch” value to see the MACHINE’s per release. > > > > - David Reyna > > > > *From:* yocto-boun...@yoctoproject.org [mailto:yocto-bounces@ > yoctoproject.org] *On Behalf Of *Ricardo Ramirez > *Sent:* Sunday, June 10, 2018 5:07 PM > *To:* yocto@yoctoproject.org > *Subject:* Re: [yocto] Target CPU architectures that Yocto Project Support > > > > Hi, > > > > Naive question from a newbie. How can this be achieved? I'd appreciate if > you could please shed some light on what steps need to be followed? > > > > Thanks in advance, > > > > -R > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Recipe reporting system] Upgradable recipe name list
This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable" You can check the detail information at: http://recipes.yoctoproject.org/ Package Version Upstream version Maintainer NoUpgradeReason --- -- usbutils 009 010 Alexander Kanavin ca-certificates 20170717 20180409 Alexander Kanavin vala 0.40.4 0.40.6Alexander Kanavin procps3.3.14 3.3.15Alexander Kanavin psmisc23.0 23.1 Alexander Kanavin sysprof 3.26.1 3.28.1Alexander Kanavin Waiting for resolution of h... systemtap-uprobes 3.2 3.3 Alexander Kanavin systemtap 3.2 3.3 Alexander Kanavin cantarell-fonts 0.0.24 0.0.25Alexander Kanavin epiphany 3.28.1.1 3.28.3.1 Alexander Kanavin apt 1.2.24 1.6.1 Aníbal Limón apt-native1.2.24 1.6.1 Aníbal Limón dpkg 1.18.24 1.19.0.5 Aníbal Limón gstreamer1.0-plug... 1.14.0 1.14.1Anuj Mittal gst-validate 1.14.0 1.14.1Anuj Mittal gstreamer1.0-rtsp... 1.14.0 1.14.1Anuj Mittal gstreamer1.0-libav1.14.0 1.14.1Anuj Mittal gstreamer1.0-omx 1.14.0 1.14.1Anuj Mittal gstreamer1.0 1.14.0 1.14.1Anuj Mittal gstreamer1.0-vaapi1.14.0 1.14.1Anuj Mittal gst-examples 0.0.1+gitX 0.0.1-new-commits... Anuj Mittal gstreamer1.0-python 1.14.0 1.14.1Anuj Mittal gstreamer1.0-plug... 1.14.0 1.14.1Anuj Mittal gstreamer1.0-plug... 1.14.0 1.14.1Anuj Mittal gstreamer1.0-plug... 1.14.0 1.14.1Anuj Mittal xkbcomp 1.4.11.4.2 Armin Kuster xf86-input-evdev 2.10.5 2.10.6Armin Kuster xf86-video-fbdev 0.4.40.5.0 Armin Kuster xf86-video-vmware 13.2.1 13.3.0Armin Kuster busybox 1.27.2 1.28.4Armin Kuster xkeyboard-config 2.23.1 2.24 Armin Kuster nss 3.36.1 3.37.1Armin Kuster bind 9.10.6 9.13.0Armin Kuster xserver-xorg 1.19.6 1.20.0Armin Kuster xf86-input-synaptics 1.9.01.9.1 Armin Kuster linux-libc-headers4.15.7 4.17 Bruce Ashfield kern-tools-native 0.2+gitX 0.2-new-commits-a... Bruce Ashfield linux-yocto 4.15.13+gitX 4.15.18 Bruce Ashfield linux-yocto-rt4.15.13+gitX 4.15.18 Bruce Ashfield linux-yocto-tiny 4.15.13+gitX 4.15.18 Bruce Ashfield kmscube git git-new-commits-a... Carlos Rafael Giani connman 1.35 1.36 Changhyeok Bae iproute2 4.16.0 4.17.0Changhyeok Bae base-passwd 3.5.29 3.5.45Chang Rebecca Swe... Version 3.5.38 requires cde... lsbinitscripts9.79 9.82 Chang Rebecca Swe... sysvinit 2.88dsf 2.89 Chang Rebecca Swe... systemd-boot 237 238 Chen Qi cups 2.2.62.2.8 Chen Qi systemd 237 238 Chen Qi bison 3.0.43.0.5 Chen Qi sed 4.2.24.5 Chen Qi sysstat 11.7.3 11.7.4Chen Qi flex 2.6.02.6.4 Chen Qi lzop 1.03 1.04 Denys Dmytriyenko xz5.2.35.2.4 Denys Dmytriyenko mtd-utils 2.0.1+X 2.0.2 Denys Dmytriyenko python3-dbus 1.2.61.2.8
[yocto] [PATCH] [yocto-autobuilder2] Fixes on schedulers default build-appliance
From: Aaron Chan --- schedulers.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schedulers.py b/schedulers.py index 8f3dbc5..02e4340 100644 --- a/schedulers.py +++ b/schedulers.py @@ -63,7 +63,7 @@ def props_for_builder(builder): props.append(util.BooleanParameter( name="deploy_artifacts", label="Do we want to deploy artifacts? ", -default=Boolean +default=False )) props = props + repos_for_builder(builder) -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
