[01:04] <ph> darkxst, hi ya - r u online?
[01:05] <ph> got a jhbuild error with webkit - it's looking for freetype.h in freetype/freetype.h but it's installed to freetype2/freetype.h should I change the script or ln freetype2 to freetype?
[01:36] <ph> darkxst, you here yet... ?
[02:33] <darkxst> ph, skip webkit
[02:33] <ph> darkxst, lol - i just got the build working now :P
[02:33] <darkxst> ph, you can just use the system webkit
[02:33] <darkxst> from trusty
[02:36] <ph> darkxst,  ah ok... you know jhbuild sysdeps command... it shows that it can use alot of existing system apps and libs, but when running the build it doesn't appear to use them.... should I be commenting out those it can use in the moduleset .module file that I'm using?
[02:36] <ph> so that it's not being forced to build them... ?
[02:36] <darkxst> I think `jhbuild sysdeps --install `is broken on ubuntu (it doesn't actually install anything)
[02:37] <darkxst> you need to manually install
[02:37] <ph> ah ok
[02:38] <darkxst> also some things like webkit are always built by default
[02:38] <darkxst> but you can skip them in .jhbuildrc
[02:39] <ph> how do you skip them?
[02:39] <ph> darkxst, when i run jhbuild sysdeps |grep -i webkit - it says WebKit (webkitgtk-3.0.pc, required=2.3.2, installed=2.2.1)
[02:40] <ph> darkxst, are you running the g-s 3.11.2?
[02:41] <darkxst> hmm webkit should have been updated to 2.3 I thought
[02:42] <darkxst> ph, "skip = ['WebKit']"
[02:42] <darkxst> yeh I am running 3.11.2
[02:42] <ph> darkxst, the steps I've done to build so far are install ubuntu gnome 14.04, base system apps, then run the introductory jhbuild script to install everything it needs, then i've configured jhbuild and run jhbuild build -aN. It failed at WebKit
[02:43] <darkxst> it will probably fail at a bunch of things!
[02:43] <ph> I don't have the staging ppa
[02:43] <ph> just the default g-s 3.8.2 that comes with u g 14.04
[02:44] <ph> is that cool so far for the steps I've run?
[02:44] <darkxst> yeh
[02:44] <darkxst> gnome-shell 3.11.2 is on staging as of this morning
[02:44] <ph> what version of WebKit do you have installed?
[02:45] <ph> lol - well I wanted to get the jhbuild environment done anyways
[02:46] <darkxst> 2.2.1
[02:47] <ph> ok cool - so if it works fine on yours with that then easiest is just to skip it then
[02:54] <darkxst> webkit shouldnt matter too much unless you are building epiphany
[02:54] <darkxst> as a first run, just skip any modules that fail, some really don't matter too much
[02:55] <darkxst> then try jhbuild buildone gnome-shell. and start building whatever it complains about
[02:55] <darkxst> things like e-d-s, cogl, clutter, mutter etc will be fairly important
[02:56] <ph> darkxst, ok cool thanks for the tip. Also is ccache enabled and used by jhbuild by default?
[02:57] <darkxst> I don't think so
[02:57] <darkxst> but generally you won't need to be building the full stack, so builds are usually pretty quick
[02:58] <ph> right ok good, so it's like the build is a one time thing and then it's just updating modules as required type thing?
[02:58] <darkxst> yeh, that is what I do
[02:58] <darkxst> although I don't build much beyond gnome-shell, g-s-d and g-c-c
[03:00] <ph> excellent... do you think you can give me some help patching g-s-d from this bug: https://bugzilla.gnome.org/show_bug.cgi?id=709859
[03:00] <ph> specifically the disable scaling for hdmi outputs
[03:01] <ph> I want to see if that resolves my huge fonts issue
[03:03] <ph> by the way my .jhbuildrc-custom is using moduleset = gnome-world-3.12 and modules = meta-gnome-core-shell, is that basically what you're running?
[03:06] <darkxst> ph, use git bz
[03:06] <darkxst> goto the gnome-settings-daemon folder and run
[03:06] <darkxst> git bz apply 709859
[03:06] <ph> oh wow - I never knew that existed :D
[03:07] <darkxst> (you might need to install the bz plugin for git)
[03:08] <darkxst> ph, how do you think the devs get their patches into the bugs? they don't manually attach them :)
[03:08] <ph> lol that's what i thought they did :P
[03:09] <ph> darkxst, so how do i build g-s-d again with jhbuild once i've patched it?
[03:15] <ph> darkxst, also I have a question - I like using guake but it relies on libglade which isn't installed in the system but has been built by jhbuild, how do I avoid guake wanting to install it in the system aswell?
[03:15] <ph> do i need to manually build guake, and then point it at the libs under myjhbuild install/ folder?
[03:16] <ph> or do I remove the libglade built by jhbuild, install it in the system and then jhbuild will use the system one?
[03:17] <ph> darkxst, so I'm avoiding duplication of apps and libs where possible...
[04:32] <darkxst> ph, it should use system lib, if you set it as skip and uninstall said lib from jhbuild
[04:32] <darkxst> patch, then: jhbuild buildone -afc gnome-settings-daemon
[04:41] <ph> darkxst, cool thanks for that - sorry was afk for a bit
[04:44] <ph> darkxst, libglade for example is a gnome library, or a linux library?
[04:47] <ph> also when running gnome-shell 3.11.2, if running things like gnome-tweak-tool from within the 3.11.2 shell, does that start the one built by jhbuild or the one that's installed in the system? ie do I need to update .desktop files to be running jhbuild run gnome-tweak-tool etc?
[05:07] <darkxst> it would launch the system installed one
[05:10] <darkxst> ph, glade is gnome
[05:18] <ph> darkxst, ok so basically all apps would need to be run via jhbuild, to use those downloaded and built by jhbuild yeah?
[05:18] <darkxst> yes
[05:19] <ph> But if running like g-s with jhbuild, and it needs to start another app, then it will run the jhbuild app or the system app?
[05:24] <ph> darkxst, I mean when running an app with jhbuild, it knows to pull in other apps and dependencies from the jhbuild environment?
[05:26] <darkxst> maybe, not entirely sure
[05:26] <ph> ah ok
[05:47] <darkxst> ph, would you be interested in helping with packaging of 3.11 for staging?
[05:48] <ph> darkxst, sure if I can
[05:48] <ph> just using like uupdate, and pbuilder?
[05:48] <darkxst> yeh
[05:49] <ph> yeah no probs
[05:49] <ph> but i'd only be able to package 64bit ...
[05:49] <darkxst> I would like to move the packaging back to bzr branches, but right now there are none, so uupdate/pbuilder
[05:49] <ph> or common
[05:49] <darkxst> ph, ppa builders deal with that, you are just testing by building locally
[05:51] <ph> ah ok cool - so it's just testing the 64bit, but it will still generate i386 packages as well depending on the commands to pbuilder?
[05:51] <darkxst> yes all ppa packages get built for amd64 and i386
[05:51] <darkxst> archive packages also get ppc and arm64
[05:52] <ph> ok - so I assume that i'd just be packaging the 3.11 packages i'm using?
[05:52] <darkxst> yes the tarballs
[05:53] <darkxst> uscan will grab them mostly (but sometimes have to edit debian/watch)
[05:53] <ph> only tarballs, so not packaging from git?
[05:54] <ph> as in master branch - just the releases only?
[05:54] <darkxst> generally yes, unless there is no tarball available, then we might use a git snapshot
[05:54] <ph> ok no worries :)
[05:54] <darkxst> ftp://ftp.gnome.org/pub/gnome/sources/
[05:56] <darkxst> ph, make sure to update all deps in control[.in] , (git log -p configure.ac, in the jhbuild folder is good for that)
[05:56] <darkxst> check NEWS for major changes etc...
[05:56] <ph> and once packaged where do I put them etc? and who makes the decisions about tarball/git snapshots?
[05:57] <darkxst> we would only use a git snapshot if there was no tarball released yet, but updated branch was required
[05:58] <darkxst> when ready take a debdiff of just the debian folder (debdiff ... | filterdiff "*/debian/*")
[05:59] <ph> ok, and the control.in part you just said what's that about exactly?
[05:59] <darkxst> sorry, filterdiff -i
[05:59] <darkxst> ph control/control.in specifies build and runtime dependencies and versions
[06:00] <darkxst> if upstream say they need gtk 3.11.2 for example, then you need to update that in the control file
[06:01] <ph> ok but the git command u said does that, or it's a manual process?
[06:01] <ph> <--- noob here
[06:02] <ph> I know how to package etc, but I've never packaged into a ppa before, so I might need to be shown or given a run through first so I know what i'm doing
[06:04] <ph> darkxst, on a side note the packages that jhbuild are failing on saying no libsystemd-login even though that's installed... should I --enable-libsystemd-login=no for those or are they actually required? I mean the system version if I attempt to remove that one as suggested in another bug it wants to remove all of ubuntu just about
[06:09] <darkxst> ph, the git command shows you what has been changed
[06:09] <darkxst> you then manually edit control file
[06:10] <darkxst> ph, what packages? we have logind
[06:10] <ph> polkit and colord are two that have failed - i got around it by doing --enable-libsystemd-login=no for polkit and --disable-systemd-login for colord
[06:11] <ph> but do they need to use libsystemd-login or they will use something else instead?
[06:14] <darkxst> they should be using logind. I get "checking for LIBSYSTEMD_LOGIN... yes" for polkit
[06:15] <darkxst> do you have libsystemd-login-dev installed?
[06:16] <ph> do you have a libsystemd-login built within jhbuild?
[06:16] <ph> do i need to have the libsystemd-login-dev installed in my system perhaps?
[06:19] <darkxst> system package
[06:20] <darkxst> likewise with anything listed as mandatory by 'jhbuild sysdeps'
[06:20] <ph> ah as you said before the jhbuild sysdeps --install wasn't working so that's why they got missed
[06:21] <ph> my fault ok cool
[06:21] <darkxst> it doesnt install any packages (but it does list them)
[06:22] <ph> yeah that's what's happened - i'll just install them manually
[06:33] <ph> ok it's back building again - so what is the git log -p configure.ac within the jhbuild folder actually doing?
[06:39] <ph> darkxst, ok it's back building again - so what is the git log -p configure.ac within the jhbuild folder actually doing?
[06:39] <ph> it opens the configure.ac file and allows me to do what with it?
[06:39] <darkxst> go to a folder, say gnome-settings-daemon
[06:39] <darkxst> then run it
[06:39] <darkxst> it will show you all changes to that file (in diff format)
[06:43] <darkxst> configure.ac contains all dependencies and versions as defined by upstream
[06:43] <ph> ok i get it - so it shows me what are the changes to dependencies from the last version, so it makes it easy to spot and then update the control.in file yeah?
[06:43] <darkxst> yeh
[06:44] <ph> nice ok - yeah coz i was going to ask what if they added new deps, but that answers that question
[06:49] <ph> so we got to the when ready take a debdiff of the debain folder. But the debian folder isn't in the tarball I downloaded from the ftp site you gave me. So you mean I need to to an apt-get source first right?
[06:49] <ph> *do
[06:50] <ph> darkxst, where do i get the source from though? just whatever is available in the ubuntu repos for whatever I'm packaging?
[06:51] <darkxst> ph, start with 3.10 package from gnome3-staging/saucy or debian
[06:52] <darkxst> if you use debian source, check the ubuntu packages for any changes that are needed though
[06:54] <ph> yeah i thought so - ok so just by adding the source for that ppa or have to download the source manually from the staging ppa? What is the debian source you mentioned?
[06:55] <darkxst> some of the 3.10 packages are in debian
[06:55] <darkxst> I use chdist to grab saucy source packages
[06:55] <darkxst> pull-debian-source to get debian packages
[06:57] <ricotz> darkxst, hi, i am going to fix up mutter 3.11.2
[07:03] <ph> can you give me an example of each of those commands?
[07:08] <darkxst> ricotz, ok
[07:09] <darkxst> ph, look at the man pages ;)
[07:09] <ricotz> darkxst, are you working on gnome-icon-theme?
[07:11] <darkxst> ricotz, there was no 3.11 release for that
[07:11] <darkxst> I will just copy the 3.10 to trusty
[07:11] <ricotz> darkxst, right, i will push a rebuild with a bumped dep
[07:12] <darkxst> ok
[07:12] <ricotz> darkxst, the copy won't suffice
[07:13] <ricotz> ah no the g-i-t-symbolic needs to be patched
[07:16] <darkxst> ricotz, oh, I see
[07:18] <darkxst> ricotz, I'm off to cook dinner, feel free to push a fix in the meantime
[07:18] <ricotz> darkxst, already did
[07:19] <darkxst> :)
[07:35] <ph> darkxst, 14 packages left to build
[07:46] <ph> darkxst, so yeah according to the doco - jhbuild will pull libs, apps etc from the jhbuild environment first, and if it can't find it then it will pull it from the system
[07:56] <ph> ricotz, r u running g-s in jhbuild?
[08:04] <ricotz> ph, no
[08:04] <ph> me likey but have some issues - gonna reboot and also i'll try setting up a session to point to jhbuild gnome-shell
[08:04] <ph> ricotz, that's a pity - what version of g-s are you running?
[08:05] <ricotz> git master
[08:06] <ph> ricotz, how did you manage that? r u running ubuntu?
[08:07] <ricotz> using PPAs and local builds
[08:08] <ph> so like install base ubuntu gnome - then staging ppa, then built from git?
[08:09] <ricotz> kind of
[08:09] <ph> ricotz, lol you're crazy!!! I'm jealous :P Is it stable?
[08:10] <darkxst> ph, yes it does, but most likely glib_spawn, does not know about jhbuild so apps launched from the shell are mostly likely not run in a jhbuild shell
[08:10] <ricotz> ph, i am using g-s git since karmic
[08:11] <ricotz> and it works fine with some drawbacks from time to time
[08:11] <ph> ricotz, nice but probably a lot of work to keep it running smooth and updated etc though?
[08:13] <ph> darkxst, well I just installed gnome-tweak-tool also and ran it by alt+f2 and it opened the jhbuild version, but you mean that it might not be wrapped properly in the jhbuild environment?
[08:14] <darkxst> if it ran, it ran!
[08:15] <ph> darkxst, lol i see - so if an app doesn't it means it's not playing nice with jhbuild
[16:24] <ricotz> darkxst, hi, keep in mind if you copy to and rebuild packages in staging, make sure the deps are built before pushing the next package
[16:24] <ricotz> darkxst, gnome-shell wasn't built against the new gjs
[16:43] <kronstadt> hello
[16:43] <kronstadt> anybody talk spanish too?
[21:53] <MaverickPT> hello people
[21:53] <MaverickPT> gnome-settings-daemon crashed on ubuntu 13.10, any ideas why?