[00:13] <Darxus> It looks like the gtk source package has a really horrible way of communicating it has noticed you built it with some additional functions in its output libraries and therefore is failing to build.
[00:32] <desrt> Darxus: you mean that we have tests to ensure that we don't mistakenly leak new public symbols?
[00:32] <desrt> Darxus: you might have to convince the rest of the world that this is a 'horrible' thing before we consider getting rid of it...
[00:34] <Darxus> desrt: No, I mean it took me forever to figure out what it was complaining about.  When I was already aware that "success" would be marked by an error about new symbols.
[00:34] <Darxus> I understand the need for that check, I'm happy it happens.
[00:42] <Darxus> Last time I did this, I could fix it with "cp -a debian/libgtk-3-0/DEBIAN/symbols debian/libgtk-3-0.symbols"... debian/libgtk-3-0/DEBIAN/symbols doesn't exist now.
[00:50] <desrt> Darxus: it's worth mentioning that gtk itself has this check builtin upstream
[00:51] <Darxus> Great.  It still would be nice if it was clearer what the build error was.  By possibly putting "error" somewhere near the error.
[00:51] <Darxus> How do I update the abi so it'll build?
[00:53] <jbicha> Darxus: debian/libgtk-3-0.symbols still exists
[00:53] <desrt> Darxus: you could also just disable the symbols check entirely
[00:54] <Darxus> jibel: Yes, but debian/libgtk-3-0/DEBIAN/symbols doesn't.
[00:54] <jbicha> why would that exist?
[00:54] <desrt> jbicha: good evening
[00:54] <jbicha> oh you mean in the build directory
[00:55] <Darxus> jbicha: Only because it did in the past, it was the updated list of exported symbols, and I was able to just copy it over the list it was checking against.
[00:58] <jbicha> Darxus: in debian/rules you could change DEB_DH_MAKESHLIBS_ARGS to -c0 or -c1 to make the build not fail when new symbols are added
[00:58] <jbicha> desrt: howdy
[00:59] <jbicha> desrt: have you tried gnome-packagekit recently? I think it works well enough now
[00:59] <desrt> no
[00:59] <desrt> i'm living a pure unity existence lately
[01:00] <desrt> and trying not to kill myself....
[01:00] <Darxus> jbicha: Huh, thanks.  What's the difference between -c0 and -c1?
[01:02] <jbicha> -c1 will still fail if symbols disappear; man dpkg-gensymbols explains more
[01:02] <Darxus> Cool, thanks.
[01:02] <jbicha> desrt: how's the dogfood? ;)
[01:03] <Darxus> I'd like to properly update the symbols, because I'd like to get this into the official quantal repos.
[01:05] <Darxus> Is there a separate exported symbol test in the upstream gtk stuff (which shouldn't be throwing an error for adding --enable-wayland backend), and in the debian packaging stuff?
[01:14] <Darxus> jbicha: With both instances of -c4 changed to -c0 in debian/rules I still got the same failure from abicheck.sh.
[01:15] <Darxus> DEB_DH_MAKESHLIBS_ARGS_$(SHARED_PKG) += -V --add-udeb=$(UDEB_PKG) -- -c0
[01:15] <Darxus> DEB_DH_MAKESHLIBS_ARGS_libgail-3-0 += -V -- -c0
[01:16] <jbicha> I don't think I've ever built GTK, you could definitely get more help on Monday if you're still having problems then
[01:16] <jbicha> does building the wayland support cause any regressions?
[01:17] <jbicha> I remember you wanted to get that in last cycle; I'm surprised you didn't push for it earlier this cycle
[01:17] <Darxus> jbicha: I've never stopped pushing... I just never get any responses.
[01:18] <jbicha> well we could have got away with just doing it at the very beginning of a cycle
[01:19] <Darxus> I keep getting freaking excuses why it's not the right time.
[01:19] <Darxus> https://launchpad.net/bugs/954352  It's all there.
[01:19] <ubot2`> Ubuntu bug 954352 in gtk+3.0 "Enable wayland backend" [Wishlist,Confirmed]
[01:19] <jbicha> I think it would require a Feature Freeze Exception now
[01:20] <Darxus> "Quantal work has not started for that long but gtk 3.5 is being prepared for upload (in fact it's ready for a bit but some theming changes mean that unico needs to be updated, the current version segfaults with the new gtk), it should go in quantal next week " - seb128, 2012-06-05:
[01:20] <Darxus> I had a ppa up with the change three months ago.
[01:21] <jbicha> right, June or July would have been fabulous
[01:21] <Darxus> Great.
[01:22] <jbicha> anyway, the buildlog should tell you what symbols you need to add to the .symbols file
[01:24] <Darxus> Thanks, so I just add them to... gdk/gdk.symbols ?  Does it need to be in order?
[01:25] <Darxus> To answer your other question, I believe there were no regressions.  (I needed to look up a segfault problem, but that was only related to running things through weston.. there's a bug open against the overlay scrollbar thing for it)
[01:25] <Darxus> And yes, I do have the list of changes in the output.
[01:26] <jbicha> alphabetical order is a good idea
[01:27] <jbicha> for debian/libgtk-3-0.symbols, leave out the -0ubuntu1 stuff, 3.5.12 is all you need
[01:28] <Darxus> Ah, yeah, I think I'm hitting a different abi check than that one....
[01:28] <Darxus> Upstream gdk/gdk.symbols.
[01:29] <Darxus> I bet after adding the symbols to that file, I'll get the old familiar check failure I had been getting last time, and can just copy over that file.
[01:37] <Darxus> Yup, okay, everything makes sense now.
[01:37] <Darxus> desrt was right, there's a bug in gtk's abi checking.
[01:37] <Darxus> 08:13PM < Darxus> It looks like the gtk source package has a really horrible way of communicating it has noticed you built it with some  additional functions in its output libraries and therefore is failing to build.
[01:37] <Darxus> ^ That was wrong, debian's abi checking / building is nice and clear about what the problem is.
[01:41] <Darxus> I apologize for my lack of faith :P
[01:45] <Darxus> desrt: Thanks a lot for your help, I don't want to think about how long it would've taken me to figure this out on my own.
[01:52] <Darxus> Woot, I have .debs.
[01:57] <Darxus> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/gtk+3.0_3.5.12-0ubuntu3+wayland0.diff.T1qCj3
[01:57] <Darxus> Hahah... I need to do that abi fix thing via quilt, right.  Grr.
[02:16] <Darxus> dpkg-source: error: unwanted binary file: debian/install/shared/usr/share/gtk-3.0/demo/gtk-logo-rgb.gif
[02:16] <Darxus> dpkg-source: error: unwanted binary file: debian/install/shared/usr/share/gtk-3.0/demo/gnome-gmush.png
[02:16] <Darxus> dpkg-source: error: unwanted binary file: debian/install/shared/usr/share/gtk-3.0/demo/apple-red.png
[02:16] <Darxus> WTF?
[02:16] <Darxus> dpkg-source: error: detected 818 unwanted binary files (add them in debian/source/include-binaries to allow their inclusion).
[02:20] <Darxus> Ah, I think I accidentally built binary packages in that directory.
[02:23] <Darxus> Hmm, nope, cleaned that up and still getting this error.
[02:25] <Darxus> Ah, I wanted to be running "debuild -S", not "dpkg-buildpackage -rfakeroot -S".
[02:32] <jbicha> man I wish the gsettings Unity/Compiz rewrite had landed sooner, I guess I should have went looking for it myself in trunk
[02:33] <jbicha> I'm trying to understand what is the point of /usr/share/glib-2.0/schemas/org.compiz.gnomecompat.gschema.xml
[02:36] <jbicha> I mean compiz gconf had something similar that was broken but I don't think it's still needed
[02:36] <smspilla|z> desrt: gtk-window-decorator
[02:36] <smspilla|z> desrt: I'll be landing the thing to port it to gsettings soonish
[02:37] <smspilla|z> jbicha: the point of that schema is to provide integration points with the gnome options
[02:37] <smspilla|z> that's all
[02:38] <jbicha> smspilla|z: but why can't you just use the already existing gnome schemas?
[02:38] <smspilla|z> jbicha: we're not using gsettings directly
[02:39] <jbicha> what are you using?
[02:39] <smspilla|z> jbicha: compizconfig
[02:39] <smspilla|z> which has a gsettings *backend*
[02:39] <smspilla|z> the thing is that compizconfig doesn't work based on the schemas themselves
[02:39] <smspilla|z> but rather what the plugins say the options /are/
[02:39] <jbicha> aren't all of the other backends unmaintained?
[02:39] <smspilla|z> jbicha: no, they aren't
[02:40] <smspilla|z> jbicha: switching to gsettings direclty would be a huge and very complicated move
[02:40] <jbicha> it just seems wrong to me, there should only be one place to change the "Run command" keyboard shortcut
[02:40] <smspilla|z> jbicha: there is only one place
[02:40] <smspilla|z> jbicha: the gsettings backend has integration code, so it just updates both at the same time
[02:41] <smspilla|z> or rather
[02:41] <smspilla|z> it ignores the compiz key and looks at the gnome key instead
[02:42] <smspilla|z> jbicha: think of it this way: I just took what we used to do with gconf, and rewrote it to use gsettings instead
[02:42] <smspilla|z> I didn't do anything else
[02:42] <jbicha> right
[02:42] <jbicha> anyway, I'm trying to figure out how to get Ctrl+Alt+T working by default
[02:43] <smspilla|z> jbicha: ah, now I think that option no longer has a gnome integration point, let me check
[02:43] <jbicha> right, GNOME dropped the explicit key in 3.4; we need to add it back somehow
[02:45] <smspilla|z> jbicha: org.compiz.integrated.gschema.xml
[02:45] <smspilla|z> command-terminal
[02:45] <smspilla|z> and uh
[02:45] <smspilla|z> 	<key type="as" name="run-command-terminal">
[02:45] <smspilla|z> 	    <default>["Disabled"]</default>
[02:45] <smspilla|z> 	</key>
[02:45] <smspilla|z> jbicha: all of the gnome options that were dropped are now in org.compiz.integratd
[02:45] <smspilla|z> (org.compiz.integrated)
[02:46] <smspilla|z> which is only exists because g-c-c needs schemas that have paths
[02:46] <smspilla|z> (compiz schemas are pathless because we need to support multiple profiles for gnome-classic and unity)
[02:51] <jbicha> smspilla|z: why are two terminal commands in that file?
[02:54] <smspilla|z> jbicha: there aren't ?
[02:54] <smspilla|z> 	<key type="s" name="command-terminal">
[02:54] <smspilla|z> 	    <default>""</default>
[02:54] <smspilla|z> 	</key>
[02:54] <smspilla|z> ^ command for the terminal
[02:54] <smspilla|z> 	<key type="as" name="run-command-terminal">
[02:54] <smspilla|z> 	    <default>["Disabled"]</default>
[02:54] <smspilla|z> 	</key>
[02:54] <smspilla|z> ^
[02:55] <smspilla|z> keybinding to run that command
[02:55] <smspilla|z> I probably should have included a <summary> section but I didn't have time to tbh
[02:55] <jbicha> which is the keybinding and what does the other one do?
[02:56] <smspilla|z> "run-command-terminal" <- the keybinding
[02:56] <smspilla|z> "command-terminal" <- the actual terminal command (eg gnome-terminal)
[02:57] <jbicha> why is panel-run-dialog in there? it's a gnome setting (Alt+F2)
[03:35] <Darxus> GTK+ + Wayland PPA for Quantal is working:  https://launchpad.net/~darxus/+archive/wayland-gtk-quantal
[04:39] <smspilla|z> jbicha: is it? I didn't find an integrated key for it
[04:39] <Darxus> Qt5 didn't make Quantal?
[04:40] <Darxus> Oh, do they even have a stable release out yet?
[04:40] <smspilla|z> jibel: ah, you're right. I'll propose a merge to get rid of those two then. Thanks
[04:40] <Darxus> Yeah, beta release was planned this month.  Nevermind.
[04:45] <jbicha> smspilla|z: yes, in org.gnome.desktop.wm.keybindings
[04:46] <jbicha> there's a panel-main-menu also but System Settings > Keyboard uses the description "Show the activities overview" for it, which means GNOME just uses it as a duplicate of Super
[04:48] <jbicha> there are several screenshot keyboard shortcuts in org.gnome.settings-daemon.plugins.media-keys
[04:57] <smspilla|z> jbicha: okay thanks
[05:03] <smspilla|z> jbicha: thanks for the advice
[05:04] <smspilla|z> I'll propose a merge soonish tomorrow
[06:30] <LLStarks> ricotz. jbicha, are you aware of the following gnome-control-center crasher? go into User Accounts and try to change your full name.
[06:31] <LLStarks> pango flips out
[06:35] <jbicha> LLStarks: that's pretty cool, please file a bug for it :)
[06:36] <LLStarks> will do
[06:37] <LLStarks> jbicha, pango_font_description_set_size error is a pango or gnome-control-center bug?
[06:40] <jbicha> it may be pango since System Settings worked in Precise but go ahead and mark it as affecting both
[06:42] <LLStarks> it's pretty nasty since it usually crashes the window manager too
[06:44] <LLStarks> hmm, not the manager, but decorations. if manager crashes, i usually can't interact with windows anymore
[06:45] <jbicha> yeah, nice catch
[06:54] <LLStarks> jbicha, sorry got disconnected. bug 1041756 filed.
[06:54] <ubot2`> Launchpad bug 1041756 in gnome-control-center "gnome-control-center crashes when trying to change full name in User Accounts" [Undecided,New] https://launchpad.net/bugs/1041756
[15:05] <desrt> jbicha: i don't like dogfood :p
[15:20] <dupondje> Hmz, if I copy a file in file-roller, and then want to paste it in Nautilus, that doesn't work
[15:20] <dupondje> 'Paste' is grayed out
[15:20] <dupondje> by design or a bug?
[15:25] <jbicha> dupondje: I've seen Paste grayed out quite a bit, but many times clicking it still works
[15:27] <dupondje> then thats surely a bug :)