[07:34] <ara> morning all!
[11:35] <mvo> jibel: just fyi http://people.canonical.com/~mvo/automatic-upgrade-testing/2010-08-30-10:24:20-stable/
[11:35] <mvo> jibel: currently only ubuntu -> ubuntu and not easy to find
[11:36] <mvo> ie. you need to check blueprints.edge.launchpad.net/ubuntu/+spec/foundations-maverick-buy-something
[11:37] <ara> mvo, great!
[11:37] <mvo> I will work on making it a big easy to find
[11:38] <mvo> jibel: I mean, you need to look at the overview http://people.canonical.com/~mvo/automatic-upgrade-testing/ to find the latest currently, but I will add a link for this
[11:39] <mvo> so that http://people.canonical.com/~mvo/automatic-upgrade-testing/current-stable will work
[11:45] <yofel> any estimate when the amd64 daily isos will build again?
[12:42] <jibel> mvo, many thanks, that's great. Once everything is set up, do you think I could add the profiles for the server images and persistent devices ?
[12:43] <mvo> jibel: server should be no problem, I'm not sure what it takes for the persistant devices
[12:43] <jibel> mvo, another question, is there a way to access the term.log and dpkg.log of the upgrade and the dpkg.log
[12:47] <mvo> jibel: does it give you permission errors?
[12:48] <mvo> jibel: dpkg.log can be arranged
[12:48] <jibel> mvo, 404
[12:53] <persia> yofel, Soonish.  I hear the issue has been discovered, and is in process of being fixed.
[12:56] <mvo> jibel: thanks, fixing that
[13:02] <jibel> ara, I added the test case http://testcases.qa.ubuntu.com/Upgrade/DesktopWhole to cover the desktop upgrades to -updates.
[13:03] <ara> jibel, awesome, thanks!
[13:03] <jibel> ara, is it you who review it ? Also I'm not sure about the naming conventions.
[13:04] <ara> jibel, anyone in the QA community can review it, but I'll review this one
[13:04] <jibel> I'm not satisfied with DesktopWhole but I can't rename the page. DesktopUpgrades would probably have been a bit better.
[14:14] <mvo> jibel: apt-term.log should be reable now
[14:15] <jibel> mvo, it works! thank you.
[14:16] <jibel> mvo, is auto-upgrade-tester supposed to work locally or do I need to create an image before running it ? I get a disk0.qcow not found error
[14:16] <mvo> yw
[14:17] <mvo> jibel: its suppoed to be able to create it for you, however it looks like ubuntu-vm-builder now outputs a random filename for the qcow image - that is rather odd and seems to be what breaks it :/
[14:17] <jibel> mvo, That's what I was suspecting. I'll have a look at it and let you know.
[15:32] <alourie> ara: I saw you fixed double linking to instructions :-) thanks
[15:32] <alourie> that definitely improves usability
[15:32] <ara> alourie, thanks for reporting!
[15:33] <alourie> ara: it's nothing :-)
[15:33] <alourie> fixing is more important
[15:55] <Zil_> hi
[15:56] <Zil_> i'm inquiring about nouveau 3d drivers progress
[15:56] <Zil_> i'm willing to use them with netbook 10.10
[16:00] <fader_> Zil_: You might have better luck asking in #ubuntu+1 -- this channel is used for coordinating testing efforts and creating tests
[16:01] <Zil_> ok thx
[16:01] <fader_> Zil_: Unless you have specific testing related questions (in which case the Ubuntu QA mailing list might be better, as I think everybody here is focused on testing the beta ISO images now :) )