[05:49] <pitti> Good morning
[05:54] <didrocks> hey pitti, how are you?
[06:01] <pitti> bonjour didrocks !
[06:01] <pitti> ça va bien, nous avons été un bon w.e. à Dresden
[06:02] <pitti> didrocks: et toi?
[06:02] <didrocks> pitti: week-end sympathique aussi :) Par contre, il n'arrête pas de pleuvoir et ça n'est pas parti pour s'améliorer dans la semaine qui vient.
[06:04] <pitti> :(
[06:04] <pitti> we had rather nice weather, we did two nice long walks
[06:08] <didrocks> lucky you!
[06:08] <didrocks> we had a nice walk yesterday, but between 2 rains stop
[06:15] <Mirv> welcome back didrocks
[06:20] <didrocks> hey Mirv! thanks :) how are you?
[06:31] <Mirv> didrocks:
[06:31] <Mirv> fine! :)
[06:48] <Mirv> didrocks: still something funny with SDK runs btw, but the intel autopilot tests did succeed now. yesterday the ati machine tests had hung somehow. now they had succeeded, but nvidia machine results are apparently hanging since there's no link for those.
[06:49] <Mirv> all in all I've success on all three autopilot machines, so I believe the sdk stack is ok if the test processes would just work hitch-free
[06:49] <didrocks> Mirv: we disabled the nvidia machine, do you still see it used anywhere? It should just have disappeared. Otherwise, it means we forget something…
[06:49] <didrocks> Mirv: do you have any handy link?
[06:51] <Mirv> didrocks: jenkins is not answering to me, but it seemed like the head/sdk/check had stallen in some wait loop, even though the autopilot tests had succeeded
[06:51] <didrocks> Mirv: hum, I'm getting no anwser as well from magners
[06:51] <Mirv> didrocks: the nvidia machine did seem disappeared, I just assumed it was something similar to yesterday's random ati machine hanging
[06:53] <didrocks> Mirv: yeah, no, the nvidia machine is used to test otto (the UTAH replacement) that I'm working on with jibel
[06:53] <didrocks> so we removed it
[06:53] <Mirv> ok
[06:53] <Mirv> let's see when jenkins is back
[06:53] <didrocks> Mirv: and yeah, ati has an installer failed utah or whatever…
[06:54] <didrocks> (I'm looking at the public jenkins)
[06:54] <didrocks> Mirv: so once jenkins is back, should we publish manually?
[06:54] <didrocks> Mirv: I'll reask to fix the creds this afternoon for you
[06:54] <Mirv> didrocks: yes. and thanks.
[06:54] <didrocks> but can do it meanwhile
[06:54] <didrocks> Mirv: great, did you look at your other stacks? everything's fine?
[06:55] <Mirv> didrocks: those are fine
[06:55] <didrocks> sweet :)
[06:59] <jibel> good morning
[07:02] <didrocks> salut jibel, ça va?
[07:02] <didrocks> bon week-end?
[07:03] <jibel> Salut didrocks! Ça va malgré le w.e pluvieux et froid digne d'un mois de novembre
[07:04] <didrocks> jibel: pareil ici :/
[07:06] <didrocks> Mirv: I can't ssh to magners as well
[07:06] <didrocks> jibel: once you have taken your first cup of coffee, FYI ^
[07:07] <jibel> didrocks, already had it, I'll have a look
[07:07] <didrocks> thanks :)
[07:11] <jibel> didrocks, I cannot reach any machine there
[07:13] <jibel> didrocks, but I can reach CDUs and KVMs, it'd mean the magners-o is down.
[07:16] <didrocks> jibel: urgh, so we have to wait for this afternoon, I guess?
[07:17] <jibel> didrocks, I afraid the answer is yes. Someone is connected to the KVM of this server and access is exclusive. I looking for a way to force disconnection.
[07:19] <didrocks> jibel: ok
[07:27] <sil2100> oh
[07:58] <Laney> hallo
[08:17] <mlankhorst> g'day
[08:23] <seb128> hey desktopers
[08:24] <Laney> hey seb128
[08:24] <Laney> good long weekend?
[08:24] <seb128> hey Laney
[08:24] <didrocks> salut seb128!
[08:24] <didrocks> hey Laney
[08:24] <seb128> yes, saturday had very nice weather, which was good in between the endless rains
[08:25] <seb128> raining since and probably until the end of the month...
[08:26] <Laney> oh... lots of time for video games then :P
[08:26] <didrocks> at least birds are singing :)
[08:26] <didrocks> but yeah, I didn't sign up for London's weather here :)
[08:26] <Laney> we had enough sun on Sunday that I could go out cycling with no jumper on for the first time in a while
[08:36] <Laney> seb128: regular "are the retracers working?" poke
[08:36] <mlankhorst> seb128: irregular 'sign my gpg key?' poke
[08:36] <Laney> someone's applying for DM
[08:37] <mlankhorst> hah :p
[08:37] <mlankhorst> it's easier to upload a package once, then copy it over from debian, less work
[08:37] <Laney> it's the way to go, for sure
[08:39] <pitti> bonjour seb128
[08:40] <seb128> pitti, salut, ça va ? tu as passé un bon W.E ?
[08:40] <seb128> Laney, no retracer lock, they should be running
[08:40] <pitti> seb128: oui, c'était très bienh
[08:40] <Laney> ok
[08:40] <seb128> pitti, ^ or did you just restarted them?
[08:40] <pitti> seb128: no, I restarted them last week
[08:41] <pitti> (and fixed the bug which made it crash)
[08:41] <seb128> Laney, ah
[08:41] <seb128> "Ubuntu 13.10 which does not have a config available, skipping
[08:41] <seb128> "
[08:41] <pitti> seb128: nous avons beaucoup de soleil, contrairement à tu
[08:42] <pitti> seb128: ah, of course
[08:42] <seb128> pitti, chanceux !
[08:42]  * pitti creates saucy retracer config
[08:42] <Laney> add it to NRCP!
[08:42] <seb128> pitti, danke
[08:42] <pitti> NRCP?
[08:43] <Laney> https://wiki.ubuntu.com/NewReleaseCycleProcess
[08:43] <Laney> (it is, in fact, already there)
[08:45] <pitti> committed/updated
[08:47] <seb128> pitti, typing "weather augsburg" in google doesn't give an happy forecast either, the google weather stuff has rain signs for 6 or the next 9 days
[08:47] <pitti> yeah; it's rather cloudy/sunny ATM, but it rained last night
[08:47] <seb128> seems you have cold weather as well?
[08:47] <pitti> it was much warmer in Dresden
[08:47] <pitti> (blue sky, sun, and 24 degrees on Sunday)
[08:48]  * seb128 wants that
[09:39] <chrisccoulson> hey seb128
[09:42] <seb128> chrisccoulson, hey, how are you?
[09:43] <seb128> chrisccoulson, I'm just done catching up with w.e email, I saw that you defeated libdbusmenu, well done! ;-)
[09:43] <chrisccoulson> seb128, yeah, i'm not too bad thanks. how are you? did you have a good weekend?
[09:44] <seb128> I'm good thanks (though I start having a start of running nose, not surprising with all this cold and rainy "spring")
[09:44] <seb128> w.e was great, we had a nice and sunny saturday, which was great
[09:44] <chrisccoulson> seb128, yeah, it's pretty miserable here. although, it was nice on sunday - i managed to get the car washed again ;)
[09:44] <seb128> and then 2 days of rain at doing nothing fancy but it was still relaxing ;-)
[09:46] <seb128> hehe
[09:46] <seb128> here saturday was nice enough that we managed to grill some meat outside for dinner ;-)
[09:46] <chrisccoulson> nice :)
[09:46] <seb128> going to rain until the end of month now though it seems :/
[09:47] <chrisccoulson> yeah, summer's finished now ;)
[09:48] <seb128> :-(
[10:11] <sil2100> Is jenkins still down?
[10:11] <mlankhorst> is so that's the perfect time to sign someone's key
[10:13] <Laney> get out there and meet some debianers http://wiki.debian.org/Keysigning/Offers#NL
[10:15] <mlankhorst> I did, but he forgot to sign too!
[10:15] <Laney> the horror
[10:16] <mlankhorst> (when I was at debian release party, half of the reason I went there too)
[10:16] <Laney> (reminds me, someone has been chasing me to meet for keysigning since october)
[10:16] <mlankhorst> same at fosdem :P
[10:17]  * Laney mails him back suggesting to meet tomorrow
[10:18] <didrocks> sil2100: right, we need to wait for the US folk to wake up
[10:22] <Laney> it's arranged
[10:23] <Laney> thanks mlankhorst for reminding me ;-)
[10:25] <seb128> mlankhorst, sorry, forgot again to sign your key, doing that now
[10:25] <mlankhorst> Laney: np :)
[10:38] <seb128> Sweetshark, xnox: hey, what's the status of "making libreoffice build on saucy" then? is that being actively worked and by who?
[10:38] <xnox> seb128: me, first day back from vacation. didn't get around looking at it during uds.
[10:38] <seb128> xnox, ok, welcome back ;-)
[10:39] <seb128> xnox, I hope you enjoyed sunny California
[10:39] <xnox> ... and Nevada and NYC =)
[10:39] <xnox> I did, indeed.
[10:39] <seb128> cool
[10:42] <seb128> Laney, mlankhorst: you guys don't have an url on debian keysigning for the dummies by any chance?
[10:42] <seb128> hate key signing :p every time I just poke around and end up doing some -sign-key and sent to a random keyring wondering if I did things right
[10:43] <Laney> seb128: I use 'caff' from the 'signing-party' package
[10:43] <seb128> does that require a working sendmail?
[10:44] <Laney> it's easiest if you have that but I think it also writes them to a file
[10:45] <Laney> I've got ssmtp as an easy to set up local MTA for that kind of thing
[10:45] <Laney> makes a few tools work, such as reportbug
[10:45] <seb128> hum, A671013C3 is not a keyid.
[10:46] <seb128> ups
[10:46] <seb128> typo
[10:46] <seb128> Laney, thanks
[10:47] <Laney> np
[10:50] <mlankhorst> seb128: using short key? naughty :P
[10:50] <seb128> mlankhorst, do you want your key to be signed or not? :p
[10:51] <seb128> mlankhorst, well I verify that the long number it gaves me matches your card
[10:51] <mlankhorst> :)
[10:51] <seb128> but I'm not going to type that :p
[10:51] <mlankhorst> good enough
[10:54] <seb128> mlankhorst, sent it to you by email, let me know if that worked out, I had to hack around to import the email caff dumped on disk since I don't have a local smtp here
[10:54] <mlankhorst> seb128: you forgot the body :)
[10:54] <seb128> hate tb
[11:02] <mlankhorst> lucky you, I'm trying to fixup the arsenal xorg scripts, it's a mess of python perl and other stuff
[11:04] <Sweetshark> seb128: bug 1182082 is a pain. I still need to figure out if the menus are not showing up at all for raring users -- they certainly do here for me, although with a delay when first opening the menu.
[11:04] <ubot2> Launchpad bug 1182082 in libreoffice (Ubuntu) "libreoffice menu not working" [Undecided,Incomplete] https://launchpad.net/bugs/1182082
[11:05] <Sweetshark> seb128: Anyone testing the stuff on https://launchpad.net/~libreoffice/+archive/ppa is highly welcome.
[11:09] <seb128> Sweetshark, ok, you should perhaps email ubuntu-devel@ about that?
[11:09] <seb128> or at least make a call for testing at the meeting this afternoon
[11:11] <seb128> mlankhorst, I sent your key to keyserver.ubuntu.com ... let me know if you can get the signature from there?
[11:16] <mlankhorst> doesn't look like it shows up there
[11:25] <seb128> mlankhorst, ok, sent you the file that the script dumped on me, can you do something from it? ;-)
[11:27] <mlankhorst> yeah
[11:28] <mlankhorst> thanks, now it shows up :)
[11:28] <seb128> excellent
[11:28] <seb128> sorry for the time it took me to do the signing :p
[11:29] <mlankhorst> np
[11:30] <Sweetshark> seb128: I just wrote bdrung that I dont want to SRU that one anymore, essentially for https://bugs.launchpad.net/df-libreoffice/+bug/1182082/comments/8. I will keep the change for saucy as it is upstream anyway there.
[11:30] <ubot2> Ubuntu bug 1182082 in libreoffice (Ubuntu) "libreoffice menu not working" [Undecided,Incomplete]
[11:31] <seb128> Sweetshark, ok, makes sense
[11:50] <ricotz> Sweetshark, hi :), while seeing this http://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-4-0&qt=grep&q=Uploading+ it is more than reasonable to backport at least matching version from saucy/debian to the ppas
[12:15] <mlankhorst> didrocks: ping?
[12:15] <didrocks> mlankhorst: pong
[12:17] <mlankhorst> didrocks: there's going to be a transition to x1.14 soon, and unity will be updated at the same time too for the new input abi, who is in charge of unity in saucy?
[12:18] <didrocks> mlankhorst: bregma's team
[12:18] <didrocks> mlankhorst: when it the transition planned?
[12:19] <mlankhorst> asap :)
[12:20] <didrocks> mlankhorst: will need a more define time, please :)
[12:20] <didrocks> mlankhorst: like, if we can have one transitionned to saucy unity landing first, that would help
[12:20] <didrocks> mlankhorst: then, we can move to the new compiz
[12:20] <didrocks> and finally the new x
[12:21] <mlankhorst> well, the problem is incompatibility, either old libxi/libxfixes/x11proto*/unity are used, or the new. There is no step in between. :(
[12:22] <didrocks> mlankhorst: yeah, hence the fact that we should plan on a date for landing
[12:22] <didrocks> and not asap ;)
[12:22] <didrocks> need something defined and clear ;)
[12:23] <mlankhorst> yeah, I'll coordinate with the right people
[12:24] <Sweetshark> ricotz: maybe ...
[12:25] <Sweetshark> ricotz: lets see what 4.1 really ends up with.
[12:25] <didrocks> mlankhorst: keep me in the loop, as we need to have a "landing side" of things :)
[12:25] <ricotz> Sweetshark, fyi this is the 4.0 branch
[12:26] <Sweetshark> ricotz:
[12:26] <ricotz> Sweetshark, what i mean is i want to ignore what is available in raring and backport the "suggested" upstream dependencies
[12:27] <mlankhorst> didrocks: sure, I just need to find the right people to make it happen :)
[12:27] <Sweetshark> ricotz: hmmm, nah. I want the PPA as a staging ground for SRUs.
[12:27] <didrocks> mlankhorst: IIRC, there was a patch laying around for the edge barriers last cycle
[12:28] <Sweetshark> ricotz: if upstream updates deps in a minor release, that is stupid in itself, but a sideeffect of SUSE pushing for a 4.0 release now.,
[12:29] <Sweetshark> ricotz: I should bring that up in the upstream ESC. Clearly updating something like wp*/mspub/cdr* on the stable branch is ... suboptimal.
[12:29] <mlankhorst> didrocks: we already have the patch in the ppa, but I want the unity team to know so they can include it in the source after the transition is done
[12:30] <ricotz> Sweetshark, i see, of course those sideeffects are bug fixes too
[12:30] <didrocks> mlankhorst: well, at the same time than the transition, right?
[12:30] <didrocks> mlankhorst: to not break saucy
[12:30] <mlankhorst> yeah
[12:30] <Sweetshark> ricotz: they are properly reviewed though ...
[12:30] <ricotz> Sweetshark, yeah, do that, but it already happened and e.g. libcdr has mentioned/reported bug fixes
[12:32] <ricotz> Sweetshark, btw are the upstream debian packages built with --disable-lomenubar?
[12:34] <mlankhorst> didrocks: it's all going to happen from the same ppa though, so it wouldn't break unity. Still it wouldn't be nice to do it without their knowledge. :)
[12:35] <didrocks> mlankhorst: hum, I would prefer we use daily landing for that instead of putting unity in another ppa :)
[12:36] <mlankhorst> didrocks: unfortunately that would kill the atomicity
[12:37] <seb128> mlankhorst, just make unity depends on libxi (>= new), it will block in saucy-proposed until the xorg side lands
[12:37] <Laney> we can block things in proposed if needed
[12:37] <Laney> or versioned deps... oh yeah that
[12:37] <seb128> get a daily landing of unity with the updated depedns
[12:37] <seb128> once it's in you can upload xorg
[12:37] <mlankhorst> ok
[12:38] <Laney> I suppose you'll need to make the testing environment use the new PPA temporarily though
[12:38] <Laney> maybe>?
[12:38] <seb128> oh, right, the merger will not like that otherwise
[12:38] <seb128> that's tricky
[12:38] <seb128> didrocks, ^
[12:38] <seb128> how do we get the patch merged if it breaks unity/test unless a new xorg, which is not in the archive, is used?
[12:39] <seb128> can we tell jenkins to run the tests using another ppa?
[12:39] <Laney> it's a bit odd because then you won't be testing what actually will land
[12:39] <seb128> or do we copy xorg in the unity staging one?
[12:39] <didrocks> seb128: that's possible for a run, we can as well do a binary copy of the new xorg and then remove it
[12:39] <pitti> why don't you put the new X into the unity PPA then?
[12:40] <pitti> right
[12:40] <seb128> pitti, snap :p
[12:40] <didrocks> well, seems we are in aggreement :)
[12:40] <seb128> bu yeah, seems the easier
[12:40] <Laney> unless you can make the daily release stuff copy X too
[12:40] <mlankhorst> stage the entire xserver transition from the unity ppa?
[12:40] <Laney> suppose blocking it in proposed is enough
[12:40] <didrocks> Laney: that starts to be tricky, I like the blocking in proposed
[12:40] <didrocks> mlankhorst: how many package is this?
[12:40] <didrocks> package*s*
[12:40] <didrocks> I guess :p
[12:40] <mlankhorst> 30 or so
[12:41] <Laney> you can just do PPA depends, should be mostly the same as uploading into that PPA
[12:41] <mlankhorst> of which 2 NEW
[12:41] <didrocks> ah, not that fun
[12:41] <seb128> well, you want to block in proposed in any way
[12:41] <Laney> if it's kept clean
[12:41] <didrocks> Laney: it's only for building
[12:41] <didrocks> Laney: doesn't work when you want to install B with A
[12:42] <mlankhorst> which is the reason why I want to do a direct copy from ppa to archive using a single ppa only :)
[12:42] <didrocks> let's add the 2 ppas for this test running
[12:42] <didrocks> mlankhorst: well, you will copy something that is not Unity trunk if you wait for some time
[12:43] <didrocks> mlankhorst: and you will have dailies meanwhile
[12:43] <mlankhorst> didrocks: well, good enough for me :)
[12:44] <didrocks> mlankhorst: sorry, not for me :p
[12:44] <mlankhorst> o.O
[12:45]  * mlankhorst no longer sure what the plan is, then
[12:46] <didrocks> mlankhorst: we can add the build-dep temporarly against your ppa once it's ready and the code is in unity
[12:46] <didrocks> mlankhorst: then, having the tests adding your ppa at the same time
[12:46] <didrocks> run all that
[12:46] <didrocks> validate
[12:46] <didrocks> and have the daily pushing to distro
[12:47] <mlankhorst> the x1.14 staging ppa should be ready at this point
[12:47] <Laney> yeah sorry, I was implying adding the deb line too
[12:47]  * Laney runs off to lunch
[12:47] <didrocks> mlankhorst: yeah, but as told, I want that to be separated by a first landing in saucy
[12:47] <didrocks> mlankhorst: which is blocked by the touch apps
[12:47] <didrocks> normally, by the end of week, we'll have one
[12:47] <mlankhorst> yeah
[12:50] <mlankhorst> didrocks: I'll ask bregma about including the x1.14 ppa then for the tests and the unity-daily build
[12:51] <bregma> mlankhorst, we've done the exercise already in the past, so it's just a matter of rebasing the barnch
[12:51] <mlankhorst> yeah :)
[12:51] <mlankhorst> and add the libxi/libxfixes versions so it won't use the old ones
[12:52] <didrocks> mlankhorst: I think I'll have to add it as I'm in charge of this :p
[12:53] <mlankhorst> :-)
[12:53] <bregma> We need to get the unity upstream changes into a PPA for testing first, then worry about merging that into distro
[13:07] <mlankhorst> didrocks: oh I didn't know you were an archive admin, can you do the copy of x-staging ppa to archive when unity is ready? :)
[13:09] <didrocks> mlankhorst: sure
[13:10] <mlankhorst> thanks!
[13:11] <didrocks> yw ;)
[13:21] <mlankhorst> didrocks: on a related note, any idea how we will solve support for precise which has to support both barrier implementations if we backport x 1.14 to precise? All solutions I came up with suck.
[13:22] <didrocks> mlankhorst: I think it's a question for bregma. The best would be to have the code inside Unity 5 first, and having to support both cases (that would help for Unity 7 as well)
[13:22] <didrocks> bregma: is the code done so that it can be backward compatible?
[13:23] <didrocks> mlankhorst: as the code didn't really change for this between unity 5 and 7 AFAIK, the backport would be easy, but we need to have Unity supporting both cases
[13:23] <bregma> we need to wait for bschaefer to appear, he can answer that better than I
[13:23] <mlankhorst> ok
[14:10] <sil2100> Jenkins restarting \o/
[14:21] <ritz_> 0to12
[14:22] <ritz_> bhaa
[14:22] <ritz_> wrong window
[14:31] <Laney> Mirv: is https://code.launchpad.net/~timo-jyrinki/ubuntu-seeds/ubuntu-touch.raring.fixlp1167197/+merge/158015 still relevant?
[14:32] <Laney> I assume s/raring/saucy/ now
[15:30] <seb128> hey
[15:31] <Laney> oops, that discussion took up my summary writing time :P
[15:31] <seb128> it's meeting time
[15:31] <seb128> hehe
[15:32] <seb128> Sweetshark, qengho, Laney, mlankhorst, tkamppeter_, attente, desrt, larsu: hey, it's weekly meeting time
[15:32] <seb128> https://wiki.ubuntu.com/DesktopTeam/Meeting/2013-05-21
[15:33] <seb128> Sweetshark, hey
[15:35] <seb128> no Sweetshark?
[15:35] <seb128> qengho, hey
[15:36] <seb128> seems like most people are not around today, what's going on :-)
[15:36] <seb128> Laney, hey
[15:36] <Laney> Two seconds, just writing it
[15:36] <Laney> definitely here though
[15:36] <Laney> :P
[15:36] <seb128> ahah
[15:36] <seb128> my fault for bringing you in #ubuntu-devel discussions :p
[15:37] <seb128> let's go back to you when you are ready
[15:37] <seb128> mlankhorst, hey
[15:38] <seb128> tkamppeter_ is on holidays
[15:38] <seb128> that's going to be a short meeting :p
[15:38] <seb128> attente, hey
[15:39] <attente> seb128, hey!
[15:39] <Laney> (done, when ready)
[15:39] <attente> between vUDS and yesterday being a holiday:
[15:39] <attente> changes to libindicator's GIcon support
[15:39] <attente> getting rudimentary support for setting the input source keyboard shortcuts in the region panel (what's missing right now is a check for conflicting shortcuts)
[15:39] <attente> the shortcut stuff is still building in the ppa, but again, if anyone wants to try: https://launchpad.net/~attente/+archive/indicator-keyboard
[15:39] <seb128> still in the indicator team meeting?
[15:39] <seb128> attente, thanks, I still have trying that on my list
[15:39] <attente> hm? me?
[15:40] <attente> we were wondering if you knew who was working on phone settings
[15:40] <seb128> I though you were with the indicator guys in their weekly memble
[15:40] <seb128> mumble
[15:40] <attente> yeah, that finishes just before this meeting :)
[15:40] <seb128> cool
[15:41] <seb128> I saw that sil2100 made progresses on the unity-gtk-module autolanding
[15:41] <seb128> hopefully that means we can start using it soon ;-)
[15:41] <seb128> attente, thanks
[15:41] <seb128> Laney, your turn
[15:41] <attente> thanks seb128
[15:41] <Laney> (A mix of the previous two weeks since we skipped last time. Short due to holidays and vUDS)
[15:41] <Laney> • Did some learning of QML which slightly rewired me, hopefully in a good way: https://ubuntuone.com/5lsRZ3ePOOhKErbBuiRZHp
[15:41] <Laney> • Started a very early implementation of the "Appearance" panel which is under my name to implement, then shelved it until we get more details about how writing these things will work: http://ubuntuone.com/7Ht9giPVcIYU0xCz2uIJRD
[15:41] <Laney> • vUDS: A few discussions - interesting ones for me were around system settings and release process (a kind of-but-not-completely 'rolling' thing)
[15:41] <Laney> • Scanned archive for apps using UPower's D-Bus interface, in case we want to move to 1.0. still to triage list.
[15:41] <Laney> • Updated some GNOME stuff (RB, others) - wondering which other ones are safe to do
[15:42] <Laney> • Scanned XSession.d scripts for ones which need updating for upstart user sessions—not so many.
[15:42] <Laney> • Converted monkeysphere's Xsession.d script per the above and asked for review in #upstart.
[15:42] <Laney> • Updated GLib. Broke Skype. Reverted a commit to fix that; reported it to Skype and waiting for their proper fix.
[15:42] <Laney> • Fixed https://bugzilla.gnome.org/show_bug.cgi?id=694134 - gsd creating a directory with broken permissions.
[15:42] <ubot2> Gnome bug 694134 in general "g-s-d sets an inotify watch on ~/.local/share/sounds, which normally does not exist.. and causes polling" [Normal,Resolved: fixed]
[15:42] <Laney> • Noticed pxgsettings crashing on startup and reported my idea for a fix upstream. Waiting on their response.
[15:42] <Laney> • More Debian merges.
[15:42] <Laney> DONE
[15:42] <seb128> do you have a bug for the pxgsettings thing?
[15:42] <Laney> yep, sec
[15:42] <Laney> have you noticed it too?
[15:43] <seb128> I saw a bug/IRC mention of .local/share being created with wrong permission breaking things earlier
[15:43] <seb128> I'm just wondering if that's the same thing
[15:43] <seb128> no I didn't
[15:43] <seb128> but I don't use a proxy
[15:43] <Laney> local/share is something else
[15:43] <seb128> ok
[15:43] <seb128> I wonder if local share is another issue with the g-s-d sound patch
[15:43] <Laney> oh, since then?
[15:43] <Laney> that would be interesting to look at
[15:44] <Laney> https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1182043 is the other one
[15:44] <ubot2> Ubuntu bug 1182043 in libproxy (Ubuntu) "pxgsettings crashed with SIGSEGV in main()" [High,Triaged]
[15:44] <seb128> thanks
[15:44] <seb128> I don't know when the .local/share thing started
[15:44] <seb128> and I don't find where I read it earlier now
[15:44] <seb128> will look after the meeting
[15:44] <seb128> Laney, thanks
[15:44] <seb128> desrt, hey, back from holidays?
[15:45] <mlankhorst> seb128: sorry, was gone, x1.14 is ready, lts-raring is still ready and still waiting acceptance
[15:45] <mlankhorst> was digging into moving arsenal over to canonical hosting, no complete luck yet, need some input from bryce
[15:45] <seb128> mlankhorst, did you try to ping infinity/slangasek about the lts-raring?
[15:45] <mlankhorst> yeah but a bit hard because of holidays
[15:46] <seb128> ok, this week should be better I think
[15:46] <seb128> mlankhorst, thanks
[15:46] <mlankhorst> np
[15:47] <seb128> Laney, oh, "safe update" ... apply best judgement is the best way to figure that out I guess (and quite some issues are documented on gnome-3-8 blueprint for GNOME)
[15:47] <seb128> I've been going through versions and updating things when the NEWS/changes look fine
[15:47] <seb128> ask on IRC for a second opinion in doubt
[15:48] <Laney> fair enough, that's kind of what I thought
[15:48] <seb128> we have quite some stuff blocked on GTK 3.8 at this point
[15:48] <seb128> which is mostly ready imho, the only blocker left is the software-center issue listed on the blueprint
[15:48] <seb128> I need to play with that
[15:48] <seb128> s-c seems to hit an xerror for quite some users
[15:49] <seb128>  
[15:49] <seb128> ok, otherwise my status update:
[15:49] <seb128> - hosted a desktop vUDS track, which took most of 3 days for me (hard to host and do something else at the same time)
[15:49] <seb128> - 3 days W.E
[15:50] <seb128> - desktop updates, merges with Debian
[15:50] <seb128> - patch pilot shift (took the remaining of one of the vUDS days)
[15:50] <seb128> - played with qml

