=== mmrazik is now known as mmrazik|afk === mmrazik|afk is now known as mmrazik === doko_ is now known as doko === henrix_ is now known as henrix [09:28] hum [09:28] can somebody reject https://launchpad.net/ubuntu/+source/gnome-control-center/1:3.4.2-0ubuntu0.10 from precise-proposed? [09:28] it's broken [09:29] libsoundnua.so bails out on a undefined symbol: gvc_mixer_ui_device_is_output [09:29] which is pretty weird seeing the diff for the update [09:29] https://launchpadlibrarian.net/131132089/gnome-control-center_1%3A3.4.2-0ubuntu0.9_1%3A3.4.2-0ubuntu0.10.diff.gz [09:29] did the toolchain change or something that could explain that? [09:53] ignore the toolchain question, found the issue, fixing it === mmrazik is now known as mmrazik|otp [10:20] please somebody from the SRU team approve http://launchpadlibrarian.net/132662315/gnome-control-center_3.4.2-0ubuntu0.11_source.changes [10:20] it's to fix a breakage from the current version in proposed, diff is trivial: [10:20] http://launchpadlibrarian.net/132662660/gnome-control-center_1%3A3.4.2-0ubuntu0.10_1%3A3.4.2-0ubuntu0.11.diff.gz === mmrazik|otp is now known as mmrazik [10:49] cjwatson, slangasek, infinity, https://blueprints.launchpad.net/ubuntu/+spec/client-1303-cdimage-android-builds [11:53] seb128: accepted [11:53] cjwatson, thanks === iulian_ is now known as iulian === jbicha is now known as Guest7800 === Guest7800 is now known as jbicha_ [16:50] cjwatson, i have inadvertantly uploaded linux-meta-lowlatency to precise directly (which makes no sense) could you reject it please [16:51] cjwatson, (in precise) [17:39] *giggle* [17:39] i think for the android builds spec i could actually revive livecd-rootfs to be something more than a wrapper for live-build again === henrix is now known as henrix_ === henrix_ is now known as henrix [18:13] apw: I don't see it - where's that? [18:16] cjwatson, seems infinity sorted it for me [18:17] thanks for checking tho. [18:20] OK === henrix is now known as henrix_ === henrix_ is now known as henrix === henrix is now known as henrix_ [19:07] is it acceptable for a proposed SRU to install an entirely new binary that was added upstream as part of a bug fix? [19:20] adam_g: sometimes yes. E.g. mdadm added "forgotten" /sbin/mdmon in an SRU into precise. But it needs to be justified with a testcase. [19:20] (was missing from /debian/mdadm.install whoops) [19:23] xnox, well, in this case (quantum) the upstream solution to a critical bug was to introduce a new cleanup utility. there's a package in quantal-proposed that is expected to ship it, but an .install needs updating. can't think of a test case other than [ ! -e /usr/bin/quantum-ovs-cleanup ] [19:24] adam_g: the test-case in the "critical bug" that now needs a cleanup utility. [19:24] adam_g: e.g. reproduce the bug, use clean-up util make sure it fixes everything. [19:24] xnox, right [19:24] adam_g: is the utility cronned or like executed on upgrade? [19:24] adam_g: document that as well. [19:26] adam_g: there is a reason why the standard SRU template ( https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ) included "In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug." [19:26] ;-) [19:27] xnox, great, thanks. that helps. [19:41] cjwatson, wrt your mail answer to highvoltage on the ML ... see that he did "s/13.04/12.10/g (oops)" in a followup === Ursinha-afk is now known as Ursinha [22:07] there's something wrong going on with the LP API that's causing a lot of json decode error in queuebot [22:07] I'm debugging this now, so no queuebot for a little while [22:11] fixed I think, corrupted cache apparently. Has been quite a while since this last happened (pretty much since I started using a separate cache per thread)