[01:52] <carlhako> i am testing alpha6 now, 8.04 would not even boot on this machine, e8500 p5qc
[03:30] <nullack> ARG - I cant only get xchat-gnome working but running it in valgrind
[03:30] <nullack> I might do a clean reinstall
[06:08] <_Zeus_> how can i be a tester for intrepid?
[06:08] <_Zeus_> or can i not
[06:09] <persia> _Zeus_: Well, at a base level, just download it, install, and use.
[06:09] <_Zeus_> http://mozilla.qa.ubuntu.com/qatracker/
[06:09] <_Zeus_> i don't see any line for intrepid
[06:09] <_Zeus_> anyway, i'll just dl it, that's fine
[06:09] <_Zeus_> it's probably better that i keep the testing versions seperately, anyway
[06:10] <persia> There's no special use-case based testing for intrepid mozilla.  Might make sense for there to be, but I think that the presumption is that most of the bugs will be found by general intrepid testing, rather than targeted testing.
[06:10] <persia> I could be mistaken, but I believe the mozilla team is usually hunting for regressions for stable updates.
[06:13] <sbeattie> _Zeus_: we'll be doing a specific day of testing for Intrepid generally this coming monday http://ubuntutesting.wordpress.com/2008/09/17/announcing-ubuntu-testing-day/
[06:17] <persia> Of course, if you've more time today, or this weekend, that's good too :)
[07:19] <ara> morning all :)
[07:19] <ara> did anyone tested alpha-6 installation in a virtualbox client?
[07:23] <sbeattie> hmm, I didn't and I don'tthink bdmurray did
[07:39] <persia> _MMA_ tested Ubuntu Studio Alpha-6 in a virtualbox client.  Given the similarity to Ubuntu Destkop, I would expect similar results.
[07:40] <persia> Note that this was the alternate installer, so it may be there is some undiscovered interaction with ubiquity.
[08:17] <ara> persia, sbeattie: i am installing now alternate alpha 6 in vbox. it seems to go smoothly :-)
[08:18] <nullack> sbeattie: The new multimedia test case page looks good, thanks
[08:18] <nullack> Evening ara :)
[08:18] <persia> ara: Have you tried live?  I'm sure alternate works, but I've not heard of a live test.
[08:18] <ara> morning nullack ;-)
[08:18] <nullack> persia : I built live current this morning no problems - AMD64
[08:18] <ara> persia: not yet, will do afterwords
[08:19] <persia> nullack: In virtualbox?
[08:19] <nullack> persia : No mate, sorry, it was direct
[08:20] <persia> nullack: That got a fair bit of testing :)  It was just realised ~1 hr ago that the only reported virtualbox installs were Ubuntu Studio alternate 32-bit, which is a fairly small sample.
[08:20] <ara> persia: trying now live under virtualbox. will let you know
[08:21] <persia> ara: No need to let me know.  I'm just adding data in hopes of reducing the number of tests you feel obliged to perform :)
[08:21] <ara> persia: sure. thanks ;-)
[08:21] <persia> I wonder if we oughtn't add something to the test report system though: to differentiate HW installs, KVM installs, virtualbox installs, etc.
[08:22] <nullack> persia I was making the point to Heno how important input data and prerequisite conditions are - I think what your saying is a very valid point along those lines
[08:22] <ara> persia: yes, I think that would be helpful
[08:22] <nullack> persia : Also being able to see the "map" of coverage too to easily spot gaps
[08:23] <nullack> persia : One of the problems in testing is getting lost in the test cases and when you dont have numbered requirements it gets trickier to do test traceability
[08:23] <persia> nullack: While I don't disagree with you, I'm fond of the gradual approach.  We have significantly greater organisation to our test coverage now than we once did, but it's far too easy to get lost in looking at some future point, and not make the small improvements that can get us there.
[08:24] <nullack> Id figure that any effort to number requirements for Ubuntu would be very very large :)
[08:24] <nullack> persia : chipping away at it has my full support :)
[08:25] <persia> Along the lines you mention, one suggestion that was presented to me previously would be to better track and associate a path from brainstorm ideas -> specifications -> test cases.  Unfortunately, this is incredibly tricky because of the relatively small influence that Ubuntu developers have on the overall product (which I consider a good thing: upstream work belongs upstream).
[08:26] <persia> (and yes, there are a fair number of Ubuntu developers who are also upstreams of one sort or another)
[08:27] <nullack> persia : good insight there, I think youre dead right.
[08:28] <nullack> Do you know Kent Beck? His approach on the famous GM project was that the spec was the source code! LOL But it worked
[08:28] <nullack> A kinda new twist to agile development methods
[08:29] <persia> That sort of model can work for targeted development, but it's less ideal for distro coordination.  Anyway, I think we're drifting away from the -testing topic.  Feel free to follow up on -quality.
[08:30] <davmor2> Morning Everybody :)
[08:30] <ara> morning davmor2 :-)
[08:30] <ara> FYI: live i386 works fine in virtualbox
[08:30] <nullack> Ello davmor2
[08:33] <davmor2> slangasek: You still about?
[08:41] <starkmjolk> alpha 6 i see :) have no x access for another hour
[08:42] <starkmjolk> what would be equivalent to update-manager -d from a terminal or should I just wait? :)
[08:43] <nullack> I dunno what -d does but I use sudo apt-get update && sudo apt-get upgrade
[08:43] <nullack> Noting to hit main instead of a mirror so Im not left behind
[08:44] <starkmjolk> that's what the ubuntu wiki recommends i think. but if it runs samee repos that should work
[08:44] <persia> starkmjolk: `do-release-upgrade -d`
[08:45] <persia> starkmjolk: You may want `do-release-upgrade -d -m desktop` if you're only temporarily without X.
[08:45] <nullack> Are you actually trying to move from hardy to intrepid instead of just a repo synch?
[08:45] <starkmjolk> ah, thanks. that was the one i was looking for
[08:46] <starkmjolk> i'm just not at a client with x, the computer itself runs x just fine
[08:46] <starkmjolk> and i'm at alpha 5, thought i needed to upgrade like this to get alpha 6. but perhaps I don't?
[08:47] <starkmjolk> without x* :)
[08:47] <starkmjolk> early morning double negation. my bad, just ignore my spelling and gammar :)
[08:50] <persia> starkmjolk: No.  Just a simple apt-get update && apt-get upgrade ought work for you.
[08:51] <davmor2> if you're already on alpha 5 then persia is right just sudo apt-get update && apt-get upgrade
[08:52] <davmor2> in fact && apt-get dist-upgrade might be better
[08:52] <starkmjolk> I do the equivalent through aptitude every day, so I'm set then :)
[08:53] <starkmjolk> will the same be true for beta, or will i have to go for the do-release-upgrade then?
[08:54] <persia> starkmjolk: do-release-upgrade is only required when shifting from one release to another, and only if you don't shift right around the time the archives open.  It has hint handlers to help work around problems you might encounter with apt-get or aptitude.
[08:54] <persia> If you use aptitude to update every day, you're already running the Alpha-6 code.
[08:57] <starkmjolk> persia: got it that far, i guess my question was if the beta will be as a new release from my point of view?
[08:58] <persia> starkmjolk: Not so much.  Each candidate release (alphas, beta, rc) is really just a specific daily build that was tested to be sure that it can be installed as a fresh system, and isn't too painfully broken.
[09:03] <davmor2> persia: I like the optimism at the end of your last line didn't you mean to say that is stable ;)
[09:05] <persia> davmor2: Actually, specifically not.  It's guaranteed not to be stable as there will be uploads the next day, which may include all sorts of changes.
[09:06] <persia> The candidate snapshots are known to work, but they are inherently ephermal.
[09:06] <davmor2> persia: I was pulling your leg :)  I know really :D  uploads are just put on hold until the next respin I know :)
[09:08] <persia> Actually, even only some uploads are put off until the alpha is released, and we don't always do a good job of knowing which uploads might affect a given flavour (especially for the universe flavours).  The goal is to put off uploads long enough to test the candidates, but that's about it.
=== starkmjolk is now known as capn-starkmjolk
[11:50] <davmor2> ara: all the images are now up :)
[11:50] <ara> davmor2: cool :-)
[11:51] <davmor2> just need to copy across the text to display the image on screenshot page :)
=== davmor2 is now known as davmor2-away
[12:23] <salty-horse> hi. error in page? http://www.ubuntu.com/testing/ -- "Alpha 6 - Released September 518h, 2008" -- 518h?
[12:51] <heno> salty-horse: thanks, reported to the webmaster
[12:51] <salty-horse> thanks
[13:38] <asac> now that alpha 6 is out, qa must be quite idle and bored, right? :-P
[13:39] <asac> heno: ^^
[13:39] <asac> :)
[13:40] <heno> asac: what needs testing? :)
[13:40] <asac> i just wonder if we could do a bit of firefox testing today ... i am a bit slow and dont have all bits and branches together, but there are a few builds in my PPA that QA could help me on
[13:41] <asac> https://edge.launchpad.net/~asac/+archive
[13:41] <heno> asac: is it urgent? (is it SRU?)We have a major testing day on Monday where this would fit nicely
[13:41] <asac> 1.5.dfsg+1.5.0.15~prepatch080614e-0ubuntu1~asac1
[13:41] <asac> heno: well. its security update
[13:41] <heno> right
[13:41] <asac> release will happen next week
[13:42] <asac> between Tue or Thu ... but its always risky because some regressions might take more then an hour to fix
[13:43] <heno> ara, schwuk: do either of you have a dapper VM set up?
[13:48] <asac> heno: yes. dapper would be good enough for today. i would get a better feeling then ;)
[13:49] <asac> heno: for the testing day we should try to get a good coverage for hardy update of 3.0
[13:49] <asac> most likely people helping out can run hardy better anyway
[13:50] <heno> davmor2: do you have a dapper setup; could you look at asac's testing request above?
[13:50] <heno> (a firefox security update)
[13:51] <heno> I guess not :)
[13:51] <schwuk> heno: no, sorry.
[13:56] <davmor2-away> heno: yes I'll have a look now
=== davmor2-away is now known as davmor2
[13:56] <heno> davmor2: rock!
[13:59] <davmor2> Yes dapper I got.
[13:59] <davmor2> about half hour-ish is that okay :)
[14:31] <davmor2> asac: dapper image doesn't want to play so I'm installing fresh should take too long
[14:33] <asac> thanks for the update
[14:35] <heno> ara, davmor2: do we really need an Attachments sub-page for each App page on the testcase wiki? Can we not simply put all the screenshots on the app page itself?
[14:35] <heno> That would be many fewer pages in searches and listings and shorter links
[14:36] <davmor2> heno: I just followed ara's request but I'm easy I can swap it round to a single page easy enough
[14:37] <heno> davmor2: just asking - when we're setting this up we should try to make the structure as clean as possible
[14:38] <heno> I'm happy to move them to new locations FWIW
[14:39] <davmor2> heno: I got np's setting up a single screenshot page as we had with Ubuntu.  I've already got all the shots still so it's easy to upload them again.
[14:40] <heno> ok, cool. I'll noodle a bit more on the structure and wait for ara's input too
[14:43] <davmor2> it'll take a little while to run through them all if I can have about an hour or so to upload them all
[14:43] <davmor2> I think that should be enough
[14:45] <davmor2> asac: Right dapper up updating do I need to enable anything repo wise?
[14:46] <asac> davmor2: my archive
[14:46] <asac> davmor2: and since thats aa PPA you most likely need dapper-updates too
[14:46] <asac> and -securiy
[14:47] <davmor2> okay no probs
[14:47] <asac> davmor2: actually the final security builds will be build without -updates ... which is a bit unfortunate, but we dont have infrastructure to provide such public bits for now
[15:01] <davmor2> asac:  I enabled everything I could think of :) I'm guessing it's the 1.5dfsg+1.5.0.15~prepatch......asac1
[15:06] <davmor2> asac: http://www.davmor2.co.uk/Screenshot.png  is there anything else I should be looking at it for?
[15:09] <_Zeus_> If i add this to my sources.list :  deb http://ppa.launchpad.net/asac/ubuntu hardy main universe
[15:09] <_Zeus_> will i get all the testing updates?
[15:09] <_Zeus_> i'm in intrepid
[15:10] <davmor2> _Zeus_: Intrepid should already be on the most up-to-date version
[15:11] <_Zeus_> oh
[15:11] <_Zeus_> um yeah, about that
[15:11] <_Zeus_> mozilla wants testing for 3.0.1 and i'm already running 3.0.2
[15:12] <_Zeus_> can i still submit a test review?  or not
[15:12] <davmor2> Pass
[15:12] <_Zeus_> got it
[15:34] <heno> davmor2: see my mail. I'm going to play with the page structure a bit more before we settle on a template
[15:35] <davmor2> heno: have you spoken to ara at all?  Sound good mail just arrived :)
[15:40] <davmor2> heno: I like the resize on the fly :)
[15:41] <heno> davmor2: the quality is not perfect but I'm sure we can adjust that in moin somewhere
[15:42] <davmor2> heno: but then it wasn't great on the thumbnails either :0
[15:42] <davmor2> :) even
[16:37] <asac> davmor2: no ... does opening urls from command line work while ffox is running?
[16:37] <asac> davmor2: like firefox http://www.google.com
[16:37] <davmor2> asac 2 ticks
[16:47] <davmor2> asac: adds a google tab to the already open firefox
[16:49] <asac> davmor2: great
[16:49] <asac> well ... not so great. its broken in my development tree when i build that on intrepid
[16:50] <asac> but maybe i should try to build rotten old code on modern software ;)
[16:50] <asac> or maybe we have a patch in the package i didnt spot yet and thats just always broken for 1.5 (in checkouts)
[16:51] <davmor2> :)
[16:51]  * PrivateVoid_Ghos kicks PrivateVoid
=== PrivateVoid_Ghos is now known as PrivateVoid
[16:58] <davmor2> GoodBye Everybody
=== asac_ is now known as asac
[18:46] <slangasek> davmor2: no
[20:26] <broken> Heya, I have a strange problem... I powered on my computer today and it failed to load any graphic interaface, I hit a key on the keyboard and the Xserver poppped up with an error saying "module ABI major version(0) doesn't match servers version(1)" "Failed to load module "dri"(module requirement mismatch, 0)"
[20:27] <salty-horse> hi. at the end of an upgrade to intrepid I get a printout of the packages which had errors during processing, followed by:
[20:28] <salty-horse> http://pastebin.com/m50acd692
[20:29] <salty-horse> and now the upgrade says: A recovery will run now (dpkg --configure -a) -- is there any way to not recover, and try to fix the errors, if fatal, myself?
[20:33] <broken> I don't understand how this xorg file works now, I have only three sections "configured video device" how am I supposed to change the device?
[20:49] <salty-horse> this bug seems to break upgrades. should it really be marked as Low priority? https://bugs.launchpad.net/ubuntu/+source/rarian/+bug/256131
[20:49] <ubot5> Launchpad bug 256131 in rarian "package update-manager 1:0.93.3 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)" [Low,New]
[22:43] <Rocket2DMn> has anybody had an issue for Intrepid not letting itself go idle?  On my test laptop, the screen will start to dim, and as soon as the screen is about to go into standby, something happens and the screen rebrightens and doesnt idle