[01:01] <Sarvatt> soren, mdz, stgraber: just noticed xorg-server isn't on the micro release exception wiki (https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions) but http://www.bryceharrington.org/files/xserver-mre.txt happened in a TB meeting? it probably fell through the cracks?
[01:03] <Sarvatt> not sure if it should be in approved or provisional so dont want to edit the wiki directly
[01:05] <stgraber> Sarvatt: added
[01:05] <Sarvatt> stgraber: much appreciated!
[10:06] <logothing> Hi
[13:00]  * stgraber waves
[13:00]  * ogra_ shores
[13:01] <stgraber> ondra has a conflicting meeting but we had a quick chat so I have a status update for him
[13:01] <ogra_> there seems to be a new error in the recovery images that should rather be tagged as warning or info ...
[13:02] <ogra_> E:Can't open /cache/recovery/ubuntu_command
[13:02] <ogra_> it seems to do no harm but people seeing it get scared
[13:03] <stgraber> heh, yeah, that probably shouldn't be an error as we support both /cache/recovery/ubuntu_command and /cache/recovery/command so neither should cause an error
[13:03] <ogra_> yeah
[13:04] <ogra_> stgraber, hmm, so is it only us two ?
[13:05] <stgraber> ogra_: I pinged barry in #ubuntu-devel, no response so far...
[13:05] <ogra_> yup, saw that
[13:06] <stgraber> waiting a couple more minutes, if he doesn't show up, it'll be a very short meeting :)
[13:06] <ogra_> yeah
[13:07] <ogra_> well, not much to report from my side anyway ... flipped is default, we're working on getting the ports over
[13:07] <stgraber> hey barry
[13:07] <barry> hey, sorry for lateness
[13:07] <ogra_> np :)
[13:08] <stgraber> ok, so we've got everyone who got actions from last week, so let's start :)
[13:08] <stgraber> last week: stgraber trying to get image update code completed this week; ogra/sergiusens/rsalveti flipping images today; ondra/rsalveti/sergiusens/stgraber looking at including static gpg build w/o NEON in the recovery initrd; barry pinging design team on update UI; barry wrapping up download service API with mandel
[13:08] <stgraber> on my side, I now have an import-cdimage script on nusakan which imports and convert the dailies into system-image
[13:09] <stgraber> I'm aware of at least one bug in my code but it only triggers when we do more than one build in a day, so I'm waiting for the next occurence to fix it
[13:09] <ogra_> do you plan to start building them parallel ?
[13:10] <stgraber> ogra_: the script simply converts your dailies into system-image compatible files directly on nusakan, that way we don't slow down the build process (it can be done at any time), doing that directly on the livefs buildds would add around 45min to the build process because of xz
[13:10] <stgraber> ogra_: so we'll just start building them clean from the source once we have the new buildds and/or can retire cdimage for our images
[13:11] <ogra_> retire cdimage ?!?
[13:11]  * ogra_ doubts there are any such plans
[13:11] <stgraber> I've also been testing that on my Nexus4, the images themselves work, my basic upgrader code in recovery works too, the only problem is the client failing to download the files
[13:11] <ogra_> and even with the highbank builders xz wont be actually fast
[13:12] <ogra_> i think we should leave that bit to cdimage on x86
[13:12] <barry> stgraber: i hope that will go away when we switch to the new download service, though it's still worth investigating the timeouts
[13:12] <stgraber> ogra_: why would we keep stuff published in 3 different formats on two different web servers when all the supported devices (those we publish on cdimage today) use system-image?
[13:12] <ogra_> adding time to the builds is pretty awkward from the point on where we cant really upgrade packages to get fixes in
[13:13] <stgraber> barry: currently it means I have no way of testing the client or the upgrader, so I'd really want this to be bumped as a high priority and not wait for the download service
[13:13] <ogra_> you cant feed the system-image server from cdimage ?
[13:13] <stgraber> barry: FWIW I ran the client around 50 times yesterday (in a while loop) and it never succeeded, but downloaded over 10GB, so it's not a network issue
[13:14] <ogra_> i would simply like to keep the builds centralized
[13:14] <ogra_> and have changes to the build system be picked up automatically, which the cdimage setup guarantees
[13:14] <barry> stgraber: https://bugs.launchpad.net/ubuntu-system-image/+bug/1199361
[13:15]  * ogra_ thought cjwatson's cdimage rewrite in python was exactly in preparation for such stuff
[13:15] <stgraber> ogra_: I'm currently feeding builds to system-image from cdimage but at least in my head and in Steve and lool's too, it's a temporary thing, once we switch phablet-flash over to using system-image, we're planning to stop publishing to cdimage
[13:16] <barry> stgraber: anything you can add to the bug report will help, but note that LP: #1156704 is blocking further progress
[13:16] <stgraber> ogra_: cjwatson was perfectly aware that system-image would eventually replace that code
[13:16] <ogra_> stgraber, i dont care where we publish, but i do massively care where and how we build
[13:16] <stgraber> ogra_: anyway, the livefs builds will still be managed by cdimage, it's just the publishing that'll happen in /srv/system-image.ubuntu.com/www/full instead of /srv/cdimage.ubuntu.com/www/full/
[13:16] <ogra_> ah
 you cant feed the system-image server from cdimage ?
