[00:02] <jibel> stgraber, https://code.launchpad.net/~jibel/ubuntu-qa-website/d7rewrite_report_searchform
[00:02] <jibel> good night
[00:03] <stgraber> jibel: good night
[13:59] <mvo> jibel: any chance you could verify #773007 ? I would like to do another lucid-proposed upload for unattended-upgrades soon. or someone else maybe? happy to help in any way I can. oh, and if you need help with that main-all profile, I'm happy to work on this as well
[14:00] <jibel> bug 773007
[14:00] <ubot4> Launchpad bug 773007 in unattended-upgrades (Debian) (and 4 other projects) "conffile_prompt check incomplete on multiple conffiles (affects: 2) (heat: 7)" [Unknown,Fix released] https://launchpad.net/bugs/773007
[14:04] <bladernr_> jibel, is there an Oneiric package containing dl-ubuntu-test-iso?
[14:05] <jibel> bladernr_, there's a PPA https://launchpad.net/~ubuntu-server-iso-testing-dev/+archive/dev
[14:08] <jibel> mvo, when is soon ?
[14:08] <bladernr_> jibel:  thanks :) gonna try to help out with some ISO testing, but noticed that my Oneiric update removed the qa-tools package :(
[14:09] <jibel> bladernr_, yeah someone (bdmurray :)) thought the package was not maintained and asked for removal :)
[14:09] <bladernr_> whoops :)
[14:09] <jibel> bladernr_, we'll probably ask to readd it.
[14:10] <jibel> mvo, for main-all pitti uploaded the package that caused the build failure of the source system this morning. I'll rerun the job and tell you how it goes.
[14:12] <patdk-wk> are we suppost to test alpha1 or daily?
[14:15] <jibel> patdk-wk, that's confusing indeed.
[14:15] <jibel> stgraber, could you hide alpha1 until there are builds available ?
[14:15] <jibel> I'm not admin anymore :(
[14:16] <stgraber> jibel: hmm, that's weird, you should still be admin as you're part of ubuntu-qa-website-devel, can you try to logout and login again?
[14:16] <jibel> stgraber, that's fine logout/login fixed it
[14:17] <stgraber> good to hear :)
[14:18] <jibel> patdk-wk, confusion is fixed. only daily is available.
[14:18] <patdk-wk> :)
[14:31] <patdk-wk> hmm, no links to download urls?
[14:31] <stgraber> jibel: btw, if you end up having some spare time today, we need to populate all the download links for precise in the new tracker. I'm still finishing the work on the UI side but the admin UI is ready to be used.
[14:31] <stgraber> patdk-wk: ^ :)
[14:31] <patdk-wk> :)
[14:32] <jibel> stgraber, spare time :)
[14:32] <stgraber> we just need to enter the right zsync, rsync, http, md5 and gpg for every product in the DB, that may take a bit of time :)
[14:32] <stgraber> jibel: yeah, I know ;)
[14:33] <stgraber> jibel: I forgot I had to do some patch piloting today, so that doesn't really help (though I cleaned up 10 or so item in the queue in less than 30 minutes, so might do some ISO tracker work on the side now)
[14:34] <stgraber> most of the easy ones I'll just script (anything that's an ISO on cdimage), the trickier ones are the netboot and the armel images
[14:34] <stgraber> as their md5sum/gpg files aren't in the same directory and some even have multiple files
[15:11] <mvo> jibel: sorry for the delay, had a call. soon would be within the next couple of days, the next update is actually ready in bzr
[15:12] <jibel> mvo, np, I'll try to verify it first thing tomorrow.
[15:17] <mvo> jibel: thanks a bunch!
[15:32] <bdmurray> jibel: I think dl-ubuntu-test-iso should be moved somewhere else most of ubuntu-qa-tools shouldn't be packaged
[15:35] <jibel> bdmurray, right and vm-tools too. It's useful and maintained by the security team.
[15:44] <stgraber> jibel: btw, I'll need to have a look at dl-ubuntu-test-iso again one of these days and see if I can merge my own version in there.
[15:45] <stgraber> jibel: I worked on a python script that parses cdimage.u.c, figures out the history (like the fact that edubuntu is based on ubuntu and kubuntu) and then uses zsync to download only a very limited delta
[15:45] <stgraber> it lets me sync all of cdimage in around 40min, most of it being CPU time
[15:45] <stgraber> and it allows pooling more than what's on cdimage as it does the cleaning up locally (I have the 10 most recent builds of each product)
[15:46] <stgraber> as it only takes around 5s to parse cdimage (when there's nothing to download), it's running every hour here so I pretty much always have all the most recent builds
[15:46] <stgraber> next step is to plug it in the ISO tracker API so it automatically symlinks the builds based on what milestone they are associated with on the tracker
[15:48] <jibel> stgraber, I did something similar to keep an historic of ISOs: http://bazaar.launchpad.net/~ubuntu-bugcontrol/ubuntu-qa-tools/master/view/head:/dl-ubuntu-test-iso/dl-iso-history
[15:48] <jibel> stgraber, but based on the build logs
[15:49] <jibel> stgraber, probably we can merge everything and have a single sync tool
[15:50] <brendand> jibel - when are we expecting alpha1 images?
[15:56] <stgraber> jibel: that'd be good. We can probably do something that's fast and very reliable, especially now that we have everything on the tracker
[15:56] <jibel> brendand, tomorrow morning
[16:02] <brendand> mvo - i'm doing tests for DebFileApplication in software-center right now. it seems if i use the test database then most of the info I would expect to find in the AppDetails are empty. Do I need to use the system database maybe?
[16:06] <mvo> brendand: hm, that should work, do you have a example?
[16:16] <brendand> mvo - i'm not sure i actually know for sure what the behaviour should be, so i'll catch you in a little while with the example i have
[16:18] <brendand> mvo - i'm testing with just a deb package i downloaded from launchpad. checkbox in this case
[17:48] <stgraber> jibel: oops, I see you just found a bug in my code (based on the logs), undefined admin variable in user_downloads. Fixed now.
[17:49] <stgraber> jibel: I'll be done with patch pilot in half an hour or so, will finish that page then
[17:49] <jibel> stgraber, yep, and the substitution VERSION -> build number doesn't work unless it isn't implemented yet.
[17:51] <jibel> stgraber, I think I'm done with the links. I verified many of them and they look ok. I'll add netboot manually.
[17:52] <jibel> skaet, now that stgraber has put a wonderful admin tool in your hand, maybe it is the right moment to disable obsolete products ?
[17:53] <jibel> *hands even :)
[17:54] <stgraber> jibel: http://91.189.93.73/qatracker/milestones/204/builds/7165/downloads looks pretty good
[17:54] <stgraber> jibel: Except that filename should be the same for all of these (as all the links are related to the same file) and I see a duplicate / in the rsync URL (but that's just me being picky)
[17:55] <stgraber> jibel, skaet: I'm fine with you disabling products, but just make sure I'm aware of it so we don't loose these changes when exporting data back to the old tracker
[17:55] <jibel> stgraber, I spent 1 hour verifying each character of this one because I knew it would be the 1rst you'd check ;)
[17:56] <stgraber> hehe, yeah, that's my usual test product as it has very few subscribers and I know it quite well :) that way I can mess with it and I'm the only one who gets spammed
[17:57] <stgraber> speaking of spamming: bzr commit -m "Switch build notification on (as in, stop spamming stgraber :))"
[17:57] <jibel> stgraber, ok, will fix the naming, I was unsure what the name was referring to. I'll fix that, after homework. See you later.
[17:58] <stgraber> jibel: thanks!
[18:06] <skaet> jibel,  re: obsolete products.   sounds good.   start of cycle is right time for this sort of thing.  :)
[18:37] <skaet> stgraber,  if I mark something disabled (and get it wrong), is it easy enough to switch back?   Also,  email ok for letting you know which have been disabled?
[18:39] <stgraber> skaet: if you disable something it'll still be on the list but marked as disabled, so you can just edit it again to set it back to enabled
[18:39] <stgraber> skaet: yes, e-mail is fine. thanks
[18:48] <skaet> stgraber,  how should I be indicating we're not putting something out as a released image, but its still being produced as part of the dailies?    I'm thinking about the powerpc images.
[19:01] <stgraber> skaet: we'll have both milestones enabled starting tomorrow (Precise Alpha 1 and Precise Daily)
[19:01] <stgraber> skaet: so powerpc should be pushed to Precise Daily and the rest to Precise Alpha 1
[19:02] <stgraber> then disable any of the dailies that are part of the Alpha 1 (so Precise Daily only shows non milestoned images)
[19:03] <stgraber> cjwatson: can you easily change the milestone so that powerpc goes to "Precise Daily" even if the rest goes to "Precise Alpha 1"? (or for any other image where we have dailies and don't want them released for a1)
[20:19] <cjwatson> stgraber: tricky, and also self-fulfilling given that these are often "get released if and only if they're tested"
[20:20] <cjwatson> wouldn't it make more sense to switch the milestone for everything and just make sure it's clear that presence on the tracker doesn't indicate that it's actually alpha status
[20:20] <cjwatson> ?
[20:23] <stgraber> cjwatson: works for me
[20:23] <stgraber> skaet: ^
[20:24] <cjwatson> it's tricky because cdimage really doesn't know - it would be yet another giant table we'd have to keep in sync
[20:28] <skaet> yeah but we do know in advance usually if there is someone willing to test it for a milestone.   Having to go in and manually disable them each time (and definitely before they get copied out as part of the release) is going to be error prone.
[20:29] <skaet> I'm wondering if there's much point in keeping the dailies going while doing a milestone?
[20:31] <skaet> stgraber,  would it be possible to have a status of active, daily only, disabled?
[20:45] <alourie> stgraber: ping
[20:45] <stgraber> alourie: pong
[20:46] <alourie> stgraber: would it be too hard to line up this: http://91.189.93.73/qatracker/milestones/204/builds/7192/testcases
[20:46] <alourie> widths of two tables are uneven, it drives me crazy
[20:46] <alourie> sorry :-)
[20:47] <stgraber> skaet: was wondering the same, we could simply disable the daily milestone while doing milestone testing, then turn it back on
[20:47] <stgraber> alourie: can you give me a screenshot? they're properly lined up here :)
[20:49] <alourie> stgraber: where do I paste screenshots?
[20:49]  * alourie is slow today
[20:50] <alourie> imgshack :-)
[20:51] <alourie> stgraber: http://imageshack.us/photo/my-images/339/screenshotat20111128224.png/
[20:52] <stgraber> alourie: wow, that's weird. What browser is that?
[20:53] <alourie> stgraber: chrome
[20:53] <alourie> let me try ff
[20:54] <stgraber> alourie: ok, I didn't test with chrome, might be some css parsing difference between the two
[20:54] <alourie> stgraber: may be. Ubuntu Friendly also had couple of those with chrome
[20:54] <alourie> stgraber: FF is fine
[20:55] <alourie> so it's with Chrome
[20:55] <alourie> considering how many people use Chrome/Chromium, I think it should be fixed
[20:56] <stgraber> agreed, layout work isn't exactly my top priority at the moment, but I'll definitely add that to the todo
[20:56] <alourie> stgraber: do you want me to open a bug? or todo list works for you?
[20:56] <alourie> :-)
[20:57] <stgraber> todo list works better at the moment, would have way too many bugs otherwise :)
[20:57] <stgraber> the todo is in the bzr branch though ;)
[20:57] <stgraber> alourie: todo updated
[20:58] <alourie> great
[20:58] <alourie> thanks
[21:07] <skaet> stgraber,  disabling daily milestone makes sense,  lets try that with alpha 1.
[21:12] <alourie> so, is alpha 1 out already?
[21:22] <stgraber> alourie: alpha1 testing starts tomorrow with alpha1 getting released on thursday (if all goes well)
[21:22] <alourie> stgraber: so testing alpha 1...without it being released?
[21:23] <alourie> how should I do that? Use dailies?
[21:24] <stgraber> alourie: starting tomorrow we'll have things appearing under the alpha-1 milestone, these are alpha-1 candidates
[21:24] <stgraber> once we're happy with the quality of these, we'll release alpha-1
[21:24] <alourie> will they appear on the new tracker? The one we're testing?
[21:24] <alourie> stgraber: ^^
[21:26] <jibel> alourie, yes, the candidates available for testing will be posted to the tracker.
[21:26] <alourie> jibel: would you mind me twittering/socializing it further?
[21:27] <alourie> I'd like to have as much folk in QA as possible :-
[21:27] <alourie> )
[21:38] <jibel> alourie, sure, we definitely need to communicate more around QA in Ubuntu. I wouldn't say no to more testers too :)
[21:40] <alourie> jibel: great
[22:57] <stgraber> jibel: I just ran http://pastebin.com/Ff3RBZkF on the DB, that should have fixed all the filenames and paths at once :)
[22:59] <stgraber> jibel: or not, there seems to be quite a few that haven't been fixed because they don't have a http_file (type == 0) image
[23:00] <jibel> stgraber, indeed armel and wubi
[23:01] <jibel> stgraber, scratch that, they should all have an http_file
[23:02] <stgraber> right, can you easily figure out the list of these that need fixing or should I try to get it?
[23:04] <jibel> stgraber, don't bother, I'll regenerate the list.
[23:05] <stgraber> ok, there's the list anyway: http://paste.ubuntu.com/753098/
[23:06] <stgraber> all the others have been fixed by my script (at least they should have)
[23:06] <stgraber> heading back home now, will be back online in 30min or so
[23:32] <jibel> stgraber, fixed and verified.
[23:33] <stgraber> jibel: cool, thanks
[23:33] <jibel> stgraber, I forgot kubuntu mobile
[23:34] <jibel> can we add a comment for upgrades instead of a link to an image ?
[23:34] <stgraber> oh, that's a good point
[23:35] <stgraber> go with:
[23:35] <stgraber> filename = Upgrade
[23:35] <stgraber> type = 5
[23:35] <stgraber> path = <your comment>
[23:35] <stgraber> (filename will be used at the title)