[00:13] 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] Darxus: you mean that we have tests to ensure that we don't mistakenly leak new public symbols? [00:32] 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] 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] I understand the need for that check, I'm happy it happens. [00:42] 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] Darxus: it's worth mentioning that gtk itself has this check builtin upstream [00:51] 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] How do I update the abi so it'll build? [00:53] Darxus: debian/libgtk-3-0.symbols still exists [00:53] Darxus: you could also just disable the symbols check entirely [00:54] jibel: Yes, but debian/libgtk-3-0/DEBIAN/symbols doesn't. [00:54] why would that exist? [00:54] jbicha: good evening [00:54] oh you mean in the build directory [00:55] 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] 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] desrt: howdy [00:59] desrt: have you tried gnome-packagekit recently? I think it works well enough now [00:59] no [00:59] i'm living a pure unity existence lately [01:00] and trying not to kill myself.... [01:00] jbicha: Huh, thanks. What's the difference between -c0 and -c1? [01:02] -c1 will still fail if symbols disappear; man dpkg-gensymbols explains more [01:02] Cool, thanks. [01:02] desrt: how's the dogfood? ;) [01:03] I'd like to properly update the symbols, because I'd like to get this into the official quantal repos. [01:05] 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] jbicha: With both instances of -c4 changed to -c0 in debian/rules I still got the same failure from abicheck.sh. [01:15] DEB_DH_MAKESHLIBS_ARGS_$(SHARED_PKG) += -V --add-udeb=$(UDEB_PKG) -- -c0 [01:15] DEB_DH_MAKESHLIBS_ARGS_libgail-3-0 += -V -- -c0 [01:16] 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] does building the wayland support cause any regressions? [01:17] I remember you wanted to get that in last cycle; I'm surprised you didn't push for it earlier this cycle [01:17] jbicha: I've never stopped pushing... I just never get any responses. [01:18] well we could have got away with just doing it at the very beginning of a cycle [01:19] I keep getting freaking excuses why it's not the right time. [01:19] https://launchpad.net/bugs/954352 It's all there. [01:19] Ubuntu bug 954352 in gtk+3.0 "Enable wayland backend" [Wishlist,Confirmed] [01:19] I think it would require a Feature Freeze Exception now [01:20] "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] I had a ppa up with the change three months ago. [01:21] right, June or July would have been fabulous [01:21] Great. [01:22] anyway, the buildlog should tell you what symbols you need to add to the .symbols file [01:24] Thanks, so I just add them to... gdk/gdk.symbols ? Does it need to be in order? [01:25] 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] And yes, I do have the list of changes in the output. [01:26] alphabetical order is a good idea [01:27] for debian/libgtk-3-0.symbols, leave out the -0ubuntu1 stuff, 3.5.12 is all you need [01:28] Ah, yeah, I think I'm hitting a different abi check than that one.... [01:28] Upstream gdk/gdk.symbols. [01:29] 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] Yup, okay, everything makes sense now. [01:37] desrt was right, there's a bug in gtk's abi checking. [01:37] 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] ^ That was wrong, debian's abi checking / building is nice and clear about what the problem is. [01:41] I apologize for my lack of faith :P [01:45] 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] Woot, I have .debs. [01:57] dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/gtk+3.0_3.5.12-0ubuntu3+wayland0.diff.T1qCj3 [01:57] Hahah... I need to do that abi fix thing via quilt, right. Grr. [02:16] dpkg-source: error: unwanted binary file: debian/install/shared/usr/share/gtk-3.0/demo/gtk-logo-rgb.gif [02:16] dpkg-source: error: unwanted binary file: debian/install/shared/usr/share/gtk-3.0/demo/gnome-gmush.png [02:16] dpkg-source: error: unwanted binary file: debian/install/shared/usr/share/gtk-3.0/demo/apple-red.png [02:16] WTF? [02:16] dpkg-source: error: detected 818 unwanted binary files (add them in debian/source/include-binaries to allow their inclusion). [02:20] Ah, I think I accidentally built binary packages in that directory. [02:23] Hmm, nope, cleaned that up and still getting this error. [02:25] Ah, I wanted to be running "debuild -S", not "dpkg-buildpackage -rfakeroot -S". [02:32] 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] I'm trying to understand what is the point of /usr/share/glib-2.0/schemas/org.compiz.gnomecompat.gschema.xml [02:36] I mean compiz gconf had something similar that was broken but I don't think it's still needed [02:36] desrt: gtk-window-decorator [02:36] desrt: I'll be landing the thing to port it to gsettings soonish [02:37] jbicha: the point of that schema is to provide integration points with the gnome options [02:37] that's all [02:38] smspilla|z: but why can't you just use the already existing gnome schemas? [02:38] jbicha: we're not using gsettings directly [02:39] what are you using? [02:39] jbicha: compizconfig [02:39] which has a gsettings *backend* [02:39] the thing is that compizconfig doesn't work based on the schemas themselves [02:39] but rather what the plugins say the options /are/ [02:39] aren't all of the other backends unmaintained? [02:39] jbicha: no, they aren't [02:40] jbicha: switching to gsettings direclty would be a huge and very complicated move [02:40] it just seems wrong to me, there should only be one place to change the "Run command" keyboard shortcut [02:40] jbicha: there is only one place [02:40] jbicha: the gsettings backend has integration code, so it just updates both at the same time [02:41] or rather [02:41] it ignores the compiz key and looks at the gnome key instead [02:42] 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] I didn't do anything else [02:42] right [02:42] anyway, I'm trying to figure out how to get Ctrl+Alt+T working by default [02:43] jbicha: ah, now I think that option no longer has a gnome integration point, let me check [02:43] right, GNOME dropped the explicit key in 3.4; we need to add it back somehow [02:45] jbicha: org.compiz.integrated.gschema.xml [02:45] command-terminal [02:45] and uh [02:45] [02:45] ["Disabled"] [02:45] [02:45] jbicha: all of the gnome options that were dropped are now in org.compiz.integratd [02:45] (org.compiz.integrated) [02:46] which is only exists because g-c-c needs schemas that have paths [02:46] (compiz schemas are pathless because we need to support multiple profiles for gnome-classic and unity) [02:51] smspilla|z: why are two terminal commands in that file? [02:54] jbicha: there aren't ? [02:54] [02:54] "" [02:54] [02:54] ^ command for the terminal [02:54] [02:54] ["Disabled"] [02:54] [02:54] ^ [02:55] keybinding to run that command [02:55] I probably should have included a