[13:17] <stgraber> ogra_: both cdimage and system-image are managed from nusakan by the cdimage account
[13:17] <ogra_> that answers this :)
[13:17] <ogra_> yeah, no issue with that
[13:17] <ogra_> i understood you wanted to build on the system image server :)
[13:17] <ogra_> (duplicating cdimage etc)
[13:17] <stgraber> ogra_: well, it depends on what we call "cdimage" :) I was saying it's a waste to import from cdimage.ubuntu.com/... when we can just directly publish to system-image.ubuntu.com, but yeah, same server ;)
[13:18] <stgraber> good, so sounds like we agree then :)
[13:18] <ogra_> yeah, i dont care what the webserver is in the end :)
[13:18] <ogra_> we do :)
[13:18] <stgraber> barry: can't you just do your work in a chroot without python-configparser?
[13:19] <barry> stgraber: this blocks the test suite
[13:20] <stgraber> barry: how so? I thought that was caused by python-configparser being installed, why would it also fail when it's not?
[13:21] <barry> stgraber: well, i guess a chroot without that package would be workable but only in the short term.
[13:22] <stgraber> sure, the virtualenv bug is a problem and needs to be fixed, I was just saying that it's not a blocker for us, system-image doesn't build-dep or dep on anything that brings python-configparser
[13:22] <stgraber> so as long as your run tox in an environment that doesn't have python-configparser, you're fine
[13:23] <stgraber> barry: did you make any progress on the download service API with mandel?
[13:24] <stgraber> I guess that was API specing rather than implementing, right?
[13:24] <barry> stgraber: yes.  he updated the wiki with the dbus api spec for the service and i think it looks good.  he's working on the implementation and packaging, the latter which i've offered to help if needed.  i want to get the service into the archive asap
[13:25] <stgraber> ok, cool
[13:25] <barry> https://wiki.ubuntu.com/ImageBasedUpgrades/Downloader
[13:27] <stgraber> so notes: stgraber => work on the upgrader code, test/integrate the client in dailies, fix bugs on system-image; barry => fix a downloader timeout bug, update default config, update client in the archive, help mandel with packging the DL service; ogra => fixing issues with flipped, helping ports move to the new model; ondra => update recovery to make missing ubuntu_command a non-error
[13:27] <stgraber> missed anything?
[13:28] <ogra_> nope
[13:28] <stgraber> barry: ?
[13:29] <barry> lgtm
[13:29] <stgraber> perfect
[13:29] <stgraber> thanks to the two of you for attending
[13:29] <ogra_> :)
[13:29] <barry> :)
[13:29] <ogra_> thanks for running stgraber
[13:29] <ogra_> and good luck with your paperwork now :)
[13:29] <barry> indeed! :)
[13:30] <stgraber> haha, yeah, nothing I like more than waiting in line at a government office...
[16:00] <yolanda> hi all
[16:00] <yolanda> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Jul  9 16:00:13 2013 UTC.  The chair is yolanda. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> 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:00] <Daviey> o/
[16:00] <yolanda> #topic Review ACTION points from previous meeting
[16:00] <yolanda> arosales to carry out post-meeting procedure (minutes, etc) documented at https://wiki.ubuntu.com/ServerTeam/KnowledgeBase for meeting of 25 June
[16:01] <yolanda> any update?
[16:01] <jamespage> o/
[16:02] <roaksoax> o/
[16:02] <yolanda> Daviey to speak to Percona about Saucy inclusion
[16:03] <Daviey> yolanda: 25 June still not done.  I'll work with arosales after this
[16:03] <Daviey> yolanda: I haven't spoken to percona this week.  Will do THIS week
[16:04] <yolanda> ok, let's leave as pending then
[16:04] <yolanda> any other pending topics?
[16:04] <Daviey> Nope
[16:04] <yolanda> #topic Saucy Development
[16:04] <yolanda> #link https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[16:05] <yolanda> #subtopic Release Bugs
[16:05] <yolanda> Daviey, any update with that?
[16:05] <arosales> sorry, joined a little late
[16:05] <arosales> here now
[16:05] <Daviey> First.. the Release Schedule
[16:05] <Daviey> DebianImportFreeze / Alpha2ish
[16:05] <Daviey> Would be good to be up to date on sync's and merges for then.
[16:06] <Daviey> rbasak has graciously fixed my delta report
[16:06] <arosales> yolanda, I think rbasak put in a new process that he is carrying forward. I will ensure the wiki has the minutes from my chair'ing for historical reasons
[16:06] <Daviey> http://people.canonical.com/~rbasak/delta.html
[16:06] <rbasak> Note: I haven't cronned that. I generated it earlier.
[16:06] <Daviey> We should try over this next week to reduce our delta with Debian
[16:07] <yolanda> rbasak, are you doing something automatic?
[16:07] <Daviey> #ACTION rbasak to land delta report to lp:ubuntu-reports, Daviey to deploy
[16:07] <meetingology> ACTION: rbasak to land delta report to lp:ubuntu-reports, Daviey to deploy
[16:07] <rbasak> yolanda: I intend to, but I haven't done it yet.
[16:07] <rbasak> ack
[16:08] <yolanda> i could help a bit with merges and syncs this week also
[16:08] <jamespage> Daviey, +1 to that
[16:09] <Daviey> Shall we look at, http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:09] <Daviey> bug 1124384
[16:09] <Daviey> smoser: Are we expecting a cloud-init upload soon?
[16:09] <smoser> yes.
[16:09] <Daviey> I noticed that Debian is carrying a delta
[16:10] <smoser> that one is fixed in raring ..
[16:10] <smoser> oh?
[16:10] <Daviey> smoser: http://ftp-master.metadata.debian.org/changelogs//main/c/cloud-init/cloud-init_0.7.2-1_changelog
[16:11] <Daviey> Might be worth checking if we can fold anything interesting
[16:11] <Daviey> bug 1196921
[16:11] <smoser> yeah. thanks.
[16:12] <Daviey> rbasak: You had thoguths on transitions such as this.  Is it worth just uploading a new rrdtool and see what breaks?
[16:12] <Daviey> (i feel evil suggesting that)
[16:13] <Daviey> adam_g: bug 1183634 ?
[16:13] <rbasak> Sorry poor connection here
[16:13] <adam_g> Daviey, progressing, slowly. security team just started moving on the python-markdown MIR
[16:14] <adam_g> Daviey, should be good once thats done
[16:14] <Daviey> Super!
[16:14] <Daviey> I see they last touched it 20 hours ago.. so making progress
[16:15] <Daviey> bug 1170393, jamespage
[16:15] <jamespage> catching up on openstack this week
[16:16] <rbasak> Daviey: I don't follow. It looks like we're up-to-date with Debian on rrdtool?
[16:17] <Daviey> rbasak: No, that isn't the problem.. there is a lua transition needed, and that package is marked as depending on it
[16:17] <Daviey> Feels very similar to the ruby and mysql issues we had.. Keeps getting deferred, then someone does it blindly.. and that prompts issues to be flushed out.
[16:18] <rbasak> Daviey: oh, so a no change rebuild?
[16:18] <Daviey> rbasak: yah
[16:18] <rbasak> I have less objection to someone blindly doing a no change rebuild, since that shouldn't introduce any new issues that didn't already exist
[16:18] <rbasak> If I were doing it I'd test it first though
[16:19] <Daviey> ok
[16:19] <Daviey> zul: Do you know why apache2 is still held?
[16:19] <Daviey> (saucy-proposed)
[16:20] <rbasak> There's a big pile of breakages it would cause. I looked today - it looks like almost everything is waiting on Debian
[16:20] <zul> Daviey:  yeah one packaging is blocking it, its being fixed in debian
[16:20] <Daviey> zul: which package?
[16:20] <rbasak> zul: it looked like many more than one to me
[16:20] <rbasak> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[16:20] <zul> Daviey:  dont remember off the top of my head
[16:21] <rbasak> I counted 62 source packages in there
[16:21] <zul> uwsgi
[16:21] <Daviey> Does someone want to volunteer to get to grips of proposed migration issues this week?
[16:22] <Daviey> I'm seeing more server seed issues on excuses.html than we'd like
[16:22] <Daviey> zul: Fancy it  ^^ ?
[16:23] <zul> Daviey:  sure
[16:23] <zul> Daviey:  not really but ill do it
[16:23] <Daviey> #ACTION zul has willfully volunteered to review and document what is blocking server related saucy-proposed migration excuses, with joy.
[16:23] <meetingology> ACTION: zul has willfully volunteered to review and document what is blocking server related saucy-proposed migration excuses, with joy.
[16:23] <yolanda> !
[16:24] <yolanda> Daviey, any more bugs to review?
[16:24] <Daviey> bug 1196979 , jamespage - can you summarise ?
[16:24] <jamespage> transition
[16:24] <jamespage> I have it on my list
[16:24] <Daviey> ok, thanks
[16:25] <Daviey> rbasak: bug 1031680 , been a bunch of discussion. Do we have a plan?
[16:26] <rbasak> Daviey: I'm happy with the plan xnox described on the ML. It needs someone to actually do it, though.
[16:26] <Daviey> rbasak: ok, thanks.
[16:26] <Daviey> Any more bugs?
[16:26] <Daviey> Blueprints.. Don't think we need to review them this week.
[16:27] <Daviey> Would like to check on.. juju-core, is there any progress on getting an update into saucy ?
[16:27] <Daviey> jamespage: ^ ?
[16:27] <jamespage> Daviey, I pinged mgz today - 1.1.1 of golang is now in saucy (I jumped the Debian maintainer and pushed a point release in myself)
[16:27] <Daviey> Super!
[16:28] <jamespage> mgz is going to work on that with davecheney ~soon
[16:28] <jamespage> end of this week latest I hope
[16:28] <Daviey> A General note.  Please make sure that if you are working on something, anything, it is captured as a WI.
[16:28] <jamespage> ^^^ that all is
[16:28] <Daviey> There are too many 0% progresses for the cycle and a 100% (!)
[16:28] <jamespage> also remember a work item can be a bug linked to a blueprint as well
[16:29] <Daviey> EOF, thanks
[16:29] <yolanda> ok
[16:29] <yolanda> #topic Ubuntu Server Team Events
[16:29] <yolanda> i received emails for OpenStack summit and free registration codes
[16:30] <yolanda> shall we register so soon?
[16:31] <Daviey> yolanda: Yes, do register :)
[16:31] <Daviey> I haven't done so yet.
[16:31] <yolanda> ok
[16:31] <Daviey> But a bunch of ~ubuntu-server people are going to Openstack Summit in Honk Kong, November.
[16:31] <Daviey> But a little early to declare it
[16:32] <yolanda> any other events?
[16:32] <arosales> OSCON coming up at towards the end of the months
[16:32] <Daviey> None in the short term, i don't think
[16:32] <arosales> OSCON = ~july 22~
[16:33] <yolanda> #topic Weekly Updates & Questions for the QA Team (plars)
[16:33] <psivaa> I am in for plars for this week
[16:33] <psivaa> Just a couple of bugs affecting the smoke tests, jdstrand and apw were working on them
[16:33] <psivaa> bug #1197484 and bug #1195710
[16:33] <psivaa> :)
[16:33] <smb> The last one being worked on by apw
[16:34] <psivaa> jdstrand said he will look into the first one
[16:34] <yolanda> ok
[16:34] <yolanda> anything else for psivaa?
[16:34] <psivaa> that's all from us this week
[16:35] <yolanda> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:35] <smb> Not much from me. Xen-4.3 is in progress and the usual funny bugs.
[16:35] <yolanda> any question for smb?
[16:36] <yolanda> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:36] <rbasak> Nothing new to report. Any questions for me?
[16:36] <doko> jamespage, are you involved with the Debian go policy?
[16:36] <doko> are don't you care?
[16:36] <Daviey> rbasak: Looking forward to learning what comes out of Connect when you return :)
[16:37] <jamespage> doko, not really but I think i may have to start....
[16:37] <yolanda> #topic Open Discussion
[16:37] <doko> jamespage, cool, lets chat about this next week
[16:37] <yolanda> any other topics to brig?
[16:37] <yolanda> bring?
[16:38] <jamespage> doko, yes - lets do that
[16:38] <yolanda> anything else?
[16:39] <yolanda> ok, so let's finish
[16:39] <yolanda> #topic Announce next meeting date and time
[16:39] <arosales> thanks for chairing yolanda :-)
[16:39] <yolanda> next meeting will be on 16th of July
[16:39] <yolanda> adam_g will be chairing
[16:39] <jamespage> so long as yolanda gets all the paper work out by then :-)
[16:40] <yolanda> sure :)
[16:40] <yolanda> #endmeeting
[16:40] <meetingology> Meeting ended Tue Jul  9 16:40:15 2013 UTC.
[16:40] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-07-09-16.00.moin.txt
[16:40] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-07-09-16.00.html
[16:40] <rbasak> Thanks for chairing yolanda!
[16:40] <yolanda> thanks for your patience! :)
[16:40] <yolanda> Daviey, thanks for the help!
[16:41] <Daviey> thanks yolanda, you did great
[17:00] <jsalisbury> #startmeeting
[17:00] <meetingology> Meeting started Tue Jul  9 17:00:18 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> 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
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <ppisati> o/
[17:00] <cking> o/
[17:00] <smb> o/
[17:00] <henrix> o/
[17:00] <apw> o/
[17:00] <sforshee> o/
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> nothing to report this week
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:01] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
[17:01] <ogasawara> || apw       || foundations-1305-arm64-bringup || 1 work item ||
[17:01] <ogasawara> || ogasawara || mobile-power-management        || 1 work item ||
[17:01] <ogasawara> || ppisati   || foundations-1305-kernel        || 1 work item ||
[17:01] <ogasawara> || sforshee  || foundations-1303-phablet-kernel-maintenance || 1 work item ||
[17:01] <ogasawara> ||           || pm-system-policy               || 2 work items ||
[17:02] <ogasawara> || smb       || servercloud-s-virtstack        || 1 work item  ||
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
[17:02] <ogasawara> Our master branch for Saucy continues to track v3.10 final.  We'll
[17:02] <ogasawara> continue in this holding pattern until the v3.11-rc#'s begin appearing
[17:02] <ogasawara> and we are able to evaluate moving to v3.11 for Saucy.
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara> Thurs July 25 - Alpha 2 (opt in)
[17:02] <ogasawara> Thurs Aug 22 - 12.04.3
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's (bjf)
[17:03] <bjf> The current CVE status can be reviewed at the following link:
[17:03] <bjf>   * http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid/Hardy (bjf/henrix/sconklin)
[17:03] <bjf> Status for the main kernels, until today (July 2):
[17:03] <bjf>   *   Lucid - Prep'ing
[17:03] <bjf>   * Precise - Prep'ing
[17:03] <bjf>   * Quantal - Prep'ing
[17:03] <bjf>   * Raring  - Prep'ing
[17:03] <bjf> Current opened tracking bugs details:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <bjf> For SRUs, SRU report is a good source of information:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <bjf> Future stable cadence cycles:
[17:03] <bjf>   * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
[17:03] <bjf> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <jsalisbury> Thanks everyone
[17:04] <jsalisbury> #endmeeting
[17:04] <meetingology> Meeting ended Tue Jul  9 17:04:45 2013 UTC.
[17:04] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-07-09-17.00.moin.txt
[17:04] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-07-09-17.00.html