Folks, We have forked M2 off to builds/milestone now and master is open again for M3 integration. M2 will take specific and targeted changes for stability and critical bug fixing. Master is

Thanks Saul for working out this list. I am a bit surprised on the large number of to-be-upgraded list: 160, because according to our plan, we actually upgrade most of the recipes in M2, and only a

Hi, Jessica Another thing is that after we bitbake the tarball, since bitbake will help us to do_unpack, so untar opkg is not needed actually. After bitbake job is finished, I will change the

Hi, Jessica I have updated the scripts. If a qemu file has been downloaded before, It will prompt user download the new or keep the old one. Any problem, just let me know. They're in the same

Hi, Jessica Sure. I will change it and send you the updated patch a little later. criping

Ke, Liping wrote: It's our current design, the thinking is no matter what rootfs (minimal, sato, sdk or lsb), very likely user needs to use some sort of package management system to add and remove

Hi, Jessica I have tested newly added image types (sato minimal) in the user configuration file. One known thing is: for extracting root fs, currently our code/configuration logic is: Only one

I'm kind of surprised when seeing this data, as I thought we have upgraded more than 110 recipes. Then distro team gathered just now to understand whether there's anything mismatch. The major point

Hi Saul, I've fixed and resubmitted the patch. Sorry for not following the patch submission convention. Best Regards, -Lianhao Saul Wold wrote on 2010-12-14: Best Regards, Lianhao

Folks, As we get ready for M3 opening up shortly, I wanted to get folks aware of where we are with M2 and the recipe updating process. Based on my rough reckoning, we had about 266 recipes that

Hi all, This is the Sanity Test Report for M2 20101211 build. QA finished sanity+weekly test cases. Toolchain testing and qemuppc testing is blocked because there is no image built out. There

Hi, all, I start looking into our LTP failures now and get some cursory picture. ( http://bugzilla.pokylinux.org/show_bug.cgi?id=169 ) I tried qemux86 sato image from latest M2 build, and there're

Liping, The newly update scripts are at: http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=jzhang/installer_ne w With following changes: more messages cleanup, fix issues: 1) download all the

Hi, Jessica I have checked in the changes based on your changeset. Now nfs extraction folders could be deleted/operated by user. And also, the config file is changed since the version number now is

OK. It's caused because you changed 0.9-post to 0.9+snapshot. The version is now defined in the yocto_installer.conf. Also, for solving the user priviledge problem, I will change user nfs root owner

Liping, All my changes are captured under: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jzhang/installer My installation stopped at: ./yocto_installer_internal: line

Hi, Scott Thanks for the review! Sure, I will use the script following distro-team conventions. And also, $MYNAME will be used in the final patch. And the debug line for building will be removed

One final thing - when you resubmit your patch this time, could you use the create-pull-request/send-pull-request scripts? That way the patch can be pulled in by Richard or Saul with minimal effort,

Thanks for the patch, Criping. This patch includes the addition of a do_configure_prepend step for the libxfixes recipe? That looks like some debugging info crept in that may not have been

We are pleased to announce some new resources on the Yocto Project. When you build a custom Linux distribution for your device using the Yocto Project, you can also build an Application Development