[02:00] <nhaines> #startmeeting
[02:00] <darthrobot> Meeting started Mon Apr 18 02:00:25 2016 UTC.  The chair is nhaines. Information about MeetBot at https://wiki.ubuntu.com/meetingology.
[02:00] <darthrobot> 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
[02:00] <nhaines> It's meeting time once again!
[02:01] <nhaines> #topic Announcements
[02:01] <nhaines> Ubuntu 16.04 LTS will be released on April 21, 2016, and it includes Snappy, which is going to lead to a single, unified code base on all Ubuntu platforms in the future.
[02:02] <nhaines> So it's exciting times ahead.
[02:02] <nhaines> #topic Other business
[02:02] <nhaines> Does anyone have anything else they'd like to share this week?
[02:03] <DonkeyHotei> wait, so dpkg is gone?
[02:03] <nhaines> No.  Snappy is here.
[02:03] <nhaines> Or `snap` is the command, I think.
[02:03] <DonkeyHotei> snappy replaces dpkg, no?
[02:03] <nhaines> No.
[02:04] <nhaines> The two are unrelated.
[02:06] <pleia2> still struggling to find a venue for the SF release party
[02:06] <pleia2> so it definitely won't be on release day, maybe some time later in May
[02:07] <nhaines> pleia2: tell jono to wave his magic wand!
[02:07] <pleia2> I haven't heard from him, nhandler said he was going to look into it
[02:07] <nhaines> On the bright side, that does give you the opportunity to request Ubuntu DVDs!
[02:07] <pleia2> or usb sticks, apparently
[02:07] <nhaines> And by DVDs I mean USB sticks.
[02:08] <nhaines> And no worries about getting Ubuntu 14.04 LTS ones by accident because those ran out two months ago.  :)
[02:10] <pleia2> haha, so I've heard
[02:10] <nhaines> I briefly considered what a release party down here would look like, but I've been so busy the last month that it hasn't really gone anywhere.
[02:11] <nhaines> So maybe in a week or two I can look into it if no one else has!
[02:12] <pleia2> our last LTS one went well, I think it might turn out ok up here to do ours a bit late
[02:13] <nhaines> Yeah, sometimes delayed parties can be fun, and especially with snappy around, there will be lots to talk about.
[02:13] <nhaines> And really, May is still in the "launch period."
[02:14] <nhaines> Okay, well, if there's nothing more, I guess that's meeting's end.  :)
[02:14] <pleia2> thanks for chairing :)
[02:16] <nhaines> Thanks.  :)  I hope to be more present in general in a week or two.
[02:16] <nhaines> #endmeeting
[02:16] <darthrobot> Meeting ended Mon Apr 18 02:16:22 2016 UTC.
[02:16] <darthrobot> Minutes:        http://ihas.5cat.com/~darthrobot/ubuntu-us-ca/2016/ubuntu-us-ca.2016-04-18-02.00.moin.txt
[02:20]  * ianorlin missed the meeting but did not really have anything to say
[02:32] <nhaines> ianorlin: you were with us in spirit.
[03:01] <nhaines> I think I'll reinstall Ubuntu on my desktop computer this week.  I like doing clean installs around LTS time.
[03:05] <DonkeyHotei> i prefer to upgrade
[03:08] <nhaines> I've already upgraded to xenial.
[03:08] <nhaines> I'm hoping that lxc might help keep my system cleaner this time around, unless Ubuntu Snappy Personal Desktop gets there first.
[03:09] <nhaines> Although technically that's still what I said.