section but I didn't have time to tbh [02:55] which is the keybinding and what does the other one do? [02:56] "run-command-terminal" <- the keybinding [02:56] "command-terminal" <- the actual terminal command (eg gnome-terminal) [02:57] why is panel-run-dialog in there? it's a gnome setting (Alt+F2) [03:35] GTK+ + Wayland PPA for Quantal is working: https://launchpad.net/~darxus/+archive/wayland-gtk-quantal [04:39] jbicha: is it? I didn't find an integrated key for it [04:39] Qt5 didn't make Quantal? [04:40] Oh, do they even have a stable release out yet? [04:40] jibel: ah, you're right. I'll propose a merge to get rid of those two then. Thanks [04:40] Yeah, beta release was planned this month. Nevermind. [04:45] smspilla|z: yes, in org.gnome.desktop.wm.keybindings [04:46] 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] there are several screenshot keyboard shortcuts in org.gnome.settings-daemon.plugins.media-keys [04:57] jbicha: okay thanks [05:03] jbicha: thanks for the advice [05:04] I'll propose a merge soonish tomorrow [06:30] 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] pango flips out [06:35] LLStarks: that's pretty cool, please file a bug for it :) [06:36] will do [06:37] jbicha, pango_font_description_set_size error is a pango or gnome-control-center bug? [06:40] it may be pango since System Settings worked in Precise but go ahead and mark it as affecting both [06:42] it's pretty nasty since it usually crashes the window manager too [06:44] hmm, not the manager, but decorations. if manager crashes, i usually can't interact with windows anymore [06:45] yeah, nice catch [06:54] jbicha, sorry got disconnected. bug 1041756 filed. [06:54] 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] jbicha: i don't like dogfood :p [15:20] Hmz, if I copy a file in file-roller, and then want to paste it in Nautilus, that doesn't work [15:20] 'Paste' is grayed out [15:20] by design or a bug? [15:25] dupondje: I've seen Paste grayed out quite a bit, but many times clicking it still works [15:27] then thats surely a bug :) === lidar is now known as LiDar