[15:50] <seb128>  
[15:50] <seb128> did I forget anyone in the status updates round?
[15:51] <Laney> you forgot larsu
[15:51] <Sweetshark> seb128: I forget me ;)
[15:51] <Laney> maybe he's away though
[15:51] <seb128> Sweetshark, ah, there you are ... you win the right to update us on what you have been doing ;-)
[15:52] <Sweetshark> seb128: last weeks work was: customer request for LO on precise, to SRU-or-not-to-SRU for 4.0.3 and bug 1085169 for raring. I guess, I am not backporting/SRUing the 1085169 fix to raring. I see some report that it results in empty menus on the first opening of the menu. I cant reproduce that, although I see a delay in the menu opening on the first try.
[15:52] <ubot2> Launchpad bug 1085169 in indicator-appmenu (Ubuntu) "LibreOffice Menus Stop Working even with libreoffice>=1:3.6.2~rc2-0ubuntu4 and indicator-appmenu>=12.10.3-0ubuntu2.1" [Undecided,Confirmed] https://launchpad.net/bugs/1085169
[15:52] <Sweetshark> As this will get in with 4.1/saucy anyway (is upstream already), Please test the build in https://launchpad.net/~libreoffice/+archive/ppa and tell me if you see the menu not being populated at all (a delay on first open is expected).
[15:52] <Sweetshark> seb128: DONE
[15:52] <seb128> ok
[15:52] <Mirv> Laney: yeah, for saucy, I'll resubmit
[15:52] <seb128> ^ everyone, if you feel like testing
[15:52] <seb128> Sweetshark, thanks
[15:53] <Laney> Mirv: ok cheers, maybe ogra_ could review that (or tell me what that seed is about and I will)
[15:53] <seb128> larsu, hey, around, want to join our meeting/do a quick status update (I guess it will be short since you were on vac last week)?
[15:53] <seb128> Laney, pxgsettings d
[15:53] <seb128> Laney, pxgsettings doesn't segfault for me
[15:53] <Laney> run it like this:
[15:53] <seb128>  /usr/lib/i386-linux-gnu/libproxy/0.4.7/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks
[15:53] <Laney> yeah
[15:53] <seb128> is what I tried
[15:53] <ogra_> Laney, ?
[15:54] <Laney> then press enter
[15:54] <seb128> from your bug report
[15:54] <Laney> after it does the initial output
[15:54] <seb128> oh ok
[15:54] <Laney> that was enough for me
[15:54] <seb128> I was missing that part :p
[15:54] <Laney> ogra_: seed update for ubuntu touch
[15:54] <seb128> ok
[15:54] <ogra_> ah, sure, merge it ... but dont upload -meta since germinate doesnt work for it
[15:55] <seb128> seems like the other team members are not around
[15:55] <ogra_> we need to manually add the stuff to -meta
[15:55] <seb128> does anyone has comments/questions/...?
[15:56] <Laney> not for me
[15:56] <attente> do you know who's working on the settings app?
[15:56] <Mirv> ogra_: laney meant this (now resubmitted to saucy) https://code.launchpad.net/~timo-jyrinki/ubuntu-seeds/ubuntu-touch.raring.fixlp1167197/+merge/164931
[15:56] <seb128> attente, define "app"
[15:57] <seb128> attente, the container app or the panels or both?
[15:57] <larsu> seb128: sure. I'll be landing a new custom menu items patch for gtk today or tomorrow (the old one worked with GTypes, which we can't use for the new unity)
[15:58] <attente> seb128, larsu and mpt were asking about it, i assume the container app
[15:58] <seb128> attente, that's mardy
[15:58] <larsu> seb128: also, I've started moving the custom indicator widgets into libido, and make the panel use them from there. MRs are coming in the next few days
[15:58] <seb128> larsu, https://code.launchpad.net/ubuntu-system-settings
[15:58] <larsu> seb128: thanks
[15:58] <seb128> mardy started on the prototype there
[15:58] <seb128> we had a vUDS session about it
[15:58] <seb128> if you want to watch it on youtube
[15:59] <seb128> we will do a followup hangout on air in 10 days or so
[15:59] <seb128> attente, ^
[15:59] <attente> thanks
[16:00] <seb128> attente, larsu: https://blueprints.launchpad.net/ubuntu/+spec/client-s-touch-system-settings as well
[16:00] <seb128> ok
[16:00] <seb128> thanks everyone
[16:00] <didrocks> seb128: just on time!
[16:00] <seb128> thanks larsu for the update
[16:00] <seb128> didrocks, indeed ;-)
[16:00] <didrocks> kenvandine, Mirv, sil2100, (cyphermox if you are around?): hey! team meeting :)
[16:00] <didrocks> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=0
[16:00] <didrocks> FYI, robru is on vacations for 2 weeks
[16:01] <didrocks> ok, let's get started
[16:01] <didrocks> "Splitting webapps and have that on daily release"
[16:02]  * kenvandine waves
[16:02] <didrocks> this is now done, it seems that robru or kenvandine didn't mark it as DONE, but from what I saw, it's all good, right, kenvandine?
[16:02]  * didrocks changes colors meanwhile
[16:02] <kenvandine> i haven't verified it, but it all built and published :)
[16:03] <didrocks> ok :)
[16:03] <didrocks> kenvandine: you will take care of robru's stack while he's on holidays?
[16:03] <kenvandine> yeah
[16:03] <didrocks> thanks kenvandine :)
[16:03] <didrocks> so next item is "
[16:03] <didrocks> Qt/SDK 5.0.2
[16:03] <didrocks> Mirv: mind giving a status update?
[16:03] <sil2100> !
[16:03]  * sil2100 almost missed it
[16:03] <sil2100> Hi guys
[16:04] <didrocks> hey sil2100 :)
[16:05] <didrocks> hum, no Mirv it seems, let's move on and we'll get back to that later
[16:05] <didrocks> "Look at head status for every stacks and make them green"
[16:05] <Mirv> didrocks: hi. so check is successful now, but it still claims failure
[16:05] <didrocks> ah :)
[16:05] <didrocks> Mirv: for Qt 5.0.2?
[16:05] <Mirv> I mean the SDK stack, sorry
[16:05] <didrocks> ah, we'll get to that later on
[16:05] <didrocks> first Qt ;)
[16:05] <Mirv> for Qt 5.0.2, it's in qt5-proper PPA now for saucy and desktop part has been tested
[16:05] <didrocks> any update?
[16:06] <didrocks> Mirv: any hope to have it that week into saucy?
[16:06] <Mirv> I've also managed to get saucy on my device and dist-upgrade went fine to 5.0.2
[16:06] <Mirv> didrocks: I think yes, I want to wait for Saviq's "success" report as well first on the device
[16:06] <didrocks> ok, let's mark something like ACTION: Mirv to get Qt 5.0.2 to saucy
[16:06] <Mirv> but I've been going over and over the branches and the upload plan (see https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AjuCdq68GSyVdFI4QzNQdWpfME5aMEV2VXo0cUpOMkE#gid=4 ), and I think it's ready
[16:07] <didrocks> Mirv: just give me a sign and I'll sponsor your uploads, ok?
[16:07] <Mirv> didrocks: I will, thanks
[16:08] <didrocks> thanks :)
[16:08] <seb128> (please put the appmenu patch back before uploading :p)
[16:08] <didrocks> seb128: yeah, I'll review it :)
[16:08] <seb128> thanks
[16:08] <didrocks> so
[16:08] <didrocks> sil2100: "Look at head status for every stacks and make them green"
[16:08] <didrocks> any update?
[16:08] <Mirv> seb128: pushed. also, testable via qt5-beta-proper PPA, it seems the build has finished
[16:08] <seb128> Mirv, will test, thanks
[16:09] <sil2100> didrocks: doing that every day, but it's still not green due to the autopilot issues we have
[16:09] <sil2100> But we're getting to it
[16:09] <didrocks> sil2100: only autopilot and hud are failing, right?
[16:09] <kenvandine> the media stack is failing too
[16:10] <sil2100> didrocks: yes, not sure about unity still, since jenkins died mid-way, will have to restart it in a moment, but I want some branches merged first
[16:10] <didrocks> on the note that Mirv told, I know that media and sdk have the -check failing for no good reason (the collect is probably wrong, I pinged jibel about it)
[16:10] <didrocks> ok
[16:10] <didrocks> so, we are on that
[16:10] <didrocks> sil2100: do you think that tomorrow, we can have the QA and hud stack passing?
[16:12] <Mirv> I'm happy to see the green on the -intel autopilot at the SDK's check phase, it seems my 'sleep 1' fixed the issue over there
[16:12] <didrocks> Mirv: yeah, it seems to have done the trick! nice work :)
[16:12] <didrocks> ok, let's make sil2100's silence an ack for tomorrow, thanks sil2100 :p
[16:12] <sil2100> didrocks: not sure about QA, but HUD yes
[16:12] <didrocks> so…
[16:12] <didrocks> ACTION: sil2100 finish having QA and HUD stack tests passing
[16:12]  * sil2100 is still fighting on the guest session
[16:12] <sil2100> ;)
[16:12] <didrocks> ACTION: didrocks to follow up with jibel about the collect failing media and sdk stacks for no good reason
[16:13] <didrocks> sil2100: please don't hack during the meeting or it will take forever :p
[16:13] <didrocks> ok, next one
[16:13] <didrocks> "Get python-evdev into distro"
[16:14] <didrocks> sil2100: you, with cyphermox
[16:14] <seb128> sil2100, didrocks: can you guys do a status update on the unity-gtk-module landing when you are done with other topics?
[16:14] <didrocks> seb128: sure
[16:14] <seb128> thanks
[16:14] <sil2100> didrocks: will take care of that this week, I promise
[16:14] <didrocks> sil2100: ok :)
[16:14] <sil2100> Since I have some other scope-related packages that need that as well
[16:14] <didrocks> on the big topics
[16:14] <didrocks> "WebCred: Fix autopilot tests keyring issue": kenvandine ?
[16:15] <kenvandine> i've added a script to utah to create the unlocked keyring
[16:16] <kenvandine> works locally in a clean session, but not in utah... i'm going to take a break from that and come back to it later in the week with a clearer head
[16:16] <kenvandine> i'm burned out on it :/
[16:16] <didrocks> kenvandine: ok ;) well, we'll have otto soon
[16:16] <didrocks> (we are nearly done on having the first machine wired up)
[16:16] <kenvandine> cool
[16:16] <kenvandine> :)
[16:16] <didrocks> that's why the nvidia machine is stolen btw :p
[16:16] <kenvandine> the good news is we have autopilot tests now that work :)
[16:16] <didrocks> yeah \o/
[16:17] <kenvandine> just not in jenkins for some reason
[16:17] <kenvandine> but... we can run tests :)
[16:17] <kenvandine> better than before
[16:17] <didrocks> heh, excellent news!
[16:17] <didrocks> sil2100: I'll mark the "transitionning to autopilot 1.3" as DONE if you don't mind, as the test part is linked to the autopilot tests, and so "make evevery stacks green" I guess.
[16:18] <didrocks> next is raring SRU for unity, Mirv, did we see progress in -proposed?
[16:18] <sil2100> didrocks: ok, fine with me :)
[16:19] <Mirv> didrocks: we did not see, they're still in the queue
[16:19] <didrocks> Mirv: mind repinging them?
[16:19] <Mirv> didrocks: ok, can try
[16:19] <didrocks> would be nice to have least have one SRU in raring, there is a fix for netbooks
[16:19] <didrocks> thanks!
[16:20] <didrocks> ok, latest "big topic" is the 100 scopes, sil2100, kenvandine: I see you have 2 topics?
[16:20] <Mirv> it would, they weren't completely happy with the new process but in the end it seemed like their newest scripts would be up to it
[16:20] <didrocks> why not just use one?
[16:20] <didrocks> Mirv: yeah, I followed that. I can only argue that we never had better quality before thanks to that process, so I still think it's a win ):
[16:20] <didrocks> :)
[16:20] <sil2100> didrocks: what do you mean by 2-topics ? ;)
[16:21] <kenvandine> dunno, i was wondering what unity-scopes-home was :)
[16:21] <didrocks> "Merge 100scopes unity into lp:unity and make it daily-releasing"
[16:21] <didrocks> "Get unity-scope-home and others into distro"
[16:21] <didrocks> sil2100:  ^
[16:21] <didrocks> that's kind of link, it's just getting 100scopes to distro :)
[16:21] <didrocks> linked*
[16:21] <sil2100> Ah, yes, ok, I created the second one ;)
[16:21] <sil2100> I should have made it one work-item, but didn't
[16:22] <didrocks> sil2100: shouldn't it just be one? or a WI? ;)
[16:22] <sil2100> Since unity-scope-home is a new package
[16:22] <sil2100> didrocks: probably ;)
[16:22] <didrocks> sil2100: I would merge the topics to have a bunch of lines
[16:22] <didrocks> sil2100: mind merging? as well, add that a MIR is required for those new components to be installed by default :)
[16:23] <didrocks> ok, the rest seems to be minor tasks to me, did I forget anyone apart from ignoring deliberately unity-gtk-module (which is marked as DONE)?
[16:24] <sil2100> didrocks: aye!
[16:24] <sil2100> Doing that, need to log in
[16:25] <didrocks> … if no question, so unity-gtk-module, sil2100, I think it was you as well, mind updating us? :)
[16:26] <sil2100> didrocks, seb128: so, unity-gtk-module should be daily-building now, it's re-enabled and the tests were fixed to work correctly, but... there's still one issue that needs to be finished
[16:27] <didrocks> what issue?
[16:27] <sil2100> I wasn't able to do that because of the 100scopes, and I'm sad about that ;/
[16:27] <sil2100> Since the current integration tests are not actually testing unity-gtk-module ;/
[16:28] <sil2100> Right now they're testing the regular appmenu-gtk backend
[16:28] <attente> sil2100, i think the only thing needed to get that working is the unpatched gtk, no?
[16:28] <sil2100> attente: yes, or simply doign packaging that unity-gtk-module forces appmenu-gtk uninstall
[16:28] <seb128> can you just do that?
[16:29] <seb128> we will drop the gtk patch once the source is in the archive
[16:29] <sil2100> didrocks, seb128: since the thing is, once appmenu-gtk is installed, it's used always, even when unity-gtk-module is installed
[16:29] <sil2100> seb128: I could do that indeed
[16:29] <sil2100> If it's fine with you guys
[16:29] <didrocks> yeah, sounds good to me as well
[16:29] <sil2100> seb128, didrocks?
[16:29] <seb128> wfm
[16:30] <seb128> sil2100, thanks
[16:30] <didrocks> sil2100: adding a line for it?
[16:30] <jasoncwarner> morning all
[16:30] <didrocks> thanks :)
[16:30] <didrocks> hey jasoncwarner
[16:30] <kenvandine> hey jasoncwarner!
[16:30] <seb128> once you land it to distro I will do the GTK changes
[16:30] <sil2100> Morning jasoncwarner!
[16:30] <Mirv> morning
[16:30] <didrocks> ok, any other question?
[16:30] <kenvandine> didrocks, i'm also going to add a stack for system settings
[16:30] <seb128> jasoncwarner, hey
[16:30] <seb128> kenvandine, \o/
[16:30] <didrocks> kenvandine: yeah, sounds a good idea :)
[16:31] <kenvandine> we'll have that merged and ready for daily release tomorrow probably
[16:31] <kenvandine> note: it doesn't do much of anything yet :)
[16:31] <kenvandine> but a good basis for plugin developers
[16:31] <kenvandine> :)
[16:31] <didrocks> kenvandine: nice first step anyway :)
[16:31] <didrocks> Time to wrap up I guess! thanks kenvandine, Mirv and sil2100! Let's get Touch into the next ppa this week (once any jenkins and utah issue are fixed) ;)
[16:32] <didrocks> do not hesitate to publish manually meanwhile
[16:32] <didrocks> (if we have at least some results)
[16:32] <didrocks> let's get that moving :)
[16:32] <Mirv> thanks didrocks! :)
[16:35] <sil2100> Thanks!
[16:35] <sil2100> :)
[16:36] <kenvandine> didrocks, so with otto coming... is there a way i can run that myself to see if i can get those autopilot tests working?
[16:36] <didrocks> kenvandine: you mean, on your hardware?
[16:36] <kenvandine> probably not worth spending more time tweaking utah
[16:37] <kenvandine> yeah
[16:37] <kenvandine> or a VM
[16:37] <kenvandine> whatever
[16:37] <didrocks> kenvandine: yeah, that's possible with your hardware, you can even take a snapshot (with the delta) and rerun it if you are using the same iso :)
[16:37] <kenvandine> awesome
[16:38] <kenvandine> i don't suppose there are instructions anywhere?
[16:39] <didrocks> kenvandine: there are some, you can look at lp:otto, but maybe wait for a couple of days that we put the first version in production? :)
[16:39] <kenvandine> sure
[16:39] <kenvandine> i'm just not going to spend anymore time on utah then :)
[16:39] <kenvandine> i need a break from that non-sense anyway... burned out!
[16:39] <didrocks> yeah, you shouldn't need to :)
[16:40] <didrocks> heh
[16:40] <didrocks> kenvandine: you can just prepare a script for doing the setup
[16:40] <didrocks> then, it will be easy to deploy what you need
[16:40] <kenvandine> i have that for utah already, so should be ready
[16:41] <kenvandine> ok, we'll come back to that next week :)
[16:41] <didrocks> ok :)
[16:43] <Laney> otto sounds like cool stuff
[16:46] <Laney> It'd be cool if I could use it as a lightweight VM-ish thing, starting different environments on different VTs
[16:54] <didrocks> Mirv: kenvandine: sil2100: just found the issue for new stacks being wrongly rejected, pushing a fix
[16:55] <sil2100> Ohh ohh!
[16:55] <sil2100> \o/
[16:55] <sil2100> didrocks: thanks! What was the root issue?
[16:55] <didrocks> so, tomorrow, media and sdk stacks should reflect the reality
[16:56] <didrocks> sil2100: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/revision/318
[16:57] <didrocks> so adding tests above the threshold was making the tests collect failing…
[16:57] <didrocks> seems jibel hates people adding tests ;)
[16:57] <sil2100> uh
[16:57] <sil2100> ;)
[17:02]  * didrocks waves good evening
[17:02] <seb128> didrocks, night
[17:02] <didrocks> seb128: see you tomorrow!
[17:02] <pitti> au revoir didrocks
[17:02] <Laney> off to watch the xbox reveal? ;-)
[17:03] <kenvandine> hehe
[17:03] <seb128> oh, right
[17:09] <seb128> Laney, their streaming sucks
[17:09] <seb128> they should use youtube :p
[17:10] <Laney> works nicely on my i7, was choppy on my c2d laptop :(
[17:13] <kenvandine> sil2100,  have you seen any failures like this:
[17:13] <kenvandine> ERROR: No artifacts found that match the file pattern "*xml". Configuration error?
[17:13] <kenvandine> ERROR: '*xml' doesn't match anything
[17:13] <kenvandine> prepare finishes, but gets marked as failed because of that
[17:13] <seb128> Laney, yeah, seems like my i5 doesn't cope with it ... they should use youtube :p
[17:13] <Laney> :P
[17:13] <Laney> wonder if I'd buy one of these
[17:13] <kenvandine> seb128, they should stream it exclusively to xbox devices :)
[17:14] <Laney> they stole the side stage!
[17:14] <seb128> ahah
[17:14] <seb128> they did!
[17:16] <sil2100> hmm, no
[17:16] <sil2100> kenvandine: I mean, no
[17:16] <kenvandine> wow... this video is unwatchable on my dual core desktop
[17:16] <kenvandine> sil2100, :/
[17:17] <kenvandine> weird... it's happening for all of the webapps stack
[17:19] <seb128> kenvandine, the xbox one?
[17:19] <kenvandine> man... what kind of video is this?  full HD streams on youtube are fine
[17:19] <kenvandine> yeah
[17:19] <seb128> great, the website returns "Unavailable" now in france
[17:19] <seb128> ms fail
[17:19] <kenvandine> the audio stream is fine... but the video is more like a slide show :)
[17:19] <Laney> they've outsourced it to akamai
[17:20] <seb128> kenvandine, right, I've the same on my i5
[17:20] <seb128> well 'had', when the site was working
[17:20] <kenvandine> it's really aweful!
[17:20] <kenvandine> my box handles full HD video perfectly fine... what in the hell did they do to make this suck so bad
[17:23] <desrt> seb128: sorry.  was having connectivity troubles
[17:24] <seb128> desrt, hey, no worry, I guess you didn't have lot of updates after your holidays anyway ;-)
[17:24] <seb128> desrt, welcome back btw
[17:25] <desrt> thanks :)
[17:26] <desrt> it was a pretty exhausting holiday, unfortunately :p
[17:26]  * desrt is happy to be back to work so he can relax
[17:26] <seb128> ahah
[17:27] <seb128> lot of walking around?
[17:27] <desrt> hells ya
[17:27] <desrt> one day 8km, another 12km, another 14
[17:27] <desrt> my feet hurt
[17:27] <mlankhorst> :O
[17:27] <seb128> nice break from sitting on the computer ;-)
[17:27] <seb128> and you can enjoy the sitting this week :p
[17:28] <desrt> yup!!
[17:28] <desrt> and back to the nice familiar problems
[17:28] <desrt> what new crack do i add to actiongroups this week?
[17:28] <desrt> :D