[00:58] hello everyone [00:58] we will begin the Ubuntu Friendly meeting in roughly two minutes [00:59] hi all! [01:00] #startmeeting ubuntu-friendly [01:00] Meeting started Wed Feb 6 01:00:17 2013 UTC. The chair is cprofitt. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [01: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-friendly Meeting | Current topic: [01:00] #meetingtopic welcome back === 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 | welcome back Meeting | Current topic: [01:00] hello all -- and welcome to the Ubuntu Friendly meeting [01:01] can everyone that is here for the meeting just let me know you are in the room [01:02] o/ [01:02] o/ [01:02] thanks for coming everyone [01:02] our agenda is: [01:02] o/ [01:03] hexr, wiki cleanup, how to improve parts of the Ubuntu Friendly system [01:03] your questions and any advice/ideas you all have [01:03] baloons are you here? [01:03] #link https://wiki.ubuntu.com/UbuntuFriendly/Meetings [01:04] alright... I might have baloons take over if he comes in, but let me tell you a bit about hexr [01:04] #meetingtopic hexr === 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 | hexr Meeting | Current topic: [01:05] #link https://launchpad.net/hexr [01:06] hexr, from my understanding, will potentially make use of the same data Ubuntu Friendly does, but it will do so to see what harware components have been tested [01:06] so it will seek to find out of a specific Nvidia card has been tested or a specific wireless card [01:07] and not look at systems, but components [01:07] #link https://launchpad.net/~hexr-dev/+members#active [01:07] the developers are listed on that page [01:08] I think knowing that could help Ubuntu Friendly add some more functionality to the site -- where people might be able to sort systems based on a desired video card or wireless card... [01:08] for now it is just something for us to know as we move forward [01:09] #topic wiki clean up === 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 | hexr Meeting | Current topic: wiki clean up [01:09] how many of you have had time to look at the wiki page for UF? [01:09] #link https://wiki.ubuntu.com/UbuntuFriendly/ [01:10] would anyone be willing to take on reviewing the pages to ensure that they are up-to-date? [01:11] cprofitt, we can put some icons [01:11] cprofitt, I can do it [01:11] #action SergioMeneses will review the Ubuntu Friendly wiki [01:11] ACTION: SergioMeneses will review the Ubuntu Friendly wiki [01:11] thanks SergioMeneses [01:11] please feel free to ask for help from others as you do that [01:12] if anyone else knows of pages that need updates please let SergioMeneses or me know [01:12] cprofitt, ok [01:12] ok =) [01:12] #topic improvements === 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 | hexr Meeting | Current topic: improvements [01:13] I know from personal experience we have some things to improve moving forward [01:13] phillw: did you want to discuss some of the thoughts you had? [01:13] anyone else? [01:14] #subtopic submissions [01:14] cprofitt: just to mention that you and laptop team are quite similar and I hope there is a good flow of informations between you both :) [01:14] phillw: I would hope so as well. [01:15] One of the things that got me involved was submissions [01:15] right now it is my understanding that submissions are not getting in to UF [01:15] but I am not sure why that is [01:15] phillw: hm, I thought the laptop testing team was for testing Ubuntu on laptops for upcoming releases, not reporting on how well supported laptops are in current releases [01:16] Im totally agree with pleia2, [01:17] pleia2: ergo, one a release is out, that information is available to what is then the 'current' release? [01:17] *once* [01:18] I would like to see two things done to improve in regards to submissions [01:18] phillw: but it would be results for when it was in development, so maybe the graphics card for that one laptop finally did end up working once the release happened, the results would be from when it wasn't working :\ [01:18] for example [01:18] i see, I'll have a chat with the laptop team :) [01:18] pleia2: I agree.. the results from pre-release could would not be invluded in Ubuntu Friendly [01:19] they're both valueable and needed projects, for sure, I just thing they provide different data to different audiences [01:19] s/thing/think [01:19] but the laptop testing team could, upon release, be a group of people who ran the tests for UF [01:19] cprofitt: indeed! [01:20] and from my understanding the database we are pulling from might actually be the same -- but with different criteria for what information is included [01:20] and also differences in how it gets displayed [01:20] it makes sense for both projects to test the same things [01:20] but I would need one of the developers to give me more information on that [01:20] I would like to see two things done to improve in regards to submissions [01:21] 1. some system be put in place to make it easy for those submitting results to know that the results were processed [01:21] if the result was invalid - let them know why [01:22] as a person who has submitted results and never saw my results in UF I know how that can cause someone to lose interest in contributing [01:22] +1 [01:23] 2. I would also want to have a group of people that could look at invalid results to ensure that how the data is being processed is accurate -- that the automated system is not makring valid results as invalid [01:23] this is particularly important as hardware changes... [01:23] failure to test a card reader when there is no such device present should not invalidate results [01:24] any other comments in regards to submissions? [01:24] #subtopic checkbox [01:25] that brings me to one more idea [01:25] this one is not mine, but one that has been discussed in the qa channel [01:25] there may be a need to refine checkbox a bit to allow for a 'simple' test [01:26] or in the case of hexr a test of specific hardware [01:26] the simple test would be an abbreviated test to make sure that basic things like wireless work etc. [01:27] I also had cases when I tested where the automated test 'failed' itself, but I knew the device was working [01:27] I think there should be some sort of mechanism for making a note of that issue built in to checkbox so that changes can be addressed with those issues [01:28] having devices 'fail' a test when they are actually working undercuts people's faith in the process and the results. [01:28] any thoughts in that area? [01:28] o/ [01:28] yes, roadmr [01:29] hello! first, if an automated test fails when the device is working, that means a bug that we'd like to get fixed [01:29] I understand this adds a lot of friction to things, so maybe thinking of ways to make this more effortless may be worthwhile [01:29] * cprofitt nods [01:29] second, the automated tests are in general more reliable but they are also quite valuable in high-volume environments [01:30] if we assume that people can be trusted, we can potentially use manual test cases instead of automated ones that are most unreliable [01:30] even so, it would be good to collect some information that can be automatically analyzed, maybe server-side [01:30] this way we can potentially re-score a submission given the raw data, even after-the-fact [01:30] admittedly there is some trust to an extent already in the testing (you can hear a sound, etc) [01:30] I too, would prefer to get the automated tests working... I think human interaction always introduces some potential for error [01:31] this would however introduce a "we're collecting stuff and sending it up to canonical" factor that some people don't like [01:31] I do like rescoring a submission after the fact [01:31] so this is an area for improvement but we always have the option of doing this manually [01:31] roadmr: in this case I think the 'collecting data' part is voluntary [01:31] at least with checkbox [01:32] cprofitt: yes, well in order to determine what's going on, some extensive logs would need to be collected [01:32] * cprofitt nods [01:32] cprofitt: but keeping the user in control would be the best [01:32] pleia2: hehe, we sought to remove the human factor from that by adding an automated audio_test :) so the computer listens to itself [01:32] could that be an optional part of checkbox -- that a user would opt-in to collecting additional data? [01:32] anyway, those are my ideas on this [01:33] roadmr: does it work? I guess I haven't run it in a bit :) [01:33] I appreciate the feedback and information roadmr [01:33] cprofitt: sure, with the current checkbox architecture it feels a bit complex to do, but we can always change that, we should bend the tool to the needs, not the other way around [01:33] pleia2: as long as you have a microphone and speakers, it works and it's very reliable [01:33] nice [01:34] roadmr: +1 we want to make it easy for people to collect data for this type of use -- improving user experience [01:34] roadmr: do you have any insight as to why results are not getting included in to Ubuntu Friendly or is that outside of your scope? [01:35] cprofitt: I have a pretty good idea why, yes [01:35] could you go a bit in to that for us? [01:36] cprofitt: two components are involved in this, the first is checkbox, which runs the tests, assembles a report and pushes that to launchpad [01:36] the second is the UF website/application, which pulls the reports (submissions) from launchpad and adds the results to the friendly database (what you see in the website) - does the scoring, aggregation and such [01:37] for a submission to appear at all, it needs to contain (and pass) all tests identified as "core" [01:37] the basics for a computer to be usable, if any core tests are failed the submission will not appear in UF [01:37] if it passes the "core" tests, it gets 3 stars, and any additional tests it passes increase its rating, up to 5 stars [01:38] a 5-star rating means that all the components we test work perfectly [01:38] so why would a submission not appear? [01:38] some of the core tests are automated, and checkbox is not very good at 1) telling you one of them failed, and 2) letting you rerun/amend the results [01:39] checkbox itself has no idea of core tests, so it can't tell you "hey, your card reader didn't work and that means you won't make it into UF - please rerun this before submitting" [01:39] is there currenlty anyway for a person who has submitted the test to see their submissions on launchpad? [01:40] that's one reason, the second is that since the UF website needs some love, there may have been a bit of "drift" into the tests checkbox submits and performs, the UF site has not been updated as checkbox whitelists (sets of tests to run) change [01:40] those would be the two main reasons [01:40] cprofitt: there's a cryptic url that you an access to see your submissions, let me find it [01:40] so, it sounds like the key is giving the user some feedback as to if their device failed a core test... and also allowing for them to resubmit [01:40] cprofitt: https://launchpad.net/~/+hwdb-submissions [01:41] cprofitt: yep, again, something that's a bit difficult to do with the current checkbox architecture which is very linear :( think of the difference between linear and non-linear video editing [01:41] in a sense, with checkbox we can only ffwd, rewind, and look at the results at the very end [01:41] * cprofitt nods [01:42] with no/little chance of going back to a specific test. [01:42] exactly... [01:42] it is also my understanding there is no ability to 'pause' a test and come back and pick up where you left off [01:42] there is, but it's very awkward heheh [01:42] roadmr: is there currently any team that reviews the failed submissions? [01:43] what you do basically is murder checkbox, when you restart it does its best to pick up where it left off [01:43] it gives you three choices: rerun the last test, skip to the next one (in case the last test outright crashed the system), or start anew [01:43] * cprofitt nods [01:43] the message is quite terse and the choices are somewhat ambiguous, so most people are/will be confused by this [01:44] cprofitt: reviewing failed submissions, not really, no. It can be done but pretty much the only person who can and knows how to do it is jedimike, by looking at how the UF results importer processed a submission [01:44] he'd have more specifics on how to do it, but it's done on an ad-hoc basis [01:45] roadmr: thanks [01:45] np :) [01:45] I asked because I saw that as part of the launchpad team description [01:45] does anyone else have any questions for roadmr? [01:46] I would like to set an initial priority for the team moving forward [01:46] I think that we have two high value items [01:47] 1. Improving the UF website process so that there is some feedback to the person who submitted the system as to the fact the results were processed but failed [01:47] 2. Documenting the current process - so others can understand it as we start to look at improving it [01:47] are there any other items people see? [01:48] roadmr: would you be willing to procude a flow chart of what you described that we could them use on the wiki? [01:48] just a rough outline of how the process currently flows? [01:49] cprofitt: sure [01:49] cprofitt: there's some documentation (an outline plus more detailed links) here: https://friendly.ubuntu.com/what-is-ubuntu-friendly/ [01:49] #action roadmr will produce a flow chart of the current process [01:49] ACTION: roadmr will produce a flow chart of the current process [01:49] #vote agree that improving feedback on submissions is important in moving foward [01:49] Please vote on: agree that improving feedback on submissions is important in moving foward [01:49] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [01:49] +1 [01:49] +1 received from cprofitt [01:50] +1 definitely heh [01:50] +1 definitely heh received from roadmr [01:50] +1 [01:50] +1 received from chilicuil [01:50] +1 [01:50] +1 received from SergioMeneses [01:50] pleia2: ? [01:50] phillw: ? [01:50] +1 [01:50] +1 received from phillw [01:51] sorry wasnm't sure if i was to vote :) [01:51] #endvote [01:51] Voting ended on: agree that improving feedback on submissions is important in moving foward [01:51] Votes for:5 Votes against:0 Abstentions:0 [01:51] Motion carried [01:52] I think for now we should move towards that; after we get that feedback improved we need to look to make some improvements to checkbox as roadmr mentioned [01:52] any other topics, questions or thoughts? [01:52] o/ [01:52] yes, roadmr [01:53] when is our next meeting? [01:53] hehe, one thing that we *can* potentially do with current checkbox is make it submit directly to a (possibly updated) UF application, so feedback is quicker [01:53] this needs writing a "plugin" and an accompanying web application, so it would need some coordination [01:53] +1 roadmr that should be explored [01:53] we're still on time to make that happen before Ubuntu Feature Freeze, but we'd have to start working soon [01:54] * cprofitt nods [01:54] ideally we sould ask jedimike if there's a way to submit directly to the UF application, because we may not have a lot of manpower to come up with a new one [01:54] sould/should [01:54] SergioMeneses: I would like us to meet again in two weeks -- I think to be fair to some of the UTC [01:54] that may be a quick way to reduce the decoupling between submission and actual result processing [01:55] folks we should have the meeting earlier; though that would require a different person to chair the meeting [01:55] perfect [01:55] roadmr: I know jedimike has spoken to me about that so I will try to touch bases with him about that [01:55] are any of you in the UTC 0/+1 TZ? [01:57] 'im on utc [01:57] alright... I will send a message to the list and see if I can get a person in that TZ to chair a meeting. [01:57] cprofitt: I'm EST (UTC-5) [01:57] phillw: would you be willing to chair a meeting on the 19th? [01:57] roadmr: I am on your TZ as well [01:57] I can if no one steps forward :) [01:57] Im UTC-5 [01:57] phillw: ok, I will send the request to the list and you will be the fall back [01:58] #action next meeting February 19th UTC 17:00 - cprofitt will send a message to the list to get a chair [01:58] ACTION: next meeting February 19th UTC 17:00 - cprofitt will send a message to the list to get a chair [01:58] what time on 19th are you thinking of? [01:59] yeah, 1700 utc would be okay if no one steps forward. [01:59] 17 utc [01:59] * cprofitt nods [01:59] yes, SergioMeneses so noon our time [01:59] cprofitt, it's not problem for me [01:59] thanks SergioMeneses phillw pleia2 chilicuil roadmr for attending. I think this has been very productive for an initial start [02:00] #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 [02:00] Meeting ended Wed Feb 6 02:00:04 2013 UTC. [02:00] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-06-01.00.moin.txt [02:00] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-02-06-01.00.html [02:00] thanks for chairing :) [02:00] thanks for chairing [02:00] cprofitt, thanks to you [02:00] I'm looking forward for helping out, I'll see you in the ml =) [02:00] chilicuil: thanks [02:00] thanks again everyone [02:01] I'm off to bed! 2am here :) [02:01] phillw, good night [02:01] night phillw === shirgall is now known as jrp-afk === mmrazik is now known as mmrazik|lunch === Tonio__ is now known as Tonio_aw === mmrazik|lunch is now known as mmrazik === Quintasan_ is now known as Quintasan === doko_ is now known as doko === lala_ is now known as lalatenduM === davidcalle_ is now known as davidcalle === Tonio_aw is now known as Tonio__ === Tonio__ is now known as Tonio_aw === Tonio_aw is now known as Tonio__ === Tonio__ is now known as Tonio_aw === Tonio_aw is now known as Tonio__ [16:01] * slangasek waves [16:02] #startmeeting [16:02] Meeting started Wed Feb 6 16:02:03 2013 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16: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 [16:02] o/ [16:02] [TOPIC] Lightning round === meetingology changed the topic of #ubuntu-meeting to: Lightning round [16:02] $ echo $(shuf -e barry doko stgraber jodh ev bdmurray slangasek ogra cjwatson xnox stokachu) [16:02] barry bdmurray ogra slangasek doko cjwatson stokachu ev xnox jodh stgraber [16:02] win! [16:02] various ue sprint tasks. file debian bugs 699491 and 699498 (adding -OO to py{,3}compile). more possibly to come there. reviewed stokachu's pytz merge and eventually syncpackaged it (bug 1116418). submitted branch for bug 1112496, with updates to come. worked on py3 whoosh and reached out to debian maintainer. various upstream pypi security discussions. [16:02] Debian bug 699491 in python-defaults "pycompile: Support -OO to suppress docstrings in .pyo files" [Wishlist,Open] http://bugs.debian.org/699491 [16:02] Debian bug 699498 in python3-defaults "python3-defaults: Support -OO to suppress docstrings in .pyo files" [Wishlist,Open] http://bugs.debian.org/699498 [16:02] bug 1116418 in python-tz (Ubuntu) "Sync python-tz 2012c-1 (main) from Debian unstable (main)" [Wishlist,Fix released] https://launchpad.net/bugs/1116418 [16:02] bug 1112496 in python-imaging (Ubuntu Raring) "python-imaging broken in raring" [High,Triaged] https://launchpad.net/bugs/1112496 [16:02] * foundations-r-python33: done. [16:03] * foundations-r-python3-oauth: bug 1077094 marked invalid as the package is going away. bug 1077087 bug 1077089 and bug 1077092 branches in various states of review. [16:03] bug 1077094 in ubuntuone-couch "Switch from python-oauth to python-oauthlib" [Undecided,Invalid] https://launchpad.net/bugs/1077094 [16:03] bug 1077087 in Ubuntu Single Sign On Client "Switch from python-oauth to python-oauthlib" [Undecided,In progress] https://launchpad.net/bugs/1077087 [16:03] bug 1077089 in Ubuntu One Client "Switch from python-oauth to python-oauthlib" [Undecided,In progress] https://launchpad.net/bugs/1077089 [16:03] bug 1077092 in Ubuntu One storage protocol "Switch from python-oauth to python-oauthlib" [Undecided,In progress] https://launchpad.net/bugs/1077092 [16:03] * foundations-r-python-versions: new python-imaging (pillow) package provides py3 support, but see above bugs for backward compatibility fixes needed. in conversations about software-center and session-installer re: wtf to do about python-xapian. we may not be able to replace it :( [16:03] done. [16:03] failed to recreate nexus7 bug 1092734 [16:03] worked on an upstart job to watch for an hp printer to replace update-notifier job [16:03] bug 1092734 in ubuntu-nexus7 "Software updater crashes, cannot update software graphically." [High,Fix released] https://launchpad.net/bugs/1092734 [16:03] removed unused firmware paths from uevent.c in update-notifier [16:03] investigation into bug 1112496 (since comix doesn't work :-() [16:03] bug 1112496 in python-imaging (Ubuntu Raring) "python-imaging broken in raring" [High,Triaged] https://launchpad.net/bugs/1112496 [16:03] investigation into and testing of bug 1096022 [16:03] removed running-unity tag from the ubuntu general apport hook and upstream apport [16:03] bug 1096022 in update-manager (Ubuntu) ""E:Error, pkgProblemResolver::Resolve generated breaks" during lucid->precise universe upgrade of amd64" [Medium,Triaged] https://launchpad.net/bugs/1096022 [16:03] verified P SRU for bug 984276 [16:03] bug 984276 in casper (Ubuntu Quantal) "installing casper on a non live system causes update-initramfs to fail" [High,Fix released] https://launchpad.net/bugs/984276 [16:03] bug triage of update-manager bugs with ubuntu-release-upgrade-core symptom [16:04] improved the speed at which the user parameter works at errors [16:04] resovled an issue on errors where + in package names and versions wasn't being encoded for using in a url [16:04] worked on bucketsystems column family code [16:04] created a new canonistack environment for errors since my previous one had died [16:04] tested and modified bucketsystems column family code in canonistack [16:04] blueprint wise I am working on foundations-r-phased-updates [16:04] ✔ done [16:04] done: [16:04] * various nx7 bugfixes [16:04] * worked with kernel team and diwic to make sound work on boot on the nx7 [16:04] * worked with kernel team to quieten the massive dmesg noise the interactive governor causes [16:04] * held UDW talk about image build infrastructure (will start a wikipage with the notes as base for proper build system documentation)# [16:04] * hunting down livefs breakage (again) [16:05] todo: [16:05] * port nx7 images to xz compression [16:05] * discuss livefs builder situation with infinity (carried over from last week, blocked on builder) [16:05] * fix plymouth vs console-setup racing somehow [16:05] done [16:05] barry: not able to replace python-xapian - hmm, have new requirements emerged, or are the alternatives proving to be inadequate? [16:06] bdmurray: planning to upload that new update-notifier upstart job soon? [16:06] slangasek: probably a conversation to have a bit later ;) [16:07] xnox: speaking of which, is usb-creator getting an upload with the fixed job that's in bzr? [16:07] ogra_: It's been pointed out that, if you plan to use xz, depending on pxz and using that might make things slightly less painful. [16:07] slangasek: yes. today. [16:07] xnox: yay :) [16:07] infinity, like ... being able to use it on the panda itself ? [16:08] slangasek: well, I thought it should really go in hplip and haven't heard from til, additionally waiting for the user session work seems fine. [16:08] ogra_: Yeah. It'll still be slower than gzip, but potentially acceptably so. [16:08] infinity, what holds me back from the switch is that i have to re-work so much stuff for it on both sides if i want nusakan to do xz [16:08] bdmurray: ah, ok [16:08] infinity, great, i'll try it then [16:08] ogra_: Easy enough to take your rootfs tarball and do some local testing on a Panda. [16:08] yep [16:08] ogra_: See if you can find a sweet spot. [16:09] after i fixed the installer from being completely unusable [16:09] ogra_: hunting down livefs breakage> are things currently broken, or currently working? [16:09] * ogra_ notes cjwatson isnt iun -desktop [16:09] slangasek, not working since we dropped a tar option [16:09] i just heard about it now [16:09] ogra_: hmm. eta for fix? [16:10] well, worst case i can roll that back immediately and we lose some memory gains cjwatson introduced [16:10] ogra_: Err, wait. What? The dropping of the tar option from the installer? [16:10] ac100-tarball-installer that is [16:10] ogra_: How did that "break" the livefs? [16:10] infinity, droppiing of -m seems to make tar crazy [16:11] * systemd packaging: slow progress [16:11] * ovmf packaging nearly done; edk2 is clearly not structured with distributions in mind [16:11] * reviewing UbuntuKylin package submissions; will mail the TB to ask this to be an official flavor as soon as the core set is accepted [16:11] i havent digged deeper yet (or seen it myself)... i know about it since the meeting started :P [16:11] (done) [16:11] ogra_: Is there a bug or any sort of analysis? [16:11] well it worked without -m, but not "without -m and adding --warning=no-timestamp" or so the report says. [16:11] infinity, only chat in #ubuntu-desktop yet [16:13] doko: your turn [16:13] - fix ftbfs for older gcc releases (changed kernel headers, missing struct siginfo) [16:13] - llvm/clang updates [16:13] - upload pillow for python3 [16:13] - openjdk security update [16:13] - FOSDEM [16:13] (done) [16:13] will follow-up on FOSDEM later [16:14] slangasek, oh, the "hunting down livefs breakage" from my report was supposed to be "hunting down livefs builder breakage" its unrelated to the current issue [16:14] (was just a coincident that you asked while i was told its broken :) ) [16:15] ah, cjwatson is off this afternoon, so stokachu: [16:15] ok [16:15] ogra_: hmm! [16:15] Followed up bug 1052038, awaits verification [16:16] bug 1052038 in eCryptfs "ecryptfs_fnek_sig missing when login at the same time on cron session close" [Medium,In progress] https://launchpad.net/bugs/1052038 [16:16] Need a little more information on bug 923876 if we are planning on applying this to precise and quantal? Or whats the overall consensus on removing old kernels on a system during upgrades? [16:16] bug 923876 in apt (Ubuntu) "FR: Limit and clean-up kernel images and headers automatically in LTS" [Wishlist,Fix released] https://launchpad.net/bugs/923876 [16:16] Did my first sync package request though im not sure how to tell if I got credit for the request or not other than looking at the bug itself. [16:16] (done) [16:16] slangasek, the builder was off for two days again this week ... thanks to elmo and infinity its back in business though [16:17] stokachu: https://launchpad.net/~adam-stokes/+synchronised-packages [16:17] (it seems to always die on saturdays ... probably going out to party on weekends or so ) [16:17] xnox: ah ok sweet [16:17] ogra_: It's probably just cause it can't count: http://sourceware.org/ml/glibc-cvs/2013-q1/msg00115.html [16:17] sourceware.org bug 2013 in libc "memccpy() gives inconsistent results on mmapped files" [Normal,Resolved: fixed] [16:17] oha [16:17] "Fix the value of TWO" [16:18] xnox: there we go :D [16:18] it couls just count one by one then :P [16:18] *could [16:18] re: apt removing older kernels is starting to make its way through internally so any thoughts on that would be appreciated [16:19] stokachu: Oh, crap. So, yeah. I was meant to backport the apt stuff last week, and got distracted by other work. [16:20] stokachu: I can still do that today, and maybe Colin will accept it. [16:20] - Feedback to Martin's code review of the grouped reports branch of apport. [16:20] This, if you don't recall, is for showing system internal errors as part of [16:20] the next regular application error. [16:20] - Code review for Brian. [16:20] - Wrote a tool to bootstrap the postgres database for local copies of Errors. [16:20] - Taught the prodstack-prep branches to talk to Swift natively when running on [16:20] canonistack/prodstack. [16:20] - Added the bulk of the Canonical engineering teams to the ACL for stacktrace [16:20] access on errors.ubuntu.com. Added code to Errors and the prodstack charms to [16:20] manage further additions to the ACL with minimal code changes. [16:20] - Big improvements to the average errors per calendar day graph over the [16:20] weekend. The text for the milestones and dates finally all fits. We now also [16:20] set the domain to (0, 0.4) so the difference between 12.04 and 12.10 should [16:20] be much more discernable. There's a few more improvements to be made that [16:20] I'll fit in while other work compiles or in the evening. I've also cleaned up [16:20] the call stack representation in the most common problems table. [16:20] - More fixes to whoopsie. Trying to get a new build out, but the tests are [16:20] failing only in sbuild due to leaks detected by valgrind. Fixed one already, [16:20] so this new memcheck test addition is already proving useful. [16:20] - If we can move the connectivity check and inotify watch into upstart, we [16:20] save about 0.8 MB of memory in whoopsie (though admittedly whoopsie no [16:20] longer runs all the time and its memory usage becomes less important). [16:20] - Not pulling in CURL takes us down to running in 200K, but we kind of need [16:20] that :). I suspect its the SSL stuff taking up the lion's share. [16:20] - More fixes to the prodstack charms. JuanJo is making good headway on getting [16:20] these deployed to stagingstack. [16:20] - Trying to build the universe to get a recent version of python-swiftclient [16:20] working in precise. [16:20] (done) [16:20] infinity: ok no worries i was just pinged internally about this yesterday so its not really heating up yet and your confirmation of it is good enough [16:21] thanks [16:21] * Short week due to Fosdem Fri-Mon [16:21] - loads of people met and conversations held [16:21] - everyone is talking about aarch64 [16:21] - everyone is waiting for aarch64 hw [16:21] - interesting talks on init systems & [e]udev [16:21] - keysigning... [16:21] . [16:21] * Last week, poked pyo optimisation with barry a little. [16:21] I want to run one last test (i think i didn't have everything [16:21] without docstrings), but it looks likes on currently idle python [16:21] processes there isn't much ram savings. [16:21] * Also gave a talk on making/fixing packages to cross-build. Need to [16:21] convert to blog post / packaging guide section. [16:21] . [16:21] * Precise: [16:21] infinity: will this be for quantal and precise? [16:21] Uploaded SRU for 2 clustered LVM issues. Not critical for 12.04.2 as [16:21] clvm is not on the server cds. bug #833368 and bug #988881 . [16:21] . [16:21] bug 833368 in lvm2 (Ubuntu Precise) "clustered lvm commands fail with "activation/monitoring=0 is incompatible with clustered Volume Group" error" [High,In progress] https://launchpad.net/bugs/833368 [16:21] * foundations-r-arm-usb-creator-fastboot-support: [16:21] bug 988881 in lvm2 (Ubuntu Precise) "/etc/init.d/clvm status exitcode always 0" [Medium,In progress] https://launchpad.net/bugs/988881 [16:21] udisks2 backend created a few sticks now. Porting/Testing last [16:21] pieces in the -helper and then we can drop udisks from CD. [16:21] . [16:22] * foundations-r-software-raid [16:22] mdadm initial merge ready, should upload by the end of the week. [16:22]