=== ph_afk is now known as ph1 === ph_afk is now known as ph1 === prth_ is now known as prth === prth_ is now known as prth [10:56] darkxst, hi, i am curious what requires libgit2-glib ;) [11:00] gitg [11:06] darkxst, i see, better requestsync to get it in utopic too [11:06] if it test-builds there fine [11:07] ricotz, yes I plan to sync it to utopic [11:08] do you have a buildd builder setup? [11:08] (sbuild) [11:08] pbuilder [11:08] test passes on pbuilder [11:09] but fails on the ppa builders [11:09] meaning if you sync it and it builds fine, avoid bumping the trusty version that way [11:09] yes of course [11:09] could be some qemu problem [11:10] (too late for that though) [11:10] oh I see what you mean [11:13] you can delete the current package and upload 0.0.12-1~trusty2 for further checks [11:14] bbl [11:23] hi everyone [11:24] I have created packages for gitg 0.3.2 as I mention in https://bugs.launchpad.net/ubuntu/+source/gitg/+bug/1291092 [11:24] Ubuntu bug 1291092 in gitg (Ubuntu) "New upstream version 0.3.2 available" [Wishlist,Confirmed] [11:24] frandieguez, please paste a debdiff [11:24] could packaging team review them as they are far from perfect [11:24] ok, I'll try [11:25] darkxst, I have created the packages by getting the tarball file from GNOME FTP and I have copied the debian/ folder from the sources of the previous version [11:26] What is the best approach to get the proper debdiff [11:26] frandieguez, debdiff old.dsc new.dsc | filterdiff -i "*/debian/*" [11:26] great [11:31] darkxst, here is it http://pastebin.com/jEssRiZ7 [11:31] please review all the build-deps and deps [11:32] this produces a funtional gitg package [11:32] but in the diff explorer it doesn't show anything [11:33] the diff explorer is the part where after selecting a commit it shows the differences of it [11:33] frandieguez, you don't need to explicitly list libs under Depends: [11:33] (they get picked up automatically from the linking [11:33] and it is quite weird because by compiling gitg through the manual process it works as expected [11:34] maybe some build-dep is still missing [11:35] darkxst, yep something is missing [11:36] I've tried creating a pbuider environment but I don't know how to pass the local libgit2-glib packages to use them while compiling gitg inside [11:36] afk for a while [11:37] frandieguez, libgit2-glib will be on -staging in about 10mins or so (upload this morning failed) [11:57] frandieguez, also make sure to include version depends where configure.ac specifies required versions! [12:01] *cough* wrap-and-sort ;) [12:13] hmm, seems to be incredibly slow at cloning ;( [12:14] oh maybe my internet is just flooded, I will never get used to this thing they call ADSL! [12:14] * mgedmin is seeing between one and two gnome-shell 3.12 crashes per day [12:18] mgedmin, please file bugs from the crash reports (retracer should be fixed now) [12:18] https://bugs.launchpad.net/ubuntu-gnome/+bug/1317060 [12:18] Error: ubuntu bug 1317060 not found [12:19] curiously, not every crash gives me an apport crash dialog [12:21] mgedmin, remind me to take a look at that after the retracer as processed it! [12:21] sure [12:41] (my hopes are low) [12:44] this is probably a duplicate of https://bugs.launchpad.net/ubuntu-gnome/+bug/1315727, which was retraced a few days ago [12:44] Error: ubuntu bug 1315727 not found [12:45] yeh that one failed to retrace properly [12:46] I tried a local apport-retrace on a different crash I think; gdb complained about addresses outside of the core file [12:47] claiming it was truncated [12:47] are there any core size limits in /proc/sys I ought to adjust? [12:53] gnome-terminal's copy paste is horribly broken as usual :( [12:54] I cannot copy the full stack trace out of the terminal window into a browser [12:55] it works better if I select smaller pieces [12:55] here: https://gist.github.com/mgedmin/2cb353007d036788860c [13:05] mgedmin, use 'set logging file' ') [13:05] one day I need to learn gdb [13:06] do I have to fix those errors in debian/control or are you taking care of the rest of packaging process? [13:06] that was a question for darkxst [13:07] frandieguez, I cleaned up and uploaded [13:07] * darkxst is off to bed now [13:10] great, thanks... I've just see that it is currently building [13:14] * mgedmin disables all shell extensions to see if the crashes will continue [21:12] Hey, is anyone getting a bug where a terminal window sort of turns into an un-killable zombie window that floats above everything? [21:14] it looks like this : http://imgur.com/rwI4yBO [22:15] sparq, nope, what version?