[08:31] <davmor2> Morning Everybody
[08:41] <ara> morning davmor2!
[08:42] <davmor2> ara: how goes the scripting?
[08:44] <ara> davmor2: we are getting some results now. I am going to publish alpha-3 results sometime this morning. scripts are very basic, but the framework is being built strong :-)
[08:44] <ara> I will let you know where you can have a look to the reports when done
[08:45] <davmor2> Cool :)  Congrats
[08:48] <ara> rebooting and/or shutdown in alpha-3 just logs out... that is annoying
[08:49] <davmor2> ara: I know the bug is reported it should be fixed shortly.  In which case you may want to re-run against the updated version.
[08:49] <ara> can you point me to the bug report number, so i can subscribe?
[08:59] <davmor2> ara: two ticks
[08:59] <davmor2> https://bugs.launchpad.net/bugs/250506
[08:59] <davmor2> ara: ^
[09:08] <ara> ok, thanks davmor
[10:58] <davmor2> morning nand how's things?
[11:13] <nand> davmor2: good morning!
[11:13] <nand> well, a bit overheated morning over there :)
[11:30] <ara> can anyone try to add a new page into wiki.ubuntu.com?
[11:31] <ara> I am getting a python error when i try
[11:37] <davmor2> ara: what page do you want?
[11:37] <ara> any
[11:38] <ara> some other users are having the same issue
[11:40] <davmor2> your right problem occurred in python script
[12:46] <jpds> ara, davmor2: The sysadmins claim to have fixed it, try again.
[12:49] <davmor2> ara: jpds: Seems to work now :)
[13:21] <cr3_> schwuk: ping, I haven't touched base with you in a while. whatcha working on these days?
[13:24] <cr3_> schwuk: by the way, I don't know if I mentionned this but I have an oops manager to report errors from the website now. it stores zip files capturing lots of information about the state of the error, so it is a bit clumsy to use right now, but an interface or command-line tools could be built eventually
[13:26] <cr3_> schwuk: which reminds me, I have a branch of yours to merge for which i got side-tracked because of the CASCADE thing. I'll try to have a look at it today
[13:58] <schwuk> cr3_: Working on a few different things, mainly documentation related (hwtest, testcases, tool comparisions). All will bear fruit soon.
[13:58] <schwuk> oops manager sounds good. Will it send out notifications, or do we need go look?
[13:59] <schwuk> I'd forgotten to chase you about that branch. I should have just gone ahead and merged it, but we wanted to see how Launchpad helped (or hindered) us with reviews.
[14:00] <schwuk> cr3_: Whilst I'm thinking about it, have you made any progress with plugins extending/enhancing the UI?
[14:00] <cr3_> schwuk: no notifications yet, just zip files being stored in some directory on the filesystem
[14:01] <schwuk> cr3_: Do I have access to the production server? I seem to recall that I don't.
[14:10] <cr3_> schwuk: nope, I've given precedence to enhancing hwtest so that derivations can more readily extend the base.
[14:11] <cr3_> schwuk: one cool new feature is that configuration parameters can now be changed from the command line. a bit cryptic but very useful
[14:11] <cr3_> for example: hwtest -c "hwtest/plugins/blacklist=manual_prompt"
[14:12]  * schwuk wonders how "cryptic" blends with "more readily extends the base"
[14:12] <schwuk> cr3_: looks interesting
[14:13] <cr3_> schwuk: it's just possible to do things that weren't possible before, but at the cost of some complexity
[14:13] <cr3_> this is all hidden from the enduser, of course, and will be well documented anyhow :)
[14:14] <schwuk> cr3_: It will :)
[14:15] <cr3_> schwuk: some of the things that are now possible: the --delay option can now be implemented as a plugin, rather than hard coded in the core; it is also now possible to optionally run hwtest at boot by using another plugin
[14:16] <cr3_> schwuk: and, when running hwtest at boot, it is furthermore possible to blacklist the manual tests so that everything can be run automatically
[14:16] <schwuk> cr3_: nice
[14:16] <stgraber> cool
[14:17] <schwuk> cr3_: So how long until it's on the LiveCD ? :)
[14:18] <schwuk> cr3_: How about the rename? Any outcome from your mails?
[14:43] <cr3_> schwuk: nice coincidence that you ask, I followed with kiko about the renaming this morning
[14:43] <cr3_> schwuk: I've also had a nice discussion with seb128 about the propery way to notify the user for running tests
[14:44] <cr3_> schwuk: one of the thorny problems I need to solve now is: where the heck does the tool submit information, launchpad and/or certification?
[14:45] <cr3_> schwuk: realistically, posting to certification will be required and to launchpad optional
[14:46] <schwuk> cr3_: Here's my take. The Hardware Testing variant (ubuntu-test-hardware or u-t-l) should post to Launchpad. Every other variant (u-t-qa, u-t-compatability etc. posts to c3.
[14:46] <cr3_> schwuk: I wanted to make the launchpad schema extensible and reviewed on Monday, before the update, but shit hit the fan which prevented me from getting work done online
[14:46] <cr3_> schwuk: "should", indeed, but "can't" as it currently stands
[14:47] <cr3_> schwuk: oh wait, just u-t-l, I agree
[14:47] <cr3_> schwuk: however, in the furture, I would like to see all variants post to Launchpad
[14:48] <schwuk> cr3_: You'd have got nowhere anyway - LP is/was in lockdown for 2.0. Any new changes (even just the schema) will be probably 6-8 weeks before going live at the moment.
[14:48] <cr3_> schwuk: I discussed this with heno and the plan is to continue trail blazing on the certification/qa websites during intrepid, learning from our mistakes. during that time, we should collaborate with Launchpad and perhaps have our code reviewed by them with the objective of later merging. after intrepid, we could then spend some time merging certification functionality into launchpad.
[14:49] <schwuk> Seems sensible
[14:49] <cr3_> schwuk: flacoste told me that Monday before 4pm couldn't made it at the finishing line :)
[14:49] <cr3_> err, could've
[14:50] <schwuk> That goes against the bugfix only mantra that's been chanted for a while, but that's their problem.
[14:50] <cr3_> schwuk: there are so many components missing in Launchpad for merging though, and I'm not sure how many of them will be accepted, this will require further discussions. for example, Launchpad doesn't have the concept of ISO images nor of tests.
[14:51] <schwuk> cr3_: If we get the schema right, then I agree that everything should go through Launchpad as soon as it can.
[14:51] <cr3_> so, if Launchpad only provides us with a hardware database, that's such a negligeable part of the website, that I'll have to see how relevant this might be for qa testing
[14:51] <schwuk> cr3_: Perhaps we should setup a virtual mini-sprint around the schema?
[14:52] <cr3_> schwuk: worst case, the schema will be right and we'll essentially be slurping submissions from the LP librarian and nothing more
[14:52] <schwuk> cr3_: That's the way I see it until they incorporate functionality.
[14:53] <schwuk> cr3_: We can even abuse Launchpad and submit non-parsable (to them) data that we can use in our systems.
[14:53] <cr3_> schwuk: the problem is not "until they incorporate" as much as "will they incorporate", some things might simply not make sense in the context of LP
[14:53] <cr3_> schwuk: I think abel is/will be performing schema validation
[14:53] <schwuk> cr3_: So Launchpad should only really care about the validity of the data they're interested in, and ignore the rest
[14:53] <cr3_> schwuk: that would make sense, otherwise you just know I'd be submitting porn images to the hardware database
[14:54] <cr3_> schwuk: exactly
[14:54] <schwuk> cr3_: Yes, yes you would.
[14:54] <schwuk> But right now the schema is far to strict about what it expects
[14:54] <cr3_> it's not my fault though, the temptation to be rude is stronger than me :(
[14:55] <cr3_> schwuk: right, and I can't tell for sure what we'll need a month from now, so something generally extensible would be nice.
[14:55] <schwuk> cr3_: Even if they are performing schema validation, they will just ignore our 'wrong' data.
[14:56] <schwuk> cr3_: which is why it should be inclusive, not exclusive
[14:56] <cr3_> schwuk: another alternative, which would simply put more responsibility on us, would be to submit part of the data to LP and another part of the data to c3. I'm already shaking my head at the idea :(
[14:56] <schwuk> No. Bad idea.
[14:56] <cr3_> right, I just want to make sure I have all insane ideas on the table to get a sense of direction
[15:38] <ara> heno: thanks for triaging the gksu bug :-)
[15:53] <stgraber> ogasawara: http://80.83.51.125/qapkgstatus/openoffice.org The categories are implemented, still need a better CSS though
[16:00] <ara> bdmurray: question about triaging. if a bug comes from a backport package, should it be treated with less importance?
[16:00] <ogasawara> stgraber: awesome, thanks!
[16:02] <bdmurray> ara: wow, I haven't actually seen one of those
[16:02] <ogasawara> stgraber: under the Totals section, it looks like the rate of change deltas are missing (should be the second column)
[16:03] <bdmurray> I'd say the same though
[16:03] <ogasawara> stgraber: ah, that's probably because of the <delta> to <metric> tag change that was made
[16:03] <stgraber> ogasawara: oops, right. Don't know what happens that bit was working fine yesterday :) I'll have a look
[16:04] <ara> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/253018
[16:04] <ara> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/252923
[16:04] <ara> those two come from the same backport version of pidgin
[16:05] <stgraber> ogasawara: hmm, weird it's working as expected locally but not on the test server ... so that's a Dapper-specific bug (the second I find today)
[16:05] <ogasawara> stgraber: ugh
[16:05] <stgraber> some missing php-xml functions I guess ...
[16:05] <bdmurray> ara: just as we have a proposed-pkg tag I'd suggest making at backport-pkg tag
[16:06] <ara> bdmurray: yes, that makes sense
[16:07] <bdmurray> then try and find out if there is a backports team to notify / subscribe to the bug
[16:08] <ogasawara> stgraber: but the categories part is cool :)
[16:09] <ogasawara> stgraber: also on the Intro page I noticed we overlapped a little in our text . . . "To learn more, choose a package from the menu.
[16:09] <ogasawara> Please choose a category then a package in the menu at the left of the page"
[16:09] <ogasawara> stgraber: I'd just get rid of that "To learn more . . . " line
[16:21] <stgraber> ogasawara: that should be fixed (both the deltas and the intro)
[16:22] <ogasawara> stgraber: looks great now
[16:27] <stgraber> ogasawara: and now you should also have the updated logo :)
[16:28] <ogasawara> stgraber: cool,  I was actually just using your redirect script and saw it there
[17:01] <davmor2> bdmurray: any idea why the screensaver keeps waking up?
[17:01] <davmor2> on intrepid?
[17:02] <davmor2> And what I should report it under?
[17:02] <bdmurray> davmor2: what do you mean waking up?
[17:04] <davmor2> I got ss set to blank screen on a default intrepid install.  Everytime the power manager kicks in and the screen goes blank 1-2 secs after it is back up onto the normal desktop again ?
[17:04] <davmor2> it's only happening on gnome too I think I'll just double check though
[17:05] <davmor2> yeah Kubuntu switches to blank screen and it stays blank
[17:55] <davmor2> evening heno :)
[17:56] <stgraber> hi heno
[17:57] <heno> hey guys :)
[18:00] <LaserJock> do I need to spam it in here to? :-) QA meeting is now in #ubuntu-meeting
[20:32] <ogasawara> stgraber: ok, I updated the xml file to have the url for the xml file and also the timestamp
[20:33] <stgraber> ogasawara: cool, thanks
[20:33] <ogasawara> stgraber: let me know if you want that timestamp format differently
[20:34] <stgraber> that's fine, php usually parse dates just fine, then I can output everything I want
[20:46] <stgraber> ogasawara: done and updated on 80.83.51.125
[20:46] <ogasawara> stgraber: thanks
[21:43] <dupondje> Whats newest -proposed kernel ? :s
[21:55] <dupondje> death here :x