[00:04] <wgrant> shadeslayer, yofel_: I've noticed that a number of Project Neon builds (eg. kate, kdegames) are hanging early in the build lately. https://launchpad.net/~neon/+archive/ppa/+build/3741043 and https://launchpad.net/~neon/+archive/ppa/+build/3741663 are representative examples.
[00:05] <yofel_> odd, I'll look at it in a few minutes
[00:06] <wgrant> I've killed them each about 3 times this weekend, so it's not particularly intermittent.
[00:06] <wgrant> But also not something I've seen much before from neon...
[00:10] <yofel_> well yeah, that shouldn't be happening...
[00:11] <yofel_> ok, at least it hangs here locally as well so I have something to debug...
[00:12] <wgrant> Ah, great.
[00:12] <wgrant> I shall perma-kill the builds next time, then :)
[00:12] <wgrant> Thanks for investigating
[00:13] <yofel_> uh oh... found the issue. The python wrapper I added is recursively calling itself. NOT good
[00:13]  * yofel_ thought he fixed that
[00:13] <wgrant> Heh
[00:13] <yofel_> *sigh*
[00:13] <wgrant> Yeah, it's odd, since it just hangs
[00:13] <wgrant> It doesn't swapstorm or anything
[00:14] <yofel_> it should though, as it should be spawning bash and python processes all the time, except it kills them at some point and then just hangs
[00:59] <yofel> wgrant: sorry 'bout that, will be fixed once project-neon-runtime r240 is published
[01:26] <shadeslayer> new ktp : http://download.kde.org/unstable/kde-telepathy/0.5.0/src/
[01:28] <yofel> debfx: what's up with those kde 4.8.5 ~ppa1.1 packages in staging?
[02:06] <ScottK> shadeslayer: Did you fix up the dvd/armhf links after the images got restored?
[02:19] <shadeslayer> ScottK: yofel fixed the DVD links
[02:20] <shadeslayer> fixing armhf links right now
[02:30] <shadeslayer> ScottK: fixed
[02:37]  * shadeslayer looks at TODO
[02:38] <shadeslayer> ok so, quassel has a very serious bug wrt rendering url's
[02:39] <shadeslayer> apparently libpng12 is deprecated and svourela tells me I should take up png maintainence in debian
[02:40] <ScottK> yofel and shadeslayer: thanks.
[02:40] <shadeslayer> then there's a new ktp release as well
[02:41] <ScottK> shadeslayer: quassel's handling URLs just fine here.   What's this bug?
[02:41] <shadeslayer> ScottK: are you on quantal?
[02:41] <ScottK> shadeslayer: On precise.
[02:41] <shadeslayer> not sure if you can reproduce on precise
[02:42] <shadeslayer> but, hover over a URL, and quassel used to show the preview
[02:42] <shadeslayer> doesn't show it in quantal
[02:43] <shadeslayer> our libpng is apparently very old
[02:43] <ScottK> Doesn't in precise either.  IIRC it was dropped.
[02:43] <shadeslayer> the feature was dropped?
[02:43] <shadeslayer> Sput: ^
[02:44] <ScottK> If it's a bug, it's not recent.
[02:44] <ScottK> IIRC there was a preference for it and I don't see that either.
[02:45] <ScottK> Since it was rendered with qtwebkit, it's just as well.  Since that's got negligible security support, I think rendering random web pages with it is risky.
[02:49] <shadeslayer> understandable, maybe upstream dropped support for it
[02:49] <shadeslayer> let's wait for Sput to get back before doing anything
[03:04] <shadeslayer> claydoh: why is a 2010 post by you appearing on planet.ubuntu.com now? :P
[03:04] <claydoh> lol I edited a mising graphic, didn't change the date 
[03:06] <claydoh> shadeslayer: no, the date is good. I dunno
[03:06] <shadeslayer> probably because wordpress updates the RSS feed and p.u.c uses that
[03:07] <claydoh> can that be changed on wp?
[03:09] <shadeslayer> don't know
[03:11] <claydoh> google says nope more or less
[03:11] <claydoh> ill put it to private for a bit
[03:11] <shadeslayer> how will that help? :D
[03:12] <shadeslayer> I'm fairly certain that once you make it public it'll be there on p.u.c again
[03:12] <shadeslayer> just leave it :P
[03:14] <shadeslayer> yofel: do you remember where Quintasan_ put his update telepathy script ? :P
[03:15] <claydoh> there is a plugin tho, I just found, else I put the post private, edit, then make it public again.
[03:15] <shadeslayer> we worked on it together, and it was on a pastebin somewhere
[03:15] <shadeslayer> but now I've lost it
[03:24]  * shadeslayer tries to use muon to upgrade stuff
[03:25] <shadeslayer> JontheEchidna: is there a way I can hide this dialog box?
[03:25] <shadeslayer> the one that shows the packages being downloaded and what not
[03:25] <shadeslayer> would be nice to hide it to the system tray
[03:25] <JontheEchidna> minimize button :P
[03:26] <shadeslayer> I tend to accidentally click stuff in the task bar :P
[03:26] <shadeslayer> plus, it shows up in alt tab
[03:50] <shadeslayer> uhhh ... what just happened to muon 0.p
[03:50] <shadeslayer> 0.o
[03:51] <shadeslayer> I double clicked some text and I'm back to the main ui where you search
[03:53] <shadeslayer> hmm ... maybe the upgrade completed ....
[06:32] <shadeslayer> fwiw I'm working on KDE Telepathy packages
[06:33]  * shadeslayer checks build queue
[06:33] <shadeslayer> ah shit
[06:51] <micahg> shadeslayer: it's much better than it was on Friday
[06:52] <shadeslayer> well ... yeah
[06:52] <shadeslayer> but still ... 12 hours is pretty long
[06:54]  * shadeslayer is still tweaking his automated script for packaging ktp
[06:54] <shadeslayer> and for some reason, uupdate sets the release as UNRELEASED
[06:54] <micahg> shadeslayer: not for that many jobs with that many builders
[06:55] <shadeslayer> I don't follow
[06:55] <shadeslayer> 331 jobs (12 hours)
[06:55] <micahg> right, with only 12 builders, that's not so bad
[06:56] <shadeslayer> ah ok, yes, true that
[07:23] <shadeslayer> new ktp being uploaded to https://launchpad.net/~rohangarg/+archive/nightly
[07:23] <shadeslayer> I've scripted the packaging, so there *might* be a issue or two ....
[07:34] <shadeslayer> Currently 16 packages building and 3 packages waiting to build. < I think launchpad likes me
[07:34] <shadeslayer> though all of them will go into dep wait till common internals is built
[07:41] <Sput> shadeslayer: if you build quassel without enabling qt-webkit support, you won't get the option for the preview
[07:41] <Sput> not sure what's the default though
[07:41]  * shadeslayer checks build log
[07:42] <Sput> defaults to automagic
[07:42] <shadeslayer> Sput: it does pull in qtwebkit
[07:42] <shadeslayer> https://launchpadlibrarian.net/97643701/buildlog_ubuntu-precise-amd64.quassel_0.8.0-0ubuntu1_BUILDING.txt.gz
[07:42] <shadeslayer> bwahaha 
[07:42] <shadeslayer> dh_install: libktpcommoninternalsprivate1 missing files (usr/lib/libktpcommoninternalsprivate.so.0.4*), aborting
[07:42] <shadeslayer> stupid regex
[07:44] <Sput> -- QtWebKit not found, disabling WebKit support
[07:44] <shadeslayer> but it has QtWebkit installed on the buildd
[07:45] <shadeslayer> possibly doesn't pull -dev headers ...
[07:45] <shadeslayer> hmm .. looks like it
[07:45] <Sput> that could be it
[07:45] <Sput> it also disables KDE integration
[07:45] <Sput> not sure if that's intended for that package?
[07:46] <Sput> ah wait, no
[07:46] <shadeslayer> :P
[07:46] <shadeslayer> quassel is a weird package in ubuntu
[07:46] <Sput> there's more than one config runs
[07:46] <shadeslayer> yep
[07:46] <shadeslayer> one is for building it without qt support
[07:46] <shadeslayer> erm
[07:46] <shadeslayer> s/qt/kde
[07:48] <shadeslayer> Sput: should we enable the link previews since qtwebkit recieves no security updates
[07:49] <shadeslayer> that means someone could attack using quassel 
[07:49] <Sput> I have no idea about the state of qtwebkit
[07:49] <shadeslayer> like I just said, recieves no security updates
[07:49] <Sput> it's used by various projects, why should it be unmaintained?
[07:50] <shadeslayer> no idea really, the qtwebkit ML looks fairly active
[07:50] <shadeslayer> maybe they're just lazy in filling CVE's and what not
[07:50] <Sput> that's what I would expect, it is an active project at least
[07:50] <Sput> but I'm also not a distro maintainer and not involved in that security stuff, so... :)
[07:52] <shadeslayer> :)
[07:56] <kubotu> ::workspace-bugs:: [1041770] Weird artefacts on screen (white traces, white boxes around windows) @ https://bugs.launchpad.net/bugs/1041770 (by cagara)
[08:22] <debfx> yofel: that was a test rebuild to see which packages missed to install files
[08:42] <shadeslayer> Sput: you were right
[08:42] <shadeslayer> enabling webkit support made all the difference
[08:43] <shadeslayer> now we just have to convince ScottK to let us add the dep in the archvies :P
[08:43] <shadeslayer> *archives
[08:56] <kubotu> ::workspace-bugs:: [1004932] kdm.conf file not removed after dpkg-reconfigure @ https://bugs.launchpad.net/bugs/1004932 (by monochromec)
[08:56] <apachelogger> shadeslayer: did Scott remove the option?
[08:57] <shadeslayer> apachelogger: more like, somone removed the build dep 
[08:57] <apachelogger> well
[08:57] <apachelogger> not documented?
[08:57] <shadeslayer> and since webkit has security issues
[08:57] <shadeslayer> nope
[08:57] <apachelogger> well
[08:57] <shadeslayer> not that I can see in the changelog
[08:57] <apachelogger> to be perfectly honest....
[08:58] <apachelogger> qtwebkit is one insanely huge build dep for previews
[08:58] <apachelogger> IMHO that should be runtime loaded Sput
[08:58] <apachelogger> anywho
[08:58] <shadeslayer> which is already installed on Kubuntu systems
[08:58] <apachelogger> shadeslayer: the KDE build ought to depend on qtwebkit
[08:58] <shadeslayer> it does
[08:58] <apachelogger> BECAUSE kdelibs is built against it anyway
[08:58] <apachelogger> so
[08:58] <shadeslayer> it didn't pull in dev headers
[08:58] <apachelogger> perhaps there never was a build dep
[08:59] <apachelogger> but kdelibs-dev pulled it in
[08:59] <shadeslayer> ahh
[08:59] <apachelogger> and now it doesn't
[08:59] <shadeslayer> maybe
[08:59] <shadeslayer> quite the possibility, yes
[08:59] <apachelogger> which also makes sense since only 1% of stuff needing kdelibs links against kwebkit, so depping -dev on qtwebkit would be somewhat ecessive ^^
[09:00] <Sput> apachelogger: I *think* it only gets loaded if previews are enabled, at least one case save tons of RAM by disabling them
[09:00]  * apachelogger cannot spell today Oo
[09:00] <Sput> *can
[09:00] <Sput> (speaking about the runtime option now_
[09:00] <Sput> )
[09:00] <apachelogger> Sput: it's not RAM that concerns me but time-it-takes-to-install
[09:01] <Sput> apachelogger: I would mention USE flags, but... :)
[09:01] <apachelogger> Sput: knowing the build time of quassel that makes matters worse :P
[09:01] <Sput> obviously we can't build webkit support without depending on the headers
[09:01] <apachelogger> Sput: I am not talking about the headers but linking
[09:02] <Sput> mh, idunno. feel free to provide a patch that improves things
[09:02] <Sput> I don't know enough about that kind of stuff myseld
[09:02] <apachelogger> me neither :P
[09:03] <apachelogger> well, actually I do
[09:03] <apachelogger> actually it's terribly simple
[09:03] <apachelogger> simplest option is to QLibrary load the lib
[09:03] <apachelogger> then manually try to resolve symbols
[09:03] <apachelogger> (manually is not really manual resolution ;))
[12:53] <wgrant> yofel_: Thanks
[15:04] <bobweaver> Hello there I was wondering if there is a kubuntu developers kguide 
[15:04] <bobweaver> pun on the kguide :D ok bad joke 
[21:19] <kubotu> ::qt-bugs:: [1041945] "multiple errors leading to this one" @ https://bugs.launchpad.net/bugs/1041945 (by Christopher Horan)