[00:09] <hzsp> hi.  I need some help building gnome-settings-daemon (first time I've tried to build an ubuntu package from source).  first off, am I in the right channel? :)
[00:09] <cyphermox> hzsp yes, or #ubuntu-desktop
[00:11] <cyphermox> cjwatson: if you share ld options for testing i may be able to kick off a few test builds locally here , then poke seb with  results
[00:12] <cjwatson> cyphermox: 14:12 <cjwatson> seb128: try ld --no-keep-memory
[00:12] <cjwatson> cyphermox: 14:13 <cjwatson> seb128: possibly --reduce-memory-overheads too
[00:13] <cyphermox> i realize it would probably take just as long to build for me though
[00:13] <hzsp> ok.  so I'm getting this error when trying to make: http://pastebin.com/d3WPkTAJ
[00:13] <cyphermox> cjwatson: thx
[00:14] <cyphermox> building something will be a nice change from the blistering cold though. :)
[00:16] <cyphermox> hzsp: its not linking properly against libnotify. how are you building it?
[00:16] <hzsp> I got the source with apt-get source and build-dep, then I tried to run ./configure && make, but I ran into some issues which I think I've overcome
[00:17] <stgraber> cyphermox: it's not that cold ;) though you can probably save a bit on heating and instead spend it on electricty for your build farm ;)
[00:17] <hzsp> make was initially telling me 'libtool: Version mismatch error'.  I ran autoreconf -i and that problem's gone away.
[00:18] <cjwatson> any reason you aren't using the package build rules?
[00:19] <cyphermox> stgraber: im at the Quebec carnival, spent most of  the day outside
[00:19] <hzsp> cjwatson: can you explain
[00:19] <cjwatson> there's a uniform way to build packages, which normally involves calling debian/rules to do configuration and compilation, not typing the commands by hand
[00:20] <stgraber> cyphermox: oh yeah, I only spent an hour or so outside today, wouldn't like to spend the whole day out, the -13C quickly becomes annoying ;)
[00:20] <cjwatson> simplest way to invoke it is 'debuild -b'
[00:20] <cjwatson> (requires devscripts to be installed)
[00:20] <hzsp> cjwatson: I see.  I was reading the INSTALL file which told me to do a configure && make
[00:20] <cjwatson> those are the upstream directions
[00:20] <cjwatson> but if you're trying to duplicate the package you should use the packaging tools
[00:20] <hzsp> I'll try that, ta
[00:21]  * cjwatson double-checks whether gnome-settings-daemon builds in current precise
[00:21] <cyphermox> most likely
[00:21] <hzsp> I'll nuke the source tree and install it again just to be safe
[00:24] <cyphermox> stgraber, we were dressed for the north pole
[00:24] <hzsp> is debuild -b going to do a make install as well?  is it likely to install into /usr/local?
[00:24] <cyphermox> hzsp: no
[00:24] <stgraber> cyphermox: hehe, good ;)
[00:24] <cyphermox> it Will give you .debs to installer
[00:24] <cjwatson> hzsp: it's incapable of installing into /usr/local, unless you run it as root (which you shouldn't!)
[00:25] <cjwatson> hzsp: it does a make install or the equivalent, but into a temporary tree
[00:25] <cjwatson> which is part of the process of building packags
[00:25] <cjwatson> *packages
[00:25] <hzsp> cjwatson: ok, thanks
[00:32] <cjwatson> hzsp: I can confirm that gnome-settings-daemon builds from source in precise using the packaging rules
[00:32] <cjwatson> haven't checked other releases
[00:33] <hzsp> cool.  I'm building on (and for) precise.
[00:34] <hzsp> it got as far as clearsign failed: secret key not available  debsign: gpg error occurred
[00:35] <hzsp> but it did build binaries ok
[00:35] <cjwatson> sure, that can be ignored
[00:35] <cjwatson> 'debuild -b -uc -us' if you want to bother suppressing that
[00:36] <cjwatson> the build output should show exactly how it invoked configure and make if you want to then do stuff by hand
[00:37] <hzsp> my next task is to figure out how to kill the default gnome-settings-daemon without it restarting itself :-P
[00:37] <cjwatson> can't help you there :)
[00:38] <hzsp> no, but google can ;)  anyway, thanks for your help!
[00:40] <apachelogger> do we have a page listing release critical bugs somewhere?
[00:47] <tumbleweed> apachelogger: not that I know of, we probably should
[00:48] <apachelogger> oh, actually I should clearify ... a page that particularly also tracks progress throughout the cycle ^^
[00:48] <apachelogger> I guess one can filter the interesting bugs via launchpad ui directly
[00:48] <tumbleweed> we have those kind of things for some core packages on qa.ubuntu.com
[00:49] <tumbleweed> http://iso.qa.ubuntu.com/qapkgstatus
[00:52] <apachelogger> tumbleweed: that doesn't seem to take milestoning into account, does it?
[00:53] <cjwatson> there's stuff like http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-mgr-p-tracking-bugs.html, on the occasions when it isn't broken
[00:55] <cjwatson> (to be fair it is more or less up to date at the moment)
[00:56] <tumbleweed> apachelogger: no
[00:56] <apachelogger> kk
[00:58] <apachelogger> cjwatson: hm, I am getting process confused now ... wasn't at one point the workflow to milestone bugs before release and only nominate after?
[01:06] <cjwatson> apachelogger: at least for some years the distinction has been that developers can milestone whatever they like to organise their own work, but if we want things to be release-critical then they have to be targeted as well
[01:07] <cjwatson> (the page above is actually only for bugs with a certain tag though - yay for more levels of abstraction, I guess)
[01:07] <broder> ubuntu-branches members - i've spotted 2 more in the sponsors queue that should be adjusted
[01:08] <broder> https://code.launchpad.net/~pali/ubuntu/oneiric/pulseaudio/pulseaudio/+merge/67286 should be work in progress - there's a newer MP that should be in the queue
[01:08] <broder> https://code.launchpad.net/~l3on/ubuntu/natty/gdevilspie/fix-for-783568/+merge/89717 should be merged - it's in UNAPPROVED
[01:08] <apachelogger> cjwatson: makes you wonder how one is supposed to explain all that to regular folks :P
[01:09] <cjwatson> aye
[01:12] <cjwatson> https://wiki.ubuntu.com/RCBugTargetting makes a valiant attempt but is (of course) out of date
[01:13] <cjwatson> that said I do actually look at traditional (non-rls-mgr-p-tracking-tagged) targeted+milestoned bug lists from time to time
[01:13] <cjwatson> so that page isn't all that bad a start
[01:14]  * cjwatson gets bored of walking down http://lintian.ubuntuwire.org/tags/preinst-uses-dpkg-maintscript-helper-without-predepends.html and goes to bed
[01:30] <lamont> interesting that dist-upgrade wants to remove ubuntu-desktop
[01:32] <stgraber> lamont: yep, that's caused by webkit
[01:32] <lamont> gwibber in this case
[01:32] <lamont> interestingly, do-release-upgrade -d from oneiric finished
[01:32] <stgraber> lamont: a bunch of important packages (apturl, software-center, gwibber, ...) all depend on some webkit stuff that in turn depends on the yet to be built arch all packages
[01:32] <lamont> I'm just wondering if it's safe to reboot
[01:33] <stgraber> if the only non-upgraded stuff is: gir1.2-javascriptcoregtk-3.0 gir1.2-webkit-3.0 gnome-control-center-data gwibber libjavascriptcoregtk-1.0-0 libjavascriptcoregtk-3.0-0 libwebkitgtk-1.0-0 libwebkitgtk-3.0-0
[01:33] <stgraber> then that's what I have on my laptop at the moment and it works fine
[01:33] <stgraber> (to start fullscreen terminals at least)
[01:34] <lamont> The following packages have been kept back:
[01:34] <lamont>   gir1.2-webkit-3.0 libwebkitgtk-1.0-0 libwebkitgtk-3.0-0
[02:16] <lamont> I guess it's time to file a bug about 3.2.0 hating my video card
[05:55] <micahg> jamespage: hi, just wanted to check with you if I missed anything, I would like to sync the latest javatools as it has bug fixes and is needed as a build dep for a new geogebra, seems sane and builds
[05:58] <ScottK> Isn't the motto JFDI?
[06:02] <micahg> yes, but I'd prefer not to break a bunch of java rdeps
[06:13] <broder>  anybody here use nomachine? i'm trying to figure out a fix for bug #682338 that's slightly less hideous than https://launchpadlibrarian.net/89032862/nx_cairo_1.10.2-6ubuntu3.patch
[06:13] <broder> in particular, i'm wondering what xdpyinfo on a nx connection looks like
[06:19] <truongan> hi all
[06:21] <truongan> i've used Ubuntu for 3 years. i want to become a developer. do you have any project for me?. my prefered language is C
[06:24] <ion> Pick any of them.
[06:52] <eQuiNoX__> hmm other than the highlighted CVE's here => https://wiki.ubuntu.com/MeetingLogs/Security/20120206 ; is there anyplace where all cve's that require traige/fixes are listed in the wiki?
[06:52] <eQuiNoX__> something ive missed? :/
[07:46] <jamespage> micahg, go for it
[07:46] <micahg> jamespage: thanks
[14:21] <ome> Where can I add/read the APT feature requests ?
[15:13] <jtaylor> doko__: numpy 1.6 merge proposal https://code.launchpad.net/~jtaylor/ubuntu/precise/python-numpy/merge-1.6/+merge/92671
[18:24] <stgraber> would be great if someone could BIN-new libindicate on i386, this would let gwibber build and allow for it to be upgradable on amd64
[18:27] <micahg> it would also let another handful or so of rdeps build
[19:29] <lifeless> RAOF: do you want any diagnostics - 2362 robertc   20   0  883m 374m  13m S    0  4.8   4:22.54 nm-applet
[19:29] <lifeless> RAOF: (yes, thats nearly 400M resident for 'you can has network GUI')
[22:06] <RAOF> lifeless: Are you sure you weren't after Sweetshark? :)
[22:07] <lifeless> RAOF: oh oh a pointer to chase? :)
[22:08] <RAOF> lifeless: Only for problems with his XI 2.2 backport :)
[22:08] <lifeless> RAOF: XI ?
[22:08] <RAOF> But I don't touch NetworkManager *at all*
[22:09] <lifeless> RAOF: yeah, but you are -desktop and -mytimezone ;)
[22:09] <RAOF> X Input; the upstream multitouch protocol.
[22:09] <RAOF> Heh.
[22:09] <RAOF> IIRC ubuntu-bug will pick up all the memory mappings nm-applet has; I guess the start might be filing a bug? :)
[22:10] <RAOF> Hurray heisenbug!  Attaching gdb prevents the crash.
[22:42] <lifeless> RAOF: bug 931167 :)
[23:57] <lamont> should libreoffice work tonight, I wonder?
[23:58] <ScottK> Heh.  I ask myself that every day, even post-release.
[23:58] <lamont> well, it seems to try to start and then *poof*: nothing