[04:42] <newbz> hi
[09:19] <tsdgeos> anyone knows if there's a lightdm channel?
[09:22] <Guest21041> Wow. repatcha. I could hardly log on. couldn't read the words.
[09:55] <sil2100> mhr3, Trevinho: how's bamf trunk right now?
[11:16] <Trevinho> sil2100: what you mean?
[11:23] <sil2100> Trevinho: is it ok for a release?
[11:43] <sil2100> Trevinho: https://code.launchpad.net/~sil2100/bamf/missing_files/+merge/117622 <- could you take a look ;) ?
[11:49] <tsdgeos> anyone in quantal can help me test something?
[11:49] <tsdgeos> it's like 3 min
[11:50] <sil2100> tsdgeos: what's up?
[11:51] <sil2100> I do have some testing packages installed though :o
[11:51] <tsdgeos> sil2100: is it a vm or "real" stuff?
[11:51] <tsdgeos> because i've already tried a vm but want to make sure it's not virtualbox playing tricks on me
[11:51] <sil2100> Real stuff
[11:51] <tsdgeos> basically i have this http://paste.kde.org/~tsdgeos/526508/ that on precise gives me a spinning spinner and on quantal vm gives me a non spinning one
[11:52] <sil2100> One moment, will try this
[11:52] <tsdgeos> sil2100: it'd be cool if you could give it a try and confirm that in real quantal it's non moving
[11:52] <tsdgeos> and then i'll have to find why it happens :D
[11:53] <sil2100> tsdgeos: ok, confirmed - my spinner does not spin
[11:53] <tsdgeos> sil2100: thanks!
[11:53] <sil2100> I get a spinner and it is not moving at all, just a steady image
[11:53] <sil2100> ;)
[11:53] <sil2100> tsdgeos: np
[11:54] <sil2100> tsdgeos: btw. you knew vala before?
[12:04] <sil2100> cnd: hi
[12:04] <sil2100> cnd: ping!
[12:31] <Trevinho> sil2100: ok... looking at it... I was wondering if I should have added them, but it was still compiling fine... :P
[12:31] <Trevinho> sil2100: need to check another thing...
[12:45] <tsdgeos> sil2100: nope, not at all
[12:48] <tsdgeos> sil2100: and no gtk3 either, so basically i'm just random guessing :D
[12:48] <tsdgeos> it's sad though that it works on precise and not on quantal
[13:27] <sil2100> Trevinho: it was compiling fine btw. ;) Just because they weren't added, they didn't land into the tarball during make distcheck ;p
[13:27] <Trevinho> sil2100: we still miss a .desktop file used for tests
[13:28] <Trevinho> sil2100: I was btw looking how we can remove generated files not to be distrubuted
[13:28] <sil2100> Trevinho: could you add that then?
[13:28] <Trevinho> sil2100: sure
[13:28] <sil2100> Trevinho: ah, that thing - that would be awesome to have - did you find anything?
[13:28] <Trevinho> sil2100: the strange fact is that... the sources defined in nodist_bamfadeamon_SOURCES are distributed anyway :°(
[13:29] <sil2100> Ouch
[13:29] <Trevinho> also, overriding the dist-hook removes them, but then I get then into the archive anyway
[13:29] <sil2100> Ok, now this is really strange
[13:32] <Trevinho> sil2100: yes... a lot
[13:43]  * Trevinho cries and implores automake to follow him
[13:58] <Trevinho> sil2100: https://code.launchpad.net/~3v1n0/bamf/missing_files_v2/+merge/117661
[14:03] <sil2100> Trevinho: aaah, the --enable-gtk-doc=yes flag - yesss, this is what we've been missing, since otherwise I had always had to call ./autogen.sh --enable-gtk-doc=yes
[14:03] <sil2100> Which was a bother ;)
[14:04] <sil2100> Trevinho: does the dist-hook remove the generated files correctly now?
[14:17] <Trevinho> sil2100: no -_-
[14:19] <sil2100> Trevinho: when trying to 'make' your branch, I get the error bamf.h:24:34: fatal error: bamf-gdbus-generated.h: File not found
[14:21] <Trevinho> sil2100: make dist or just make?
[14:22] <sil2100> Trevinho: just ./autogen.sh && make
[14:23] <Trevinho> sil2100: yep, my fault I removed one thing for testing, then i forgot to put it back
[14:27] <Trevinho> sil2100: pull it again
[14:30] <sil2100> Trevinho: re-testing it right now
[14:31] <Trevinho> sil2100: it seems that you stil need to pass the --enable-gtk-doc thing btw
[14:33] <sil2100> Awww
[14:33] <sil2100> ;)
[15:04] <sil2100> Trevinho: do you have a moment?
[15:04] <Trevinho> sil2100: yep
[15:05] <sil2100> Trevinho: could you maybe ACK https://code.launchpad.net/~sil2100/unity/geis_rename/+merge/117666 ?
[15:05] <sil2100> Trevinho: since this is breaking all merges right now
[15:05] <sil2100> Trevinho: there is a distro patch doing this which is broken
[15:05] <sil2100> Trevinho: if we accept this, I'll ask for reverting the distro patch itself
[15:07] <Trevinho> sil2100: ok approved
[15:08] <Trevinho> sil2100: but.... with with p we can still build unity?
[15:08] <Trevinho> I mean, is that package available somewhere?
[15:08] <sil2100> Trevinho: well, the catch is - without this change you can't build it on Q
[15:09] <Trevinho> sil2100: ok... but then we'd need to backport the new package to the staging ppa as well (for precise=
[15:09] <Trevinho> isn't it?
[15:10] <sil2100> Trevinho: probably, yes - if precise= is being built from unity trunk
[15:10] <Trevinho> sil2100: well, the staging ppa is built with unity trunk
[15:10] <Trevinho> for both p and q
[15:10] <Trevinho> we must make this continue working
[15:11] <Trevinho> (both for developers and testers)
[15:11] <sil2100> True true, but anyway unity staging is broken since a few weeks :/
[15:11] <sil2100> I'll fix it up as soon as possible though
[15:22] <Trevinho> sil2100: ok
[16:01] <sil2100> jaytaoko: ping
[16:02] <jaytaoko> sil2100: pong
[16:08] <sil2100> jaytaoko: can you approve https://code.launchpad.net/~sil2100/nux/geis_rename/+merge/117665 ?
[16:08] <sil2100> Since the name has changed recently
[16:10] <jaytaoko> sil2100: sure can do...
[16:10] <sil2100> Ok guys, I need to pop out for a while to get some movement ;)
[16:10] <sil2100> But I'll be back a bit later
[16:11] <jaytaoko> sil2100: approved
[16:12] <sil2100> jaytaoko: thanks!
[17:47] <MCR1> bschaefer, Trevinho: Hi :) Any news about the Jenkins Unity-merger problems ?
[17:50] <bschaefer> MCR1, hmm not that I have heard
[17:50] <bschaefer> MCR1, I think a branch is in the works to fix that though
[17:52] <Trevinho> MCR1: fixes are coming
[17:52] <Trevinho> MCR1: but we need to get fixed the packaging side before
[17:52] <Trevinho> MCR1: then we've already a branch by sil2100 to fix unity itself
[17:53] <MCR1> ah, ok - thx 4 the info - the geis_rename, yes ?
[18:39] <jaytaoko> sil2100: ping
[18:55] <sil2100> jaytaoko: pong, what's up?
[18:59] <jaytaoko> sil2100: hello! we have a branch to merge in Nux. It is required for some features in unity. Is this a good time to merge it. I saw your email on the status of unity trunk
[18:59] <sil2100> jaytaoko: let me check
[19:03] <sil2100> jaytaoko: once one of my approved merges goes in, I think it can get merged - I actually wanted to release unity and nux, but eh, due to Didier not being around and me not having all permissions, I don't think that's a good idea
[19:03] <sil2100> Since if I made a freeze tomorrow, we would have to release onf Friday - and we all hate Friday releases
[19:03] <sil2100> jaytaoko: what change is it?
[19:05] <jaytaoko> sil2100: this branch: https://code.launchpad.net/~dandrader/nux/geis/+merge/108239
[19:05] <jaytaoko> sil2100: it relates to adding geis support in Nux
[19:06] <sil2100> jaytaoko: does it change non-touch behavior as well?
[19:07] <sil2100> Or for normal input users it should not change anything?
[19:07] <jaytaoko> sil2100: no it does not
[19:08] <jaytaoko> sil2100: I have confirmed with dandrader who is the author
[19:08] <jaytaoko> sil2100: but you said you have a freeze pending?
[19:09] <jaytaoko> sil2100: or is it scheduled for tomorrow?
[19:09] <sil2100> jaytaoko: no, it's fine - if the branch is well tested you can merge it in
[19:09] <sil2100> jaytaoko: it's not really scheduled, since it was supposed to happen today or yesterday even
[19:09] <sil2100> But it didn't due to some problems
[19:09] <jaytaoko> sil2100: ok, we are ready to merge on our side
[19:10] <jaytaoko> sil2100: it will happen today. If not I will let you know.
[19:10] <sil2100> jaytaoko: thanks!
[19:10] <sil2100> I need to finish up for today sadly
[19:10] <sil2100> So see you tomorrow!
[19:11] <jaytaoko> sil2100: yw