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