=== Jacky is now known as JackyAlcine === JackyAlcine is now known as Jacky === Jacky is now known as siibot === siibot is now known as Jacky === astraljava1 is now known as astraljava === Cees_ is now known as Cees === yofel_ is now known as yofel [13:47] morning/afternoon everyone [13:56] howdy [14:00] morning everyone.. [14:00] shall we begin? [14:00] #startmeeting QA community [14:00] Meeting started Wed May 23 14:00:25 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 | QA community Meeting | Current topic: [14:00] who all is about on this fine day? [14:00] YO [14:01] o/ [14:02] * gema hides [14:02] hehe [14:02] alright, this meeting is mostly going to be about sharing plans and talking about goals for the cycle [14:03] We have no previous actions, so let's start with ubuntu [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 | QA community Meeting | Current topic: Ubuntu Updates [14:04] gema, would you care to start off and talk about your team's plans? [14:04] you don't need to worry about being exhaustive :-0 [14:04] hahaha, no worries [14:04] I can summarize it quite neatly: we are going to improve automated testing [14:05] how? [14:05] well, we keep working on UTAH and will start using it in the lab soon [14:05] we've improved the lab and installed a massive openstack, we are calling it QA Stack [14:05] and we will be trying to convey all the test results and new testing we start doing more effectively [14:06] by reporting results to the tracker as well [14:06] we are also going to start having the team meetings on youtube [14:06] just in case people are curious what we are up to [14:06] g+ streaming to youtube [14:07] and I have a suggestion to you nick, we could do the same with this meeting [14:07] EOM [14:07] gema, thanks for the update.. So where might I get to see your meetings on youtube? [14:08] will you send a link out to the mailing list? [14:08] balloons: I am talking to IS at the moment to get the whole thing set up [14:08] balloons: I will let you know once it is up, I am not sure how it will look like [14:08] gotcha. Once you've trialed it out I'm open to ideas on doing the same on this meeting [14:09] ack, will keep you posted [14:09] right now you would be seeing me and a puppy :-) [14:09] everyone loves puppies right? [14:09] yes [14:09] :) [14:09] :-) [14:09] the nice thing about it is that people can join the hangout and drop when they finish talking [14:09] and then the 10 people limit doesn't matter [14:10] cos many can watch and whoever needs to talk can join [14:10] Ok, I guess I will also update before moving onto flavors. Does anyone have questions for gema before I give my speil? [14:10] it's very cool [14:11] * gema goes to hide again [14:11] no questions? awesome. So on my end, I am still finalizing the last of the blueprints and decisions we made at UDS. I plan to blog once everything is complete. Should be sometime this week [14:11] However, here's a quick summary, of which I'm happy to take questions [14:13] I am remaining focused on manual testing this cycle -- and that is going to include iso, sru and application testing. [14:14] the feedback from UDS was to: improve the process, recognize contributors, avoid burnout [14:15] The biggest change is that we are going to use the isotracker software to handle running application testcases, sru's and do our testcase management [14:16] that should make everything easier. I'm going to continue and expand the adopt an iso program to ensure people are not getting burned out by having to do everything by themselves; especially at the increased cadence we would like to see. Also, we're focusing on ensuring our tests our meaningful and avoiding re-work [14:18] on the community front, I'm organizing a roundtable that we'll plan on doing once (perhaps twice?) a cycle to ensure we as a community (flavors teams, testing teams, etc) are all communicating and participating and helping each other as needed. As we learn best practices and create new tools, this will be an oppurtunity to share [14:19] we'll also be cleaning up and revitalizing a couple current launchpad teams to ensure membership is current and the folks are active. [14:20] I think that's hitting most of the high points.. There are other things we will look to accomplish, and I'm always open to ideas, so as ever feel free to contact me [14:20] any questions for me? [14:21] has this membership confirmation been done in the past too? [14:21] cesilko, what do you mean membership confirmation? [14:22] you mean with the launchpad team cleanup? [14:22] you said that you want to assure that folks are active [14:22] yes. Many launchpad teams have an expiration policy to ensure teams stay current and relevant [14:22] I apologize if this is a dumb question, I am kind of a newbie here :) [14:22] no no -- great question [14:23] okay, thanks for the answer [14:23] I am curious as well, I know there was a drawn out discussion in the mail list [14:23] the idea is once a cycle (or whenever we wish), folks would be asked to click a link to renew membership in the team [14:24] makes sense, great [14:24] people will come and go, and we want to make sure people on the team want to be on the team and are actively participating [14:24] exactly, we do it too @ NetBeans [14:24] balloons: just expire us all and wait until we come to you begging ;) [14:26] Ohh, I should also mention on the recognition front. I want to do a few things. First off, I want to make sure we as a community recognize each other's work. I think we are fairly successful at this. Secondly, I want to provide some swag, enhanced responsibility/opportunity for folks who demonstrate good work. This could mean getting some hardware to help test (if they don't have access to it), etc. Also, I want to clarify and help anyone who is [14:26] contributing but is not a ubuntu member know that there QA contributions can be reognized towards membership [14:27] I myself am applying for membership, so if there are any ubuntu members who can speak for me, I would appreciate comments on my wiki page :-) https://wiki.ubuntu.com/balloons [14:28] so yea.. LOTS of opportunities this cycle.. I could type and type, but I will move on to flavor updates :-) [14:29] [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 | QA community Meeting | Current topic: Ubuntu Flavor Updates [14:29] ok, I know several flavors couldn't make it today [14:29] so I'll just call each one and see who is here [14:29] Xubuntu? [14:30] Kubuntu? [14:30] Lubuntu? [14:31] Hello [14:31] Hi ScottK :-) [14:31] Yesterday we uploaded KDE SC 4.8.3 to precise-proposed. [14:31] That'll be a QA focus for us and we'd love to have more testers. [14:31] .. [14:32] ScottK, the best way to get involved with kubuntu qa is to vist the #kubuntu channel yes? [14:32] balloons: #kubuntu-devel. [14:32] #kubuntu is user support. [14:32] ahh yes, sorry :-0 [14:32] We handle QA on the dev channel. [14:32] No problem. [14:32] It's still building, so don't go try to install it this very minute. [14:33] Any plans for the cycle surrounding QA? Any changes to testing ideas, iso testing, etc? [14:33] I wasn't at UDS, so I'm not sure. [14:33] one of the things discussed at UDS was testcases for flavors [14:33] meaning writing the tests with the flavors in mind, and not using the generic ubuntu testcases.. not sure if kubuntu was going to pursue that or not [14:33] I've found when doing ISO testing that I can figure out what I should test for Kubuntu based on the Ubuntu test case. [14:34] Personally I'd expect it to be more work than it was worth. [14:34] (I didn't discuss it with anyone thoug) [14:34] ScottK, gotcha. Thanks for the update [14:34] h [14:34] don't worry we're not holding you to speaking for all of kubuntu :-0 [14:35] ok, how's about edubuntu? [14:36] Maybe adding a footnote or two to the existing Ubuntu test cases would do it. [14:36] That'd be a lot less maintenance work, but still help out where people might be confused. [14:36] Just a thought. [14:37] ScottK, well you would be able to clone the existing tests.. Something to talk about and think about over the cycle [14:37] Right, but once it's cloned, then if the Ubuntu test gets updated, someone has to import the change into the Kubuntu test case. [14:37] yep, [14:38] That's the maintenance burden that worries me. [14:38] It'd be way smoother if we could do it without having to fork the test case. [14:38] balloons: maybe we could tag test cases as to which flavours they apply [14:38] yes, it's something you will have to maintain [14:38] balloons: that way the flavors that can actually use the test cases as is do not need to worry about the maintenance burden [14:39] not me, the community [14:39] we are talking manual testing, right? [14:39] gema, I'm not sure what you mean persay.. as of right now you get a link [14:39] you mean the testcase can apply to multiple flavors? [14:39] it's that way now [14:39] now it is like that because it happens to be [14:40] we could make it explicit, and therefore manageable [14:40] we could tag the test cases as applicable to ubuntu, kubuntu and ubuntu studio , for instance [14:40] and that test case will be one to take into account for those flavors in particular [14:41] balloons: this is a burden on stgraber, because it is more implementation [14:41] that's all [14:41] can you remember and bring it up next week when meeting with stgraber ? [14:41] yes [14:41] thanks [14:41] ok, finally let's try and see if ubuntu studio has anyone about? [14:41] and then we can close out this topic [14:43] ok, great. [14:43] moving on [14:43] [TOPIC] Other topcis === 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 | QA community Meeting | Current topic: Other topcis [14:43] my fat fingers.. :-) [14:44] basically, this is open to anything anyone wishes to discuss.. let me know and the floor is yours. [14:44] ! [14:44] yes tristenw go ahead [14:44] I'm looking to switch from a testing perspective to coding, I just need someone to mentor me a little [14:44] have python background already [14:45] tristenw, hehe.. do you like web programming and/or have messed with django? [14:45] haven't no [14:45] If so, there's oppurtunities to help develop tools we as a QA community use [14:45] o/ [14:45] could learn I guess though [14:45] If your focusing on wanting to learn desktop apps, I can put you in touch with some folks on that end as well [14:46] that would be superb, and I'll start working on django too [14:46] tristenw, send me an email afterwards and I'll get you hooked up [14:46] k [14:46] yes skaet , go ahead [14:47] https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule [14:47] and thank you tristenw :-) [14:47] yw [14:47] draft is getting pretty close to finalized now. [14:47] skaet, ahh yes.. good point to mention [14:47] if anyone has concerns about it, email to ubuntu-release maillist. :) [14:48] So if everyone has a look, you'll notice we have a column on that schedule [14:48] balloons, actually thats: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock :) [14:48] ohh.. you didn't send the big sheet link [14:49] I just pasted the master schedule first. Now you've got the link to the "big one" :) [14:49] skaet, thanks [14:49] so yes, please have a look. As a community, we're looking to perform the tasks and work in that community testing column [14:50] * skaet nods [14:50] basically we want to help ensure things are smooth before milestones, and before isotesting events. We want a lighter workload, with more people testing.. but there is more being asked of us this cycle [14:52] ok, anything else? [14:52] any questions or comments on the schedule? I'll open a thread on the ml about it also so everyone gets a chance to see it [14:53] if not, thanks for coming out everyone and we're done! :-) [14:53] thanks! :) [14:53] bye :) [14:53] #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:53] Meeting ended Wed May 23 14:53:21 2012 UTC. [14:53] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-23-14.00.moin.txt [14:53] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-23-14.00.html [14:53] I have one more question if I can but it's not schedule related. [14:53] cesilko, sure [14:54] Does Ubuntu have purely date driven releases or is there a minimal release criteria that must be satisfied before new version is shipped? [14:54] Imagine that a day prior the planned release a true showstopper is found. What happens then? [14:55] Is there a Wiki describing that? [14:55] I didn't find one. :| === debfx_ is now known as debfx [14:57] cesilko, there is release criteria indeed [14:58] the release team is the best folks to ask for more information about that [14:59] joining #ubuntu-release is probably not a bad place to ask.. I hope :-) [14:59] but let me find you some wiki pages [14:59] okay, I will turn to #ubuntu-release then [15:01] * slangasek waves [15:01] * stgraber waves [15:02] * ogra_ moos [15:02] #startmeeting [15:02] Meeting started Wed May 23 15:02:26 2012 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:02] 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:02] [TOPIC] lightning round === meetingology` changed the topic of #ubuntu-meeting to: lightning round [15:02] $ echo $(shuf -e barry doko stgraber jodh ev bdmurray slangasek ogra infinity cjwatson xnox) [15:02] barry jodh infinity xnox ev cjwatson bdmurray ogra slangasek stgraber doko [15:02] * barry wins! [15:02] syncs: twisted, python-testtools, python-defer, subunit, dbus-python. reviewed py3 branch for testresource. started working on bug 1000801 (lazr.restfulclient port). started porting wsgi-intercept. reviewed glatzor's py3 branch for software-properties. patch pilot: reviewed xnox's python-couchdb merge, bkerensa's fix for bug 962974, takluyver's py3 python-tz branch (merged & uploaded), bug 1002861 (sync'd canto). dmb meeting. todo: [15:02] return to porting the lazr.restfulclient stack. done. [15:02] er, wait [15:02] Launchpad bug 1000801 in lazr.restfulclient "Add support for Python 3" [High,New] https://launchpad.net/bugs/1000801 [15:02] Launchpad bug 962974 in landscape-client (Ubuntu) ""Management Service" is gratuitously vague" [Low,Opinion] https://launchpad.net/bugs/962974 [15:02] Launchpad bug 1002861 in canto (Debian) "Sync canto 0.7.10-3 (universe) from Debian unstable (main)" [Unknown,New] https://launchpad.net/bugs/1002861 [15:02] stokachu: are you here? [15:03] too late :) [15:03] $ echo $(shuf -e barry doko stgraber jodh ev bdmurray slangasek ogra infinity cjwatson xnox stokachu) [15:03] jodh bdmurray ev xnox stgraber doko ogra infinity stokachu barry slangasek cjwatson [15:03] new order ;) [15:03] * barry loses [15:03] barry: you'll just have to go twice ;) [15:03] * [misc/planning]: fleshed out work items (and sizings) for 7 blueprints. [15:03] * [boot/upstart]: [15:03] - wrote spec for stateful re-exec (https://wiki.ubuntu.com/FoundationsTeam/Specs/QuantalUpstartStatefulReexec) [15:03] - evaluated a number of JSON libraries. [15:03] - wrote a basic JSON test prog to validate a fragment of the expected [15:03] JSON schema. [15:03] - started work on stateful re-exec. [15:03] - NIH blog post. [15:03] - drafted an Upstart blog post on logging. [15:03] ㄆ [15:03] * infinity wakes up. [15:04] modified apport to set importance of python tracebacks to Medium [15:04] modified apport to carry over release tags from duplicates to the master bug [15:04] wrote and ran launchpadlib code to copy tags over from duplicate apport-crash bug reports [15:04] apport branch to block 'not a debian format' archive bug reporting [15:04] put checks for corrupt packages for package install failures in apport instead of having apt check [15:04] update-manager merge for the fix to bug 999890 [15:04] Launchpad bug 999890 in update-manager (Ubuntu Precise) "does not block follow up errors from earlier reports" [High,Triaged] https://launchpad.net/bugs/999890 [15:04] slangasek: oh, i get it: new order <- joy division <- warsaw [15:04] wrote lplib code to delete update-manager clone attachments due to security issue [15:04] modified bug bot to remove bad attachments from update-manager reported bugs [15:04] hah [15:04] modified bug bot to write to a log file for easier auditing of work done [15:04] modified search-bugs in bugpatterns to show count of duplicates for the master bug [15:04] modified lp-grab-attachments to have a --descriptions option [15:04] updating firefox-lp-improvements with the new version of lp_work_item_editor [15:04] arsenal branch to create a report of bug task with the most duplicates [15:04] \o/ [15:04] wrote a bugpattern for ubiquity bug 998492 [15:04] Launchpad bug 998492 in ubiquity (Ubuntu Precise) "Fails to detect package download errors on architectures other than amd64" [High,In progress] https://launchpad.net/bugs/998492 [15:04] added a11y opportunity to harvest-data [15:04] moved harvest opportunity creation scripts from ubuntu-qa-tools to harvest-data [15:04] review of package install failures due to /etc/default/grub modifications gone bad [15:05] done‼ [15:05] bdmurray: That seemed out of order. :P [15:06] - worked on organising and tidying specs [15:06] - spent a lot of time looking into armel/armhf toolchain woes [15:06] - spent even more time looking into nscd/netgroups bugs [15:06] ... [15:06] ^-- Remarkably short this week. [15:06] infinity: I was following the new order === emma is now known as em [15:06] infinity: you are out of order =) [15:06] bdmurray: Oh, I completely missed the new new order. [15:06] infinity, i added a WI for you to https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-drop-preinst-images [15:07] (just for tracking purposes) [15:07] * infinity isn't all here today. [15:08] * xnox looks for ev [15:08] xnox, just move :) [15:08] ev: [15:08] software-raid: [15:08] * collaborating with kees on https://wiki.ubuntu.com/ReliableRaid/History [15:08] * already from above, prepared some udev fixes for mdadm bug 957494 bug 968074 bug 1002357, pending sponsorship [15:08] * establishing access to bare metal machines in the QA lab [15:08] * ordered external quad HDD housing for RAID testing, being shipped from china [15:08] * next step to establish RAID Architecture Specification [15:08] ubiquity-lvm-luks: [15:08] * added workitems to the blueprint [15:08] * discussing requirements/roadmap/first steps with stakeholders [15:08] * next step to start building/modifying ubiquity [15:08] python-versions: [15:08] * tracker deployed at http://people.canonical.com/~ubuntu-archive/transitions/onlypy3oncd.html [15:08] * next step finish up local py3 branch for apparmor [15:08] Launchpad bug 957494 in mdadm (Ubuntu Precise) "Missing added utility 'mdmon'" [Undecided,New] https://launchpad.net/bugs/957494 [15:09] bug 968074 [15:09] xnox: thanks for the tracker! [15:09] bug 1002357 [15:09] xnox: you are doing the python3 porting for apparmor? [15:09] ev: you're not here [15:09] xnox: [15:10] jdstrand: well, i did a little work (there isn't much tbh) spotted a few things that were not bi-lingual [15:10] py2/py3 [15:10] jdstrand: are you doing it as well? [15:10] xnox: ok, feel free to takl to me after the meeting [15:10] ok [15:10] xnox: we have work items for it, yes [15:11] xnox: did you give up on getting access to the lab machines for HD testing, then? [15:11] xnox: I might also mention that ufw is actively being ported [15:11] jdstrand: nice [15:12] * jdstrand has a work item for that [15:12] slangasek: I got VPN today, but don't have access to any machines behind the VPN yet. I still one both. Lab for automatic, local for troubleshooting/personal dogfooding [15:12] xnox: ok [15:12] s/one/want/ [15:13] stgraber: [15:13] Short week, was off on Monday: [15:13] - Networking [15:13] - Spent some time testing candidates SRU for an IPv6 bug in Network Manager [15:13] - SRU [15:13] - Verification testing of nagios-nrpe and lxc [15:13] - Started preparing the next lxc SRU [15:13] - Containers [15:13] - Reworked the lxc-ubuntu template to be much easier to maintain [15:14] (then no doko, so ogra_ next) [15:14] - Worked with Serge on API design for liblxc, worked on the initial structure of the python binding [15:14] - Fixed some races in lxc-start-ephemeral, made it consistently call sudo and dropped the separate [15:14] and complex lxc-ip for a simple call to the new "ip netns" instead [15:14] - ISO tracker [15:14] - Continued the work to get qa-q-isotracker-testcases implemented, all of the backend work is done [15:14] and most of the frontend work nears completion, there's some admin UI work left and API update [15:14] - Migration code works fine, result can be seen at http://iso.qa.dev.stgraber.org [15:14] If you don't see anything, that's fine, the idea was not to loose any history data and have the new cool [15:14] stuff show up only for the new products. [15:14] - Other [15:14] - Drafted and sent all my specs for review [15:14] - Patch pilot on Friday [15:14] - TODO this week [15:14] - Push an LXC SRU, cherry-picking the important fixes from the recent quantal uploads [15:14] - Get enough of the ISO tracker work done so that QA can test it and work on smaller changes [15:14] (DONE) [15:14] phew [15:14] done: [15:14] * ascension day on thu. [15:14] * filled WIs on foundations-q-embedded-rootfs, foundations-q-hwpack-integration and added two items to foundations-q-drop-preinst-images [15:14] (for tracking purpose only) [15:14] * finally MoM is back, worked on merges [15:14] * started looking into the gcc-4.7 FTBFS list on debian (on request from doko) [15:15] todo: [15:15] * more merges [15:15] * more FTBFS [15:15] * start looking into the armhf image situation in preparation for A1 [15:15] (fells so small to go after stgraber) [15:15] .. [15:16] ogra_: you're just better at summarizing it ;) [15:16] haha [15:16] stokachu: here? [15:16] stokachu: no worries if not [15:17] * xnox the new new order is broken, we need an SRU [15:17] Yeah, I have to figure out how to expand more too. :P [15:17] looks like that makes it my turn [15:17] Or just mention every single AA, SRU, etc task. [15:17] lets hire a ghostwriter ;) [15:17] * fixing up update-notifier SRU, apparently our translators are too efficient and translate things that shouldn't be (bug #1003100) [15:17] Launchpad bug 1003100 in update-notifier (Ubuntu Quantal) "package-data-downloader: KeyError: 'paquetes'" [High,Fix committed] https://launchpad.net/bugs/1003100 [15:17] * pushed a bug report to plymouth in Debian, requesting a backport for an API mountall needs [15:17] * mountall bug triage in preparation for uploading to Debian [15:17] * SRU processing generally [15:17] * sponsored sudo merge, and uploaded pkexec (bug #982684) [15:17] Launchpad bug 982684 in sudo (Ubuntu Quantal) "sudo, pkexec don't apply global environment settings from /etc/environment" [Medium,In progress] https://launchpad.net/bugs/982684 [15:17] * ia32-libs SRU for bug #1000541 [15:17] Launchpad bug 1000541 in ia32-libs (Ubuntu Quantal) "ia32-libs-multiarch depends on gstreamer0.10-fluendo-mp3, causing problems when installing packages from partner" [Medium,Fix released] https://launchpad.net/bugs/1000541 [15:17] cjwatson: [15:17] * getting things organized for DebConf [15:17] (done) [15:18] Uploaded ubiquity Python 3 port. Fixed some resulting breakage (decoding Unicode at wrong point). [15:18] Landed per-packageset build scoring. [15:18] Started work on allowing per-pocket archive permissions. [15:18] Verified dh-make SRU. [15:18] Uploaded ubuntu-keyring with new archive and cdimage signing keys. Needs SRUs. [15:18] Resurrected merges.ubuntu.com, with help from IS. [15:18] Lots of merges. [15:18] Fixed stale files being left behind in ftpmaster's germinate output directory. [15:18] Arranged for buildd admins to be able to adjust per-archive build scoring (pending deployment). [15:18] Moved Ubuntu-specific publishing hooks out of Launchpad, in preparation for upgrading them to use the new archive signing key for >=quantal. [15:18] Made a couple of live-installer improvements requested by the server team. [15:18] Various adjustments to cope with recent kernel flavour renamings. [15:18] Removed "Essential: yes" from python-minimal. [15:18] Merged xdeb staged-bootstrap patch. [15:18] Opened main vs. universe discussion with kubuntu-devel (https://lists.ubuntu.com/archives/kubuntu-devel/2012-May/006080.html). [15:18] Gave Daviey some basic archive admin training. [15:18] ☕ [15:19] is that a coffepot or something else that generates steam ? [15:19] U+2615 HOT BEVERAGE [15:19] ah [15:19] so not what my initial thought was then :) [15:19] * xnox ogra_: there is scribe team for ghostwritting ;-) hot beverage! I want an iced tea ;-) [15:20] infinity: FYI the per-archive scoring will basically be: [15:20] archive = whatever [15:20] archive.relative_build_score # fetch attribute to work around bug 662740 [15:20] cjwatson: I was actually more interested in the bullet point about finally dropping python-minimal out of Essential. \o/ [15:20] Launchpad bug 662740 in lazr.restfulclient "Setting an attribute on a shim object without first reading an attribute causes a crash" [Low,Triaged] https://launchpad.net/bugs/662740 [15:20] archive.relative_build_score = whatever [15:20] archive.lp_save() [15:21] infinity: it's still in prio required though ;) [15:21] Oh. [15:21] Less excited. [15:21] ogra_: pile of poo is a different unicode character [15:21] Though I guess dpkg won't complain if you remove it. [15:22] slangasek, heh, yeah, but its small enough to misread it in my xchat :) [15:22] bug #820034 [15:22] Launchpad bug 820034 in Ubuntu Font Family "Expansion: Miscellaneous Symbols and Pictographs U+1F4A9" [Wishlist,Triaged] https://launchpad.net/bugs/820034 [15:23] any more questions about any of the above? [15:23] *grin* [15:23] [TOPIC] Bugs === meetingology` changed the topic of #ubuntu-meeting to: Bugs [15:23] * ogra_ likes the elegant aspect in that bug :) [15:24] bdmurray: anything showing up yet to worry about for 12.10? [15:24] slangasek: no not yet [15:25] there are a few bugs jibel's been escalating to us based on the auto-tests... I need to pin down this debootstrap one today [15:25] I'm about to look at bug 1003443 [15:25] Launchpad bug 1003443 in ubiquity (Ubuntu Quantal) "Ubuntu Quantal Desktop 21120523 failed to install" [Critical,New] https://launchpad.net/bugs/1003443 [15:25] * slangasek nods [15:25] May be an HD fault as the error suggests, but might as well check [15:26] right [15:26] And I'm just fixing bug 1003440 now [15:26] Launchpad bug 1003440 in ubuntu-meta (Ubuntu Quantal) "Unicode characters in language list" [Medium,Triaged] https://launchpad.net/bugs/1003440 [15:26] the debootstrap bug is bug #1001460 [15:26] Launchpad bug 1001460 in sysvinit (Ubuntu Quantal) "preinst fails in d-i" [Critical,Triaged] https://launchpad.net/bugs/1001460 [15:26] which I still have no idea how that's happening :P [15:26] Have you had a chance to compare against a /var/log/bootstrap.log for precise? [15:26] (hints accepted, if someone knows) [15:26] cjwatson: hmm, no, good idea [15:27] The one I have to hand shows makedev successfully running insserv, so not just the set +e => -e thing I pointed out [15:27] But that dates from 2011-12-20 [15:27] Aha [15:27] successfully *running* insserv? [15:28] Here's one from 2012-03-20: [15:28] Selecting previously unselected package makedev. [15:28] Unpacking makedev (from .../makedev_2.3.1-89ubuntu2_all.deb) ... [15:28] update-rc.d: using dependency based boot sequencing [15:28] Can't exec "insserv": No such file or directory at /usr/sbin/update-rc.d line 402. [15:28] update-rc.d: error: insserv rejected the script header [15:28] hmm [15:28]