From: Tom Zanussi <tom.zanussi@...> Most of the time, we want a -live image, so add it to the IMAGE_FSTYPES by default. Signed-off-by: Tom Zanussi <tom.zanussi@...> ---

From: Tom Zanussi <tom.zanussi@...> These are all now handled or obsoleted by tune-atom.inc, so remove them here. --- meta-fishriver/conf/machine/fishriver.conf | 2 -- 1 files changed, 0

From: Tom Zanussi <tom.zanussi@...> A few updates for meta-fishriver dealing with the new tune file and live image changes. This also moves the kernel to 3.0. Boot tested successfully with

Hi all, There is no BLOCK issue with this build. QA will continue fullpass testing with it, if there is no new build. Best Regards, Jiajun

Hi All, This is the weekly test report for Yocto 1.1 M3 RC3 20110806 build. There is one new bug found. RPM package can not be installed on qemuarm and beagleboard. Some lsb images build

Hi all, Last week is for M3 stabilization. The new-submit vs. fixed bug is 43 vs. 42. Open bug number increased to 178. WDD number increased to 921. Bug status of WW32 could be found on

I found the correct location in the autobuilder, but it seems that the sstate-cache is bad and should be removed, I thought we where removing sstate before starting a nightly? The bad sets

Look at http://autobuilder.yoctoproject.org/nightly/CURRENT/sstate-cache That is the saved sstate for that build. Is this also what is occurring during the meta-intel builds? -- Elizabeth

I was thinking about this point over the weekend, and I realized that it may not have been clear that I'm talking largely about the kernel here. Not all the associated userspace/config, etc that we'd

I am still working on reproducing this one, might be autobuilder related as my local autobuilder build seems to be OK right now. I have 2 sets of sstate for fstests, which may mean that something is

Folks, We currently have 3 failures on the RC3 build for M3. They are all related to LSB builds. If you are on the TO: line please review your issues as we need a prompt fix. 1348: Qt3 Fails to

Song, Thanks for pointing the white board info out. 684 is med enhancement, in general, people should focus on bug fixing. Enhancements will be pushed out for post 1.1 unless people has no

Jessica, the following 2 bugs have comments in the whiteboard asking not to include them in 1.1 or lower the priority to low. I’m not sure if you guys missed those or do not agree with the owners.

<richard.purdie@...> wrote: And -u depexp is a nice wrapper around it too. If you want to get at what's going to be installed on the target however, I think you'll need to poke it a

bitbake -g will dump out a task-depends.dot file which shows which tasks will run and the task interdependencies... Cheers, Richard

Is there some command to get the set of packages that will be attempted to be built? - k

Agenda:   1. Opens collection - 5 min (Song) 2. M3 release criteria review - 15 min (team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria 3. M4 plan & schedule - 15 min (Song)

Darren's the right person to give a proper summary, since he was driving our beagleboard work. But he's out on Jury duty at the moment, so we'll have to wait. I can attempt a quick summary here. The

Would you mind re-summarizing the discussion? I know there has been a lot of back and forth, and it seems like a summary would be helpful for people who stopped following the discussion. It is very

I'm hoping to not repeat all the discussions that we've had around the beagle board here. Anything that applies to that applies here. This is a reference BSP done by the Wind River folks on top of