[04:20] <pitti> Good morning
[04:51] <RAOF> pitti: Hey, I'm testing colord 1.0.1. Does adt
[04:51] <RAOF> pitti: Hey, I'm testing colord 1.0.1. Does adt-run-test support Restrictions: build-needed? Because it seems to not be doing that.
[04:54] <pitti> hey RAOF
[04:55] <pitti> RAOF: it does, but ATM it does it wrongly, see debian bug 711209
[04:55] <ubot2`> Debian bug 711209 in autopkgtest "autopkgtest: build-needed restriction doesn't actually run tests in built tree" [Normal,Open] http://bugs.debian.org/711209
[04:55] <pitti> RAOF: that bites me in umockdev as well, so today I'll look for a workaround
[04:55] <pitti> RAOF: or rather, fix that in adt-run
[05:07] <RAOF> pitti: So, with that caveat, you may enjoy the debian/1.0.1-1 tag in colord's collab-maint git repository.
[05:07] <pitti> RAOF: yay
[05:08]  * pitti checks whether the keyring update in Debian has happened by now
[05:08] <pitti> RAOF: ah, seems it didn't yet, so I can't upload yet
[05:09] <RAOF> Heh. Fair 'nuff.
[07:04] <jibel> good morning
[07:09] <didrocks> salut jibel, ça va?
[07:12] <jibel> salut didrocks , bien et toi?
[07:14] <pitti> bonjour didrocks
[07:15] <didrocks> bonjour pitti, ça va?
[07:15] <didrocks> jibel: ça va, semaine qui démarrre en fanfarre, mais bon :)
[07:15] <pitti> didrocks: ça va très bien ! j'ai eu un bon week-end
[07:15] <didrocks> pitti: tu as fait quoi?
[07:16] <pitti> didrocks: I'm going to blog/G+ about it RSN, watch out :)
[07:18] <didrocks> pitti: heh, will do! :)
[07:34] <seb128> good morning desktopers
[07:35] <didrocks> salut seb128!
[07:36] <seb128> lut didrocks!
[07:36] <sil2100> Morning!
[07:36] <sil2100> didrocks: hi! How was your long weekend? :)
[07:37] <seb128> hey sil2100
[07:37] <didrocks> sil2100: hey, was hot in Lyon! :) Got to the spa on Friday morning
[07:37] <didrocks> was good, not too many people
[07:37] <sil2100> Excellent
[07:37] <didrocks> then, a lot of cycling (~30 kms) within the city
[07:38] <didrocks> how was yours?
[07:38] <sil2100> Ahh, I miss my bike, would love to ride a bit now that the weather is so nice
[07:39] <pitti> didrocks: done :)
[07:39] <pitti> bonjour seb128
[07:39] <didrocks> pitti: looking :)
[07:39] <sil2100> didrocks: not bad, only had one day for resting theoretically, but I bummed around as much as I could ;)
[07:39] <seb128> pitti, salut, ça va bien ?
[07:39] <sil2100> didrocks: btw. I see that the queue still has dbus-cpp and location-service waiting as (sync)
[07:39] <didrocks> sil2100: yeah, I waited to ask you for it
[07:40] <didrocks> it's from yesterday's right?
[07:40] <pitti> seb128: en effet, je vais très bien ! mon weekend était mervellieux
[07:40] <sil2100> didrocks: it was from Friday
[07:40] <didrocks> sil2100: oh, is seb128 to blame? :p
[07:40] <seb128> pitti, super, tu as fait quoi ?
[07:40] <sil2100> seb128: hi! Was there some issue with NEWing those two? ^
[07:40] <pitti> seb128: https://plus.google.com/107564545827215425270/posts/VtrGcA74wP9
[07:40] <didrocks> sil2100: I can NEW them, I reviewed them, apart if seb128 has some remarks on them
[07:40] <seb128> sil2100, no, they were just not in the queue at 7pm friday when I called it a week
[07:41] <didrocks> seb128: tsss, 7pm on Friday and you call it a week? How dare you! :p
[07:41] <sil2100> seb128: ok! didrocks: could you NEW ;) ?
[07:41] <didrocks> sure
[07:41] <seb128> haha
[07:41] <sil2100> Thanks, I'll check the stacks now
[07:41] <didrocks> sil2100: ok, so on the stacks they both are, maybe you should rebuild those components
[07:41] <didrocks> sil2100: once the merge back to trunk is done
[07:41] <sil2100> I think we missed some new packages, but since there were some issues with tests and releasing, we only got that many new ones out
[07:41] <didrocks> (for dbus-cpp and location-service)
[07:41] <didrocks> sil2100: otherwise, the changelog will be screwed
[07:42] <seb128> didrocks, I was not sure they would land there since we had issue earlier in the day due to the lillypilly checklist (I think)
[07:42] <didrocks> seb128: yeah, I saw a reject
[07:42] <seb128> didrocks, the copy there was not uptodate and not listing some of the components
[07:42] <didrocks> telepathy-ofono
[07:42] <didrocks> right?
[07:42] <seb128> and apparently trying to republish the same version doesn't work
[07:42] <seb128> yes
[07:42] <sil2100> Yes
[07:42] <didrocks> seb128: you have to cheat, it's possible to republish
[07:43] <didrocks> seb128: sil2100: so that you know how it works
[07:43] <seb128> we tweaked the changelog
[07:43] <seb128> to bump the version
[07:43] <didrocks> remember those .project files?
[07:43] <didrocks> this is what are used to track what we didn't publish yet and need to monitor
[07:43] <sil2100> didrocks: hm, so what should I do now with dbus-cpp and location-service? Should I rebuild those stacks and republish? Or merge something to their trunks?
[07:43] <sil2100> didrocks: remember those, yes
[07:43] <didrocks> as you can rebuild one part of the stack, we remove those .project file and recreate them
[07:43] <didrocks> but you can as well publish them multiple times
[07:43] <didrocks> (without rebuilding the whole stack)
[07:44] <didrocks> so they are renamed .project_<timestamp>
[07:44] <seb128> ok
[07:44] <didrocks> if you need to republish the same version again, you need to mv package.project_<timestamp> package.project
[07:44] <didrocks> then launching the publication
[07:44] <sil2100> Awesome to know
[07:44] <sil2100> \o/
[07:44] <sil2100> Cheating is awesome
[07:44] <didrocks> heh
[07:45] <didrocks> well, it's not that easy, but in practice, this is "only" for new components
[07:45] <seb128> pitti, that sounds like a fun sunday ;-)
[07:45] <didrocks> sil2100: so, yeah, once the changelog is merged back to dbus-cpp and location-service, please rebuild those
[07:45] <didrocks> (just those components)
[07:45] <didrocks> so get a real changelog :p
[07:46] <didrocks> pitti: waow, excellent!
[07:46] <sil2100> But but dbus-cpp and location-service already have 0.0.1daily13.06.14.1-0ubuntu1 in them ;p
[07:46] <didrocks> sil2100: oh oh, silly me :)
[07:46] <didrocks> yeah, it was "just" in NEW
[07:46] <didrocks> but the diff isn't correct
[07:46] <sil2100> Since those got published and just got stuck in the queue
[07:46] <didrocks> yep :)
[07:47] <didrocks> the only thing not "right" is the diff
[07:47] <didrocks> between distro and bzr
[07:47] <didrocks> to know if anything new was generated
[07:47] <pitti> seb128: indeed it was, Lieutenant!
[07:47] <seb128> pitti, ;-)
[07:47] <didrocks> sil2100: so, just wait them to be published in -proposed
[07:47] <didrocks> sil2100: and then relaunch them, maybe (I guess even :p) nothing new will be to be published
[07:48] <sil2100> \o/
[07:48]  * didrocks loves http://piware.de/fotos/Filmwelt-Bakede-Jun2013/slide_09.html
[07:48] <didrocks> with the red eyes, it seems to be on purpose
[07:50] <pitti> didrocks: je crois que Kirk n'ai pas des yeux rouges ?
[07:50]  * hyperair wonders if anyone here is having intermittent issues with gtalk authentication in empathy
[07:50] <didrocks> pitti: non, en effet, juste que je trouve que ça va bien dans le contexte tout de même :)
[07:50] <pitti> hyperair: I actually used to have, but it seems to have stabilized in the recent weeks
[07:50] <pitti> didrocks: :)
[07:51] <hyperair> pitti: in saucy?
[07:51] <didrocks> pitti: hum, it seems that Unity 7 became jaleous of the Unity 9 interface and decided to freeze :p
[07:51] <pitti> hyperair: yes (is there any other release? :) )
[07:51] <hyperair> heh
[07:51] <hyperair> that should mean there's an SRUable patch, shouldn't it?
[07:52] <pitti> hyperair: I had the impression it was due to changes on the google side
[07:52] <hyperair> no, i'm not sure it is.
[07:52] <hyperair> i just killed signonpluginprocess, and it worked again
[07:52] <pitti> hyperair: maybe you have something different
[07:52] <hyperair> previously i'd been removing and re-adding the google account in signon-ui
[07:59] <sil2100> didrocks, seb128: I'll jump out for a quick exercise now, since the weather is excellent
[07:59] <didrocks> sil2100: enjoy :)
[07:59] <sil2100> Be back in some moments!
[07:59] <seb128> have fun!
[08:00] <Laney> morning
[08:01] <hyperair> weather eh.. it's hazy as hell over here in singapore.
[08:35] <seb128> Laney, oh, I didn't notice your "morning" earlier, good morning! ;-)
[08:35] <Laney> heh
[08:35] <Laney> hey seb128!
[08:35] <Laney> it does seem quiet ;-)
[08:35] <pitti> hey Laney, good morning
[08:35] <seb128> everybody doing monday email catchup etc I guess
[08:36] <didrocks> hey Laney!
[08:37] <Laney> \o/
[08:44] <mlankhorst> morning
[08:44] <mlankhorst> i mean
[08:44] <mlankhorst> bonjour!
[08:44] <pitti> ça va mlankhorst ?
[08:44] <mlankhorst> very good
[08:44] <mlankhorst> I exhausted my french for this week :-)
[08:46] <mlankhorst> but the weather was nice saturday http://imgur.com/uVxApz4
[08:47] <didrocks> bonjour mlankhorst :)
[08:49] <pitti> mlankhorst: wow, that's a funny bike that you have there!
[08:51] <mlankhorst> aye, I haven't tried the max speed yet
[08:52] <Laney> bet it requires a lot more maintenance than a push bike :P
[08:54] <mlankhorst> yeah but I don't have to do most of it myself :-)
[09:02]  * mlankhorst is still using a conventional bike to get to the stables
[09:29]  * didrocks tries some reboots, bbiab
[09:31] <didrocks> sil2100: back from exercising? :)
[09:47] <didrocks> Laney: hum, you do have some upstart-session knowledge, right? :)
[09:47] <Laney> a small amount
[09:48] <didrocks> do you have time for a small experiment? I think I probably did something wrong and it will take more time for me to debug
[09:48] <didrocks> if you apt-get source unity
[09:48] <Laney> if I can't help then there are others who know more though :P
[09:48] <didrocks> and apply that patch: http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3364
[09:49] <didrocks> does it start the panel service on session startup for you?
[09:49] <didrocks> (it doesn't for me)
[09:49] <didrocks> I wonder if ted is relying on one of the new indicators to emit indicators-loaded
[09:49] <didrocks> and we don't have that signal
[09:49] <didrocks> (in a vanilla installation)
[09:50] <Laney> Looking at the file it could be that 'start on started' is too late
[09:50] <Laney> depending on what it needs
[09:50] <Laney> but let me try
[09:50] <didrocks> $ grep indicators-loaded /usr/share/upstart/sessions/*
[09:50] <didrocks> /usr/share/upstart/sessions/unity-panel-service.conf:emits indicators-loaded
[09:50] <didrocks> and nothing else
[09:50] <didrocks> Laney: yeah, keep me posted :)
[09:50] <didrocks> thanks!
[09:50] <Laney> that means that it sends a signal for others to look at
[09:51] <didrocks> yeah, I just realized I misread
[09:51] <Laney> shouldn't affect the emitting service being run
[09:51] <didrocks> I'll blame the hot weather :p
[09:51] <sil2100> Back ;)
[09:51] <didrocks> oh but, the other patch is "if we are under gnome-session… don't use the unity upstart job"
[09:52] <Laney> the other?
[09:52] <sil2100> Resuming loking at stacks this very instance! Had to freshen up, since it's a bit too sunny for exercising
[09:52] <didrocks> Laney: no, ignore me, the script exit 0, I think the event is emmitted
[09:52] <didrocks> (in unity.conf)
[09:53] <didrocks> sil2100: do you have time for a quick hangout to catch up?
[09:53] <Laney> didrocks: does 'status unity-panel-service' show it running?
[09:53] <sil2100> didrocks: how about in 7 minutes?
[09:53] <didrocks> sil2100: sure
[09:54] <didrocks> Laney: I ran it by hand, does it impacts it? I can try a guest session
[09:54] <didrocks> $ status unity-panel-service
[09:54] <didrocks> unity-panel-service stop/waiting
[09:54] <didrocks> $ status unity
[09:54] <didrocks> unity stop/waiting
[09:54] <Laney> I don't have a unity upstart job
[09:55] <didrocks> Laney: weird, I didn't revert that one AFAIK
[09:55] <didrocks> http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3361
[09:55] <didrocks> start on started gnome-settings-daemon and xsession SESSION=ubuntu
[09:55] <Laney> wait, I'm lying
[09:55] <didrocks> ah :)
[09:55] <didrocks> gnome-settings-daemon is started here
[09:55] <Laney> but it isn't running
[09:55] <Laney> unless I got it today
[09:56] <didrocks> Laney: no, not from today
[09:56] <didrocks> and not running here as well
[09:56] <didrocks> so "and xsession SESSION=ubuntu" is faly?
[09:56] <didrocks> falsy*
[09:56] <Laney> let me see
[09:56] <didrocks> ah, there is a stop in the script
[09:57] <Laney> aha, yes, it's tripping that
[09:57] <Laney> see ~/.cache/upstart/unity.log*
[09:57] <Laney> so your indicator event won't happen
[09:57] <didrocks> right
[09:57] <didrocks> grrr ted :p
[09:58] <didrocks> in fact the check should be in the exec part
[09:58] <Laney> that's the right way to do a conditional start
[09:58] <didrocks> yeah, but we still want to see the "unity" event started
[09:59] <didrocks> can this be expressed in some way? (I don't think we want a super long "exec" line)
[09:59] <Laney> kind of confused by this
[09:59] <Laney> when wouldn't gnome-session be used?
[09:59] <didrocks> Laney: touch
[10:00] <didrocks> (I know, no sense for unity7 without xmir for now)
[10:00] <didrocks> but I think ted wanted to implement it for the future
[10:00] <didrocks> (the day of releasing unity 7 of course, hence the revert I had to do :p)
[10:00] <sil2100> didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/apps_extra_packages_for_gallery/+merge/169756 <- could you take a look?
[10:01] <Laney> I guess started unity is the wrong thing for us at this point
[10:02] <didrocks> sil2100: ok, making sense, thanks!
[10:02]  * Laney fires up the vm
[10:02] <sil2100> didrocks: this would unblock Apps, looking at Indicators but LP is taking its time today\
[10:03] <sil2100> didrocks: hanging out in a moment?
[10:03] <didrocks> Laney: do you mind tracking that once ted is back? you clearly have more knowledge on how we should build the sessions upstart once moving away from gnome-session to upstart to handle it
[10:03] <didrocks> sil2100: I'm ready right now, tell me when you are
[10:03] <didrocks> (I'll just exercice after this hangout)
[10:03] <Laney> I can probably figure out something to fix this up
[10:03] <sil2100> didrocks: I'll just finish indicators and ready
[10:03] <Laney> but I don't really have a handle on moving away from gnome-session completely
[10:03] <didrocks> thanks Laney :)
[10:04] <Laney> np
[10:04] <didrocks> sil2100: ok
[10:05] <sil2100> didrocks: ok, it seems that jbicha broke indicator-session on Saturday
[10:05] <sil2100> Will have to wait for him to pop up
[10:05] <didrocks> "nice", ok :/
[10:07] <sil2100> didrocks: do you have a hangout link ready by any chance ;)?
[10:08] <didrocks> sil2100: https://plus.google.com/hangouts/_/d9e1fb52de2cf1cc1d14d5aca163296f609ed875?hl=fr
[10:24] <seb128> sil2100, how did he break it?
[10:36] <Laney> didrocks: OK, got it
[10:36] <Laney> didrocks: try "start on started unity or desktop-start DESKTOP_SESSION=ubuntu" / "stop on desktop-end"
[10:52] <Laney> seb128: have you tried system-settings on the device?
[10:52] <seb128> Laney, no, I planned to do that today ... does it work?
[10:52] <Laney> it's a bit buggy
[10:52] <Laney> like I couldn't get back from the individual panels
[10:52] <seb128> it's a bit annoying that you can't just deploy from qtcreator as you do for pure qml programs
[10:52] <seb128> oh
[10:53] <seb128> I will have a look
[10:53] <Laney> it just flicked instead
[10:54] <Laney> do you think it's ok to merge the appearance stuff with the example content?
[10:54] <Laney> I don't think I can do much more without dconf or the content picker
[11:02] <didrocks> Laney: sorry, was in this hangout :)
[11:02] <Laney> np
[11:02] <didrocks> Laney: nice!
[11:02] <Laney> does it work?
[11:02] <didrocks> let me try
[11:03] <Laney> you can't have 'stop on stopping unity' because that is triggered by the job aborting itself
[11:03] <Laney> that one confused me for a bit
[11:03] <didrocks> started unity is true even if the job stopped I guess?
[11:04] <Laney> no
[11:04] <didrocks> ah or
[11:04] <Laney> but stopping is
[11:04] <didrocks> hum
[11:04] <Laney> pre-start -> stopping -> stopped I think
[11:04] <didrocks> I think ted wanted to start only if unity startede
[11:04] <didrocks> started*
[11:04] <Laney> that's what the desktop-start should do
[11:04] <Laney> it comes from gnome-session
[11:04] <Laney> so you have both
[11:04] <didrocks> yeah, it's a bit "uncrystalclear"
[11:05] <didrocks> but works in theory
[11:05] <didrocks> let me see :)
[11:05] <Laney> can comment it
[11:05] <didrocks> contrive* was the term I was looking for :)
[11:05] <Laney> it's new world and old world
[11:05] <didrocks> heh, right
[11:05] <Laney> you're going to get stuff like this until we are ... converged ...
[11:07] <didrocks> Laney: working fine :)
[11:07] <didrocks> (tried multiple starts)
[11:07] <didrocks> so yeah, please, add a comment and I'll approve it :)
[11:07] <Laney> I suppose you could simplify it further if you made the unity job emit that desktop-start signal
[11:07] <Laney> thanks!
[11:08] <didrocks> yeah, not sure if we can emits since the pre-start script though
[11:08] <didrocks> from*
[11:08] <Laney> you'd probably do it in post-start
[11:08] <Laney> see /usr/share/upstart/sessions/gnome-session.conf
[11:09] <didrocks> ah, so you mean, removing the unity signal, but have "destkop-start & session==…"
[11:09] <Laney> edit debian/unity.conf to have the same post-start and pre-stop as gnome-session does
[11:09] <Laney> then have unity-panel-service just listen for desktop-start/desktop-end
[11:10] <didrocks> not sure if it's semantically correct, it's like if we were telling the session is ready if unity is ready (and we don't care about the rest)
[11:10] <didrocks> as you wish, the best in your opinion :)
[11:11] <didrocks> if we tell "DESKTOP_SESSION" is used to detect we are using gnome-session, I'm fine with it
[11:12] <Laney> ok
[11:12] <Laney> where's the MP?
[11:13] <didrocks> Laney: oh, there is none, it's part from a revert, so reintroduce the revert + your additional commit I would say
[11:13] <Laney> sure
[11:13] <didrocks> (I had to revert it in a hurry the day we released unity 7 as having that + a segfault was enough :p)
[11:14]  * Laney meditates for a minute on what is better
[11:14]  * didrocks lights a candle for Laney
[11:16] <seb128> Laney, sorry, I was grabbing a bite ... merge the background panel makes sense yes
[11:17] <Laney> ok
[11:17] <Laney> I want to get a widget merged into the ui toolkit first, so will try that this afternoon
[11:18] <seb128> cool
[11:20] <xclaesse> is there a trick to restart unity and keep the workspace where each window are?
[11:20] <xclaesse> like gnome-shell does when doing alt-f2 r
[11:20] <xclaesse> if I just do unity --replace then all my windows goes to first workspace
[11:21] <seb128> hum, they should not, seems like a bug
[12:25] <sil2100> seb128: regarding the indicator-session, I just checked and my conclusions were too soon - jbicha did not break it, it broke itself probably due to changes in saucy
[12:25] <sil2100> seb128: as it's the same issue as with some other packages - pthread errors
[12:25] <seb128> sil2100, what's the error it hits?
[12:26] <seb128> oh, yeah, new binutils being pickier about incorrect linkage
[12:26] <sil2100> /usr/bin/ld: libgtest.a(gtest-all.o): undefined reference to symbol 'pthread_key_delete@@GLIBC_2.2.5'
[12:26] <sil2100> Yes
[12:30] <Laney> grr, silent rules!
[13:12] <seb128> Laney, how did you run the settings app on the device?
[13:24] <didrocks> sil2100: needing any packaging ack?
[13:33] <sil2100> didrocks: not yet, uno momentos
[13:37] <didrocks> tedg: hey! FYI, after some tests, there was still an issue with your panel-service + upstart branch, after talking to Laney, there is a solution that is merging right now (https://code.launchpad.net/~laney/unity/user-session-jobs/+merge/169771)
[13:38] <didrocks> tedg: basically, the issue was that unity event always stops when using gnome-session, so the event for starting unity-panel-service was never triggered
[13:39] <tedg> didrocks, Ah, cool!
[13:39] <tedg> didrocks, Great stuff!
[13:40] <didrocks> thanks Laney for providing an elegant solution :)
[13:40] <tedg> It should make debugging the indicator issues there *much* easier.
[13:40] <didrocks> and make it starting faster
[13:40] <didrocks> I can feel the difference, even on my beefy machine :)
[13:40] <tedg> Heh, great!
[13:40] <didrocks> stopping seems a little bit longer, but on startup, it feels like if unity was already started :)
[13:42] <tedg> didrocks, I think that's because not all of our stuff is responding to SIGTERM properly.
[13:42] <tedg> didrocks, So then upstart has to formally kill things after a 5 second timeout.
[13:43] <didrocks> tedg: I agree with you, we seem to timeout systematically
[13:43] <tedg> didrocks, I think we should look at some of the offenders, we have a SIGTERM handler in HUD that just shutsdown the mainloop gracefully, and it works with usptart well.
[13:43] <tedg> didrocks, Probably need to add that code around.
[13:44] <sil2100> didrocks: hmmm... still checking that, but the new package dependency of gir1.2-dbusmenu-glib-0.4 for raring is a bit fishy
[13:44] <didrocks> tedg: do you know if upstart has a way to tell "this is what timed out"
[13:44] <didrocks> at least to have a list
[13:45] <didrocks> sil2100: hum, didn't we decide to look at saucy first, making all possible publication and move on the SRU then?
[13:45] <sil2100> didrocks: since I checked all the obvious projects and the only place where the gir1.2-dbusmenu-glib-0.4 dependency was added was libdbusmenu, but for saucy
[13:45] <sil2100> didrocks: doing that too, was waiting for Apps to finish, I also re-ran Unity, will check the publications too
[13:46] <didrocks> ok :)
[13:46] <sil2100> didrocks: I'm just afraid that there might have been a stack publishing missing somewhere ;/
[13:46] <didrocks> sil2100: so let's ignore it
[13:46] <sil2100> FOr raring
[13:46] <tedg> didrocks, Hmm, not sure it has a way to see that.  It can give a reason that it was stopped, but I think the only cases now are pass/fail.  Perhaps we could add "timeout"
[13:46] <didrocks> sil2100: I wonder if it's not part of the "this used to work"
[13:46] <didrocks> (ignored by UTAH checks)
[13:46] <didrocks> and now otto really checks it
[13:47] <didrocks> tedg: yeah, that would be interesting for debugging
[13:47]  * didrocks proposes a shutchart :)
[13:49] <Laney> seb128: I installed and launched it from the terminal
[13:49] <Laney> don't know why it didn't appear in the app lens
[13:49] <seb128> Laney, do you know how to get an icon for it?
[13:50] <Laney> it has a desktop file
[13:50] <seb128> kenvandine, hey, do you know what would be needed for system settings to get an icon on ubuntu touch.
[13:50] <seb128> ?
[13:51] <Laney> didrocks: that was one of the issues ;-) The other one was that the condition for gnome-session was never fired so you never got it started on the desktop
[13:52] <didrocks> indeed :)
[13:53] <Laney> ooh, britney/autopkgtest is coming
[13:53] <Laney> so everyone will really have to make sure tests work ;-)
[13:54]  * mlankhorst still can't push xorg-integration-tests :(
[13:56] <mlankhorst> it won't compile until x1.14 lands
[13:58] <sil2100> didrocks: maybe... are you ready for some ACK's for publishing? ;)
[13:59] <didrocks> sil2100: I fully am!
[13:59] <kenvandine> just need to reference an icon that is installed
[14:00] <kenvandine> right now it is using one from a theme that isn't installed
[14:00] <kenvandine> seb128, ^^
[14:00] <sil2100> didrocks: platform: http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qtubuntu_0.51daily13.06.17-0ubuntu1.diff/*view*/ <- but here I see a small problem with the changelog
[14:00] <sil2100> didrocks: as one entry is duplicated by Tim and Ken
[14:00] <didrocks> sil2100: it's not an issue, it means that both contributed to the branch that was merged
[14:00] <didrocks> (they did each one at least one commit)
[14:01] <sil2100> Awesome, then it's all ok in my eyes
[14:01] <didrocks> sil2100: fine for me as well, feel free to publish :)
[14:01] <seb128> kenvandine, ok, I will do a MR to fix that then ;-)
[14:03] <sil2100> didrocks: published, now sdk:
[14:03] <sil2100> http://10.97.0.1:8080/view/cu2d/view/Head/view/SDK/job/cu2d-sdk-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_dee-qt_3.0daily13.06.17-0ubuntu1.diff/*view*/
[14:03] <sil2100> (no deps, just packaging)
[14:04] <kenvandine> seb128, cool
[14:04] <didrocks> sil2100: good good! :)
[14:04] <Laney> seb128: kenvandine: I thought there was a touch icon theme?
[14:04] <Laney> Some of the panels in there don't have icons either
[14:05] <seb128> Laney, ubuntu-mobile-icons
[14:05] <seb128> Laney, but it's not complete
[14:05] <Laney> so the ones we chose are just what it will be?
[14:06] <seb128> you mean? the icon names? no, I tried to pick available icons as place  holders
[14:06] <seb128> we will need to update that once design provides the icons
[14:06] <didrocks> sil2100: on the indicator with binutils being pickier, this is fixed/merging or do we need help?
[14:07] <sil2100> didrocks: published, settings now: http://10.97.0.1:8080/view/cu2d/view/Head/view/Settings/job/cu2d-settings-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-system-settings_0.1daily13.06.17-0ubuntu1.diff/*view*/
[14:08] <sil2100> didrocks: I think it's not being worked on yet, but I guess I could quickly fix that
[14:09] <didrocks> sil2100: +1
[14:09] <didrocks> (we can notice seb128 writing commit message of 3 kms long :))
[14:09] <seb128> heh
[14:10]  * Laney approves of that!
[14:10] <seb128> I'm writing nice details for you to read ;-)
[14:10] <didrocks> seb128: that's kind of you :p
[14:10] <didrocks> seb128: "settings": is there anything else? it's the name of the panel?
[14:10] <didrocks> the settings panel of system settings?
[14:10] <sil2100> didrocks: cyphermox fixed the indicator-session thing, so it's getting merged now
[14:10] <didrocks> \o/
[14:11] <cyphermox> moo
[14:11] <didrocks> thanks cyphermox :)
[14:11] <sil2100> ;)
[14:11] <seb128> didrocks, no, it's the settings app itsel ... you can notice some are "about: ..." which is the about panel
[14:11] <cyphermox> didrocks: I was surprised Laney didn't beat me to it like for indicator-datetime :)
[14:11] <Laney> I got the wrong impression that those were all fixed
[14:11] <Laney> otherwise I would have ;P
[14:12] <cyphermox> Laney: ahah ;)
[14:12] <didrocks> cyphermox: oh, he did merge back his commit for it now?
[14:12] <didrocks> Laney: did you? ^
[14:12] <cyphermox> hmm, I should double-check
[14:12] <Laney> did I what?
[14:12] <Laney> oh hey, datetime is stuck in proposed
[14:12] <cyphermox> yup
[14:12] <Laney> oh, /that/
[14:12] <Laney> now I remember
[14:12] <didrocks> and it's not in trunk
[14:12] <cyphermox> yes, it's fine
[14:12] <didrocks> so the daily release is sad and complaining:
[14:12] <didrocks> A version (12.10.3daily13.06.07-0ubuntu2) is available at the destination for that component but is not in trunk which is still at 12.10.3daily13.06.07-0ubuntu2. Ignoring that component for source: indicator-datetime, branch: lp:indicator-datetime, series: saucy.
[14:12] <cyphermox> didrocks: sure it is?
[14:13] <Laney> I didn't do this to the archive
[14:13] <didrocks> interesting
[14:13] <Laney> I only touched trunk ;-)
[14:13] <cyphermox> oh, but UNRELEASED
[14:13] <didrocks> ah!
[14:13] <didrocks> so my system works \o/
[14:13] <cyphermox> yup
[14:13] <didrocks> hum, I thought sil2100 fixed it IIRC
[14:13] <didrocks> or maybe I'm misleading with something else?
[14:14] <sil2100> What what?
[14:14] <cyphermox> unmerged still
[14:14] <Laney> it should be fine if you can somehow tell it to ignore that
[14:14] <didrocks> sil2100: do you remember that you backported a commit?
[14:14] <didrocks> ah, unmerged :p
[14:14] <Laney> the one in saucy is effectively a no-change rebuild
[14:14] <cyphermox> sil2100: needs fixing: https://code.launchpad.net/~sil2100/indicator-datetime/include_direct_push/+merge/169255
[14:14] <didrocks> Laney: no, it's on my list of enhancement
[14:14] <didrocks> Laney: but yeah, would be cool
[14:14] <sil2100> uuuh
[14:14] <didrocks> I prefer to be too strict for now :)
[14:15] <sil2100> Ok, so libical-dev
[14:15] <didrocks> ah, it was that one :)
[14:15] <sil2100> It should work now
[14:15] <sil2100> I'll reapprove, as 1.0 is in ubuntu now
[14:15] <Laney> hrm, not sure I like calling it a bad idea
[14:15] <Laney> the FAQ says it's fine ;-)
[14:15] <didrocks> Laney: sorry, what about a bad idea?
[14:16] <Laney> "Include the missing version that got directly pushed to the distro... which is generally a bad idea. Someone pushed directly to distro and now we have to fix that."
[14:16] <Laney> on that MP ^
[14:16] <didrocks> Laney: I think the "bad idea" that sil2100 is telling is about not taking care of Vcs-Bzr :p
[14:17] <didrocks> (or at least asking)
[14:18] <sil2100> ;)
[14:18] <sil2100> Yep, it's generally a bad idea to workaround our daily-release machinery ;p
[14:18] <didrocks> sil2100: have you touch to the .project files for dbus-cpp and location-service?
[14:18] <sil2100> Without letting us know that is
[14:19] <didrocks> 2013-06-17 14:16:08,599 ERROR A manual upload of location-service (0.0.1daily13.06.14.1-0ubuntu1) to distro has been done after the current daily release was prepared (it was at 0) at this time.Ignore uploading 0.0.1daily13.06.17-0ubuntu1.
[14:19] <didrocks> 2013-06-17 14:16:12,870 ERROR A manual upload of dbus-cpp (0.0.1daily13.06.14.1-0ubuntu1) to distro has been done after the current daily release was prepared (it was at 0) at this time.Ignore uploading 0.0.1daily13.06.17-0ubuntu1.
[14:19] <sil2100> didrocks: hm, I don't think so
[14:19] <didrocks> ah no, that's normal
[14:20] <didrocks> as it wasn't in distro and we NEW them afterwards
[14:20] <didrocks> there has been an intermediate upload to distro for it
[14:20] <didrocks> that's why it ignored it
[14:20] <didrocks> sil2100: you didn't relaunch a build for them as we discussed this morning, right?
[14:26] <sil2100> didrocks: oh shit, hoho, dammit, I did not relaunch, I just published the platform stack
[14:26] <didrocks> sil2100: no worry, it's just creating a dummy commit upstream
[14:26] <didrocks> (with a revision from today)
[14:27] <didrocks> it will never surface to distro, just pollute upstream (well, low level pollution) :)
[14:27] <didrocks> sil2100: thanks for testing my protection code btw :p
[14:29] <sil2100> didrocks: in the meantime while your coffee is being made! apps stack: http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_gallery-app_0.0.67daily13.06.17-0ubuntu1.diff/*view*/
[14:30] <didrocks> sil2100: +1
[14:56] <sil2100> didrocks: heh, funny thing - I just wanted to add the missing gir1.2-dbusmenu-glib-0.4 to packages in raring, but it's there already!
[14:56] <sil2100> didrocks: just a redeploy was missing
[14:56] <sil2100> didrocks: can I redeploy?
[14:56] <didrocks> sil2100: sure sure, if the stack is not running
[15:03] <didrocks> sil2100: so, with all those publishing, it seems I didn't break the traditional "copy to distro" case, at least, right?
[15:07] <sil2100> didrocks: right, at least I see that gallery-app got uploaded properly, so it should work alright
[15:07] <didrocks> sil2100: ok, let's see what will happened once you publish the SRUs :)
[15:17] <sil2100> huh
[15:19] <sil2100> bleh...
[15:19] <sil2100> didrocks: in the meantime, media looking good:  http://10.97.0.1:8080/view/cu2d/view/Head/view/Media/job/cu2d-media-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_camera-app_2.9.1daily13.06.17-0ubuntu1.diff
[15:20] <didrocks> sil2100: sounds fine
[15:24] <sil2100> didrocks: btw. I checked wrongly and my indicator-datetime merge can't go in still, since libical-dev 1.0-0ubuntu1 is still in -proposed, not in saucy ;(
[15:25] <sil2100> s/go/get
[15:32] <jbicha> sil2100: ical won't migrate to saucy until after indicator-datetime is built with the new ical
[15:35] <sil2100> jbicha: that might be hard to do, as because of someone's direct push to the archive, indicator-datetime cannot be released before we get the changelog entry back into trunk manually, which is failing to merge - one solution would be to merge in directly without the merger, as the merger does not have -proposed enabled
[15:35] <sil2100> jbicha: but I'll merge it in manually then
[15:35] <sil2100> didrocks: you fine with that? ^
[15:36] <jbicha> like I said last week, I think you guys would have /less/ problems if you just built against -proposed than requiring manual overrides every time there is a transition
[15:36] <didrocks> sil2100: I'm fine with that
[16:03]  * Sweetsha1k improved the general build time of LibreOffice by 10% on all platforms at the Hackfest it seems ...
[16:40] <mlankhorst> it now takes 55 minutes instead of 50?
[16:42] <sarnold> lol
[16:54] <Sweetsha1k> mlankhorst: on Windows it now takes 89 minutes instead of 99 minutes on a i7-4470K with 16GB RAM. on big bertha it takes 2min10sec instead of 2min25sec to build from scratch ....
[17:09] <rickspencer3> kenvandine, hey, I think that maybe gallery -> facebook uploads broke?
[17:09] <rickspencer3> it seemed to not work for me over the weekend
[17:10] <kenvandine> rickspencer3, i haven't been able to test it on saucy yet
[17:10] <kenvandine> rickspencer3, i'll check it out today
[17:13]  * didrocks waves good evening
[17:17] <rickspencer3> thanks kenvandine
[17:17] <rickspencer3> kenvandine, is there anyway to automate it?
[17:17] <rickspencer3> I know that the web apps team have some automated tests to catch when web integration breaks
[17:20] <kenvandine> not without storing credentials in a public place
[17:20] <kenvandine> we do have autopilot tests for webcred
[17:20] <kenvandine> friends itself hasn't changed, i think there are problems with the webcred saucy stack on the device
[17:21] <kenvandine> works on the desktop fine
[17:21] <kenvandine> and i just got saucy flashed to my phone
[17:21] <kenvandine> so i'll test
[17:59] <kenvandine> rickspencer3, confirmed, sharing works with the version of signon-ui in saucy-proposed
[17:59] <kenvandine> we just need to get that published, blocked on the lack of powerpc build
[17:59] <rickspencer3> kenvandine, ok, I'll try it later this week ;)
[17:59] <rickspencer3> lack of powerpc build?
[17:59] <rickspencer3> er
[17:59]  * rickspencer3 shakes fist at PowerPC
[18:00] <kenvandine> yeah
[18:00] <kenvandine> it depends on qtdeclarative
[18:00] <kenvandine> which doesn't support ppc
[18:00] <kenvandine> so anything qml lacks ppc builds
[18:00] <kenvandine> and for signon-ui to work on the phone... we have to use the qtdeclarative
[18:01] <rickspencer3> hmmmm
[18:01] <kenvandine> rickspencer3, also of interest... i just added my facebook account with  ubuntu-system-settings
[18:01] <rickspencer3> I don't think we want to hold up all phone development for PPC
[18:01] <kenvandine> rickspencer3, indeed... it's been a real pain
[18:01] <rickspencer3> kenvandine, well, we should find a way to decouple it
[18:01] <kenvandine> yes
[18:02] <rickspencer3> aiui we only support PPC for the Xubuntu flavor community
[18:02] <kenvandine> we've been working on that everywhere we've hit this
[21:00] <Laney> so it seems that nautilus double signal handler disconnect wasn't the bug ;-)
[22:24] <xnox> Is there a ppa or something for me to try gtk 3.9+?
[22:26] <jbicha> xnox: ricotz/testing has a git snapshot; it's not been packaged elsewhere that I know of
[22:28] <xnox> jbicha thanks =)