Hi all, This is the weekly test report for Yocto 20110423 build. All meta-intel BSP build are failed on autobuilder. A new boot up failure bug is found on both routerstationpro and

I think that is a fantastic idea, it gets my vote. gitorious++ -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

This is one simple patch to fix seg fault of evolution-data-server, when new contact is added for new created DB. The root cause is simple: do_create (bf, XIMIAN_VCARD,....) would

Op 27 apr 2011, om 05:00 heeft Darren Hart het volgende geschreven: Have you though about setting up a gitorious instance on git.yocto? Regards, Koen

Well, sort of. The personal trees would be writable only by their owner. Otherwise you would have to manage all the user authentication. I forgot about the new meta-intel contributors. I would

Yeah, that's what you and I do already. But we now have people coming online who will be be continually pushing changes to their bsps in meta-intel and we don't necessarily want to give them write

I believe so. Bruce and I can use kernel.org for now. Tom and I can use personal branches in meta-intel. But I'd like to see a solution here before we see widespread use of kernel.org and github to

I think these are two distinct but overlapping problems: 1) place to share on the common core (poky, linux-yocto*) 2) place to share new stuff that may not amount to anything For #1, the *-contrib

My thinking (I guess - I didn't really think that much about it at the time) when requesting the meta-intel-contrib repo was that repos that could expect to get continual contributions from many

I also think this is a good idea, but can we wait until we get things transitioned to the new server and stabilized before adding new things right now? Sau!

Right. I just pushed meta-boottime to my kernel.org account as well. I'd much rather have that be: git://git.yoctoproject.org/dvhart/meta-boottime.git -- Darren Hart Intel Open Source Technology

Only a 2nd vote for something like this. I've had a need for this on several occasions, and often I'd like to get something out, and then slot it into a more "official" location later. My

git.yoctoproject.org hosts a number of different repositories, some of which host limited user contributions (such as poky-contrib). These repositories are setup and administered by a yoctoproject.org

So the kernel guys agree that menuconfig should used everywhere. Surprise, Surprise. ;-) -- Darren -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

And I'd add another +1 to that. Bruce

All, Here are the notes from the Yocto Technical Team meeting on April 26th. Let me know if you have any changes or corrections. Thanks. - Julie Attendees: Beth, Darren, Tom, Joshua, Julie, Dave,

Yocto Technical Team, We will meet again on Tuesday, April 26th at 8am Pacific. Details are below: Dial in information: Tuesday, April 26, 2011, 08:00 AM US Pacific Time 916-356-2663, Bridge: 1,

In case anyone cares, the "per-recipe based staging" used in OE-lite, and proposed as a future design concept for OE-core (although clearly not going to be used in OE-core anytime soon) is also task

http://www.flickr.com/photos/davest/sets/72157626431159625/ Fresh back from vacation, thought I would upload a fewphotos from the week. Will write a blog entry at some point, including

Input we got from the ELC talk suggested that people did think it would be intuitive and useful to expand the kernel menuconfig 'UI' down to all the other packages in the image. I've used UIs