16:01 #startmeeting 16:01 Meeting started Thu Jan 9 16:01:47 2014 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:01 16:01 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 16:01 [TOPIC] Lightning round 16:02 $ echo $(shuf -e barry doko stgraber jodh bdmurray slangasek cjwatson xnox stokachu) 16:02 cjwatson stokachu barry bdmurray stgraber doko slangasek jodh xnox 16:02 oh look 16:02 It's been a "catch up after new year" week 16:02 bah =) /me missed the chat 16:02 Miscellaneous: 16:02 *sorry* 16:02 - Bits and pieces of arm64/ppc64el porting (wcslib, mozjs17, libgksu, lcms, telepathy-logger, pvm, umockdev 16:02 - Various other build failure fixes (mutter, gnome-shell, obexd, renpy 16:02 - Caught up a bit on the trusty-proposed backlog with a bunch of rebuilds and such. 16:02 - base-passwd 3.5.30, with more secure defaults for shells of various global static users. Hoovered up fallout in a dozen or so packages (one of which broke phone tests, oops). 16:02 12.04.4 preparation: 16:03 - Reviewed a bunch of enablement uploads. 16:03 - Prepared debian-installer for lts-saucy enablement tree. 16:03 Started on libclick. 16:03 .. 16:03 Oh and sorry to anyone upset by the missing close parens there. Here: ) ) 16:04 :) 16:04 stokachu: around? (it's a new year, so maybe? :) 16:04 cjwatson: there's an emacs mode for that 16:04 Nothing from me this week 16:05 stokachu: ok, cool :) 16:05 as far as bugs go, working on getting sosreport 3.1 relead 16:05 done 16:05 short week due to winter break. was mostly off-line, so plenty of catching up this week. 16:05 system-image: LP: #1259326 (triaged, discussed) 16:05 Launchpad bug 1259326 in system-image (Ubuntu) "system-update panel not blocking screen lock/blank while downloading" [Medium,Confirmed] https://launchpad.net/bugs/1259326 16:05 autopilot: LP: #1266574. branches ready for address-book-app, camera-app, cordova-ubuntu in progress. discussions with #ubuntu-autopilot folks 16:05 Launchpad bug 1266574 in autopilot (Ubuntu) "autopilot_tracepoint.c is not Python 3 compatible" [Undecided,New] https://launchpad.net/bugs/1266574 16:05 ubuntu/debian: python-apt 0.9.1ubuntu1 (for dep8 fix). window-mocker python3/pybuild support for cgoldberg. 16:05 done 16:05 queried errors database to see if bug 1024590 is fixed in saucy 16:05 tested unattended-upgrade bug 1265729 16:05 uploaded a fix for bug 1237119 16:05 bug triage of bug 1264887 16:05 bug 1024590 in aptdaemon (Ubuntu) "update-manager crashed with AttributeError in _on_download_changed(): 'NoneType' object has no attribute 'get_value'" [Medium,Fix committed] https://launchpad.net/bugs/1024590 16:05 bug 1265729 in unattended-upgrades (Ubuntu) "unattended-upgrade might enter an infinite loop if an upgradable package is on hold" [Undecided,Incomplete] https://launchpad.net/bugs/1265729 16:05 bug 1237119 in gnome-control-center (Ubuntu) "ERROR: hook /usr/share/apport/package-hooks/source_gnome-control-center.py crashed: TypeError: add_info() takes 1 positional argument but 2 were given" [Medium,Fix released] https://launchpad.net/bugs/1237119 16:05 bug 1264887 in ubuntu-release-upgrader (Ubuntu Trusty) "After upgrade 12.04 -> 14.04 there was no display manager (kdm or lightdm)" [High,Confirmed] https://launchpad.net/bugs/1264887 16:06 uploaded whoopsie-preferences with a change for location of apport/autoreport (bug 1239811) 16:06 bug 1239811 in whoopsie-preferences (Ubuntu Trusty) "whoopsie-preferences crashed with SIGSEGV in _IO_new_fclose()" [High,Fix released] https://launchpad.net/bugs/1239811 16:06 uploaded update-notifier, apport, lxc-android-config with a change for location of apport/autoreport 16:06 updated bug bot to handle not erased media ubiquity install failures 16:06 updated bug bot to recommend people try 12.04.3 not 12.04.[12] 16:06 modified phased-updater not to keep setting stopped updates to 0% 16:06 subscribed teams to packages 16:06 trying to setup an instance of errors in canonistack to work on retracer issue 16:06 worked with canonical support to get my core limit increased for deploying the error tracker in canonistack 16:06 barry: there's an emacs mode for everything 16:06 testing autoreporting of crashes and whoopsie on trusty (bug 1245524) 16:06 bug 1245524 in whoopsie (Ubuntu) "whoopsie fails to notice/process .upload files on trusty" [Critical,Confirmed] https://launchpad.net/bugs/1245524 16:06 ␗ done 16:06 oh can someone remove sponsors team from bug 1121874? 16:06 bug 1121874 in mysql-5.5 (Ubuntu Saucy) "MySQL launch fails silently if < 4MB of disk space is available" [Medium,In progress] https://launchpad.net/bugs/1121874 16:06 now that arges can sponsor packages he just can't remove the team from subscribers list 16:06 cjwatson: true! there's even one for vi users :) 16:07 - cgmanager: 16:07 - Followed the progress made by jodh and hallyn, discussed and reviewed initial packaging 16:07 - LXC: 16:07 - Preparing for rc1 next week (ton of code reviews and a few fixes) 16:07 - Wrote a bit about LXC: https://www.stgraber.org/2013/12/20/lxc-1-0-blog-post-series/ 16:07 - Tested and prepared systemd upload to turn on all cgroup controllers in logind 16:07 - Follow up on PAM change to get unprivileged containers working properly 16:07 - Branch to make apport work with LXC (some extra changes needed) 16:07 stokachu: I guess somebody did it, doesn't seem to be subscribed now 16:07 - Ubuntu touch 16:07 barry: what kinds of discussions have you been having on #ubuntu-autopilot? are they excited about the python3 move? :) 16:07 - Images now have discard enabled by default 16:07 - Fixed a few bugs in my experimental port/private-server system-image branch, working on tests now. Test server at https://phablet.stgraber.org 16:07 - Other 16:07 - SRU/New reviews 16:07 - A few merges 16:07 (DONE) 16:07 cjwatson: ah ok must've just happened lol, thanks for checking 16:07 slangasek: i'm happy to discuss a few things after the lightening round 16:07 barry: ack 16:09 - two full days of merges, not yet finished with main, and didn't look yet at universe. merges in general seem to be behind this cycle 16:09 - start packaging GCC 4.9, including four new runtime libs 16:09 - gcc-4.8/arm64: trying to reproduce a testcase for 1263576 16:09 - finishing tcl/tk updates 16:09 - made python3.4 a supported python3 version. fixed most packages 16:09 build-depending on python3-all-dev. 16:09 - started a first test rebuild, currently for main on all archs. 16:09 universe will follow later this week. 16:09 - looked at ruby-ffi on arm64 and ppc64el. not much progress 16:09 - finished the glew transition 16:09 - uploaded ppc64le cross toolchain to trusty 16:09 - update of python interpreters 16:09 - MIR processing, component mismatches, ... 16:09 (done) 16:11 doko: gcc 4.9> and that's not landing in the archive this cycle, right? 16:12 slangasek, depends ... =) 16:12 doko: on what? 16:12 * post-holiday email wrangling 16:12 * learning the ropes on the TB (congrats to everyone else who was elected, thanks to everyone else who stood) 16:12 * sprint prep 16:12 * continuing to work on filling our open position on the team 16:12 * Debian upstart/systemd discussions 16:12 * monitoring upstream kdbus discussions 16:12 * worked with stgraber to land pam_loginuid userns support upstream 16:12 * ongoing ppc64el discussions 16:12 (done) 16:12 * core-1311-upstart-roadmap: 16:12 - cgroup support: 16:12 - Upstart can now run a job in a cgroup using the cgmanager. 16:12 Continuing to work with stgraber + hallyn on cgmanager design and 16:12 implementation. 16:12 - async spawning: Have a prototype branch that will boot a system and 16:12 a Session Init, handling child comms asynchronously. Needs 16:12 polishing and also necessitates reworking some of the existing 16:12 tests and writing additional state-machine checking tests. 16:12 if gccgo-4.9 looks better than -4.8 16:12 Currently extending the serialisation format to handle resuming the 16:13 async operations post re-exec. 16:13 ◣ 16:13 no, not as the default 16:13 * Emulator / Autopilot: 16:13 - working on automating autopilot execution in the emulator 16:13 - finding / identifying / filing bugs about issues with test 16:13 failures, which are regressions over mako. 16:13 - solving scalability of testing with juju charm development to 16:13 reliably run all tests quickly. 16:13 - see ubuntu-phone mailing list post + bugs tagged "jemjem" 16:14 * installer: 16:14 - worked on improving support for Qemu/OVMF targets 16:14 * over christmas time: 16:14 - helped with icu and glew transitions, ppc64el fixes. 16:14 doko: would we be able to use gccgo-4.9 with libgcc from 4.8, or does this require updating libgcc? I thought you were opposed to pulling in 4.9 for the runtime libs 16:14 * I'm away on holidays from 11th to 19th of January 16:14 .. 16:14 xnox: we should chat about autopilot+emulator some time :) 16:14 slangasek, I'm opposed to overwrite libstdc++6 16:15 and as I said, I just started the packaging this week ... 16:15 barry: well today is best as i'll be available most of the evening. tomorrow, i'll be finishing sharp at EOD. 16:15 doko: ack 16:16 xnox: ack 16:16 any more questions/comments on status? 16:17 barry: should we talk about autopilot? 16:17 slangasek: sure 16:18 [TOPIC] autopilot & python3 16:18 we have buy-in that autopilot tests in packages should be py3, which is great because we'll be able to ditch py2 on touch 16:18 some disagreement on whether there should be a "flag day" or switch things over package by package 16:19 otoh, if we go by xnox's list in emulator branch, there's only 11 packages that need porting, so i think it's silly not to just flag day it 16:19 yes; but all the plans for switching things over package-by-package had huge overhead on the packaging side 16:19 * slangasek nods 16:19 slangasek: yeah, i thought you'd back me up on that :) 16:20 i've already ported address-book-app and camera-app and am working on cordova-ubuntu. really, porting the actual packages is not difficult 16:20 one thing i'm unsure of atm is whether the click package tests in xnox's branch use autopilot. i think not, but not sure atm 16:20 barry: oh, i see. Yeah, I was confused why all tests seem to run in python2 mode, when they are mostly 1.4 autopilot based and should be python3 capable. 16:21 barry: all of them use autopilot, after a huge amount of wrapper scripts =) 16:21 right, we have /usr/bin/autopilot (py2) and autopilot-py3 as test runners 16:21 xnox: okay, so the click package tests will need porting too then. that adds to the mix 16:22 other open questions: whether to have one big tracking bug with bugtasks, or a bug per package 16:22 barry: i can wedge /usr/bin/autopilot to be /usr/bin/autopilot-py3 & give you logs of how much things fail, would you be interested in that? 16:22 and the really difficult one: testing :( 16:22 testing> that's why we have charms :) 16:23 xnox: what kind of times are you getting out of running all the testsuites, now? 16:23 xnox: what i'd like to talk about later is fiddling with your emulator scripts to switch between py2 and py3, and using local packages. but then there's the cross-building issue 16:23 barry: one big bug with bugtasks, doesn't scale that well. Having one bug per project/package with a common tag works better. As one can request launchpad to list them all "e.g. tag jemjem from all projects" 16:23 xnox: that's probably how we'll go 16:23 slangasek: some instances get stuck, so i need to add watchdog. Last run I did was about 3h across all non-failing projects. 16:23 since i suspect package maintainers will prefer that 16:24 barry: is python3 autopilot seeded on the images yet? 16:24 xnox: not bad, not bad... seems like a few more iterations, and we should be able to get solid test results for the autopilot transition 16:24 right now the easiest thing seems to be: install the amd64 packages and run the tests locally. a few py2 tests will fail (e.g. i have no camera) but oh well. then, build and install the amd64 py3 ported package locally and run with autopilot-py3. icky, but has the advantage of actually working :) 16:25 xnox: python3-autopilot gives you /usr/bin/autopilot-py3 16:25 autopiloters seem to do all testing on devices, including package builds. but i think that's almost unnecessarily slow for porting purposes 16:26 barry, do you test with 3.4 too? ;-p 16:26 barry: and autopilot-touch is not a python based? it has python-autopilot & python-evdev depends. 16:26 doko: ha ha ha! 16:27 barry: +1 for anything that speeds up the development cycle by leveraging native hardware :) 16:27 xnox: i *think* those are just ap's own tests, which can be run against py2 and py3 using tox in their trunk branch 16:27 cool. 16:27 slangasek: yeah, i think that'll at least get us 99% of the way there 16:27 at least to the point of mp's 16:28 so, aside from porting, we'll have to get ci to switch over to autopilot-py3. that's a whole 'nuther discussion 16:28 (some of which has been discussed before) 16:28 anyway, i think that's about it. xnox's emulator is awesome btw, and if we can leverage it for testing as described above, i think that would give us extra confidence 16:28 eot 16:29 yeah, there's no way we can propose having a py3 flag day for autopilot /without/ testing in emulation... we need to get the py3 autopilot test failures down to where they match the existing py2 tests, and that requires testing on arm 16:31 so next steps: 1) iterate through the test suites on amd64, fixing any obvious py2/3 issues; 2) generate reports for py2 vs. py3 autopilot testing in the cloud; 3) lather, rinse, repeat; 4) flag day when we hit parity? 16:31 agreed. i think the phablet-tools test runner can be pointed to local packages and/or ppas, so one of the steps in this process should be uploading to a ppa all the ported tests, twiddling the runner to use py3, and running them on actual devices and/or the emulator 16:31 slangasek: yes 16:32 ppas> only relevant for the .debs, I guess, not the click packages 16:32 right 16:32 barry: ok - sounds like a plan. What do you think the timeline looks like? I guess if you haven't looked at the test suites yet for any of the click packages, it's hard to project? 16:33 slangasek: right. but i'm mildly confident i can finish the non-click porting this week or early next week 16:33 ok 16:34 barry: thanks! 16:34 sure thing! 16:34 anything else for today? 16:34 [TOPIC] AOB 16:36 beuller 16:36 nothing? :) 16:36 #endmeeting