[00:08] <cwayne_> rvr, thanks for catching
[00:08] <rvr> cwayne_: You're welcome
[00:20] <cwayne_> rvr, so would it just be Fotos de Telegram then?
[00:20] <rvr> cwayne_: Right
[00:52] <cwayne_> rvr, fix pushed, building image now
[00:52] <rvr> cwayne_: Ack
[01:18] <cwayne_> rvr, image ready for you tomorrow morning :)  ill flash now and give it a looksie
[01:19] <rvr> cwayne_: Oki doki! :)
[01:26] <cwayne_> rvr, looks good, please shoot me an email when it's ready (I'll start early tomorrow so I can push as soon as we're ready)
[01:26] <rvr> cwayne_: I just flashed it
[01:28] <rvr> Mis fotos de Facebook, that's +1
[01:28] <rvr> Now login in Telegram
[01:29] <rvr> Fotos de Telegram
[01:30] <rvr> Mensajes recientes
[01:30] <rvr> cwayne_: It's ok
[01:30] <cwayne_> :D
[01:30] <cwayne_> so what happens now, can I push, or do I need to wait for sil?
[01:31] <rvr> I don't know! :)
[01:32] <cwayne_> I guess I can't push without a +1 from someone on landing team..
[01:32] <rvr> To which channel is the image being pushed?
[01:33] <cwayne_> 14.09-proposed
[01:33] <rvr> robru: You there?
[01:33] <robru> rvr: hi
[01:33] <rvr> robru: ^
[01:34] <robru> rvr: what? Are you talking about a silo?
[01:34] <rvr> robru: cwayne_ wants landing team approval before pushing the proposed-customized image to 14.09-proposed
[01:35] <robru> rvr: cwayne_: well I'm not aware of any reason why not...
[01:37] <cwayne_> good enough for me
[01:37] <rvr> robru: cwayne_ will blame you if he breaks Internet ;)
[01:37] <cwayne_> rvr, just to double check, you checked the functioanlity and stuff earlier right? i.e. you weren't *just* testing i18n
[01:37] <robru> rvr: cwayne_ I'm a bit confused, are you talking about printing an image?
[01:38] <cwayne_> robru, 'promoting' the custom tarball, so it gets pulled into 14.09-proposed
[01:38] <rvr> cwayne_: Some minutes ago, I logged into Telegram, and checked that the photos and messages are displayed both in Today's scope and in Photos scope
[01:38] <cwayne_> from 14.09-proposed-customized
[01:39] <rvr> cwayne_: Earlier today, in previous images: «Exploratory testing with Today, NearBy, Photos, Telegram and Fitbit scopes. Logged in Facebook Photos, Telegram, FitBit, Instragram and Flickr. All of these are ok.Exploratory testing with Today, NearBy, Photos, Telegram and Fitbit scopes. Logged in Facebook Photos, Telegram, FitBit, Instragram and Flickr. All of these are ok».
[01:39] <robru> cwayne_: yeah I'm not really up to speed with those kinds of decisions... Maybe check with pmcgowan if you really need some kind of approval.
[01:40] <cwayne_> rvr, ah great, and the only things that've changed since then is translations, great
[01:40] <rvr> cwayne_: You can leave an email to sil2100 and jibel for tomorrow if you prefer
[01:40] <rvr> cwayne_: I guess sil2100 can promote from one channel to another, right?
[01:40] <rvr> And that's a quick process, isn't it?
[01:42] <cwayne_> yeah it's very quick, I'll just shoot an email to sil and do it tomorrow morning, should've gotten a +1 from sil earlier, but oh well
[01:46] <rvr> Time to sleep, see you tomorrow!
[02:10] <imgbot> [03:40] <imgbot> [03:40] <imgbot> [04:11] <robru> veebers: ah, no vivid silos available at the moment. I sent an email asking people to clean up some silos that seemingly aren't being used, hopefully one will free soon
[04:12] <veebers> robru: ack, thanks :-) I'll make sure the rest of the team is aware so that when possible we start testing (once we get a silo)
[04:19] <veebers> robru: hmm, when I tried to close the spreadsheet page it complained that some data might not get saved, also while filling out the row it also complained a couple of times about fatal errors
[04:19] <veebers> do I need to double check anything?
[04:19]  * veebers eyeballs the row
[04:19] <veebers> seems good to me
[04:19] <robru> veebers: yeah i just got that as well, it seems the spreadsheet is imploding again. Not much we can do
[04:21] <veebers> ack, thanks robru. As long as it wasn't my fault :-)
[04:21] <robru> veebers: nope, this is well known pain and misery
[04:21] <robru> veebers: you're welcome
[07:17] <dbarth_> good morning trainguards; i have an oxide 1.5.6 release update on line 64
[07:18] <seb128> hey there, is there any plan to free vivid silos?
[07:39] <Mirv> dbarth_: seb128: we're still out of silos and 5 lines waiting for silo
[07:40] <seb128> Mirv, right, hence my question
[07:42] <seb128> Mirv, we have several dirty silos and experimental ones (like the new qt)
[07:42] <seb128> maybe some can be reclaimed to make space for pending landings?
[07:44] <Mirv> 3 of the waiting ones are ubuntu-system-settings while there's already 006 with u-s-s too. I wonder if any of those could be combined.
[07:44] <seb128> Mirv, oh, in fact 11 seems available, maybe it can be assigned :-)
[07:44] <Mirv> seb128: not without pinging, and with yesterday's poll none could be relieved.
[07:44] <Mirv> seb128: yes, I'm trying to assign that to the next one in queue
[07:44] <Mirv> spreadsheet is acting up
[07:45] <seb128> Mirv, well, settings is only in 1 by itself, the other 2 silos it's in that's part of a transition/bigger changes
[07:45] <seb128> in fact it's only in 2
[07:45] <Mirv> seb128: yes, but there are also 2/3 (2 set to ready) pending landings of u-s-s
[07:46] <Mirv> I just mean that there's a bottleneck in landing those fixes as they go in one after another
[07:46] <Mirv> not in terms of silo usage but simply that it takes maybe too much time to get all of those in
[07:46] <sil2100> hmm
[07:47] <sil2100> I wonder is silo 004 is still needed
[07:47] <seb128> Mirv, oh right, but landing are limited nowadays right? like we need an approval for fixes and QA verification, can't just batch a stack of bugfixes and get that in easily...
[07:48] <Mirv> sil2100: I think that could be a good candidate for freeing even without asking, since it's cheap to rebuild
[07:48] <Mirv> seb128: yes sure if not all of those are on the vivid milestone bug list they'd need separate approvals.
[07:48] <seb128> Mirv, need to check with jgdx and kenvandine
[07:49] <sil2100> We might need to poke some release team members about the UNAPPROVED silos I guess
[07:49] <Mirv> sil2100: we could also have 10 sru silos... :)
[07:50] <seb128> Mirv, then you would ping the SRU team ;-)
[07:50] <seb128> speaking of which, I've a trusty SRU, I'm pondering doing out of the CI due to that
[07:50] <Mirv> I mean, SRU silos could have a separate quota since they tend to keep on the silos for a longish time (approval + minimum 7 days in -proposed)
[07:53] <Mirv> pinged #ubuntu-release on the unapproved ones. compiz and unit have been there for 3+ weeks
[07:56] <seb128> right
[07:59] <Mirv> sil2100: fatal errors dance in the spreadsheet again, but some changes possible
[07:59] <Mirv> bfiller: cleaning 004 for now, ubuntu-keyboard build copied to ppa:canonical-qt5-edgers/qt5-proper
[08:07] <sil2100> Mirv: oh no...
[08:07] <sil2100> Mirv: that's too soon!
[08:09] <Mirv> dbarth_: ^ copied and silo status refreshed
[08:09] <sil2100> I give up, I have no idea what now caused the spreadsheet to go wild again
[08:09] <sil2100> There's not so many users even
[08:11] <dbarth_> Mirv: yup; seen that; thank you!
[08:13] <sil2100> Yeah, officially since 3 in the night the spreadsheet is not refreshing again
[08:19] <sil2100> This is bullshit, we only had a week of peace from those issues
[08:20]  * sil2100 is disabling stuff again
[08:51] <Mirv> thanks to infi_nity for reviewing the unapproved queue for us
[08:51] <Mirv> immediately it'll help with getting only 1 silo since those trusty SRU:s will be in the SRU queue for at least 7 days
[09:12] <sil2100> jibel, ogra_, Mirv, davmor2: how about I kick a new image now?
[09:12] <ogra_> go for it
[09:12] <jibel> sil2100, +1
[09:13] <sil2100> Actually not sure if we had anything landing inbetween, would have to check, but I think I remember some changes happening
[09:13] <sil2100> And this way maybe I'll force the importer to use the new custom
[09:14] <jibel> sil2100, new unity8 to fix a GPS issue
[09:15] <jibel> with the new custom tarball, I think that's all
[09:16] <Mirv> no problem
[09:20] <imgbot> [09:25] <popey> sil2100:  you have mail :)
[09:27]  * davmor2 deletes said mail
[09:30] <sil2100> popey: thanks! Will add it in a few moments
[09:40] <sil2100> Mirv: either google stopped reporting errors to me or the time-driven scripts stopped erroring-out
[09:41] <sil2100> Which might be a good sign
[09:42] <Mirv> hmm
[10:07] <cwayne_> sil2100, hiya
[10:07] <sil2100> cwayne_: hey! :)
[10:07] <sil2100> cwayne_: I see it picked up the tarball now
[10:08] <sil2100> cwayne_: took much longer than I expected, especially that the importer is running every 5 minutes
[10:08] <cwayne_> sil2100, \o/ its supposed to be all automagic so that;s good
[10:08] <sil2100> But yeah, it happened automagically
[10:08] <cwayne_> sil2100, weird, it's often done in a matter of minutes
[10:08] <sil2100> Thanks again :)
[10:08] <cwayne_> unless it;s doing something else which is taking its time
[10:09] <cwayne_> sil2100, np, sorry for all the troubles
[10:11] <cwayne_> sil2100, let me know if there's any other issues and I'll get em fixed
[10:11] <cwayne_> in the meantime, 6am calls for coffee
[10:14] <sil2100> cwayne_: go back to sleep! :)
[10:15] <sil2100> hmmm
[10:16] <sil2100> ogra_: image build 265 seems to have finished on the cdimage side
[10:16] <ogra_> thats good :)
[10:17] <ogra_> ogra@nusakan:~$ ps ax|grep import
[10:17] <ogra_> 13887 ?        Ss     0:00 /bin/sh -c TMPDIR=/srv/system-image.ubuntu.com/tmp /srv/system-image.ubuntu.com/bin/import-images
[10:17] <ogra_> 13894 ?        R      1:33 /usr/bin/python /srv/system-image.ubuntu.com/bin/import-images
[10:17] <ogra_> 24979 pts/5    S+     0:00 grep --color=auto import
[10:17] <ogra_> import-images only runs since 1:33 :)
[10:17] <ogra_> patience ;)
[10:18] <sil2100> I was worried something got b0rken ;p
[10:18] <sil2100> Thanks for checking
[10:24] <oSoMoN> ubuntu-qa: any chance silo 27 will be signed off today?
[10:25] <sil2100> jibel, davmor2, rvr: ^ ?
[10:25] <rvr> oSoMoN: I'll take it right now
[10:26] <davmor2> rvr: nice one
[10:26] <sil2100> ogra_: seems the importer is slowich today
[10:27] <ogra_> not really
[10:27] <ogra_> it usually takes 30min +
[10:28] <oSoMoN> rvr, awesome, thanks!
[10:50] <imgbot> [10:50] <imgbot> [10:50] <ogra_> there you go :)
[10:54] <sil2100> Phew
[10:55] <sil2100> Somehow today I'm really impatient
[11:06] <sil2100> Ok, I drive out for lunch now
[11:06] <sil2100> o/
[11:07] <brendand> sil2100, veebers made a request to get a vivid silo for autopilot yesterday, apparently there were none free. do you know anything?
[11:38] <Mirv> brendand: no such request is visible on the spreadsheet at least. we're constantly out of silos despite constant attempts to free them... currently 1 free
[12:05] <brendand> Mirv, oh - hope it didn't get lost
[12:13] <Mirv> brendand: there's nothing regarding autopilot on the spreadsheet unfortunately, but we also haven't heard reports yet of anything being magically removed on the new(est) spreadsheet.
[12:14] <Mirv> oh well
[12:14] <Mirv> oh well
[12:14] <Mirv> until now
[12:14] <Mirv> sil2100: backups..?
[12:14] <ogra_> hiccups rather
[12:14] <Mirv> brendand: my check up was anyway _before_ it now started resetting itself :D
[12:15] <Mirv> ogra_: also resetted to yesterday
[12:16] <Mirv> although it errors out constantly and reloads so it's hard to say. but from sil2100's backups it will be possible to restore the lines once the spreadsheet is even somewhat functional.
[12:16] <ogra_> yesterdays hiccups then :)
[12:16] <ogra_> we are trapped in a time loop !!!
[12:32] <jibel> sil2100, Mirv I approved line 53 3 times but the spreadsheet doesn't want it. Can you publish? silo 005/address-book-app
[12:32] <pmcgowan> jibel, sil2100 everything good? will be offlie for a bot
[12:32] <pmcgowan> bit
[12:36] <jibel> pmcgowan, we are waiting on a device tarball to trigger a new build which will be our promotion candidate. It won't include the touch panel fix.
[12:36] <pmcgowan> jibel, thats too bad
[12:37] <pmcgowan> ok
[12:38] <john-mcaleely> jibel, sil2100 I've pushed the brightness tarball you +1'd
[12:38] <jibel> pmcgowan, we'll start testing if the touch panel fix can land before tomorrow we can always respin an image with the fix
[12:38] <jibel> john-mcaleely, thanks
[12:38] <john-mcaleely> device_krillin-20150331-b430246.tar.xz
[12:38] <Mirv> jibel: sure
[12:38] <pmcgowan> john-mcaleely, any eta on the panel fix?
[12:38] <john-mcaleely> pmcgowan, working on it now. not clear if it's an hour or a day
[12:39] <pmcgowan> ok
[12:40] <ogra_> pmcgowan, for how long will you be offline ?
[12:41] <ogra_> pmcgowan, ycheng did set up a meeting about the OTA stuff we discussed yesterday ... in 20min ... i was about to ask if you could participate
[12:41] <pmcgowan> ogra_, well I am double booked then but I can try
[12:41] <pmcgowan> ogra_, changing my offline plan then
[12:54] <sil2100> \o/
[12:55] <sil2100> Mirv: yeah, it seems it started being broken again
[12:55] <sil2100> It seemingly worked from 12:30 till 14:15, now I again get error logs from google on every timed event
[13:00] <jibel> sil2100, can you trigger a new build with the device john-mcaleely pushed so we can start testing?
[13:00] <jibel> device tarball*
[13:03] <jibel> sil2100, nm, it's 266
[13:03] <sil2100> jibel: it should automatically create the new image, but it might take the importer a few moments to pick it up
[13:03] <sil2100> I thought it's instant, but sometimes it can take a few minutes
[13:04] <jibel> sil2100, actually it was pretty fast and thought it didn't build yet
[13:04] <jibel> sil2100, so 266 is the candidate for now
[13:04] <sil2100> Strange, since I have waited for the custom tarball to appear for like 15 minutes
[13:04] <sil2100> Yeah
[13:05] <sil2100> I heard the news about the device tarball, indeed no need to wait for it to start testing
[13:05] <sil2100> Too much time would be wasted
[13:07] <sil2100> Mirv: sometimes I feel as if all these spreadsheet problems don't have anything to do with our actual trigger-scripts, but actually related to the number of people viewing the spreadsheet
[13:07] <sil2100> Mirv: when the spreadsheet got better today, I saw there were only 5 people using it - now it was around 9
[13:08] <sil2100> Mirv: I suppose google spreadsheet syncs combined with the triggers and formulas leads to the backend breaking
[13:10] <Mirv> something like that..
[13:14] <jibel> trainguards you can publish ubuntu/silo-001 approved yesterday
[13:15] <davmor2> rsalveti, Mirv, sil2100: silo9 pulse corking good to go incase there is an issue with SS still
[13:16] <sil2100> jibel: ah, ok, let me publish then
[13:16] <sil2100> davmor2: same here :)
[13:19] <sil2100> ogra_: can you +1 a packaging change for me? There's no mention of the recommends-addition in the changelog, but I suppose it's less serious than not mentioning dep-changes: https://ci-train.ubuntu.com/job/ubuntu-landing-001-2-publish/98/artifact/indicator-power_packaging_changes.diff
[13:20] <ogra_> sil2100, ACK, looks fine
[13:21] <sil2100> Thanks :)
[13:21] <sil2100> jibel, davmor2: both silos are publishing
[13:22] <ogra_> why does a silo from a core dev need manual acking ?
[13:22] <ogra_> (referring to the last queuebot msg)
[13:23] <davmor2> ogra_: because a woodchuck could chuck wood?
[13:23] <ogra_> would a woodchuck chuck wood if it could ?
[13:24] <davmor2> ogra_: wait no, take their hats off, no that is popes in a beetle, the answer will come to me at some point
[13:25] <sil2100> ogra_: it's complicated
[13:26] <ogra_> davmor2, haha
[13:26] <sil2100> ogra_: we would have to either: 1) base that on who's set as the lander or 2) auto-analyse the changelog to make sure that the only change visible is made by a core-dev
[13:26] <ogra_> well, 2 would be nice in general :)
[13:27] <sil2100> In case of 1), this is a potential security leak as we would have to doublecheck that someone didn't simply include someone's else name in the field - with 2), well, it's work to implement that and I'm not sure it's a big deal without it ;)
[13:27] <davmor2> I love it all this work just fell into the abyss
[13:27] <sil2100> Since when I see a change made only by a core-dev I anyway override it and auto-approve
[13:28] <ogra_> sil2100, well, i'D already be happy if my changelogs wouldnt be reduced to the very last entry if i built my source package with -v ....
[13:28] <ogra_> i think our changelog handlin could need some love as a whole
[13:29] <ogra_> (but yeah, low prio task ... definitely)
[13:36] <seb128> hum
[13:36] <seb128> http://people.canonical.com/~platform/citrain_dashboard/ has a weird status for 024
[13:36] <seb128> it's a u-c-c desktop landing and status has "ready to build" but also "Migration: indicator-datetime is in the UNAPPROVED queue. "
[13:37] <seb128> the migration part is weird
[13:38] <seb128> gra, the "build" url is pointing to a wrong jenkins as well
[13:39] <seb128> or not
[13:39] <seb128> how confusing
[13:40]  * ogra_ doesnt see the queuebot pick up his rebuild of silo 19 :/
[13:41] <rvr> sil2100: About to approve silo 27
[13:42] <rvr> sil2100: "Note: requires a FFe, granted at bugs/1441232"
[13:43] <rvr> Looks good
[13:43] <rvr> Will the spreadsheet work?
[13:44] <rvr> The action you're trying to perform is causing a fatal error and cannot be performed.
[13:47] <seb128> grrrr
[13:48] <seb128> the CI table keeps hitting backend error and loosing edits
[13:48] <oSoMoN> trainguards: can silo 27 be published, please?
[13:56] <Mirv> oSoMoN: sure, trello is enough even if spreadsheet keeps resetting
[13:57] <Mirv> ogra_: core dev ack for https://ci-train.ubuntu.com/job/ubuntu-landing-027-2-publish/lastSuccessfulBuild/artifact/webbrowser-app_packaging_changes.diff ? are in main.
[13:58] <ogra_> oSoMoN, Mirv, NACK, please mention the added dependencies in the changelog
[13:59] <Mirv> ogra_: thank you for reviewing. it does make sense to enforce more directly describing the packaging changes.
[14:00] <Mirv> folder list model is not mentioned at all, settings is mentioned but not that it adds a dep
[14:00] <oSoMoN> ogra_, I agree that it would be useful, but it should be automatically done by the CI train, now it’s going to take a rebuild just to add a line in the changelog…
[14:00] <ogra_> right, i warned that i would do this about 6 months ago ... and poked people about it for the last 6 months but still acked ... i think after 6 months it is now the time to expect it to be proper
[14:01] <Mirv> that would be a good feature request for train, filing
[14:04] <Mirv> bug #1441638 . cihelp, do you have some project to file future CI Train replacement feature requests under?
[14:08] <oSoMoN> Mirv, I updated the commit messages on the relevant MRs, I’ll trigger a rebuild of silo 27
[14:09] <Mirv> ok
[14:13] <pmcgowan> sil2100, 266 is building?
[14:16] <ogra_> pmcgowan, i think it is done
[14:16] <davmor2> pmcgowan: 266 is done
[14:16] <ogra_> was only a tarball update
[14:17] <pmcgowan> ah great
[14:17] <ogra_> (they are fast and not noticed by the bot)
[14:17] <sil2100> pmcgowan: yeah, QA is already testing it
[14:17] <pmcgowan> woot
[14:17] <ogra_> sil2100, any idea why the queuebot didnt pick up my watch-only rebuild of silo 19 ?
[14:22] <sil2100> ogra_: he might be a bit confused because of the spreadsheet reverting its state, but normally it shouldn't have any problems
[14:23] <jdstrand> cwayne_: fyi, apparmor-easyprof-ubuntu 1.3.10 on vivid uploaded (not sure if you are doing custom tarballs yet for vivid)
[14:25] <elopio> ping trainguards, any vivid silos available today to release autopilot?
[14:25] <sil2100> elopio: hey
[14:25] <sil2100> We currently have 2 free vivid silos
[14:26] <sil2100> We're not sure about the number of landing requests as the spreadsheet reverted itself to the state of last night
[14:26] <elopio> sil2100: can we get one of those to autopilot before somebody else take it?
[14:26] <sil2100> elopio: try filling in a request and I'll try assigning it to you
[14:27] <elopio> sil2100: ok.
[14:28] <seb128> sil2100, I've some pending, if you can try that as well :-)
[14:28] <sil2100> seb128: I see them now ;) Probably got reverted as well, right?
[14:29] <seb128> sil2100, yeah, some of them
[14:29] <sil2100> Sorry for the spreadsheet troubles again guys
[14:29] <seb128> not your fault
[14:32] <om26er> jibel, during silo 14 testing I found a regression. During flight mode, Not network or SIM lock, the app title becomes blank in the right edge switcher.
[14:32] <om26er> http://i.imgur.com/VGm6t5v.png
[14:32] <om26er> jibel, salem_ says they are aware of it and its something they can't fix right now
[14:33] <seb128> bfiller, you put a landing up for settings with the storage panel fix for arale, did you see that there was another landing request from jgdx in the list including that and some other fixes? would have been nice to picked the other fixes as well rather than superseeding with a more limited set
[14:33] <om26er> jibel, I have blocked the landing, what do you say ?
[14:35] <jibel> om26er, it is a regression introduced by the silo?
[14:35] <om26er> jibel, yes it is.
[14:36] <salem_> jibel, hi, so, the original problem is that apps can be sigpaused at any time, and in this specific case, dialer will be frozen with a certain header title that might not reflect the current state anymore when you invoke the carousel with a right-> left swipe
[14:36] <jibel> om26er, ok, so we land bug fixes, not new bugs when we find them. It's correct to reject
[14:36] <salem_> bfiller, ^
[14:39] <kgunn> Mirv: sil2100 ...hey, we can manage giving back silo 0
[14:40] <elopio> sil2100: added the autopilot row.
[14:40] <elopio> that was hard.
[14:41] <sil2100> elopio: yeah... let me refresh as I didn't see your row
[14:42] <elopio> yes, my nick disappeared. Filled now.
[14:42] <elopio> It seems I was fighting seb128 and dbarth_ on the spreadsheet.
[14:43] <sil2100> Yeah, the spreadsheet doesn't sync
[14:43] <elopio> cool :)
[14:46] <elopio> sil2100: after hitting build, I don't have to fill anything on jenkins, right? Last time I did this was long ago.
[14:47] <bfiller> seb128: no I didn't see that
[14:47] <bfiller> seb128: feel free to change, just trying to get this fix landed as it was on the arale list
[14:47] <seb128> bfiller, k, just a note for next time to maybe check pending requests then :-)
[14:48] <seb128> bfiller, well, now it's in a silo so I guess we can as well get the landing through
[14:48] <bfiller> om26er, jibel : I wouldn't say it's a regression
[14:48] <seb128> bfiller, but if somebody wants to include the other ones feel free
[14:48] <sil2100> elopio: nothing :)
[14:48] <bfiller> om26er, jibel : it's an expected change as there is no other way to solve the bug
[14:48] <sil2100> elopio: only if some special care is needed
[14:48] <bfiller> seb128: will do
[14:48] <elopio> ok, thanks.
[14:49] <seb128> bfiller, thanks
[14:51] <elopio> I don't really understand that.
[14:51] <om26er> bfiller, jibel it clearly looks like a regression, user drags from right edge and poof no title. I remember we still have issues on the design side as they are trying to show app icon in the right edge switcher. So now with no title in this case is a regression
[14:52] <sil2100> popey, ogra_, robru, davmor2, rvr: let's skip the evening meeting
[14:52] <ogra_> sil2100, +1
[14:52] <sil2100> elopio: this means that your trunk branch, so the branch to which you want to merge to, doesn't seem to have all the released versions merged
[14:52]  * ogra_ had/has enough meetings today, one less will be good :)
[14:52] <bfiller> om26er, jibel: a regression is something unintended. this was known and deemed an acceptable tradeoff to fix the bug at hand
[14:52] <sil2100> elopio: so probably someone released autopilot to the archive directly and didn't merge that back to trunk
[14:53] <sil2100> Or at least didn't merge the changelog
[14:53] <bfiller> om26er, jibel : I agree it's not ideal, but better than showing the wrong state when the app is brought to the foreground which is the case today
[14:53] <davmor2> the cancelmonger strikes again +1 though :)
[14:53] <om26er> its a regression until approved by design IMO.
[14:53] <sil2100> davmor2: ;)
[14:54] <rvr> sil2100: Ack
[14:54] <sil2100> robru: just so you know - spreadsheet b0rken againz
[14:54] <cwayne_> jdstrand, ack, thank you, will kick a vivid build
[14:56] <elopio> sil2100: I'm looking at the 1.5 branch, that's what we release. It seems I filled the wrong branches. Trying again now.
[14:56] <popey> sil2100: ok
[14:57] <dbarth_> o/ trainguards; hi, can i get a silo for line 68 please?
[14:57] <sil2100> dbarth_: hey! Let me refresh and try assigning
[14:59] <elopio> sil2100: I updated the MPs, now rebuild?
[15:01] <jdstrand> cwayne_: thanks!
[15:03] <sil2100> elopio: you only modified the code in the MPs, right? Or did you change the MPs in the spreadsheet row?
[15:03] <elopio> sil2100: changed the MPs in the spreadsheet.
[15:03] <sil2100> elopio: this needs a reconfigure
[15:04] <sil2100> Let me try reconfiguring for you as the spreadsheet is brokennish
[15:05] <elopio> sil2100: yes please. I can't find that landing tools menu.
[15:06] <sil2100> elopio: should be reconfigured and ready to build
[15:06] <elopio> thanks sil2100
[15:07] <sil2100> yw
[15:20] <fginther> Mirv, I think the current home for bug #1441638 is a good place for wishlist items, eventually these would be requested based on their priorities
[15:21] <fginther> Mirv, so these should live where other tasks for the ci-train are tracked
[15:39] <rvr> Bad news. I found a regression in image 266, related to wizard and Oxide.
[15:39] <rvr> Filling bug.
[15:46] <boiko> trainguards: can I get vivid silo 21 reconfigured? I added new components there (telephony-service and history-service)
[15:53] <rvr> mterry: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1441708
[15:54] <rvr> mterry: That's a regression in RTM proposed 266
[15:55] <mterry> rvr, sounds like the affected version of oxide got backported to rtm
[15:55] <mterry> or at least, the patch did
[15:55] <rvr> mterry: Yes, jibel told me that we have the same version in Vivid and RTM.
[15:56] <mterry> rvr, of oxide?  bummer
[15:56] <mterry> rvr, ok will mark as dup of main bug and open a subtask
[15:56] <sil2100> boiko: hey!
[15:56] <sil2100> boiko: ok, let me reconfigure while the spreadsheet still keeps the state
[15:57] <boiko> sil2100: I got a fatal error at the spreadsheet, is it broken again?
[15:57] <sil2100> boiko: yep, see the topic, it's bullshit again
[15:57] <sil2100> But we're working with google on that
[15:57] <boiko> sil2100: ok
[15:57] <sil2100> I mean, we try to :|
[15:59] <rvr> mterry: I would say this is a high priority bug, as can prevent promoting OTA3. Not that I am the one who makes those decisions, but...
[15:59] <sil2100> boiko: could you refresh the spreadsheet and double-confirm the right branches are in your row?
[15:59] <sil2100> rvr: wow, I knew we had this in vivid, but now it's in rtm as well?
[15:59] <rvr> sil2100: Yes
[16:00] <mterry> rvr, chrisccoulson is probably the guy to quick-fix this -- it's a two line fix, but needs to be applied to the rtm branch
[16:00] <boiko> sil2100: let me see
[16:01] <boiko> sil2100: yep, it is the three branches there plus telepathy-qt (which was a source upload)
[16:01] <rvr> chrisccoulson: ^^
[16:03] <sil2100> boiko: reconfiguring then
[16:05] <boiko> sil2100: thanks!
[17:04] <rvr> bfiller: ping
[17:04] <bfiller> rvr: pong
[17:04] <rvr> bfiller: https://bugs.launchpad.net/telephony-service/+bug/1441746
[17:05] <bfiller> salem_: ^^^
[17:10] <salem_> rvr, can you miss another call from the same number just to make sure the bug is still reproducible with 2?
[17:10] <rvr> salem_: Right, let me check
[17:12] <rvr> salem_: "2 missed calls"
[17:14] <rvr> salem_: http://people.canonical.com/~vrruiz/missed-calls.png
[17:42] <robru> seb128: the thing about the two different statuses in the dashboard is that the lower, smaller-font one comes from the spreadsheet, so that's just a side effect of the spreadsheet being totally busted.
[17:42] <sil2100> robru: are you getting fatal errors right now? Since I again stopped getting errors from the time-driven scripts from the spreadsheet
[17:43] <robru> sil2100: I just did an assignment without any errors
[17:43] <sil2100> (which might mean it's temporarily working)
[17:43] <sil2100> Ok
[17:43] <robru> bfiller: got you silo 15
[17:43] <sil2100> Who knows, maybe google is *actually* looking into it
[17:43] <robru> sil2100: did you report the issues to them?
[17:44] <sil2100> robru: yeah, but Didier said he did that in the past as well and they didn't do anything, but maybe this time it was different
[17:45] <robru> sil2100: I'm starting to think we should rip *all* the code out of the spreadsheet and use it purely as a dumb data-store, and do all the calcuations/formulas in jenkins, where we can write things testably.
[17:46] <sil2100> robru: might be a good way forward, although I think it actually might not be directly related to the scripts themselves... I suppose the thing that triggers it is simply the internal google sync-between-open-clients code
[17:47] <robru> sil2100: yeah the syncing is definitely impacted, but I have a hard time believing that google is incapable of making a service that can sync among 30 people. google is known for scalability, it must be our scripts/formulas that are dragging it down
[17:48] <sil2100> robru: all in all, I wouldn't waste time on this as our top-priority should be the replacement - I would push more on getting some google people actually working on this instead
[17:49] <robru> sil2100: yeah, the ticket system isn't as far along as we previously thought. I'm not sure how long it will take before it will be ready. I think we really need to stop the bleeding before we can consider the replacement. think of all the man-hours lost to spreadsheet fuckery, how many more months can we sustain that for?
[17:51] <sil2100> I would say let's then assign more resources to the replacement and get this done faster then, at least until we know that there's nothing that google can do to help
[17:51] <sil2100> *-then
[17:53] <sil2100> Me and Steve will be poking about that the CI team tomorrow
[17:53] <sil2100> Since the recent problems popped-up, we want much much more priority set on it
[17:54] <robru> sil2100: yeah, if we can get people on it that would be great
[17:55] <sil2100> robru: let's discuss all the possibilities tomorrow, we'll know more about the current priorities and we can set the plans accordingly
[17:55] <sil2100> And there's next week too, we can discuss it further
[17:56] <robru> sil2100: yeah next week will be good
[18:20] <john-mcaleely> fresh rtm tarball for krillin
[18:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150408-4f14058.tar.xz
[18:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150408-4f14058.changes
[18:20] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-testresults-20150408-4f14058.ods
[18:20] <john-mcaleely> sil2100, pmcgowan ^
[18:20] <sil2100> \o/
[18:20] <sil2100> davmor2: hey, I guess you'll be EOD pretty soon, right?
[18:21] <john-mcaleely> sil2100, ping me in telgram if you get a +1 I can action tonight
[18:21] <john-mcaleely> (or the mobile in the corp. dir)
[18:21] <pmcgowan> john-mcaleely, thanks
[18:21] <davmor2> sil2100: indeed
[18:22] <davmor2> jibel: who will be best for this om26er maybe or do you want to leave it till the morning
[18:23] <john-mcaleely> (also in the tarballs & clicks tab of the spreadsheet)
[18:27] <bzoltan> ogra_: any chance to push this out, to keep mzanetti happy? https://code.launchpad.net/~bzoltan/ubuntu-seeds/add_libssl_and_qtpim_devs/+merge/254902
[21:28] <lool> Hi folks, I'm not sure what's happening with silo 12
[21:29] <lool> it doesn't seem to be up in the QA board, actually I thought it had passed yesterday
[21:29] <lool> (this is for vivid)
[21:29] <lool> trainguards ^
[21:31] <robru> lool: looks like you need to run the build job. The train doesn't think anything has been done there which is why it isn't submitted for qa
[21:31] <robru> lool: i see you uploaded a package but you haven't done anything to inform the train of this
[21:32] <lool> aha, thanks
[21:32] <lool> I'll just press build then?
[21:32] <robru> lool: yep
[21:34] <lool> Ok, so it's "packages built" now; I guess I dont need to press anything for the QA dashboard addition though?
[21:36] <lool> great
[21:36] <lool> looks good in trello now
[21:37] <robru> lool: yep ;-)
[21:58] <john-mcaleely> pmcgowan, so, om26er has given a +1 to the device tarball. I'll push it now, so there's a build with it in
[22:01] <pmcgowan> john-mcaleely, great
[22:02] <pmcgowan> I think someone needs to kick a build
[22:02] <pmcgowan> rsalveti, still about?
[22:02] <john-mcaleely> pmcgowan, generally, the machines spot new tarballs and do that
[22:02] <pmcgowan> oh
[22:02] <john-mcaleely> unless that's been turned off
[22:02] <john-mcaleely> give it 10 mins
[22:17] <john-mcaleely> imgbot, status 267
[22:17] <imgbot> Error: No rootfs build found, was this a device or custom build ?
[22:18] <john-mcaleely> pmcgowan, ^ imgbot tells all :-)
[22:18] <john-mcaleely> 267 contains the device tarball
[23:24] <rsalveti> pmcgowan: yup, what's up?
[23:25] <rsalveti> pmcgowan: yeah, the device tarball is kind of automatic


[08:05] <didrocks> good morning
[09:23] <MacSlow> Greetings everybody
[09:23] <MacSlow> *sigh*
[09:24] <didrocks> Good morning MacSlow!
[09:24] <MacSlow> hey didrocks
[10:14] <apw> can anyone tell me how to get rid of AM/PM on the new indicatory clocky thing?
[10:15] <apw> and indeed how to get the date back in the clocky thing
[10:42] <mpt> apw, implement <https://wiki.ubuntu.com/TimeAndDate?action=AttachFile&do=get&target=settings-clock.jpg> :-)
[10:56] <apw> mpt, joy
[10:57] <seb128> or http://askubuntu.com/questions/17226/how-do-i-show-the-date-in-the-clock-indicator
[10:58] <seb128> that's at least for the date
[10:58] <seb128> not sure you can change the format, that comes from the locale
[11:45] <apw> do we already know that on random logins the theme is incorrectly set, showin nice coloured icons instead of our black and white ones ?
[11:55] <seb128> apw, it's likely gnome-settings-daemon failing to start
[11:56] <seb128> there is some bug about it
[11:56] <seb128> would be interesting to know if you have anything in .xsession-errors about g-s-d
[11:56] <seb128> or a crash
[11:56] <apw> seb128, no crash reported by apport
[11:57] <apw> seb128, and it was running still when i logged out
[11:59] <apw> seb128, scratch that, wrong machine.... no crash reported though, lost the error log on the affected box, will look next time
[12:01] <apw> do we know about the NM applet 'connecting' animation being missing?
[14:44] <jcastro> wb njpatel!
[15:12] <jcastro> cando_: jamalta: fagan: vish: I'm doing a unity report today on the bitesizes, if you've claimed a bug and have no progress and want to throw it back in the pool today would be the day to do that.
[15:12] <jcastro> also, if you did anything cool in the meantime let me know
[15:14] <cando_> jcastro, i've a bug half-finished...but sincerely i've not time to do it...(univ exams..).. :(
[15:14] <cando_> my branch is linked to the bug...
[15:14] <jcastro> no worries
[15:14] <jcastro> want me to ask if someone wants to finish it?
[15:14] <lamalex> API, how is it coming?
[15:15] <API> lamalex, fine, although I spent most of yesterday revamping my development environment
[15:15] <cando_> jcastro, i would like to finish it but i understand that i can't take this bug for me forever..
[15:15] <cando_> so yes...
[15:15] <API> I still used the "long path" to compile unity
[15:15] <API> anyway
[15:15] <jcastro> it's ok, it's not like people are stomping on you trying to take it. :)
[15:15] <API> I have the code to load the bridge
[15:15] <API> done
[15:16] <API> now I need to test it (a freeze last time I tested it)
[15:16] <cando_> jcastro, meanwhile should i assign that bug back to nobody?
[15:17] <jcastro> cando_: nah, let's just roll with it, we have plenty in the meantime
[15:17] <cando_> jcastro, :)...ok thanks jorge
[15:18] <jcastro> you're the one doing us the favor, I don't want to come across as whiny. :)
[15:18] <ronoc> njpatel, hey, developing indicators in unity, trying to kill me indicator-applet so that i can run my own
[15:18] <cando_> ;)
[15:18] <ronoc> can't right click on the applet
[15:18] <ronoc> killall indicator-applet ?
[15:19] <jcastro> cando_: You don't take as long as DBO does, for example.
[15:20] <seb128> ronoc, you can right click on the handle on the left
[15:20] <cando_> ahahah, ok...^^
[15:21] <ronoc> seb128, can't see this handle, left of the panel ?
[15:21] <njpatel> ronoc, killall unity-panel-service
[15:21] <ronoc> cool
[15:22] <njpatel> you might need to then run it, but it should autostart again
[15:22] <seb128> ronoc, oh, you are using unity
[15:22] <seb128> ronoc, I though that was under GNOME
[15:22] <njpatel> ronoc, that'll re-load all the indicators
[15:22] <didrocks> just be quicker than the autostart :)
[15:22] <ronoc> yep moved this morning
[15:23] <ronoc> njpatel, anyway i can stop it from running again, I want to run up my service and indicator
[15:24] <njpatel> ronoc, mm, I didn't right the autostart code, there might not be a easy way to disable that yet :/
[15:25] <cando_> jcastro, forget me..i want to finish this bug..i can stop my study for an hour..eheheh..but i need some mentoring: can you point me to somebody willing to help?
[15:25] <seb128> njpatel, ronoc: I don't think there is one no
[15:26] <jcastro> cando_: DBO probably, but really, you should study
[15:26] <ronoc> seb128, right must continue developing on classic desktop then
[15:26] <cando_> jcastro, no problem.. :)
[15:26] <cando_> DBO, have you got some time for a quick mentoring?
[15:27] <DBO> cando_, yes
[15:27] <cando_> DBO, https://bugs.launchpad.net/unity/+bug/688407
[15:28] <cando_> i've already written the quick list..i've to write the callback for the Empty trash
[15:29] <DBO> cando_, I think the idea is to use gio here
[15:29] <DBO> looking at it
[15:29] <cando_> i've looked to unity-private, but obviuosly it's in vala...i've looked to nautilus code and it's pretty difficult..my question is: is there a simple way?or should i use (like in nautilus) gio_schedule?
[15:32] <DBO> cando_, probably should do it how nautilus does
[15:32] <DBO> do you have the code snippet handy?
[15:32] <cando_> if the latter...it's a pretty big thing, right? (i've never used gio_schedule and simils)..i've to create the jobs and so on..
[15:32] <cando_> yep..just a moment
[15:33] <cando_> DBO, http://git.gnome.org/browse/nautilus/tree/libnautilus-private/nautilus-file-operations.c
[15:33] <cando_> from row 6118
[15:35] <DBO> cando_, okay what this does in all its complexity is delete everything contained in the trash: file
[15:35] <cando_> DBO, yes...but do we need that complexity? the jobs and the schedules?
[15:36] <DBO> no
[15:36] <DBO> you could do this all inline
[15:36] <didrocks> njpatel: I'm adding a global variable for disabling the autostart
[15:37] <cando_> DBO, really? sorry but...it won't be a problem if a i have a very full bin?
[15:37] <DBO> cando_, you should still do it async
[15:37] <DBO> but you shouldn't need a job for that
[15:38] <cando_> DBO, ok..i'll try...thanks!
[15:38] <njpatel> didrocks, awesome!
[15:41] <lamalex> DBO, didn't you write trash emptying for docky via gio?
[15:42] <DBO> lamalex, yeah but I dont honestly care that it did not account for things like nfs
[15:44] <lamalex> didrocks, how does your super key merge affect super + e and the other compiz bindings?
[15:46] <jcastro> is holding down super going to still do the number overlays like in 10.10?
[15:47] <seb128> jcastro, it should
[15:50] <lamalex> DBO, cando_ nautilus added a dbus api for file ops, is empty trash one of them?
[15:51] <DBO> counting on nautilus to be present is not a good idea
[15:51] <cando_> really?didn't know...
[15:51] <lamalex> erm, maybe it hasn't been added yet anyway
[15:54] <seb128> lamalex, it's in GNOME3 which is not in natty
[15:54] <seb128> well the dbus interfaces
[15:54] <seb128> not sure the trash empty action has one
[16:01] <gs> Hello everyone! mostly technical discussion here? anyway I wrote a blog post on Unity and interface design you might be interested in, would love to get some feedback: http://georgesullivan.wordpress.com/2011/01/02/unity-a-missed-oportunity/
[16:02] <lamalex> seb128, ah ok
[16:08] <coz_> hey all
[17:01] <didrocks> I need some testing on different hw…
[17:01] <didrocks> can people try to run: /usr/lib/nux/unity_support_test; echo $?
[17:01] <didrocks> and give the result (should be 0 or 1) here?
[17:03] <lamalex> didrocks, sure
[17:04] <dbarth> it returns 0 for me didrocks
[17:04] <lamalex> didrocks, does nux need to be from trunk or is the packaged version ok
[17:04] <dbarth> and i'm running unity right now
[17:04] <didrocks> lamalex: packaged version is ok
[17:04] <didrocks> dbarth: thanks :)
[17:05] <lamalex> didrocks, I also get a 0 return code
[17:05] <didrocks> just that we had a segfaulty version on some card some weeks ago and I want to ensure that some random hw config is working now :)
[17:05] <didrocks> lamalex: thanks!
[17:05] <lamalex> I'm on a macbook pro, nvidia graphics
[17:05] <didrocks> I think dbarth is on ATI
[17:06] <didrocks> seb gave me for intel
[17:06] <cyphermox> kvalo, ping?
[17:06] <didrocks> but if other wants to play the game, they're welcome :)
[17:06] <didrocks> cyphermox: !!! I'm sure you want to try /usr/lib/nux/unity_support_test; echo $? and give the result here! :)
[17:07] <cyphermox> sure
[17:07] <cyphermox> it's 0
[17:08] <didrocks> \o/ thanks cyphermox
[17:08] <didrocks> jcastro was the one having the segfault IIRC
[17:08] <Omega> What do I need to install to be able to run that?
[17:08] <cyphermox> didrocks, I'm on a system with an i3 though, so Intel Corporation Core Processor Integrated Graphics Controller (rev 12) for the graphics card... not much in terms of difference
[17:09] <didrocks> Omega: if you have unity, you should have it
[17:09] <didrocks> Omega: nux-tools is the package containing it
[17:09] <didrocks> cyphermox: well, it's mostly testing we don't have a segfault at least :)
[17:10] <jcastro> didrocks: I get 0 on nvidia
[17:10] <cyphermox> fair enough.. no segfault, unless I happily go hacking in unity ;)
[17:10] <didrocks> hehe :)
[17:10] <didrocks> thanks jcastro!
[17:11] <cyphermox> btw, I re-added the wifi strength icons in nm-applet: http://twitpic.com/3n0a95. That's just  on my system for now, but the animations are back in, the padlock for VPN over whatever connection is on, and this.
[17:11] <cyphermox> what's the process for shipping a few more icons with the ubuntu-mono-* themes? is there anything special?
[17:12] <jcastro> cyphermox: cool, I'll add that to my unity report!
[17:13] <cyphermox> jcastro, I need to ship icons for it to work though
[17:13] <didrocks> cyphermox: awesome \o/
[17:13] <jcastro> right, disclaimer, etc.
[17:13] <cyphermox> I quickly made the ones I needed in inkscape locally, since it's just inserting the padlock on the existing ones to create new files.
[17:13] <cyphermox> but I guess that's not quite kosher ;)
[17:16] <didrocks> Omega: did you have a change to test it?
[17:18] <seb128> cyphermox, try talking to sladen about those
[17:18] <cyphermox> seb128, thanks
[17:19]  * sladen looks at cyphermox
[17:20] <cyphermox> sladen, I'd like to ship more icons with the ubuntu-mono-* themes, basically, new icons for the gsm and wifi signal strength drawings but with the nm-vpn padlock included, and one of the same for wired
[17:21] <cyphermox> that way nm-applet doesn't need to composite icons to add the padlock, which it can't do in the context of indicators anyway
[17:23] <jcastro> didrocks: typical thursday/friday unity upload this week?
[17:23] <jcastro> didrocks: also, anything of significance you'd like to see mentioned?
[17:23] <sladen> cyphermox: would it be possible to dynamically composite/combine them at package build-time
[17:24] <didrocks> jcastro: let's try/hope we can go on Thursday. As I'll be on a plane on Friday, I prefer to avoid last minute issues :)
[17:24] <cyphermox> sladen, well, I guess it would be, but wouldn't that be done in the theme's package and not by nm-applet?
[17:25] <didrocks> jcastro: in trunk? not yet landed? well, there is improved drag and drop from the panel (as if it was a real title), some little new options to control the panel
[17:25] <sladen> cyphermox: the plan is long-term to get more stuff (such as uniform adding of shadows) done with code, to make the most efficient use of artist/human time
[17:25] <didrocks> and the launcher
[17:25] <didrocks> jcastro: but nothing really important this week, bug fixes and such
[17:25] <jcastro> yep, got a list of those
[17:25] <jcastro> this will be a nice rollup report
[17:25] <cyphermox> sladen, fair enough. anyway all I need is already available, just need to layer the two images
[17:26] <cyphermox> I just have no idea how to do this on the command line yet
[17:26] <didrocks> great :)
[17:26] <sladen> cyphermox: yeah, as long as nm-applet is pulling in uniquely-named icons it the way in which they are produced (human, package build stage, dynamically, application) can be tweaked, but their the names are suitably abstracted that's probably not easily done
[17:27] <sladen> cyphermox: man convert  should do it, but if they are vectors, it would be good to keep them as vectors
[17:27] <cyphermox> sladen, right
[17:27] <cyphermox> sladen, for now, I was creating images with the same name, -sec appended to the end, and coded nm to look for images with that name
[17:28] <sladen> cyphermox: what's 'sec' ?
[17:28] <sladen> cyphermox: but I think you're on the right path!
[17:28] <cyphermox> sladen, was short for "secure" or whatever. just to note there is a padlock ;)
[17:29] <sladen> cyphermox: okay, my preference would be to spell it out as '-secure' so that it's obvious even for idiots like me
[17:29] <cyphermox> no problem
[17:29] <sladen> cyphermox: if you have a script that codifies what you want to do, I can look over it/help/assist
[17:30] <cyphermox> sladen, sure, I'll do a quick search to find a way to script this and write up something
[17:30] <cyphermox> any idea if this is done elsewhere already?
[17:33] <sladen> cyphermox: if there's a Makefile somewhere you should be able to do    out-secure.image: in-nonsecure-1.image in-padlock.image  \n   convert ... $< $@
[17:34] <sladen> cyphermox: or probably even just   %-secure.image: %.image padlock.image
[17:34] <cyphermox> heh, I was expecting convert to break vectors
[17:36] <kvalo> cyphermox: pong
[17:40] <Omega> didrocks: Sadly, no ):
[17:41] <didrocks> Omega: no worry :)
[17:41] <Omega> I need to find a usb stick.
[17:45] <sladen> cyphermox: convert does indeed produce ugly bitmapness.  inkscape commandline doesn't quite work.  One pointer I've found is to however https://launchpad.net/memaker does it
[17:46] <sladen> cyphermox: and another is a trival XML joiner
[18:16] <cando> jcastro, don't know if you have already written your bitesize report...but i'm fixing my bug..
[18:17] <jcastro> cando: I've got it queued up, but I can add an addenum like tomorrow, that would be brilliant!
[18:17] <jcastro> that way I can get a pic of it, etc.
[18:17] <cando> :) fine
[18:18] <jcastro> ok now set it for review and go back to studying. :)
[18:18] <jcastro> I don't want to be responsible if you mess up an exam, heh
[18:18] <cando> i've still to add the confirmation dialog..
[18:18] <cando> ahahah ok!
[18:18] <cando> after that i'll study..:)
[18:34] <Omega> jono: try /usr/lib/nux/unity_support_test; echo $? and give the result here! :>
[18:35] <jono> Omega, not on my compiz unity box right now
[18:35] <Omega> Ah, same problem here ):
[18:51] <achiang> hello, if i think there's a papercut bug in a package (gnome-system-tools package -> time-admin binary package), what is the proper way to mark it so that someone can decide if it's actually a papercut or not?
[18:54] <achiang> is it simple as just filing the bug and then tagging it with papercut?
[18:54] <achiang> or possibly bitesize?
[19:20] <sense> achiang: File a bug in the 'hundredpapercuts' project at Launchpad and someone will process it.
[19:21] <achiang> sense: ah, thank you.
[19:21] <sense> yw
[20:04] <cando> DBO, sorry  a small question...why g_file_delete deletes also not empty folders? the docs says the opposite:If the file is a directory, it will only be deleted if it is empty.
[20:05] <DBO> cando, its a bit of a safety measure really
[20:05] <DBO> its kind of related to the reason we dont allow hardlinking of directories
[20:06] <cando> so in the patch i don't have to do a recursive deletion?
[20:07] <DBO> you do
[20:07] <DBO> you must recursively delete
[20:07] <cando> mmm ok
[20:15] <lamalex> DFS FTW
[20:24] <lamalex> tedg, is there any way to do more custom layouts in an indicator? Can entire widget be sent over?
[20:25] <tedg> lamalex, No, we want everything to be declaritive.  But, the goal is to support more complex layouts.
[20:26] <tedg> lamalex, We have some ideas whiteboarded out, but I need to type them up and make them more complete.
[20:26] <lamalex> cool
[20:27] <lamalex> I really miss international clock from the gnome panel
[20:27] <tedg> lamalex, Having the multiple timezones in the menu?
[20:27] <lamalex> tedg, yah
[20:27] <tedg> lamalex, klattimer has that on his plate after getting the EDS integration in.
[20:28] <lamalex> :D
[20:31] <lamalex> DBO, did you figure out what was up in nux that was blocking that guy's dual monitor support patches?
[20:31] <DBO> ah fudge I forgot to follow up on that
[20:31] <DBO> my mistake
[20:38] <jcastro> tedg: if you've got time today/tomorrow I'd like a quick skype
[20:39] <tedg> jcastro, np. Can we just use the phone?
[20:40] <jcastro> sure, want me to call you?
[20:42] <tedg> jcastro, Sure, either way.
[23:43] <achiang> hm, what package contains the icons for the window controls? (close, minimize, maximize)


