I've looked over the changes and spent this afternoon testing them, I believe they are appropriate for the 0.9 release. Cheers, Joshua -- Joshua Lock Intel Open Source Technology Centre

I'm so predictable... :-) Yes, I'm nervous. I looked at all of the patches and with the exception of one or two, they mostly seem like good ones. I will accept these if Josh/Mark/Saul give us a +1 on

I think my build just has some stale data that the various cleans haven't cleared. I'm going to try some clean builds today. -- Darren Hart Embedded Linux Kernel

Coming up to release there are a few things that the extended testing has shown up which we have fixes for and which we should consider including in the release. I also finally got around to doing the

Hmm, I've commits to fix both of those issues in meta-demo master since at least yesterday morning.b Cool! Already done I'll take this AR I'll take this AR too I'll handle the Rygel and gupnp-av-cp

Bug 468 needs confirmation by someone in PRC with the HP Mini netbook. I've verified the other 4 I opened. -- Darren Hart Embedded Linux Kernel

If noarch is universally used in RPM word, I think we should use it. Sounds reasonable. After all, zypper is only intended to be a frontend utility to the lower end package tool. Then we won't need

Zypper also does something similar: defCompatibleWith(_armv5tejl, _noarch,_armv3l,_armv4l,_armv4tl,_armv5l,_armv5tel); Yes, only a small part. And the way I prefer is to add an alias in

This is a good start. I don't know if this is the place to add it, but I just wanted to capture the details of what I've done so far to get my setup working. For now mainly in case anyone else could

RP, Yes. The original reporter is responsible for bug verification. Please do it as more as possible. Do we need to close (verify) all fixed bugs before 0.9 release? QA can help to close the old

boards list used in this demo. Also a simple figure is always more intuitive to catch the intention here. :-) One thought is, could we convert this demo page into something more useful as the

I think this is already done - I have it on my image and it works for me. eth0 on the rygel image seems to come up ok, it's just the mediatomb image that doesn't afaics. I'll probably look into this

Media Network Demo ================== We're looking to have a section on the web site for the demo that explains what each use-case is and possibly how it can be replicated. I'm taking the approach of

I build mediatomb and rygel live atom-pc images from today's poky/master + meta-demo/master. I booted mediatomb on the BlackSand and rygel on the netbook. I had to manually start the rygel renderer on

Attending: Paul, Davest, Dirk, Richard, Saul, Alex, Mark,Jessica, Bruce, Darren Goal: Review the release criteria and make a clear decisionto see that we're ready to release. Summary: Launch

Video is a nice to have, but not required for the UK demo. -- Darren Hart Embedded Linux Kernel

poky-image-nas should work on any hardware -- just keep in mind that by default it serves everything over "eth1". Update the config files in meta-demo/images/poky-image-nas/* to point to eth0 (or

We will need to do some additional verification on RPM -- but it appears to me that RPM should not have a problem with this. As far as I'm aware, RPM5 simply ignores the ARCH field for the most part.

We can certainly look into translating "all" to "noarch" post 0.9. That might make it easier for people coming from the RPM world, to understand what is in the package. This is a bug in Zypper. The

Nice - thanks Tom and Josh Sent from my Blackberry