/srv/irclogs.ubuntu.com/2011/06/01/#ubuntu-meeting.txt

=== debfx_ is now known as debfx
=== txwikinger2 is now known as txwikinger
DavieyIs there a UDD meeting now?12:01
jelmerDaviey: I think so (according to my calendar), but I haven't seen Barry yet12:03
jelmerDaviey: oh, thanks for that Sync ACK earlier :)12:03
Davieyjelmer: np :)12:04
jelmerhi Barry12:08
barryhi jelmer12:09
barrysorry about getting here late.  only 2 more weeks of school left :)12:09
barrylet me bring up the agenda and then we'll start12:09
barry#startmeeting12:09
MootBotMeeting started at 06:09. The chair is barry.12:09
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]12:09
barryhello and welcome to this week's ubuntu distributed development steering meeting.  who's here today?12:10
* jelmer waves12:10
barry[LINK] https://wiki.ubuntu.com/DistributedDevelopment/2011060112:10
MootBotLINK received:  https://wiki.ubuntu.com/DistributedDevelopment/2011060112:10
barryno poolie?12:11
jelmerI just pinged in #bzr12:11
barrythanks!12:11
barryhi jam12:12
james_wyo12:12
jamhi barry. Why did I think this was the "not-a-meeting" week?12:12
barry;)12:12
jamI guess because I'm crazy12:12
jamI see it on the calendar12:12
barrylet's give poolie another minute or so12:13
jamI don't think he realized, he didn't mention it in our standup this morning12:13
jamI wouldn't wait too long12:13
barryokay then12:13
barry[TOPIC]12:14
MootBotNew Topic:12:14
barry * Action items12:14
barry 12:14
barry   * jelmer to study the feasibility of merge helper ([[https://bugs.launchpad.net/bzr-builddeb/+bug/608675|bug 608675]]) as an intermediate step for quilt support12:14
barry 12:14
ubottuUbuntu bug 608675 in bzr-builddeb "merge-package should have support for manipulating quilt v3 patch stacks" [High,In progress]12:14
jelmerI've been sprinting and holiday'ing since our last meeting so I haven't had much time to look at that yet12:15
barryokay, no worries, we'll just leave it on for next time12:15
barry   * poolie to send condensed summary of uds sessions12:15
barry 12:15
barrydoes anybody know, was this done?12:15
jambarry: I assume he would send it to the udd list, and I haven't seen anything from him since April12:16
jamso I'm guessing not12:16
barryyep, i just looked at gmane and didn't see anything.  okay, continuing12:17
barry   * Riddell to give summary of current import failures with rough HARD/NOTHARD classification, and failure numbers12:17
barry 12:17
barryp-i.u.c looks flat.  i guess this is still todo.12:18
barry   * jelmer to look into [[https://bugs.launchpad.net/udd/+bug/609187|bug 609187]] (warn when package import is out of date)12:19
barry 12:19
ubottuUbuntu bug 609187 in Ubuntu Distributed Development "users are not warned when branching ubuntu:foo (or lp:ubuntu/foo) and the package import of foo is out of date" [High,Triaged]12:19
barryjelmer: continue for next time?12:19
jelmerbarry: yeah12:19
barryk12:19
barry[TOPIC]  * Package importer progress12:20
barry 12:20
MootBotNew Topic:   * Package importer progress12:20
jamjelmer: if you're interested, I'd be happy to pair with you on some of those12:20
jelmerjam: me too, perhaps next week some time ?12:20
barryjam, jelmer awesome12:20
Riddellhi12:21
barryany status on the package importer?  did i see some traffic on that the last couple of days?12:21
barryRiddell: hi12:21
Riddellon the classification I discussed it with maxb who said that any one error would have several reasons for failure12:21
Riddelland by the time you diagnose the failure enough to classify it you're most of the way to fixing it any way12:21
jamjelmer: sure12:22
jamI'm off the rest of this one :)12:22
maxbIndeed - I propose that attempting an overall classification of all current failures is less valuable that iterating a "pick one; fix" approach12:22
maxbs/that/than/12:23
barryRiddell: question: once you've done that for one bug in a class, does that help with the other similar failures?12:23
maxbWhen I say "pick one", I mean one distinct failure cause, rather than one single package12:23
barrymaxb: hi.12:23
jammaxb: one of my concerns is this failure: http://package-import.ubuntu.com/status/5cabf40249181425fdb66e301d75f02b.html12:24
Riddellbarry: depending on the bug you can do a mass retry for all the ones with that error, then you just have to see which ones it fixes and which are caused by something else12:24
jamit feels like you have to check each package manually12:24
jamwith 100 failures, that's a lot of overhead.12:24
jamany ideas on it?12:24
maxbWe looked a little at that one at the sprint, and established that there are at least two sub-classes to that traceback12:24
maxbOne involves the revision ids having identical timestamps, one not.12:25
barrymaxb, Riddell okay.  it sounds like the effort is better spent on just fixing the problems.  i can take this one off the todo list.12:26
maxbI got as far as rerunning the importer for a subset of those packages locally, but did not return to analyze the results yet12:26
barryjam, jelmer if i can put in a plug for increasing the priority of 609187 then :).  having that warning will i think at least give people a better feeling that they won't be wasting their time, and will simplify the docs.12:28
jelmerbarry: ok12:28
barryany other thoughts on the package importer?12:28
jambarry: was "run 'bzr is-package-current'" a sufficient first pass at that?12:28
jamI think there is already code for that, just waiting on making it faster.12:29
barryjam: is that a real command?12:29
maxbI have added "UDD failure ratchet: 487" to the topic of #bzr, to 1) make the descending count more visible, and 2) ensure it stays descending12:29
jambarry: I don't know the command name. I do know someone wrote a plugin that interfaces with launchpadlib12:29
barryjam: i must have missed it12:30
maxbIn doing so, I have realized that it would be useful for the package-import status page to separately count permanent and will-be-retried failures12:30
maxbFor example, it's up to 522 right now, but many of those appear to be transient errors12:31
barrymaxb: that would be nice to know12:31
barrymaxb: what's the interval for auto-retries?12:32
jambarry: maybe it was just discussed in the bzr sprint?12:32
jamI remember discussing it12:32
maxbbarry: Looks to be 3 hours currently - presumably to bridge a typical Launchpad downtime12:32
barryjam: on the face of it, some easy to spell check command would be a decent first shot12:32
barrymaxb: ack, thanks12:32
barryokay, moving on...12:33
barry[TOPIC] Bugs of interest:12:33
MootBotNew Topic:  Bugs of interest:12:33
barryhttp://people.canonical.com/~mbp/kanban/canonical-bazaar-kanban.html12:33
maxb<barry> p-i.u.c looks flat. <--- but remember the scale is logarithmic12:33
MootBotLINK received:  http://people.canonical.com/~mbp/kanban/canonical-bazaar-kanban.html12:33
barrymaxb: right, thanks for the reminder!12:33
vilasorry for the late arrival, lunch time12:34
barryvila: hi12:34
barrywow.  lots of bugs in needs release.  do you know which (if any) are being back ported to stable releases and which are for the next release?12:35
jambarry: http://webnumbr.com/ubuntu-package-import-failures.max%28800%29.min%28400%2912:37
jam[link] http://webnumbr.com/ubuntu-package-import-failures.max%28800%29.min%28400%2912:37
MootBotLINK received:  http://webnumbr.com/ubuntu-package-import-failures.max%28800%29.min%28400%2912:37
jambarry: bzr bugs generally go straight to released. plugin bugs go into needs-release12:38
barryjam: ah, i didn't know that!12:38
jamI think we just need to poke jelmer12:38
jelmerau!12:38
jamhe did all that wonderful bug fixing, just needs to release it to the public12:38
barryc'mon jelmer, bask in the glory!12:39
jelmeryeah, I need to do a few more releases12:39
barryany other thoughts on bugs?12:39
barry[TOPIC]  * Alternate meeting times?12:40
MootBotNew Topic:   * Alternate meeting times?12:40
barryso, 1100utc is doable for me, but it's way to early for slangasek.  i fear there's no way to have one single time that works for au, us-east, us-west, and euro.  otoh, it's hard enough to remember to meet at the same time (for me too!) so alternating will only make it worse.  i'm open to any thoughts.  what are your preferences?12:42
jamI prefer a same-time meeting12:43
jambut right now that is in my favor...12:43
barryjam: and 2100utc, or thereabouts is still bad for you, right?12:44
vilasame here, Wednesday is less practical family wise though (shudder, one more constraint type ;-/)12:44
jelmer1100utc works well for me too, as well as in the .au morning12:44
barryi talked briefly w/slangasek and he's okay if we keep a time more convenient to the bzr center of mass, so i guess for now we'll just keep it at 1100utc12:45
jambarry: 2100 is about 11pm. So it could work but not something I can do regularly12:46
barryjam: yep, and i think moving it an hour or so earlier starts to make it infeasible for pooie12:46
barryer, poolie12:46
barryokay, 1100utc it is12:47
barry[TOPIC] Any other business?12:47
MootBotNew Topic:  Any other business?12:47
barrynothing really on my plate, anything else from y'all?12:48
vilaYou covered max's wonders earlier ?12:48
barryvila: ?12:49
viladiagnosis on import failures, bugs with recipes to fix, etc12:49
barryvila: yep12:49
vilaok12:50
barryokay then, i think we're done.12:50
barry#endmeeting12:50
MootBotMeeting finished at 06:50.12:50
barrythanks everybody12:50
jelmerthanks barry12:53
=== brendand_ is now known as brendand
=== bdrung_ is now known as bdrung
* slangasek waves16:01
mvohello16:01
* stgraber waves16:01
jhunto/16:02
psurbhio/16:02
slangasek#startmeeting16:02
MootBotMeeting started at 10:02. The chair is slangasek.16:02
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:02
slangasek[TOPIC] lightning round16:02
MootBotNew Topic:  lightning round16:02
slangaseklet's dive right in :)16:02
slangasek$ echo $(shuf -e cjwatson barry doko csurbhi stgraber jhunt mvo ev vorlon bdmurray)16:02
slangasekmvo cjwatson stgraber doko csurbhi barry bdmurray ev vorlon jhunt16:02
slangasekmvo: how's it goin'/16:03
mvojo16:03
mvosoftware-center: work on qml branch (basic UI works and animations etc are really cool and simple to do), work on a bunch of branch merges (backend refactor, weblive-x2go, lp790450-for-4.0, ...), add support for icon-download-url from s-c-agent, SRU for 4.0.3 that includes propoer pagination support16:04
mvogdebi: work on gtk3 version and upload to oneiric16:04
mvoapt: fix wrong test for invlaid packages files16:04
mvoupdate-manager: make releasenotes display between check-release-update-gtk and update-manager consitent, port to oneiric vte, add profiles for natty->oneiric automatic testing16:04
mvosponsor indicator-multiload16:04
mvoreview/merge lp:~j-johan-edwards/archive-crawler/use-aptfile for improve archive-crasler (j-johan-edwards rocks!)16:04
mvo(done)16:04
stgraberoh right, no cjwatson today :)16:05
stgraberLooked at isc-dhcp-client-udeb to make sure it works for both DHCPv4 and DHCPv6.16:05
stgraberGot Software Center to play nicely with both x2go and qtnx, including proper status report and dealing with exceptions.16:05
stgraberStarted looking at what would be needed to get a working Edubuntu by tomorrow (hopefully, not much)16:05
stgraberPlayed with xpra as a potential way of filtering/isolating X apps, to be used in Arkose for desktop app containing.16:05
stgraberDid a few merges (more to come)16:05
stgraberLooked at the new sssd and got a community member to take care of getting the missing build-dep in Ubuntu (and to Debian) so hopefully I should be able to upload the latest release to Ubuntu quite soon, fixing bug 757499 and bug 746981.16:05
ubottuLaunchpad bug 757499 in sssd (Ubuntu) "Ubuntu should update to SSSD 1.5.x (LTM release)" [Undecided,In progress] https://launchpad.net/bugs/75749916:05
ubottuLaunchpad bug 746981 in sssd (Ubuntu) "sssd fails to find memberof.so" [High,In progress] https://launchpad.net/bugs/74698116:05
stgraberToday I'm planning on fixing Edubuntu so we can get an alpha-1.16:05
mvox2goooooo \o/16:05
stgraberRest of the week will likely be spent working on Arkose. Porting it to pygi, lxc and get xpra integrated with it. Then work on getting test packages using it.16:05
stgraberI'll also probably spend a bit of time blogging on x2go, lxc (on armel) and arkose (once I get something working nicely).16:05
stgraber(done)16:05
stgraberyeah!16:06
mvostgraber: there was a guy (ximion) interessted in using it for some packagekit releated project16:06
mvoit == arkose16:06
stgrabercool16:06
slangasekstgraber: isc-dhcp-client-udeb> AFAICS we should just drop udhcpcd in favor of this everywhere, shouldn't we?16:07
stgraberslangasek: yep, mentioned it to cjwatson and I guess we should just make netcfg depend on it, the code will then use it instead of udhcpc16:07
stgraberslangasek: then we'll need to teach netcfg about the -6 option to do both dhcpv4 and dhcpv6 (you need two instances of dhclient for that)16:07
* slangasek nods16:08
slangasekso what's broken with edubuntu today?16:08
stgrabergnome-classic :)16:09
slangasekheh, alrighty16:09
slangasekno doko_ at the moment, so...16:09
slangasekpsurbhi:16:09
stgraberI just did a seed change to include gnome-session-fallback and uploaded a new edubuntu-artwork to set it as default :)16:09
psurbhi*) changing the event handling for pivot event to an initctl command interface. Mostly done. But need to work on passing arguments to the real init (as the argument parser cuts off the --args which are not registered and in our case depending on the init the args could be anything)16:10
psurbhi*) working on an ext4 bug (but mostly working on the admin stuff before actually getting a chance to work on the bug :-/) wrote one patch for not marking inode dirty when filesystem is frozen. Testing that.16:10
psurbhi*) National holiday in Finland tomorrow.16:10
psurbhi(done)16:10
barryshort week due to usa holiday; merges: python-numpy, python-support; worked on python 3.1 eradication; worked on a little aptdb tool (lp:~barry/+junk/aptdb); udd stakeholders meeting; done.16:11
slangasekpsurbhi: when do you plan to set upstart-in-initramfs loose on us? :)16:11
psurbhislangasek, i need to finish the argument parsing, then a little testing and then i will let it loose16:11
psurbhihopefully next week end16:11
psurbhior the beginning of the week after the next16:11
psurbhi:)16:11
slangaseksweet16:11
james_wbarry, what's aptdb?16:12
psurbhislangasek, provided the upstart patch is accepted16:12
slangaseka mouthful16:12
psurbhiby keybuk and James16:12
slangasekpsurbhi: <nod>16:12
barryjames_w: it a dumb little tool for parsing the _Sources file into a sqlite db so you can do sql queries on things.  i really dislike grep-dctrl ;)16:12
james_wheh16:13
slangasekbarry: fwiw, the current round of CDs for alpha1 are coming in about 24MB oversized; the sooner we have a ballpark figure for the impact of python3, the better... :)16:14
barrythe nice thing is that only takes about 4m on my box to parse and populate the db.16:14
barryslangasek: gotcha16:14
slangasekbdmurray:16:15
bdmurraybranches for update-manager, meta-release and aptdaemon, finish teams in ubuntu bug control membership policy spec16:15
bdmurrayuploading fix for LP: #769205 (python-pysnmp4) to lucid-proposed and updating the bug for the SRU process16:15
mvo\o/16:15
bdmurraylaunchpad greasemonkey script fixs for display dup count and date last updated, uploaded new version of firefox-lp-improvements16:15
bdmurraymoving ftbfs milestones from alpha-1 to alpha-216:15
bdmurrayadding package person upload count code to ubuntu-qa-tools16:16
bdmurrayhanding off the ubuntu boot speed project to patrickmw16:16
bdmurray(done)16:16
slangasekbdmurray: what's the membership policy spec? (link?)16:16
bdmurrayhttps://blueprints.launchpad.net/ubuntu/+spec/other-qa-o-ubuntu-bugcontrol-membership-policy16:17
slangasekthanks16:17
slangasekheh, it even shows up on http://status.chrisjohnston.org/ubuntu-oneiric/canonical-foundations.html now \o/16:18
slangasekev:16:18
* slangasek leaks beta urls into the channel :)16:18
evDone:16:18
ev- Investigated the state of the gobject-introspected Cheese bindings, as well16:18
ev  as our own C-based approach.  The latter is slightly buggy, not properly16:18
ev  initializing gstreamer (though this can be worked around easily), and the16:18
ev  former, like so many other GI-based APIs seems to be at best a guessing16:18
ev  game.16:18
ev- Started the gobject-introspection migration of Ubiquity and port to GTK+3.16:18
ev  This has been slow going due to the lack of proper documentation, or even a16:18
ev  dump of the API.  Currently fighting unicode interaction in Gtk.ListStore.16:18
ev  Kill me now.16:18
ev- MIRs for python-xklavier and xvfb.16:18
ev- Added pyflakes checking to the check make target in ubiquity. This includes16:18
ev  code to filter out errors that we don't care about, but should massively16:18
ev  help avoid silly typo uploads - I hope.16:18
ev- Upgraded main development machine to Oneiric. Spent the morning fighting a16:18
ev  udev bug.  Thanks to jibel and pitti for discovering and fixing it.16:18
ev- Discussed the measuring installation failure / success proposal with mdz.16:18
ev  Replied to Kees on the technical-board mailing list, attempting to address16:18
ev  his concerns with the proposal.16:18
ev- Fought ubiquity dependencies to the death in trying to get a new version16:18
ev  out. Lost, but Colin caught an error in the unit tests that was the source16:18
ev  of the build breakage.16:18
evTODO:16:19
ev- Build out more unit tests as I port ubiquity to GTK+3/PyGI/Python 3,16:19
ev  starting with full coverage of gtkwidgets.py.16:19
ev- Still need to reply to more of the discussion around installation failure /16:19
ev  success.16:19
ev- Need to figure out what the next steps are with respect to the automatic16:19
ev  crash reporting and database.16:19
ev- Need to sit down with mpt and work out what the long-term vision around16:19
ev  feedback collection, starting with cancelling the installation, will be.16:19
ev  This will help determine whether Mozilla Input / Feedback is overkill for16:19
ev  said task. Then obviously I need to finish deploying Mozilla Feedback16:19
ev  locally, modifying it along the way to suit our needs.16:19
ev- Need to follow up with John Lea and Ale on the Wubi design work, then start16:19
ev  integrating the migration stuff.16:19
ev(done)16:19
* slangasek scrambles to hold the papers down on his desk as ev blows through16:19
evlol16:19
mvoyeah, don't do this while I drink tea, dangerous to me equipement!16:20
evhaha16:20
mvoand my sympathies for the gtk3/gi, I feel the same when it comes to porting s-c16:20
slangasekev: xvfb has been in main forever, what's the MIR there?16:21
evhmm, maybe it wasn't xvfb then16:22
* ev checks16:22
ev(do continue, I'll report back)16:22
* slangasek nods16:23
slangasekme next16:23
slangasekshort week due to US holiday16:23
slangasekgetting the last of my multiarch deltas flushed to oneiric from ppa16:23
slangasekworking with Debian maintainers to get multiarch landed upstream so we can get rid of our deltas16:23
slangasekfinishing off spec approvals... behind on this, if you're still waiting for a spec, you can yell at me now16:23
slangasekfollowing up on some tricky merges16:23
slangasekturning the cranks for alpha-1 this week16:23
slangasekEOF16:23
slangasekand if there are no questions... jhunt:16:23
jhuntShort week. Remainder: Upstart bzr merge hell.16:23
jhuntEOT16:23
jhuntNote quite that bad, but very painstaking. See16:23
jhuntlp:~jamesodhunt/upstart/1.3 on my lp code page for progress. Plan:16:23
jhuntfinish natty merges into 1.3 branch and release Upstart 1.3. Then, add16:23
jhuntpsurbhis initramfs changes, discuss oneieric plans on ML and then16:23
jhuntstart coding!16:23
jhuntEOT (really this time :)16:23
slangasekshould lp:upstart be redirected to lp:~jamesodhunt/upstart/1.3 now?16:25
jhuntwell, we could redirect now, but that branch is changing very rapidly right now and isn't fully tested yet.16:25
slangasekwell, does it build / run? :)16:26
jhuntI was planning to finish the merging, test thoroughly, update my upstart ppa with the code and invite feedback and then switch the link.16:26
slangasekas you wish :)16:26
jhunt"yes", but due to the number of changes, I'm not remerging into an ubuntu pkg for each change, building, and actually testing that a system boots with that commit.16:26
slangasekok16:27
jhuntThat has to happen, but I was planning to do the next round of such testing when I finish merging the visualisation code (prolly today/tomorrow AM)16:27
* slangasek nods16:27
jhuntCI could be useful to me right now :)16:27
slangasekheh16:27
slangaseksegway....16:27
slangasek[TOPIC] CI support from QA team16:28
MootBotNew Topic:  CI support from QA team16:28
slangasekI sent out an email call for recommendations of packages the QA team could start doing CI on16:28
slangasekbecause they're keen to get continuous integration coverage of the system, and who are we to argue!16:29
mvothe auto-upgrade-tester stuff would be good16:29
mvoI would love to hand this off16:29
slangasekso if you have packages... like upstart... that you'd like CI for, let me know16:29
slangasekmvo: this is testing that upgrades run successfully from the previous release to the current dev release, yes?16:29
psurbhiI would like initramfs tested once the changes are in16:29
mvoslangasek: yes16:30
slangasekpsurbhi: how do you think we can structure such tests?  Is it just to make sure the system boots to userspace after a change to the initramfs packages (upstart, initramfs-tools, busybox)?16:31
psurbhislangasek, yes16:31
slangasekok16:31
psurbhibut that needs to be done for desktop, servers with different configurations16:32
psurbhilike md array, lvm, crypted devices, none of these, etc16:32
doko_hi16:32
evisn't this the wrong way around? Shouldn't we be coming up with a list of the things that should be tested and run under a CI system, rather than the tests that could be restructured under CI? Or am I missing the point entirely? :)16:32
mvothe apt testsuite would be another candidate indeed16:33
slangasekpsurbhi: alright - I'll pass it on to QA that this is one of our target areas, if you can get me a list of things we need to test we can set them to work on getting the configs up16:33
psurbhislangasek, sure, will do that.. thanks!16:34
slangasekev: well, we don't want to rerun initramfs tests after *any* package has changed... just trying to get a feel for what we think we need tested when16:34
evapologies, that was a bit poorly worded on my part16:34
evat what step do we sit down and determine the things that we're not testing, and come up with a plan to test them16:35
evl16:35
evlarger components, for example, like how do we test grub exactly16:35
slangasekso I've got initramfs, auto-upgrade-tester, apt testsuite.  If anyone has other ideas of packages we want QA to test for us, shoot me an email16:35
slangasekev: let me add grub to the list then, we'll see what QA can figure out ;)16:36
slangasekdoko_: hey there!  would you like to give a status update?16:36
doko_- filed MIR's, reviewed and promoted packages for component mismatches16:36
doko_- some merges16:36
doko_- built OpenJDK 7, now in the archive, JamVM bug triage16:36
doko_- GCC updates16:36
doko_- Linaro toolchain WG call16:36
evslangasek: cool, thanks16:36
doko_not much interesting ...16:36
slangasekuninteresting GCC updates... that's good :-)16:37
doko_well, some wrong-code fixes =)16:37
slangasekany wrong code that we should be concerned about?16:38
jhuntanything armel related?16:39
doko_I don't know, libstdc++ was found mis-compiled16:39
slangasekah, but who uses that16:39
doko_nothing armel related. we didn't have linaro updates after the initial one16:40
slangasek[TOPIC] AOB16:40
MootBotNew Topic:  AOB16:40
slangasekGood news, bad news?16:40
bdmurrayI'm still looking for insight regarding aptdaemon crash report quantities ... https://lists.ubuntu.com/archives/ubuntu-devel/2011-May/033302.html16:41
slangasekjhunt: I think finding that CA is not the blocker for upstart we thought it would be is good news :)16:41
mvos-c qml branch is basicly working, can show categories, pkglist, details, install stuff search16:41
ScottKThere's a python-defaults with 2.7 as default in experimental so it's easier for Debian people to test.  Another step along the way ...16:41
ScottKThis is relevant for when we'll drop 2.6.16:41
jhuntslangasek: good point! It *has* simplfied the merge work.16:42
barryScottK: \o/16:42
slangasekmvo, barry: any idea on bdmurray's aptdaemon issue?16:42
slangasekScottK: how close is that to going to unstable?16:43
barryslangasek: not off the top of my head, but i can investigate a bit16:43
mvobdmurray: I need to look into this16:43
slangasekok, you two can thumb wrestle for the honor16:43
ScottKslangasek: I think the critical path item will be a transition slot from the release team.16:43
* ScottK didn't formally ask for one yet, but has started discussions and research for the official bug filing.16:44
bdmurrayokay, thanks16:44
mvobdmurray: I suspect (correct me if I'm wrong) that actually writing the report (like aptdaemon is doing) is enough to trigger the code in u-n to fire up the GUI to report it even if the actual daemon is disabled16:44
barryScottK: i haven't seen much progress on debian bug 62227916:44
ubottuDebian bug 622279 in release.debian.org "transition: python-defaults (switching default: 2.6 -> 2.7)" [Normal,Open] http://bugs.debian.org/62227916:44
slangasekScottK: does that actually require a coordinated transition into testing?16:45
ScottKslangasek: It does require some coordination.  It's not exactly like a library transition, but we can end up tying multiple transitions together if we're not careful.16:46
slangasekok16:46
mvobdmurray: yeah, that seems to be it16:46
ScottKbarry: Mostly the blockers are otherwise broken/we decided we aren't going to let it stop us.16:46
barryScottK: excellent16:46
evgoing to be attempting to create a status board in the office as a fun weekend project with Iain (http://hungfu.wordpress.com/2010/03/14/not-that-kind-of-bored/). Suggestions welcome for useful data points that would define how close we are to a finished Ubuntu release.16:47
slangasekother than a burndown chart? :)16:48
bdmurraymvo: hunh, I thought apport had to be running to detect and deal with a file in /var/crash16:48
evslangasek: indeed, other than the burndown charts :)16:49
evthose are the obvious ones, perhaps16:49
evthough as it will be presumably be viewed by people in the office, they don't really care about things like release bugs16:49
mvobdmurray: apport will detect crashes when it runs, but aptdaemon will bypass that by catching the crash directly, this is also the case with apt itself, so this explains the many reports it seems16:49
ev(and those are entirely unhelpful in the early stages anyway)16:49
* slangasek nods16:50
slangasek#endmeeting16:51
MootBotMeeting finished at 10:51.16:51
evthanks!16:51
barrythanks!16:51
slangasekalrighty... back to work16:51
slangasekthanks all :)16:51
ScottKev: Isn't 'the release is finished' defined by 'the calendar says this is release day'?16:51
stgraberthanks!16:51
jhuntthx16:51
evScottK: don't get me started on that one :-P16:51
ScottK;-)16:51
mvothanks16:51
mvooh, pucblic holiday tomorrow in germany!16:52
* charlie-tca waves18:00
charlie-tcaLet's get this Ubuntu QA team meeting rolling18:00
* bdmurray waves18:00
charlie-tca#startmeeting18:00
MootBotMeeting started at 12:00. The chair is charlie-tca.18:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:00
charlie-tcaAs usual, the full agenda is available at https://wiki.ubuntu.com/QATeam/Meetings18:00
charlie-tcaPrevious Actions (all)18:01
charlie-tcaCommunity Efforts/Testing18:01
charlie-tcaAutomated/Systems Testing18:01
charlie-tcaEngineering Team Bug Status18:01
charlie-tcaOther Topics18:01
charlie-tcaChair Selection18:01
charlie-tcasince we can't all get the pages to load when we would like them to.18:01
charlie-tca[TOPIC] Previous Actions18:01
MootBotNew Topic:  Previous Actions18:01
charlie-tcaI do not recall any. Does anyone else know of a previous item we need to discuss?18:02
charlie-tca[TOPIC] Community Efforts/Testing18:02
MootBotNew Topic:  Community Efforts/Testing18:02
bdmurrayI believe hggdh wanted me to publish some code (to find number of packages uploaded by people) which I did18:02
bdmurrayI put it in ubuntu-qa-tools for lack of a better idea18:02
charlie-tcaThank you18:02
jibelo/18:03
charlie-tcago ahead, jibel18:03
jibelA word about SRU testing and another about Oneiric Alpha118:04
jibelSRU Testing: 7 new high importance bugs need verification this week18:04
jibelbug 728088 open-iscsi (Natty) High18:04
jibelbug 755608 ntrack (Natty) High18:04
jibelbug 772185 nux (Natty) High18:04
ubottuLaunchpad bug 728088 in open-iscsi (Ubuntu Natty) "iscsi root with or without auth fails to boot" [High,Fix committed] https://launchpad.net/bugs/72808818:04
ubottuLaunchpad bug 755608 in ntrack (Ubuntu Natty) "Ntrack dead loop in function get_nl_link_by_index " [High,Fix committed] https://launchpad.net/bugs/75560818:04
ubottuLaunchpad bug 772185 in nux (Ubuntu Natty) "launcher sometimes doesn't hide when there are windows beneath it" [Undecided,Fix committed] https://launchpad.net/bugs/77218518:04
jibelbug 777759 casper (Lucid, Maverick, Natty) High18:04
jibelbug 778520 mdadm (Natty) Critical18:04
ubottuLaunchpad bug 777759 in casper (Ubuntu Natty) "10.10 live CD prompts to upgrade to 11.04" [High,Fix committed] https://launchpad.net/bugs/77775918:04
ubottuLaunchpad bug 778520 in mdadm (Ubuntu Natty) "install on degraded raid1 does not boot, drops to initramfs shell" [Critical,Fix committed] https://launchpad.net/bugs/77852018:04
jibelbug 781874 aptdaemon (Natty) High18:04
jibelbug 784888 vm-builder (Natty) High18:04
ubottuLaunchpad bug 781874 in aptdaemon (Ubuntu Natty) "<type 'exceptions.TypeError'>: __init__() takes exactly 2 arguments (1 given)" [High,Fix committed] https://launchpad.net/bugs/78187418:04
ubottuLaunchpad bug 784888 in vm-builder (Ubuntu Natty) "indexerror in vmbuilder when partitionfile contains 2 columns or less" [Undecided,Fix committed] https://launchpad.net/bugs/78488818:04
jibeland we still need verification of18:05
jibelbug 695290 grub2 (Lucid, Maverick) High18:05
jibel    Requires dual RAID controllers18:05
ubottuLaunchpad bug 695290 in grub2 (Ubuntu Maverick) "10_lupin case problem with ntfs UUIDs" [High,Fix committed] https://launchpad.net/bugs/69529018:05
jibelbug 778026 lirc (Natty) Critical18:05
jibel    Requires an Infrared Remote Control18:05
ubottuLaunchpad bug 778026 in lirc (Ubuntu Natty) "lirc-modules-source breaks in-kernel lirc support" [Critical,Fix committed] https://launchpad.net/bugs/77802618:05
jibelThe complete list is available at18:05
jibel[LINK] http://reports.qa.ubuntu.com/reports/sru/latest.html18:05
MootBotLINK received:  http://reports.qa.ubuntu.com/reports/sru/latest.html18:05
jibeland http://people.canonical.com/~ubuntu-archive/pending-sru.html18:05
jibelso please go there and test a SRU18:06
jibelany question about SRU testing ?18:06
charlie-tcaThank you very much. Let's see if we can get those SRU's done this week, everybody. :-)18:06
jibelok, Oneiric Alpha 1 ISO Testing18:07
jibelImage were published very late to fix with udev, apt and ubiquity defects, and kubuntu images have been published a few hours ago only. So the image coverage is low:18:07
jibel * Image Coverage       : 36.51% (23/63)18:07
jibelon the other hand no release blocker have been found at this stage of the testing.18:08
jibelThe main issues discovered concern unity-2d:18:08
jibelbug 791213 , bug 79112718:08
ubottuLaunchpad bug 791213 in unity-2d "unity-2d-places crashed with SIGSEGV in QMetaObject::metacall()" [Critical,Confirmed] https://launchpad.net/bugs/79121318:08
ubottuLaunchpad bug 791127 in unity-2d "unity-2d-places crashed with SIGSEGV in QTJSC::Structure::materializePropertyMap()" [Critical,New] https://launchpad.net/bugs/79112718:08
jibel2 very common crashes:18:08
jibelbug 788714 , bug 78871018:08
ubottuLaunchpad bug 788714 in gnome-user-share (Ubuntu) "gnome-user-share crashed with SIGABRT in g_option_context_parse()" [Medium,Confirmed] https://launchpad.net/bugs/78871418:08
ubottuLaunchpad bug 788710 in gnome-settings-daemon (Ubuntu) "gnome-settings-daemon crashed with SIGSEGV in exit()" [Medium,Confirmed] https://launchpad.net/bugs/78871018:08
jibela theming issue with nautilus: bug 78420918:08
ubottuLaunchpad bug 784209 in nautilus (Ubuntu Oneiric) "Background fails to redraw" [High,Triaged] https://launchpad.net/bugs/78420918:08
jibel7 reports need a confirmation. The complete list is available at http://reports.qa.ubuntu.com/reports/isotesting/oneiric/opened.html18:08
jibelespecially bug 791121 which has been fixed yesterday but a tester is still facing it with the latest desktop build.18:09
ubottuLaunchpad bug 791121 in udev (Ubuntu) "user dropped into busybox shell after installation" [High,Incomplete] https://launchpad.net/bugs/79112118:09
jibelAnd we need more testing on real hardware or in VMs with 3D enabled to heavily test Unity (not 2D)18:09
jibelSo, join us on #ubuntu-testing and help us to cover the remaining cases.18:09
jibelThanks for your help!18:10
jibel..18:10
charlie-tcaThanks, jibel . Any help we can get with testing these images would be greatly appreciatedQ!18:10
charlie-tcaAny questions about alpha1 testing?18:10
charlie-tca[TOPIC] Automated/Systems Testing18:11
MootBotNew Topic:  Automated/Systems Testing18:11
charlie-tcaI'm still learning these new agenda items. Anyone to talk about automated testing?18:11
charlie-tcaOkay, Maybe we will see someone before the meeting ends...18:12
charlie-tca[TOPIC] Engineering Team Bug Status18:12
MootBotNew Topic:  Engineering Team Bug Status18:12
charlie-tcapedro_: ?18:12
pedro_yes? :-)18:12
pedro_not much to share, we had a great Compiz bug day on last Thursday so thank you guys for helping!18:13
pedro_and as a quick reminder this week we're having a bug day for Evolution: https://wiki.ubuntu.com/UbuntuBugDay/2011060218:13
pedro_so if you use/like/love that application and wanna learn a bit more about it, please join us tomorrow the *whole* day your timezone18:13
pedro_as always at the #ubuntu-bugs channel where the cool people hang ;-)18:14
pedro_..18:14
charlie-tcaThank you, pedro_ . Any questions for Engineering Team?18:15
bdmurrayI've nothing special to report18:15
charlie-tcaThank you, bdmurray.18:16
charlie-tca[TOPIC] Other Topics18:17
MootBotNew Topic:  Other Topics18:17
patrickmwo/18:17
xdatap1o/18:17
charlie-tcago ahead, patrickmw18:17
patrickmwsorry, I'm late. I was on an urgent call.  Quick automation update:18:17
patrickmwUbuntu Package Testing:18:17
patrickmw- Received package lists from Desktop and Server teams18:17
patrickmw* Currently creating the Jenkins job config files for easy import to the new CI server18:17
patrickmwKernel SRU Testing:18:17
patrickmw- Autotest has been split into the individual test suites18:17
patrickmw- Original suites are compressed and live in a new project also contain Ubuntu patches (for testing)18:17
patrickmw* Currently testing that the patching and remote execution work as expected18:17
patrickmw..18:17
charlie-tcaThank you for the update, patrickmw18:19
charlie-tcago ahead, xdatap118:19
xdatap1thank you charlie-tca18:19
xdatap1It's about bug workarounds18:19
xdatap1For those who don't know me, my name's Paolo Sammicheli, community guy from Italian LoCo, involved in testing.18:19
xdatap1Last UDS in Budapest, while discussing ubuntu friendly program people expressed the idea that the workaround is an useful information from an end user point of view.18:19
xdatap1I though about it a litte and then, after chatting with people involved in QA I decided to draft a blueprint for proposing the idea.18:19
xdatap1https://wiki.ubuntu.com/BugsKnownWorkAround18:19
xdatap1After drafting the blueprint I was pointed to the following bug which was proposed back in 200618:19
xdatap1https://bugs.launchpad.net/launchpad/+bug/5465218:19
ubottuUbuntu bug 54652 in Launchpad itself "Add a "workaround" field to bug" [Low,Triaged]18:19
xdatap1where somebody suggested me to raise the discussion on the launchpad-dev mailing list.18:20
xdatap1The discussion was not so long, you can read it by thread starting from here:18:20
xdatap1https://lists.launchpad.net/launchpad-dev/msg07174.html18:20
xdatap1As usual somebody thinks it's a nice idea, somebody else thinks it's not really necessary.18:20
xdatap1The thing is, I'm a bit lost on that mailing list. I'm not sure what to do also because I probably miss the big picture.18:20
xdatap1You (or better, We) guys are the guardians of the quality in ubuntu. Do we really think that this idea would be useful?18:20
xdatap1Otherwise I would stop bother the launchpad people with this thread.18:20
xdatap1:)18:20
charlie-tcaI like the idea of a separate box for workarounds. It removes it from the jumble of the descrtip18:21
charlie-tcadescription, which can get quite involved18:21
charlie-tcaanyone else have an opinion on this?18:22
patrickmwI don't think its really necessary.  I feel adding WORKAROUND: in the description field is adequate18:22
bdmurrayI don't think a separate bit is necessary either and maybe adding a tag in addition to the description modification would be a good idea18:23
charlie-tcaxdatap1: looks bad for adding a separate block18:24
xdatap1the goal, from a community point of view, would be to export it (forum, ask ubuntu, etc) and to search for it. How to implement it it's not really important, imho. If parsing the description would work it's ok18:25
patrickmwI like the tagging idea18:25
xdatap1do you think that the features it's needed?18:25
xdatap1apart the implementation18:25
charlie-tcaI would recommend not pursueing it, just try to teach the triagers that it should be WORKAROUND: in caps at the bottom of the description, along with a tag?18:26
bdmurraybefore starting work it'd probably be a good idea to see how many bugs have workarounds18:26
charlie-tcaIs there a way to search the description for it?18:26
bdmurraycharlie-tca: I have my ways18:27
charlie-tcaheh, yeah, I figured18:27
patrickmwbdmurray is the LP Wizard18:27
charlie-tcaxdatap1: might want to get with bdmurray on it then.18:27
xdatap1charlie-tca, perfect. If I can help more just let me know18:28
charlie-tcaThe Workaround is needed, especially on a bug that gets tons of comments, since it can get buried fast in a comment18:28
charlie-tcaThanks for bringing that up18:28
xdatap1bdmurray, thanks in advance :)18:28
charlie-tcaAnyone else have something to discuss?18:28
bdmurraycharlie-tca: maybe we should document that as a thing to do for next meeting?18:29
charlie-tcabdmurray to find the numbers of bugs with WORKAROUNDS, so we can discuss a possible tag for them.18:30
charlie-tcasound right?18:30
charlie-tca[ACTION] bdmurray to find the numbers of bugs with WORKAROUNDS, so we can discuss a possible tag for them.18:30
MootBotACTION received:  bdmurray to find the numbers of bugs with WORKAROUNDS, so we can discuss a possible tag for them.18:30
bdmurraywell, I think just tagging them workaround is a good idea too18:31
bdmurraythen repromote using workarounds in the bug description and see how many we have18:31
charlie-tcaI do to. It would make them easier to search for, too18:31
bdmurraybefore working on exporting them somewhere else18:31
charlie-tcaThat sounds right to me18:32
charlie-tcaand last but not least,18:32
charlie-tca[Next Chair]18:32
charlie-tca[TOPIC] Next Chair18:33
MootBotNew Topic:  Next Chair18:33
charlie-tcaDo we have any volunteers to chair the next meeting?18:33
charlie-tcaIt's not that hard, and you get the previous business action item, too!18:34
charlie-tcaWe all get to be anyway, too18:34
bdmurrayI'll do it18:34
charlie-tcaThank you, bdmurray18:34
charlie-tcaI really appreciate that18:35
charlie-tca[ACTION] bdmurray to chair next meeting, 2011-06-0818:35
MootBotACTION received:  bdmurray to chair next meeting, 2011-06-0818:35
charlie-tcaThere being no more business,18:35
charlie-tca#endmeeting18:35
MootBotMeeting finished at 12:35.18:35
charlie-tcalet's all get back to testing and work, right? :-)18:35
pedro_thanks!18:36
xdatap1thank you!18:36
charlie-tcaYou are welcome18:36
skaetThanks all.18:40
=== steveire_ is now known as steveire
=== niekie_ is now known as niekie
=== apachelogger is now known as transitlogger
=== ayan_ is now known as ayan
=== yofel_ is now known as yofel
=== valorie_ is now known as valorie
=== valorie_ is now known as valorie

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!