[00:19] <lifeless> rockstar: around ?
[00:19] <lifeless> https://bugs.edge.launchpad.net/launchpad-code/+bug/623102 needs qa
[00:19] <_mup_> Bug #623102: AttributeError on +request-builds page <oops> <qa-needstesting> <recipe> <Launchpad Bazaar Integration:Fix Committed by rockstar> <https://launchpad.net/bugs/623102>
[00:19] <lifeless> its now the front of the queue in https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[01:16] <wgrant> Fuck.
[01:17] <wgrant> Does anyone know how far back we keep primary archive publisher logs?
[01:24] <jelmer> good morning wgrant  :-)
[01:25] <wgrant> jelmer: Morning.
[01:48] <wgrant> >>> BinaryPackagePublishingHistory.distroarchseries in [1]
[01:48] <wgrant> True
[01:48] <wgrant> That looks like a bit of a misfeature.
[01:54] <jelmer> whu? How is that happening?
[01:56] <wgrant> jelmer: I suspect it's because __eq__ returns a Storm expression.
[01:56] <wgrant> Which evaluates to True.
[02:00] <wgrant> (and causes a very nasty bug.......)
[11:00] <lifeless> wgrant: nice branches
[11:00] <wgrant> lifeless: I'm getting lots of timeouts on MPs tonight.
[11:00] <wgrant> Hah, nice timing.
[11:00] <lifeless> got some #'s
[11:00] <wgrant> OOPS-1736EC482
[11:01] <wgrant> I suspected librarian issues, but then there were some reports of abnormal IBugTarget:+bugs timeouts in #launchpad.
[11:03] <lifeless> 113003.01SQL-launchpad-main-masterSELECT "_6".branch, "_6".id, "_6".revision, "_6".sequence FROM BranchRevision AS "_6" LEFT JOIN BranchRevision AS "_7" ON "_7".revision = "_6".revision AND "_7".branch = %s WHERE "_6".branch = %s AND "_6".sequence IS NOT NULL AND "_7".id IS NULL ORDER BY "_6".sequence DESC LIMIT 10
[11:04] <lifeless> (13 seconds)
[11:05] <lifeless> possibly fat indices on branchrevision
[11:07] <wgrant> Or general DB slowness.
[11:07] <wgrant> Given the other issues this evening.
[11:22] <lifeless> were there oops ids for them?
[11:22] <lifeless> we might be running on a different master I guess; I dunno where the migration got to.
[11:23] <wgrant> OOPS-1736F673
[11:24] <wgrant> lifeless: That was one of them.
[11:28] <lifeless> 115046.01SQL-launchpad-main-masterSELECT Bug.heat FROM Bug, Bugtask WHERE Bugtask.bug = Bug.id AND Bugtask.product = 8920 ORDER BY Bug.heat DESC LIMIT 1
[11:28] <lifeless> (15 seconds)
[11:28] <lifeless> so yes, some issue
[11:29] <lifeless> man the sodium crashes make our reporting so useless
[11:29] <lifeless> I can't really tell if there is an oops spike or not.
[11:51] <lifeless> jml: around ?
[12:01] <jml> lifeless: am now.
[12:03] <lifeless> jml: ah, lp:~lifeless/launchpad/bug-627701
[12:03] <lifeless> jml: It failed on ec2; I've pushed up a fix, but its a little deeper than previous
[12:04] <lifeless> jml: I would like another eyeball over it
[12:05] <jml> lifeless: sure
[12:06] <lifeless> jml: I'm primarily worried about clarity for the next person eyeballing the code
[12:06] <jml> pep8 grumble grumble
[12:08] <lifeless> I will also admit that I sent it to ec2land when I thought you were out :> I will land a tweak if you have changes, and it gets through as-is.
[12:09] <jml> +        # DB tracers are not safe for reentrant use, so we nmust do this
[12:09] <jml> typo
[12:10] <lifeless> thanks
[12:10] <jml> lifeless: other than that, looks about as clear as it's going to get. _get_request_timeout is hard to follow, but that's not new in your most recent change.
[12:12] <jml> lifeless: I suspect anyone wanting to change this code is going to have to think hard & do some poking around (e.g. what's opstats? I kind of know, but I'd want to know more before I changed that code)
[12:12] <lifeless> yeah
[12:13] <lifeless> the opstats conditional there is fugly
[12:24] <lifeless> jml: I hope my mail about qa didn't come across as grumpy or whatever; it wasn't meant to be
[12:24] <jml> lifeless: no, it doesn't.
[12:24] <jml> lifeless: I have some problems with the process that I think are fairly significant
[12:24] <lifeless> https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[12:25] <lifeless> jml: we should debug those
[12:25] <jml> lifeless: but it's hard to be clear about them at the same time as being civil. :)
[12:25] <lifeless> jml: in private mail you can be less civil if you like ;)
[12:25] <jml> lifeless: ok :)
[13:06] <lifeless> wgrant: I think there may be a db issue; theres a spike in OOPSes even though the data is crap.
[13:07] <lifeless> losa ping - we're seeing normally fine queries ballooning to 15 seconds, multple tables; if someone can eyeball the db servers health etc that would be awesome
[13:13] <wgrant> lifeless: sodium's still being crap?
[13:19] <lifeless> wgrant: yes
[15:56] <seiflotfy> hey guys
[15:56] <seiflotfy> oh nigelb is here too
[15:56] <nigelb> heh
[15:57] <seiflotfy> Ursinha, there?
[15:57] <seiflotfy> Ursinha, we need help
[15:57] <seiflotfy> i registered a project but set the worng maintainer
[15:57] <seiflotfy> and now cant change it to m4n1sh
[15:58] <seiflotfy> beuno, jml ^^
[15:58] <seiflotfy> or lifeless ^
[16:17] <Ursinha> seiflotfy, what happens when you try to change?
[16:17] <Ursinha> or you just can't?
[16:20] <Ursinha> I can't
[16:20] <Ursinha> (at least can
[16:20] <Ursinha> (at least can't find where the option is..)
[16:20] <maxb> maintainer == owner, no?
[16:21] <maxb> and you can only give ownership to teams you are a member of
[16:24] <seiflotfy> maxb, Ursinha i cant do anything
[16:24] <seiflotfy> i cant change it bac
[16:24] <seiflotfy> althoug i creatd the project
[16:24] <seiflotfy> there is no team (yeT)
[16:25] <maxb> as I said, you can only change it to teams you are a member of
[16:25] <seiflotfy> i have zero access
[16:26] <nigelb> you created a team and gave access to somone else wrongly?
[16:26] <nigelb> s/team/project
[16:27] <seiflotfy> nigelb, yes
[16:28] <nigelb> In retrospect using a team would have been a better idea.  I suppose somone here can change it for you.
[16:32] <seiflotfy> yes please
[18:54] <m4n1sh> any LP admins here? me and seiflotfy have made a huge mistake. jml lifeless Ursinha
[19:32] <maxb> m4n1sh: What exactly is the problem? Project has been given away to person who is not associated with it?
[19:34] <m4n1sh> maxb: check https://launchpad.net/trophylicious
[19:34] <m4n1sh> seiflotfy registsred it and tried to assign it to me (~manishsinha)
[19:34] <m4n1sh> maxb: but did a mistake and assigned it to ~manish
[19:34] <m4n1sh> maxb: now since he is just the driver, he cant revert it back
[19:35] <m4n1sh> maxb: what is the solution now?
[19:36] <maxb> seiflotfy should file a question (https://answers.launchpad.net/launchpad/+addquestion) explaining what happend and asking for it to be reassigned
[19:36] <m4n1sh> maxb: sure. Will tell him when he is around
[19:37] <m4n1sh> thanks
[19:37] <nigelb> sigh, I suggested that at the beginning.
[19:39] <m4n1sh> nigelb: that was the only way even I could have thought of, but still
[19:39] <m4n1sh> nigelb: seeing your after a long time. sup?
[19:40] <nigelb> m4n1sh: all good, what about you?
[19:40] <maxb> I'm afraid I think you need a full admin to change project ownership, so this will almost certainly have to wait for Monday
[19:40] <m4n1sh> nigelb: mine is also fine, too much work, too much code to handle :)
[19:40] <nigelb> lol
[19:41] <m4n1sh> maxb: full admin means? means the admin who handles LP Registry?
[19:41] <m4n1sh> I mean the team which takes orphaned projects and re-assigns them? that team?
[19:41] <m4n1sh> nigelb: yeah. Zeitgeist integration is very very time consuming
[19:41] <maxb> full admin rather than registry-admin
[19:43] <m4n1sh> maxb: okay fine. We can wait till monday. Will tell seiflofty to file the question tomorrow, which can be taken care on monday
[19:45] <maxb> m4n1sh: It would be wise to come back here on Monday and ask nicely for an admin to look at the question
[19:50] <m4n1sh> maxb: who all are the LP admin present on this channel?
[19:50] <m4n1sh> I see gary online a lot of time, does he have admin rights?
[20:32] <lifeless> moin
[21:48] <seiflotfy> waaaaaaaaaaah
[21:48] <seiflotfy> i need help
[21:58] <lifeless> hi, whats up ?