[01:56] <xnox> Please reject https://code.launchpad.net/~cosmos-door/ubuntu/quantal/libproxy/fix-ftbfs-1057613/+merge/126724 as Laney already applied the same fix.
[02:45] <micahg> infinity: I've got a problem with webkit in precise now on arm*, it seems to be abort happy...do I need the gstabs fix there as well or is there some other thing I can do to get a complete build, these builds worked back in July...
[02:52] <infinity> micahg: *sigh*... It's not that webkit or the toolchain have changed, it's that we need to revert the abort timeout to what it was.
[02:52] <micahg> infinity: please? :)
[04:57] <mih1406> I have submitted my feature request for Ubuntu One, I believe it is a great addition to Ubuntu One's future!! https://bugs.launchpad.net/ubuntuone-client/+bug/1058900
[11:32] <geser> doko_: I see that you removed ldc and added it to the sync blacklist. Should the same happen to libtango too as it build-depends on ldc? (see also bug #935267)
[11:38] <cjwatson> doko_: I'd actually prefer that you didn't add such things to the sync-blacklist any more, please
[11:38] <cjwatson> doko_: Only use the sync-blacklist when we never want the package in Ubuntu again even after it's been fixed in Debian
[11:40] <cjwatson> doko_: The auto-sync is interactive nowadays when packages have been previously published in Ubuntu, so it shouldn't cause any accidents, and it's much easier to maintain things if you don't use the sync-blacklist for this kind of thing
[11:41] <cjwatson> (And in particular the auto-syncer will just ignore versions that were previously published and removed)
[11:43] <geser> cjwatson: Rhonda asked in #ubuntu-motu how go get a package never synced to Ubuntu. Is getting it on the sync-blacklist the right thing?
[11:45] <cjwatson> Yes
[11:45] <cjwatson> Subscribe ~ubuntu-archive to an appropriate bug
[11:45] <geser> not branch, patch, propose a merge?
[11:45] <cjwatson> Waste of time
[11:46] <cjwatson> I mean you can if you *really* want I suppose but it's pointless
[11:46] <cjwatson> And I suspect merge proposals won't work anyway because it's a +junk branch
[12:15] <jtaylor> why is python3.3 not in python-all?
[12:17] <cjwatson> jtaylor: Too late for 12.10
[12:17] <jtaylor> why have python3.3 then at all?
[12:18] <cjwatson> https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-python33
[12:18] <jtaylor> no extensions, apport going crazy about every traceback etc
[12:18] <xnox> jtaylor: such that it's possible to do a rebuild against it?
[12:18] <cjwatson> You can at least do basic experiments with it
[12:18]  * xnox after patching things up....
[12:19] <ogra_> and you can forward port for R while being on Q
[12:22] <jtaylor> it will confuse users
[12:24] <ogra_> how ?
[12:24] <jtaylor> e.g. bug 1059017 confused me until I figured out its not in -all
[12:25] <jtaylor> granted its not too bad, but some people might expect a fully functioning python3.3 when they install the package
[12:26] <jtaylor> and understanding these types of issues is not trivial
[12:27] <ogra_> not hard to switch off apport orjust ignore it though
[12:27] <ogra_> indeed its a bug but really not that fatal
[15:33] <kenalex> hello
[16:20] <IDWMaster> Hi
[16:20] <IDWMaster> I'm having a really annoying problem when I use GTK in a library
[16:20] <IDWMaster> I'm trying to write a utilities library that uses GTK+, and I've followed the instructions on the website for compiling with pkg-config, but whenever I call a GTK function the program just terminates.
[16:21] <IDWMaster> Does GTK also have to be linked with the program I'm embedding the library into?
[16:21] <IDWMaster> I thought that wasn't required for .so libraries.
[16:26] <tumbleweed> IDWMaster: yes, .so = shared library, you link to it, it isn't embedded
[16:27] <IDWMaster> I'm using dlopen to link to my library
[16:27] <IDWMaster> and then my library is linked to GTK+ using compile-time pkgconfig
[16:28] <IDWMaster> However; when I call a gtk+ function from my library; it crashes
[16:28] <tumbleweed> btw, this is faily off topic for this channel, which is about development of Ubuntu, not support
[16:28] <IDWMaster> Isn't this development-related?
[16:28] <tumbleweed> development *of* Ubuntu, not development on Ubuntu
[16:29] <IDWMaster> Where's the appropriate development on Ubuntu channel?
[16:30] <stgraber> IDWMaster: #ubuntu-app-devel according to this channel's topic
[20:52] <JHOSMAN> Hello for all!
[20:53] <JHOSMAN> I have Ubuntu Quantal problem but still do not know if you report it as bug.
[20:57] <JHOSMAN> =( hello
[20:59] <jtaylor> JHOSMAN: #ubuntu+1 is for quantal support
[20:59] <JHOSMAN> THanks! go to!
[21:51] <doko> cjwatson, will look at these tomorrow
[21:56] <trism> doko: if you get a chance could you retry the gecko-mediaplayer build on amd64,armhf, I think they just hit the archive at a bad time (firefox-dev was uninstallable)
[22:04] <jtaylor> trism: done on amd64
[22:05] <trism> jtaylor: thanks
[22:11] <jtaylor> looks like it worked, started armhf
[22:21] <trism> jtaylor: looks good on armhf too, excellent thanks much