=== vibhav is now known as Guest81049 === smb` is now known as smb === yofel_ is now known as yofel [12:06] sorry, something wrong with my network connection. === Guest81049 is now known as vibhav === doko_ is now known as doko [14:00] .me waves [14:00] #startmeeting Ubuntu QA [14:00] Meeting started Wed Jun 20 14:00:58 2012 UTC. The chair is balloons. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [14:00] 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 === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Meeting | Current topic: [14:01] o/ [14:01] Hello everyone [14:01] * pitti waves hello [14:01] * hggdh waves discreetly [14:02] hggdh, :-) [14:02] [TOPIC] Previous Actions === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Meeting | Current topic: Previous Actions [14:03] I don't believe we had any.. just checking to confirm :-) [14:03] Nope, k [14:03] [TOPIC] Ubuntu Updates === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Meeting | Current topic: Ubuntu Updates [14:03] hggdh, care to talk a bit about ubuntu? [14:03] heh [14:04] We are going on nicely. There was a bit of a scare yesterday, with bug... [14:04] * hggdh goes check [14:05] bah, cannot find it. But it was a problem with dpkg amd multiarch [14:05] that caused dpkg to completely fail to work. Corrected yesterday, and a new dpkg is now available [14:06] apart from that, it is business as usual. We have pretty much been able to provide working images continuously this cycle [14:06] well, almost continuously ;-) [14:06] .. [14:07] :-) [14:07] I saw gema talk a bit about UTAH [14:07] what's going on now with that? Is there a meeting place for people interested now? [14:08] there is a mailing list for -- ubuntu-utah-dev@lists.ubuntu.com [14:08] anyone interested can subscribe, and we expect it to be low-volume [14:08] we do not have meetings or presentations scheduled for UTAH right now [14:09] but we can set one if there is a need [14:09] are you able to demo it hggdh ? [14:09] no, I am not -- I am just now getting to use it. Sorry [14:09] but [14:10] UTAH is currently limited to dealing with VMs (specifically libvirtd) [14:10] support for bare-metal installation and testing will come in a few weeks [14:11] thanks hggdh [14:11] the whole idea of UTAH is to provide a common base for test submission and control (and, up to a point, reporting) [14:11] questions? [14:12] [TOPIC] Ubuntu Flavor Updates === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Meeting | Current topic: Ubuntu Flavor Updates [14:13] phillw, care to start us off? [14:13] all quiet on lubuntu, just one bug that seems possibly hardware related. [14:14] they're finalising off the applications that will be included by default [14:14] any big changeups? [14:14] nothing as yet, the application changes are planned after A2, afaik [14:15] they're testing the applications before inclusion, so hopefully there will be very little impact on the iso (famous last words!). [14:16] that's all from me :) [14:16] hehe! [14:16] alright, let's see.. how about xubuntu? [14:16] Yes, hi. [14:16] howdy astraljava [14:17] Well, we have finally had some testing, and the tests have gone pretty nicely, a few bugs of course. [14:17] We're having the team meeting right after this one, and I want to discuss our participation on Alpha-2 milestone. [14:17] My personal opinion is that we should do it, but let's see. [14:18] I just started to gather data through the xml-rpc interface, but haven't really made it there, yet. [14:18] But it'll be of more value during the milestones, anyway. [14:18] We've also started to enhance our testcases. [14:19] During one of those discussions, some confusion arose about the categorization of bugs. [14:19] But we should talk about them later this meeting. [14:20] That's pretty much it for Xubuntu. No questions? Moving on. *smirk* [14:20] .. [14:20] astraljava, sounds good, we'll discuss the bug issue in a moment [14:20] alright, kubuntu? [14:22] mythbuntu? [14:24] edubuntu? [14:24] :-) ubuntu studio? [14:24] Still here. :) [14:24] yes, take two astraljava [14:25] sorry what meeting is this again? [14:25] hey highvoltage :-) [14:25] Studio is a bit of a poor puppy here. We haven't had a working image since $deity_remembers_when. [14:25] heya balloons [14:25] this is the qa community meeting [14:25] ah ok [14:26] Contributions to the flavor has been to a minimum. We have left packages hanging in the FTBFS state for way too long. [14:26] k.. so plans for alpha 2? [14:26] going to skip? [14:26] Also there were some changes in the infrastructure (xfce4), which we just neglected to react to. [14:27] My feeling is yes, that'll be likely. [14:27] Unless something miraculous happens during the few upcoming days, definitely. [14:28] Things are picking up, though, so still very much looking for the Beta milestones. [14:28] .. [14:28] looking forward* [14:29] sounds good [14:29] alright any last questions before we move on? [14:29] [TOPIC] Other Topics === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Meeting | Current topic: Other Topics [14:30] So, I have an update to talk a little about, but we'll start with your bugs questions astraljava [14:30] Alright, so we chatted about the critical bugs vs. just bugs on the tracker. [14:31] We did agree that whenever you stumble upon a bug that is not highly relevant to the testcase, you can mark the test as passed, but mention the bug number. [14:31] But where we didn't come to a conclusion is, and my question is: What exactly is a critical bug? [14:31] Failing to install? Sure. [14:32] But other parts? What's your take on it over at the vanilla side? [14:32] we just had this same discussion [14:32] I was hoping to remove the concept of "critical bugs" and go with just bugs [14:33] however, as it stands the definition is something that prevents the testcase from passing [14:33] in other words, in the testcase failed, you should file a critical bug [14:33] if it didn't fail any bugs you found are just bugs [14:34] Yeah, but some parties were of the opinion that only the uninstallability marks the test as failed. [14:34] But I was thinking more of the releasability. [14:34] if it failed, and you found other bugs which didn't neccessary lead to it failing somehow, you could also have just bugs on a normal entry [14:34] well, testcases are diverse [14:35] so it may very well install but fail the arch check or something [14:35] by the current definition, it would still be crtiical [14:35] I can't remember where we left the discussion ATM [14:35] Right, so if you may, I'd present the exact case that lead us bickering; our case wants to check for possible USB sticks, and mounting them. [14:35] it's probably worth continuing on the mailing list / opening a bug against the ubuntu qa website [14:36] Now I agree that the case should be worded better. But what good is mounting a stick, if you cannot browse it? That's what happened with the tester. dmesg correctly identified the stick, but thunar couldn't browse it. [14:37] Nevermind the beef of the case here, but I would want the guidelines clear for any similar cases in the future. :) [14:37] I'd consider not being able to browse a mounted usb stick as critical. [14:38] though as to which application to file it against... that is another matter. [14:38] Yeah, me too; again with the releasability, I would not release such an image where file browsing of removable media doesn't work. :) [14:38] well, my idea was the terms are confusing and unneeded. Simply note the bugs filed when they happen [14:38] lp will take care of severity [14:38] That's true. So we'll just figure out inside the project, whether the bug constitutes the test as failing or passing? [14:39] well, I mean if the test fails, it fails [14:39] etheir way you note the bugs [14:40] as far as when you release and what you release it's up to the team [14:40] you can release note (almost) anything ;-0 [14:40] Right. Well let me put it another way; are there situations where a point in the testcase fails, but will not fail the whole test? [14:41] Or are all points critical in that sense; fail any, and the whole test is marked as failed. [14:43] astraljava, right.. as of now, everything is crticial [14:43] if ANYTHING fails, the whole thing fails [14:43] Ok, thanks. We'll just have to be careful with the wording, then. Cheers! :) [14:43] .. [14:44] ok, from my end, I'll be quick, we're running out of time. phillw and myself prototyped out the structure for the new testcase mgmt on the tracker [14:44] i'll be migrating over the first testcases today and sending a mail off for feedback [14:45] so look for that, and be sure and share your thoughts. We'll discuss the admin side in more detail tomorrow @ the roundtable.. [14:46] A new team has been created in order to help maintain testcases.. I'll be asking some folks who are already involved to help staff it. The goal is to get a good group of trusted folks to maintain and expand the tests over time [14:47] that said, anyone can 'file a bug' to add a new testcase or issue a correction to a testcase [14:47] The testcase format hasn't changed, but I will be sending it around as well [14:47] Any questions? [14:48] for flavors it should allow you to setup testcases for your images, using the ubuntu testcases as needed.. So it should work out nicely [14:49] Looking forward to seeing that. Good job! [14:49] stgraber has been wonderful in helping us get this all done.. be sure and thank him [14:50] alrighty, any final questions or comments? [14:50] o/ [14:50] yes phillw [14:51] I will not be here next meeting, I'm hoping to have cover in place; but cannot guarantee. [14:51] * balloons notes that his IRC client really refuses to tab-complete phillw's name [14:52] no worries phillw. [14:52] if no one is able to fill in, we'll catch up the following week [14:52] alright folks, that's a wrap! [14:52] thanks for coming out everyone [14:52] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [14:52] Meeting ended Wed Jun 20 14:52:58 2012 UTC. [14:52] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-06-20-14.00.moin.txt [14:52] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-06-20-14.00.html [14:53] thanks for chairing balloons [14:53] Thanks guys! [14:53] thank you for coming ;-) === skaet_ is now known as skaet [15:00] * xnox 0/ [15:00] o/ [15:00] * slangasek waves [15:01] #startmeeting [15:01] Meeting started Wed Jun 20 15:01:30 2012 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15: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 [15:01] o/ [15:01] [TOPIC] lightning round === meetingology changed the topic of #ubuntu-meeting to: lightning round [15:01] $ echo $(shuf -e barry doko stgraber jodh ev bdmurray slangasek ogra infinity cjwatson xnox stokachu) [15:01] cjwatson stgraber ev infinity doko bdmurray ogra stokachu barry jodh xnox slangasek [15:03] * xnox in security team they play tag during lightning round. Somebody goes first, and then at the end chooses who goes next. keeps people on their toes & make them follow the meeting ;-) [15:03] Some minor merges and syncs. [15:03] Converted apt-setup to new world order for dpkg multiarch configuration. [15:03] Experimenting with efilinux's interface. [15:03] Got per-pocket upload permissions working, and deployed them for -backports and -security. [15:03] Finished LP API exports needed for new-style change-override. [15:03] Fixed a bug where lp/debian/+source/* imports get confused for Debian source packages that require DEB_VENDOR=debian to extract correctly. [15:03] Worked on making Archive.copyPackage work for the security team. [15:03] .. [15:04] cjwatson: yeah. is that for lp only or for package-import as well? the DEB_VENDOR bit? [15:05] LP only [15:05] sorry, still typing [15:05] udd probably ought to do it but I don't work on that :) [15:06] stgraber: shall I go while you finish? [15:06] cjwatson: ok. [15:07] ev: go ahead [15:08] - Updated average time between failures to the latest nvd3 goodness and told [15:08] it to fetch up to 30 days (efficiently) at a time, so you should start to [15:08] see a better picture being formed once that gets deployed. [15:08] - Cleaned up the problem pages on errors.ubuntu.com. We now have colorized [15:08] traces for both binary and interpreted crashes. [15:08] - Wrote an LEP for the bugs to fixed binary packages work in Launchpad. [15:08] Waiting to hear back from Francis and Rob: [15:08] https://dev.launchpad.net/LEP/BugsToFixedBinaries [15:08] - Had a long conversation with pitti over the design of the duplicates [15:08] database. The existing model lets multiple crash signatures exist and has an [15:08] algorithm to map duplicate bug reports to the correct master bug report for [15:08] a given signature. We agreed that this wasn't ideal. This is especially so [15:08] given that errors.ubuntu.com effectively uses crash signatures as a primary [15:08] key and I've run head first into this in attempting to weld apport's [15:08] - Duplicating lots of bugs to a single bug used to cause timeouts. [15:08] - Before we had nice controls around per bug mail notification people would [15:08] get spammed with messages they didn't care about. [15:08] - Sometimes two distinct problems share the same crash signature. [15:08] The first two points are resolved and the second one needs to be addressed [15:08] properly. So we agreed that the following will be done: [15:08] - We'll have a single master bug for a given crash signature. [15:08] - As the problem gets fixed in releases, the release task status will be [15:08] changed. [15:08] - We'll let developers split apart crashes with the same signature by [15:08] creating a new signature using the server-side apport hooks. [15:08] - Since we didn't have a team meeting last week, you fortunately missed my [15:08] detailed whinging of why talking to Launchpad as a web service is a road [15:08] paved with landmines. I was going to build a celery worker to service [15:08] requests to communicate with Launchpad, but I talked with Rob about it some [15:08] more and he felt that the more expedient option of talking straight HTTP to [15:08] Launchpad's API was acceptable. [15:08] - So I wrote code to do just this for the case of creating bugs [15:08] from the errors.ubuntu.com front page as part of the e.u.c API and bound [15:08] the AJAX code I had written for handling this POST operation to it. I'm [15:08] also going to have the bucketing process automatically create these bugs [15:08] when the instance count gets above 30 or so, so you'll likely rarely see [15:08] the 'create bug' links or care about them. [15:09] - Started writing the Daisy (Cassandra) apport crashdb implementation [15:09] (lp:~ev/apport/daisy-duplicates-db) as eluded to above. This will let [15:09] crash-digger and the daisy.ubuntu.com retracers share knowledge of the [15:09] mapping of crash signatures to bugs. This in turn will let us have 'create [15:09] bug' links on http://errors.ubuntu.com and is required for the 'fixed binary [15:09] packages for a given crash signature' work. [15:09] - Verified the latest USB disks for the shop. [15:09] - Started implementing errors from hanging applications in apport [15:09] (lp:~ev/apport/reports-from-hangs) now that we have an approach that the [15:09] security team is happy with: [15:09] https://bugs.launchpad.net/ubuntu/+source/whoopsie-daisy/+bug/1006398 [15:09] - Looked into handling hanging Python applications with help from Colin: [15:09] https://bugs.launchpad.net/whoopsie/+bug/1015080 [15:09] - Started implementing recoverable error reporting in apport. [15:09] - Fixed some minor bugs in lp:daisy and lp:errors. [15:09] - Landed my libwhoopsie branch on trunk and released a new version. [15:09] - Landed by 'show previous crash reports' branch on lp:activity-log-manager. [15:09] Cleaned things up for a release, but after talking with the zeitgeist guys [15:09] that wont be until next week. [15:09] (done) [15:09] Launchpad bug 1006398 in whoopsie-daisy (Ubuntu) "Bypassing ptrace restrictions for errors from hanging applications" [Undecided,New] [15:09] Launchpad bug 1015080 in Whoopsie "Retrieve Python tracebacks from hanging applications" [Wishlist,New] [15:09] * stgraber is ready now [15:09] Is it just me, or are the novels getting longer? [15:09] * xnox is there a pager plugin for xchat? [15:09] infinity: :) [15:09] infinity, they are [15:09] i cant read fast enough [15:10] - 12.04.1 [15:10] - Preparing team meeting, team meeting and meeting notes. [15:10] - Helped verify a few items in the queue [15:10] - Containers [15:10] - Improved our apparmor profiles to be easier to edit/fork by our users [15:10] - Converted Serge's initial work on liblxc into a quilt patch [15:10] - Implemented python3-lxc, a python C binding of liblxc0 with some python overrides [15:10] - Got test packages built and published in my PPA [15:10] - Working on updating the bindings as Serge implements new features in liblxc [15:10] - Still need some more work on memory/error management in my C code... [15:10] - ISO tracker [15:10] - Implemented the remaining items from the QA team [15:10] - Merged the testcase management branches into their respective trunk branches [15:10] - Got IS to deploy the new code and ran the DB upgrade, so far all looks good [15:10] - Worked on a few minor UI fixes that should land later this week [15:10] - Networking [15:11] - Posted a long reply to a bridge-utils Debian bug, trying to explain how that [15:11] even based networking stuff works in Ubuntu. [15:11] - Other [15:11] - Patch pilot on Friday [15:11] - TODO this week [15:11] - Minor bugfixes to the ISO tracker [15:11] - More LXC work on the API and python binding, hoping to have something we can send [15:11] upstream over the next few weeks. [15:11] - Go through the networking bugs, merge/sync the networking packages, including bumping isc-dhcp [15:11] to 4.2. SRU any important fix found while doing that. [15:11] - Continue going through the pending-sru and help for these that are stuck on verification-needed [15:11] (DONE) [15:11] oh, and I'll be off on Monday (Quebec day) [15:12] - Lots of PlusOneMaint fixing, sponsoring and archiveadminning [15:12] - Dealt with several SRU kernels [15:12] - Hunted down one mono/armel bug, only to find that the natty kernels are giving us more issues; this needs escalating [15:12] - dpkg merge done, with upgrade fallout needing to be dealt with [15:12] - debhelper merge and eglibc fix in to match the new dpkg [15:12] ... [15:12] * infinity needs to write these things earlier, so he can be as verbose as the cool kids. [15:12] ev: I think one of your sentences got cut off ;) "weld apport's [...]" [15:12] ev: so did you have to manually adjust the sizes of the usbsticks to make them fit for validation purposes? [15:12] infinity, dont ! i have to summarize it for the release meeting [15:12] slangasek: rubbish, okay….pasting [15:13] - gcc-4.7 c++11/c++98 ABI issues [15:13] - python3 porting jam [15:13] - python3.3 updates, and cross builds [15:13] .. [15:14] key and I've run head first into this in attempting to weld apport's [15:14] duplicates database into daisy's Cassandra database. The reasons for this [15:14] behavior were as follows: [15:14] - Duplicating lots of bugs to a single bug used to cause timeouts. [15:14] - Before we had nice controls around per bug mail notification people would [15:14] get spammed with messages they didn't care about. [15:14] - Sometimes two distinct problems share the same crash signature. [15:14] The first two points are resolved and the second one needs to be addressed [15:14] properly. So we agreed that the following will be done: [15:14] - We'll have a single master bug for a given crash signature. [15:14] - As the problem gets fixed in releases, the release task status will be [15:14] changed. [15:14] - We'll let developers split apart crashes with the same signature by [15:14] creating a new signature using the server-side apport hooks. [15:14] - Since we didn't have a team meeting last week, you fortunately missed my [15:14] detailed whinging of why talking to Launchpad as a web service is a road [15:14] paved with landmines. I was going to build a celery worker to service [15:14] requests to communicate with Launchpad, but I talked with Rob about it some [15:14] more and he felt that the more expedient option of talking straight HTTP to [15:14] Launchpad's API was acceptable. [15:14] hopefully that fills the gap [15:14] http://paste.ubuntu.com/1051056/ - in case it doesnt [15:14] porting of update-notifier to python3 [15:14] added in dist-upgrade tag to apport package failures in update-manager [15:14] made apport not report 'dpkg-deb --control returned error exit status 2' package install failures [15:14] set up rls-q-incoming report in arsenal and on cranberry [15:14] set up ubuntu-bugcontrol-tools branch which is separate from ubuntu-qa-tools branch [15:14] updated bugsquad greasemonkey tags and replies [15:15] wrote code to check to see if bugs for which a bug pattern has been written are fixed [15:15] removing bug patterns that exist for fixed bug reports that are no longer needed [15:15] blog post regarding lp-bug-dupe-properties being merged and how awesome it is [15:15] landed launchpad branch for bug 912137 [15:15] Launchpad bug 912137 in Launchpad itself "bug subscribers portlet sorted in reverse order" [Critical,Fix released] https://launchpad.net/bugs/912137 [15:15] Launchpad bug fix for bug 826864 (created_before searchTasks parameter in API) [15:15] Launchpad bug 826864 in compiz-fusion-plugins-main (Ubuntu) "Grid plugin + xterm = no size cycling" [Undecided,New] https://launchpad.net/bugs/826864 [15:15] . done . [15:15] * jodh thinks his eyes may have reached todays byte quota. [15:15] hmm not that bug [15:15] doko: the c++11/c++98 discussion on ubuntu-devel seems to have stalled; can you send a mail today, to make sure the desktop team knows what they need to do to get un-stuck? [15:16] done: [15:16] * some flash-kernel fixes [15:16] * merges [15:16] * started looking into livecd-rootfs to add diversions for flash-kernel where needed when building ac100 [15:16] images, turned out to be a missing env var [15:16] * work through ftbfs arm list [15:16] * tested new nvidia-tegra driver with the quantal ac100 kernel [15:16] ahh, yes, will do [15:16] * piloting [15:16] todo: [15:16] * livefs switch for arm images [15:16] * build ac100 again [15:16] * upload nvidia tegra armhf driver to archive (was waiting for the 3.1 kernel) [15:16] * add support for panda and ac100 to ubuntu-drivers-common [15:16] … [15:16] * xnox wants lightlighting round in mobi format to read on my kindle ahead of meeting ;-) [15:16] bdmurray: update-notifier> I believe I've landed your merge but didn't upload, fwiw [15:16] * DONE http://pad.lv/496922 - Gave detailed instructions on how to extend snmp with external calls [15:16] Launchpad bug 496922 in net-snmp (Ubuntu) "Ubuntu snmpd package doesn't include all net-snmpd modules" [Wishlist,Confirmed] [15:16] * TODO http://pad.lv/578536 - Backported 2 patches that address hanging automount and listing stale mount points in /proc/mounts during a re-read of map entr$ [15:16] Launchpad bug 578536 in autofs5 (Ubuntu Natty) "when stopped, automount orphans some mounts" [Medium,Fix committed] [15:16] * TODO http://pad.lv/951343 - SRU and merge proposal done, is now waiting on merge proposals to go through. (On track for 12.04.1) [15:16] Launchpad bug 951343 in nss-pam-ldapd (Ubuntu Precise) "[SRU] authentication fails silently with long pam_authz_search filter" [Medium,In progress] [15:16] * DONE http://pad.lv/933903 - SRU added and pushed to precise-proposed (On track for 12.04.1) [15:16] Launchpad bug 933903 in dropbear (Debian) "Dropbear's initramfs scripts mount /dev/pts a second time" [Unknown,New] [15:16] Data Not Available [15:16] oops [15:17] * TODO http://pad.lv/977952 - Blocked on http://pad.lv/977947 being completed. [15:17] * TODO http://pad.lv/977940 - SRU complete, waiting on micahg response from comment #5. (On track for 12.04.1) [15:17] Launchpad bug 977952 in libbonoboui (Ubuntu Precise) "Please transition libbonoboui to multi-arch" [Medium,Triaged] [15:17] * TODO http://pad.lv/977964 - SRU template written, needs debdiff for precise. (On track for 12.04.1) [15:17] Launchpad bug 977947 in libbonobo (Ubuntu Quantal) "Please transition libbonobo to multi-arch" [Medium,Triaged] [15:17] Launchpad bug 977940 in gnome-vfs (Ubuntu Precise) "Please transition gnome-vfs to multi-arch" [Medium,In progress] [15:17] * DONE http://pad.lv/890928 - SRU complete, pushed to -proposed (On track for 12.04.1) [15:17] Launchpad bug 977964 in libart-lgpl (Ubuntu Precise) "Please transition libart-lgpl to multi-arch" [Medium,Triaged] [15:17] * Additional Issues brought to my attention [15:17] Launchpad bug 890928 in libxkbfile (Ubuntu Precise) "When trying to install libxkbfile1:i386 the pkg manager asks to remove too many important packages [Multi-arch]" [Low,Fix committed] [15:17] ** TODO http://pad.lv/979661 - Need to discuss with Foundations on status of case. [15:17] Launchpad bug 979661 in update-manager (Ubuntu Quantal) "oneiric to precise: debconf: unable to initialize frontend: Gnome and falls back to Dialog" [High,Confirmed] [15:17] bdmurray: in addition to the rls-q-incoming report, will you also set up a report for tracking accepted targeted bugs, please? [15:17] ... [15:17] (AFAIK we don't have that yet? or I don't know the URL) [15:18] slangasek: I'd thought that launchpad was sufficient for tracking those [15:18] bdmurray: not afaik because we can't get the report directly from LP broken down by team :/ [15:18] I had typoed bug 8268654 [15:18] Error: Launchpad bug 8268654 could not be found [15:18] I had typoed bug 826854 [15:18] Launchpad bug 826854 in Launchpad itself "It should be possible to search bugs given a range of date_created using the API" [Low,Fix released] https://launchpad.net/bugs/826854 [15:19] slangasek: If the team accepted the bug won't they know about it? [15:19] more python 3 porting: apturl (landed), python3-xapian (ongoing upstream discussion), libpeas (upstream supports it, needs packaging work, thanks xnox for the cdbs magic!). helped stgraber with some python3/lxc debugging. patch piloted. todo: continue with libpeas and xapian. what's up with twisted? done. [15:20] bdmurray: not reliably? :) [15:20] ogra_: is the livefs switch for arm images coming before alpha2? [15:20] slangasek, i was planning to have that before yep [15:20] barry: i have further thoughts on the libpeas, will talk to you later. [15:20] slangasek: okay [15:20] xnox: cool [15:20] i'll start rolling manually built images tomorrow [15:21] and see what falls over [15:21] if someone has time to review http://pad.lv/951343 to get the merge proposal pushed into proposed i'd appreciate it [15:21] Launchpad bug 951343 in nss-pam-ldapd (Ubuntu Precise) "[SRU] authentication fails silently with long pam_authz_search filter" [Medium,In progress] [15:21] stokachu: I can do that [15:22] stgraber: great, thanks! [15:22] xnox: i backported 2 patches for autofs, assuming test goes well do you think it'd be a problem getting SRU for lucid? Data Not Available [15:22] jodh: buffer overflow ? =) [15:23] xnox: http://is.gd/RpIFyQ [15:23] sorry, paste buffer is being stupid [15:23] stokachu: i have problems with 5.0.6, working on them. Will check if you picked up a broken patch or not which does check_nfs [15:23] jodh: your turn [15:24] * boot/upstart: Working on stateful re-exec. [15:24] - Can now mostly serialise and deserialise Sessions, Events and [15:24] Processes in basic form and getting close with JobClasses. [15:24] - Identified that we'll need json-c version 0.10 (currently beta) [15:24] for Upstart as previous library versions don't appear to provide [15:24] the ability to detect garbage JSON data which can lead to crashes. [15:24] j [15:25] stokachu: did you right the patch or did you backported/cherrypicked stuff? [15:25] is 'j' the unicode 'done' marker of the day? :) [15:25] xnox: cherry picked [15:25] excess flood ? [15:25] stokachu: ok. [15:25] slangasek: yeah. It's a good letter :) [15:25] jodh: heh [15:25] jodh: do you know when json-c 0.10 is due out? [15:26] * xnox should it not be "-- Sir J." ?! =) [15:26] slangasek: no - will chase up on that. [15:26] may I? [15:26] xnox: yes [15:26] * python sprint: helped porting apt-btrfs-snapshot, [15:26] ubuntu-drivers-common, apparmor. Helped with packaging [15:26] questions. The funny one, was libpeas with cdbs flavor's build [15:26]