[00:04] <LeartS> cyphermox, robru: updated the bug: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/646798
[00:04] <ubot2`> Launchpad bug 646798 in Eye of GNOME "eog window size exceeds screen height" [Medium,Confirmed]
[00:04] <LeartS> Is it ok?
[00:05] <LeartS> lol thanks ubot2`
[00:05] <robru> LeartS, yes, I like it. the simplified description is much easier to understand ;-)
[00:08] <cyphermox> thanks cool
[00:09] <LeartS> Should i attach the patch on launchpad?
[00:09] <cyphermox> well, it's not necessary
[00:09] <cyphermox> it's clear on the upstream bug :)
[00:10]  * cyphermox prepares the upload for  the fix
[00:10] <LeartS> Or shall I? I've never understood the difference
[00:10] <cyphermox> to do what?
[00:11] <LeartS> cyphermox: there is a whitespace/tab only line on the first patch I uploaded (I don't know how much you care given it should be temporary)
[00:11] <LeartS> I mean when to use shall
[00:11] <LeartS> English in not my mother tongue
[00:11] <cyphermox> oh
[00:12] <cyphermox> well, nah that's not big deal, I'll just fix it as I make the package
[00:12] <cyphermox> LeartS: I meant, if you want to learn packaging I can also let you do it, but that may be more reading for you to do ;)
[00:15] <LeartS> No, I'll let you do it. I had enough fun for today..
[00:16] <cyphermox> hehe alright :)
[00:17] <cyphermox> hmm, seems it's one that is slightly bugged in UDD too
[00:20] <LeartS> Yeah, I had problems branching the latest realease
[00:20] <LeartS> It would branch 3.2 :/
[00:21] <LeartS> 3 days learning baazar, and the first bug I try to fix I can't use it..
[00:34] <cyphermox> LeartS: that's because lp:ubuntu/eog is out of sync
[00:35] <cyphermox> we package many gnome desktop thingies in lp:~ubuntu-desktop/<package>/ubuntu
[00:36] <cyphermox> fix verified...
[00:36] <cyphermox> so now I'll build the source package and upload
[00:39] <LeartS> Cool. cyphermox: would you mind uploading a screenshot of eog open with an image that was giving you problems before? I'd like to see if the new behavior is consistant
[00:40] <cyphermox> ok
[00:40] <cyphermox> it's pretty agressive with the scaling but that's fine
[00:42] <cyphermox> http://people.ubuntu.com/~mathieu-tl/Capture%20du%202013-05-09%2020:40:39.png
[00:44] <cyphermox> LeartS: uploaded to saucy.
[00:45] <cyphermox> once we get the review I'll upload to raring as well
[00:45] <cyphermox> but yeah, I expect I'll wake up tomorrow with the email in my inbox
[00:45] <LeartS> Yeah, I fear that is a remark they could do upstream. I actually never liked how eog would open large images almost maximized and prefer the size now, but I understand that it is subjective and with smaller resolutions it may be a little too much
[00:46] <cyphermox> good job anyway
[00:46] <cyphermox> scaling to 0.75 is reasonable anyway
[00:47] <LeartS> Thanks :)
[00:47] <cyphermox> otherwise you could possibly try to calculate the scale factor needed to match to the actual screen size
[00:47] <cyphermox> but yeah, this is fine
[00:47] <LeartS> well, I already know how to do that.. it came in mind when finding the bug formula
[00:48] <cyphermox> ok
[00:48] <cyphermox> bbl, I need to get back home.
[00:48] <LeartS> Just need to change 0,75 to the inverse of the aspect ratio
[00:48] <LeartS> Bye!
[01:06] <LeartS> Bye all!
[01:20] <robru> cyphermox, home yet? ;-)
[01:33] <cyphermox> now I am, yes
[01:37] <cyphermox> robru: want to review one change for me? https://code.launchpad.net/~mathieu-tl/cupstream2distro-config/autopilot-tests-autopilot/+merge/162463
[01:39] <cyphermox> robru: also https://code.launchpad.net/~mathieu-tl/cupstream2distro-config/unity-gtk-module/+merge/163247 for attente
[01:42] <cyphermox> robru: rev 299 in stacks/head/webapp.cfg seems very very wrong to me
[01:45] <cyphermox> hmm
[01:45] <cyphermox> on the other hand I guess this hook stuff is just for CI
[01:47] <robru> cyphermox, which one seems wrong? vrruiz did actually make a mistake in there recently, but he reverted it...
[01:48] <cyphermox> hooks: D09add-ppa~webapps~staging
[01:48] <cyphermox> it seems to be CI
[01:48] <cyphermox> it's still a symptom of a badly configured CI setup imho
[01:50] <robru> cyphermox, yeah, that was for CI. we were having a terrible issue getting the webapps to do CI properly because of a really heinous build-dep/bootstrapping issue.
[01:50] <cyphermox> robru: so I'm going to start the webapp run now; but still pointing to the next/daily-build-next PPAs with saucy
[01:50] <robru> cyphermox, eah
[01:50] <robru> yeah
[01:51] <robru> cyphermox, I am not certain about that particular line; if you feel it's wrong you should raise that with vrruiz and fginther, they worked on that quite a bit today and that's a small part of what they had to do to get CI even working at all. or maybe that was just a failed attempt that didn't get reverted; I'm not sure
[01:51] <cyphermox> I brought it up
[01:51] <cyphermox> I'm sure it's something that can be avoided by changing the CI logic slightly
[01:51] <cyphermox> ie. grabbing the right build-depends first.
[01:52] <cyphermox> hmm
[01:52] <robru> cyphermox, I think probably it won't be an issue once unity-webapps-common 2.4.15 is more widely distributed (eg, once it hits distro). because that version was necessary to have in the CI environment in order for CI to function on webapps (webapps packages need that dep in place even if you're just making the source package)
[01:52] <cyphermox> though I guess it's build-depends between source packages of a similar stack, so it's fine
[01:53] <robru> yeah, basically all of the lp:unity-webapps-* branches can't even do a source package build without unity-webapps-common in place (because unity-webapps-common provides the shared debian/rules file used by all webapps packages). so this situation is wreaking havoc on a lot of the tooling; nobody expected that there would be such a thing as a build dep that was needed at source-package-creation time, only at build time ;-)
[01:57] <cyphermox> ok running now
[01:57] <robru> cyphermox, so yeah, let me know if any of the stack fails. I'm pretty sure I fixed everything, but there could be a new issue now ;-)
[02:06] <cyphermox> sure
[02:06] <cyphermox> well, things are running now
[02:06] <cyphermox> but all the other stacks triggered, too
[02:06] <cyphermox> wanna watch webapps yourself? you'll see what explodes in jenkins directly
[02:06] <robru> is that bad? or just slow?
[02:06] <robru> yeah
[02:06] <robru> ok
[02:07] <cyphermox> here's another for review: https://code.launchpad.net/~mathieu-tl/cupstream2distro-config/master-job-template-sync/+merge/163249
[02:07] <cyphermox> well, it's not slow
[02:07] <cyphermox> but all the other stacks started, and some triggered before the prepare jobs started
[02:08] <robru> I don't understand this review. what's that token and why are we changing it
[02:08] <robru> ?
[02:08] <cyphermox> if you look at the queue, before webapps reaches the build stage, it will have to be done triggering a few of the other prepare jobs for things like unity
[02:08] <cyphermox> robru: it's the issue with cu2d-run
[02:08] <robru> cyphermox, clearly the original is just a placeholder. is the token not supposed to be secret?
[02:09] <cyphermox> it's just configuration; I had made an initial fix (the value you see removed) and properly fixing it here
[02:09] <cyphermox> robru: it's already not secret.
[02:09] <robru> cyphermox, alright then
[02:12] <cyphermox> hmm wtf
[02:12] <robru> what in the hell is libeatmydata?
[02:12] <cyphermox> for some reason some jobs actually trigger with cu2d-run anyway ?! o.O?
[02:13] <cyphermox> robru: it's a library that makes things not fsync() and sync() to make them go faster
[02:14] <robru> cyphermox, well it's awfully broken in jenkins right now
[02:14] <cyphermox> is it?
[02:14] <robru> http://10.97.0.1:8080/job/cu2d-webapp-head-1.1prepare-unity-webapps-facebookmessenger/11/console like 80% of this log is errors from it. it's spamming madly
[02:18] <cyphermox> fun
[02:19] <cyphermox> well it's not hugely damaging as it is right now
[02:19] <cyphermox> I'll take note and look into this tomorrow
[02:20] <cyphermox> I wish I understood what's happening with jenkins... someone must have made changed because starting jobs was definitely failing yesterday, and I could only get them to run with the token change
[02:21] <cyphermox> I truly don't understand
[02:22] <robru> cyphermox, uh, go back to that link I just linked... there's some error about saucy there
[02:22] <cyphermox> someone had to go back and fix the bug
[02:22] <cyphermox> ok
[02:23] <robru> cyphermox, it seems the PPA itself is not built for saucy? hrm... with friends stack we didn't encounter this because we just skipped straight to distro
[02:23] <cyphermox> *sigh*
[02:23] <cyphermox> it should just work...
[02:24] <robru> cyphermox, to be honest I'm quite weary of all these jenkins issues, maybe we should just push directly to distro and then fix whatever breakages we may find.
[02:24] <robru> cyphermox, I don't think anybody could blame us for breaking the dev series in the first month ;-)
[02:25] <robru> cyphermox, plus, webapps is hardly mission-criticial infrastructure. it's just web chrome ;-)
[02:27] <cyphermox> right, but I suspect it would fail just as much
[02:27] <cyphermox> well...
[02:28] <cyphermox> that shouldn't actually be failing the build either
[02:30] <robru> cyphermox, are there any saucy packages in the PPA? maybe pushing a saucy package manually would help jenkins along
[02:30] <cyphermox> meh
[02:31] <cyphermox> it probably would
[02:31] <cyphermox> but that's a really crappy way of fixing this ;)
[02:31] <robru> cyphermox, it would create the index file that jenkins is puking about not having
[02:31] <cyphermox> yes
[02:34] <cyphermox> this is so ugly.
[02:35] <robru> yep.
[02:35] <cyphermox> alright, I copied ubuntu-unity-next ;)
[02:35] <robru> hehe
[02:36] <cyphermox> just waiting until it's actually published and then I'll rerun
[02:37] <cyphermox> I don't want to just upload to distro -- we have all this tooling to avoid pushing broken stuff, so we might as well use it ;)
[02:37] <robru> cyphermox, yeah, but it's not the stuff that's broken, it's the tooling ;-)
[02:37] <cyphermox> only part of it
[02:37] <cyphermox> only the parts didrocks didn't write himself :P
[02:38] <cyphermox> actually, scratch that
[02:38] <cyphermox> this bug we're hitting is one in the scripts didrocks wrote
[02:38] <cyphermox> possibly even a feature, but I'll track it down tomorrow and file a merge
[02:39] <robru> cyphermox, fair enough. must be late there
[02:42] <cyphermox> robru: getting late yet
[02:42] <cyphermox> *yes
[02:42] <cyphermox> ok, trying again
[02:48] <cyphermox> robru: you know, this could actually be caused by the hook..
[02:48] <robru> which hook? and how?
[02:49] <robru> oh, the libeatmydata thing?
[02:49] <cyphermox> oh wait no, it's a different ppa
[02:49] <robru> cyphermox, yeah, was gonna say, webapps/staging shouldn't have too much crap in it... just webapps stuff
[02:53] <cyphermox> well, it wasn't about eatmydata
[02:56] <robru> cyphermox, you lost me. you think having an extra PPA enabled causes jenkins to die of a 404?
[02:56] <cyphermox> no
[02:57] <cyphermox> it's just late, I'm tired
[02:58] <robru> cyphermox, haha, get some sleep. I'm watching the build. it looks like it just got past that 404 now at least
[03:02] <cyphermox> yeah
[03:02] <robru> cyphermox, BAH, it's not done yet, but I just saw in the log that it downloaded unity-webapps-common 2.4.14, so basically I can already tell that this is going to fail...
[03:02] <cyphermox> ok, why?
[03:03] <cyphermox> things should just work by building from this PPA
[03:03] <cyphermox> well
[03:03] <cyphermox> by building from the same archive that it does right now
[03:03] <cyphermox> otherwise we'll need to do bootstrapping magic
[03:03] <robru> because all of lp:unity-webapps-* *require* having unity-webapps-common 2.4.15 in order to even think about building. 2.4.14 does not provide rules.mk, and therefore none of the webapps have a debian/rules file.
[03:04] <cyphermox> well, that's fine for the prepare task
[03:04] <cyphermox> actually
[03:04] <robru> cyphermox, does the prepare task build a source package?
[03:04] <cyphermox> what's that rules.mk file for?
[03:04] <cyphermox> right
[03:04] <robru> cyphermox, rules.mk *IS* debian/rules
[03:04] <cyphermox> so you need it for the OH
[03:05] <robru> cyphermox, I just provide it from unity-webapps-common since it's identical across all 41 webapps and I didn't want it to be a copy&paste nightmare
[03:05] <cyphermox> yeah, we'll need to first upload unity-webapps-common to the ubuntu-unity/daily-build-next ppa in that case
[03:05] <robru> cyphermox, so every webapp just has a 1-line debian/rules that imports rules.mk
[03:05] <cyphermox> hmm
[03:05] <robru> cyphermox, yeah, but I thought didrocks did that already.
[03:05] <cyphermox> ah, maybe for raring
[03:06] <robru> crap
[03:06] <cyphermox> ok, yeah it's there for raring
[03:06] <robru> unity-webapps-common 2.4.15 is so utterly critical that we should really bump it to version 3.0
[03:07] <cyphermox> that's up to you
[03:07] <robru> yeah, I'll talk that over with webapps guys tomorrow
[03:07] <cyphermox> ok, so there will be some magic needed to properly depend on that package then for the build
[03:08] <robru> cyphermox, by magic do you mean "we need to upload a saucy build of 2.4.15"?
[03:11] <cyphermox> well, that too :)
[03:11] <robru> cyphermox, what else is required?
[03:11] <cyphermox> no issues here with eatmydata btw, so it's got to be special to the pbuilder chroot used or whatnot
[03:17] <cyphermox> in the daily-build-next all of this should depwait until u-w-c is built, but it won't because I'll need to upload a copy of u-w-c to the ppa first in order for things to successfully prepare
[03:17] <robru> cyphermox, yep
[03:20] <cyphermox> robru: I guess it's fine, yeah I'll have to copy the package to saucy in that ppa as well
[03:24] <cyphermox> robru: actually, I don't
[03:24] <cyphermox> robru: http://10.97.0.1:8080/view/cu2d/view/Head/view/WebApps/job/cu2d-webapp-head-1.1prepare-webapps-applications/13/
[03:24] <cyphermox> watch this one; at the end, it should upload directly to ubuntu-unity/daily-build-next
[03:24] <cyphermox> in which case you'll get the package in saucy properly
[03:24] <robru> cyphermox, right, then just run the whole stack again?
[03:25] <cyphermox> then we can do another run again, yes
[03:25] <robru> cyphermox, but wait, won't it fail the whole stack?
[03:25] <cyphermox> it will fail everything else yeah, and not run through the build task
[03:25] <robru> cyphermox, jenkins will hold back the whole stack upon any single failure, so webapps-applications won't get publisehd
[03:25] <cyphermox> it will still be uploaded and actually build on the ppa
[03:25] <cyphermox> nah, it will
[03:25] <robru> ok....
[03:26] <cyphermox> in ubuntu-unity/daily-build-next only
[03:26] <cyphermox> not in ubuntu-unity/next
[03:26] <cyphermox> daily-build-next is just scratch space for the builds
[03:26] <cyphermox> everything is copied to their final destination after, and IIF the autopilot tests pass
[03:27] <robru> ok
[03:27] <cyphermox> that said, I'll do a rerun in my morning
[03:28] <cyphermox> in 6-7 hours
[03:28] <robru> cyphermox, great
[03:28] <robru> cyphermox, thanks
[03:28] <cyphermox> np
[03:28] <cyphermox> so, if anything happens send me an email
[03:28] <robru> cyphermox, ok. just about dinner time for me, I'll check it when I get back
[03:29] <cyphermox> ok
[03:29] <cyphermox> as for the token stuff, I don't know what happened
[03:29] <cyphermox> I'll need to ask retoaded in the morning, I'm convinced something was modified, I could trace the packets and see that something wasn't right
[03:30] <cyphermox> jenkins was definitely telling me to bugger off and that I had wrong credentials
[03:30] <cyphermox> maybe the extra permissions they gave me are now kicking in and didn't before
[03:34] <robru> cyphermox, no idea
[04:51] <pitti> Good morning
[04:59] <robru> pitti, hello!
[04:59] <Mirv> hello
[04:59] <pitti> hey robru, how are you?
[04:59] <robru> pitti, getting by I suppose
[04:59] <robru> pitti, how's germany treating you?
[05:00] <pitti> robru: that doesn't sound too good?
[05:00] <robru> pitti, yeah, things are rough now, not gonna lie. gf of 4 years just broke up with me. :-/
[05:00] <pitti> robru: pretty well; we had a nice hike yesterday (national holiday)
[05:00] <pitti> robru: argh, I'm sorry to hear that; that's terrible!
[05:00] <robru> it's ok
[05:01] <robru> hike sounds sweet. I've always wanted to visit germany. we should plan the next sprint for there!
[05:03] <RAOF> I'd go for a Berlin sprint.
[05:03] <robru> RAOF, yeah!
[05:05] <pitti> we had one there, although in the least fashionable part of the cicy
[05:05] <pitti> city
[05:06] <pitti> but the go-kart race was awesome :)
[05:06] <robru> pitti, yes, well, that seems to be the modus operandi around here ;-)
[05:06] <robru> (i mean, oakland is the least-fashionable part of SFO ;-)
[05:07] <pitti> heh, yes
[05:07] <pitti> as long as it's easy to get to the good parts
[05:33] <darkxst> are the category labels (left-hand pane) in software-center, required to have text wrapping?
[05:39] <pitti> darkxst: I uploaded the systemd SRU you requested FYI
[05:46] <darkxst> pitti, thanks ;)
[05:49] <darkxst> pitti, I will add the SRU paperwork a little later
[06:15] <cyphermox> pitti, robru, sprint in Montreal where you could not do it anywhere near the least fashionable parts
[06:15] <cyphermox> ;)
[06:16] <pitti> hehe -- UBZ in 2005!
[06:16] <pitti> ("Ubuntu Below Zero")
[06:16] <cyphermox> yeah
[06:16] <cyphermox> except ATM its ua35
[08:47] <sil2100> cyphermox: hi! Did you re-deploy the QA stack in the end?
[08:47] <sil2100> cyphermox: since I want to know if I forgot something in the config or not... ;)
[09:15] <Mirv> sil2100: did you figure out which version of autopilot is being run via jenkins?
[09:15] <Mirv> I now see some autopilot 1.3 test changes have been merged in trunk, and some not
[09:16] <sil2100> Mirv: it *should* use 1.3 now, since that's what's in the PPA and Francis fixed the jenkins job to do a proper upgrade
[09:16] <sil2100> Mirv: and from one job I saw, it seems that it's indeed using 1.3 already
[09:18] <sil2100> Mirv: yep, at least the OIF stack is using 1.3 - so I think it's the same for all
[09:24] <Mirv> sil2100: ok, good, better that way, now we just need to merge remaining fixes / do more fixes to run on 1.3
[09:24]  * sil2100 just got a failure by success
[09:31] <sil2100> attente_: hi! Once you're here, I re-merged trunk into that 1.3 autopilot branch -> https://code.launchpad.net/~sil2100/unity-gtk-module/autopilot_1.3_modifications/+merge/163203
[09:31] <sil2100> attente_: if you want to test it with autopilot 1.3, we have the latest autopilot in our daily-build-next PPA
[09:32] <sil2100> attente_: https://launchpad.net/~ubuntu-unity/+archive/daily-build-next
[09:32] <sil2100> attente_: if you want to test it on 1.3, after adding that PPA install/upgrade autopilot-desktop and unity-autopilot
[10:23] <sil2100> fginther: ping once you're here
[11:33] <LeartS> When trying to connect to pad.ubuntu.com, It says: "PAD has requested some personal information. Please choose what you would like to share:" but there is nothing I can check, and if I click on "Yes, log me in" it says that I have not granted access ..
[11:38] <czajkowski> LeartS: are you part of the etherpad team ?
[11:38] <czajkowski> LeartS: https://launchpad.net/~ubuntu-etherpad
[11:39] <LeartS> No, I just saw the link in the channel topic and paid a visit :)
[11:39] <LeartS> What's the etherpad team?
[11:40] <LeartS> It has a lot of members!
[11:40] <czajkowski> it does we use it for UDS for note takig
[11:40] <czajkowski> *taking
[11:41] <LeartS> UDS = Ubuntu Development ?
[11:42] <czajkowski> summit
[11:43] <czajkowski> uds.ubuntu.com
[12:51] <fginther> sil2100, pong
[12:51] <attente_> sil2100, thanks
[12:56] <LeartS> czajkowski, robru: the patch has been accepted upstream.
[12:56] <czajkowski> nout to do with me
[12:56] <attente> sil2100, i'm getting the following: ImportError: cannot import name get_compiz_option
[12:57] <attente> this is with a 1.3 version of autopilot-desktop
[12:58] <attente> and python-autopilot
[12:58] <LeartS> ops, sorry czajkowski ! I meant cyphermox
[13:02] <sil2100> attente: did you install latest unity-autopilot?
[13:03] <attente> ah, that's still coming from archive, thanks
[13:03] <LeartS> Can I force a remote bug watch update on launchpad?
[13:06] <fginther> sil2100, ping?
[13:06] <sil2100> fginther: ah!
[13:06] <sil2100> fginther: morning!
[13:07] <sil2100> Didn't notice your pong ;) Sorry, been eating
[13:07] <sil2100> fginther: ok, so, I actually have two things related to generic job again... :<
[13:08] <sil2100> fginther: let me pastebin the question I poked Martin with already
[13:08] <sil2100> fginther: http://paste.ubuntu.com/5651092/
[13:08] <fginther> sikon, ok
[13:08] <fginther> sikon, sorry, wrong id
[13:08] <fginther> sil2100, ok
[13:08] <sil2100> fginther: it's related to the recent AP test runs failing quickly, in mid-test
[13:13] <fginther> sil2100, have you talked to the utah guys?
[13:14] <sil2100> fginther: not yet, but you think it's mostly utah at fault? Since it's happening since like a few days already maybe
[13:15] <fginther> sil2100, I don't know yet, just wondering if they've had a look yet
[13:18] <fginther> sil2100, did #328 fail for the same reason?
[13:19] <sil2100> fginther: I checked and I'm not sure, as it was able to execute all tests it was said to
[13:19] <sil2100> Since there aren't too many for the OIF stack
[13:19] <sil2100> fginther: probably yes, as there's the same message: "Build step 'Execute shell' marked build as failure"
[13:34] <attente> sil2100: i'm still having the same problem, even with the updated python-autopilot
[13:34] <attente> can you tell me what versions of autopilot-desktop, python-autopilot and unity-autopilot you're using?
[13:37] <sil2100> autopilot-desktop: 1.3daily13.05.08ubuntu.unity.next-0ubuntu1, python-autopilot: 1.3daily13.05.08ubuntu.unity.next-0ubuntu1 and unity built locally yesterday from trunk, so actually 7.0.0daily13.05.08ubuntu.unity.next-0ubuntu1 should be fine
[13:37] <sil2100> As it's working for the auto-builders
[13:40] <sil2100> attente: I saw an error message like this before, but it disappeared when the new unity-autopilot package appeared in the PPA
[13:46] <attente> sil2100, the index for the packages in saucy has the unity-autopilot package fixed to an older one 7.0.0daily13.05.01.1ubuntu.unity.next-0ubuntu1
[13:47] <attente> is there a way for you to update it?
[13:47] <sil2100> Ah, saucy!
[13:47]  * sil2100 is still on raring
[13:48] <attente> ;)
[13:48] <sil2100> Since the daily-release machines are still running on raring ;)
[13:48] <sil2100> Ok, but that explains all - you can simply do a bzr bd on lp:unity and temporarily install unity-autopilot from the generated packages
[13:49] <attente> sure
[13:49] <sil2100> Thanks! I would put it up somewhere, the package that is, but I just recently removed it when cleaning up my workspace ;p
[13:49] <bashrc> I wonder if anyone can advise me on how to get an application into the messaging menu
[13:55] <sil2100> robru: give me a ping when you're around
[14:15] <bashrc> I'm basing the messaging code on http://developer.ubuntu.com/resources/technologies/messaging-menu/
[14:15] <bashrc> with appropriate .desktop file and window showing function
[14:15] <bashrc> but nothing appears on the messaging menu
[14:15] <bashrc> any ideas on why not?
[14:16] <bashrc> (tumbleweeds roll by)
[14:22] <bashrc> (wind whistles gently)
[14:24] <sil2100> ;)
[14:25] <czajkowski> bashrc: patience people are working and  may not be looknig at irc
[14:25]  * ogra_ hands bashrc a kite ... 
[14:25] <bashrc> ok, I'll try not to disturb the sleep
[14:25] <czajkowski> bashrc: or work :)
[14:25] <czajkowski> people do work
[14:26] <czajkowski> oh an ogra_ ello
[14:26] <bashrc> (mars rover moves slowly across the landscape)
[14:26] <ogra_> hey czajkowski
[14:26] <sil2100> hehehe
[14:27] <mitya57> bashrc: that guide is outdated, one should use libmessagingmenu instead
[14:27] <bashrc> ok
[14:27] <mitya57> (probably dpm can remove/update that)
[14:29] <dpm> hi mitya57, what's up?
[14:29] <mitya57> bashrc: there is some HTML documentation in libmessaging-menu-dev package
[14:29] <bashrc> ok
[14:29] <bashrc> well hidden
[14:29] <mitya57> dpm: code on http://developer.ubuntu.com/resources/technologies/messaging-menu/ is outdated and does not work in >= quantal
[14:30] <bashrc> I see
[14:30] <dpm> mitya57, ah, thanks. Would you mind filing a bug and pointing to the changes required?
[14:31] <bashrc> ok
[14:31] <mitya57> dpm: just remove that page. I can try to write a better example if you want, but not today
[14:34] <bashrc> To be clear, what should I file a bug against in Launchpad?
[14:35] <mitya57> I'm filing it myself
[14:35] <bashrc> ok
[14:39] <mitya57> bashrc, dpm: bug 1178700
[14:39] <ubot2`> Launchpad bug 1178700 in Ubuntu App Developer site "Python code snippets are outdated and don't work" [Undecided,New] https://launchpad.net/bugs/1178700
[14:43] <bashrc> Thanks.  https://github.com/Bitmessage/PyBitmessage/issues/135#issuecomment-17724056
[14:43] <dpm> thanks mitya57
[14:44] <mitya57> bashrc: I can suggest you to use https://code.launchpad.net/unity-mail as an example of working code
[14:46] <bashrc> ok I'll check it out
[16:08] <sil2100> fginther: can I have one more request? In some free moment - since lp:unity-gtk-module doesn't seem to have autolanding enabled
[16:08] <sil2100> fginther: we want to add it to daily-release
[16:09] <fginther> sil2100, I think cyphermox was working on that
[16:13] <cyphermox> sil2100: there's a merge for that
[16:13] <cyphermox> or did I forget to file the merge and just do the change locally
[16:37] <sil2100> cyphermox: awesome
[16:40] <sil2100> robru: piiing?
[16:42] <sil2100> cyphermox: about the QA stack redeployment... did you redeploy in the end?
[16:42] <cyphermox> I missed that it seems
[16:42] <cyphermox> I was fighting issues with webapps
[16:42] <cyphermox> sil2100: it ran today though
[16:51] <sil2100> cyphermox: ok, since in the morning I didn't see the check job I added, so I was wondering if I screwed something up in the config
[16:59] <desrt> mterry: so... ~/.cache/music is a thing now
[16:59] <desrt> my music library from my media server, so i can carry it around with me
[16:59] <desrt> symlinked from ~/Music/Library -> ~/.cache/music
[17:00] <mterry> desrt, ok.  you see a problem?
[17:00] <desrt> no
[17:00] <desrt> it's glorious
[17:00] <desrt> i love it
[17:00] <mterry> desrt, ah  :)  A happy tale
[17:00] <desrt> well
[17:00] <desrt> i'll see a problem if dejadup decides to follow that symlink :)
[17:00] <desrt> but i think it doesn't
[17:00] <mterry> desrt, that's nice.  Is that a setup you made or something a program does for you?
[17:01] <desrt> mterry: i made it... i'm thinking about scripting it a bit, though
[17:01] <mterry> desrt, no it won't, unless you point directly at a symlink in includes/excludes
[17:01] <desrt> most of my music collection is flac
[17:01] <cyphermox> sil2100: what job?
[17:01] <desrt> i have this program called flacsync that whacks it down to .ogg files
[17:01] <desrt> and i have only the oggs on my laptop
[17:02] <mterry> desrt, ah nice
[17:05] <sil2100> cyphermox: in the QA stack, since I added autopilot tests so theoretically cu2d-qa-head-2.2check should appear in QA Head, but I don't see the job there
[17:10] <sil2100> cyphermox: are we ready for announcing the touch components daily-releasing, or are there some problems still?
[17:10] <sil2100> robru: ^ ?
[17:17] <cyphermox> sil2100: not everything is done being prepared
[17:19] <cyphermox> sil2100: sorry, guess i misunderstood -- I updated the qa stack you'll have the check job now
[17:19] <cyphermox> I'll do a rerun now
[17:19] <cyphermox> do you know what python-upa is?
[18:41] <robru> cyphermox, I see you ran webapps again this morning and it's failed again. I'm looking at the logs though and I don't see it even trying to do anything useful -- it just pukes early on, before all the deps are even installed.
[18:41] <robru> cyphermox, so I think something is really fishy with the jenkins server. who should we ping on that? mmrazik?
[18:57] <tkamppeter> jasoncwarner, hi
[19:02] <cyphermox> robru: it fails in many ways. retoaded may be able to help
[19:03] <robru> cyphermox, ok. well I'm officially off today so if you could try to pester some people about that it would be super. I'm still reasonably confident that the stack is in good shape for landing, it's just jenkins itself that is very broken
[19:04] <cyphermox> yes
[19:05] <robru> off to the beach!
[19:33] <cyphermox> kenvandine: around?
[19:33] <cyphermox> kenvandine: I need help with a few MPs if you have time
[19:33] <cyphermox> https://code.launchpad.net/~mathieu-tl/cupstream2distro-config/python-upa-daily-false/+merge/163348
[19:35] <kenvandine> cyphermox, sure
[20:02] <bashrc> Making progress on the messaging menu
[20:03] <bashrc> is there a way to prevent an application selected on the messaging menu from opening more than one instance?
[20:06] <larsu> bashrc: yes, make the app single instance
[20:06] <bashrc> is there a way to do that in python?
[20:06] <larsu> certainly. Are you using gapplication?
[20:07] <larsu> oh wait, are you using gtk at all?
[20:07] <bashrc> It's Qt
[20:07] <bashrc> Qt4
[20:08] <larsu> hm, I don't know a lot about qt...
[20:09] <larsu> a quick google seasrch brings up QtSingleApplication, but it seems to be some kind of addon, not included with qt4
[20:10] <bashrc> ok
[20:10] <bashrc> Anyway, I have the messaging menu mostly working now
[20:11] <geser> given a package (razorqt) synced from Debian which build-depends on liblightdm-qt-dev (doesn't exist in Ubuntu): is replacing this build-dependency with liblightdm-qt-3-dev and have pkg-config check for liblightdm-qt-3 (instead of liblightdem-qt-2) the right "fix" to let the package build?
[20:11] <bashrc> one curious thing is when selecting an item (number of unread messages) it then disappears
[20:11] <larsu> bashrc: that's by design
[20:12] <bashrc> ok, but I'm not sure I follow
[20:13] <larsu> the messaging menu should only show sources that have unread stuff in it. When clicking, your app should present a window showing the unread items
[20:13] <bashrc> From the design standpoint should I be showing mail folders with numbers of unread messages, or individual messages?
[20:14] <larsu> which messaging menu are we talking about, the one on the desktop or on the phone?
[20:14] <bashrc> desktop
[20:16] <larsu> show mail folders on the desktop (but be aware that this might change soon)
[20:16] <bashrc> ok.  If I show folders with unread messages, then select it it doesn't necessarily imply that all unread messages have been read
[20:17] <bashrc> intuitively it doesn't make much sense for it to disappear if there are more than a single unread message
[20:19] <larsu> it's more about "new" messages than it is about "unread" messages
[20:19] <larsu> there's a good explanation of it here: https://wiki.ubuntu.com/MessagingMenu#Recommended_behavior_for_e-mail_clients
[20:19] <bashrc> ok, so I should only be showing anything that's new
[20:19] <larsu> exactly
[20:22] <bashrc> Ok I think I understand how it's intended to work now
[21:59] <mlankhorst> Laney: biked 80 km today ;P