[03:24] <Gaming4JC> Any chance of getting a fix for https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/821100 in natty?
[03:24] <Gaming4JC> package needs updated
[03:25] <Gaming4JC> not to mention BZFlag and Hedgewars should just be removed altogether if there's no plan in updating
[03:25] <Gaming4JC> neither of them work anymore, waste of FTP space :P
[03:25] <Gaming4JC> e.g. the versions were discontinued
[03:26] <RAOF> Gaming4JC: Does that actually *apply* to natty?
[03:26] <Gaming4JC> seems, to I am running natty right now and suffering the bug
[03:26] <Gaming4JC> the workaround works in #3 but it's ages slow
[03:27] <RAOF> Huh, apparently true.
[03:29] <Gaming4JC> yeah it seems affected for sure, version in my repo is showing 20090808ubuntu13
[03:29] <Gaming4JC> fix was released in the  -25 edition
[03:30] <RAOF> Well, ia32-libs is a bit of a bastard to update.  And, given there's no natty task on that bug, no-one currently plans on fixing it.
[03:31] <RAOF> ie: as far as we're aware, it's fix-released.
[03:31] <Gaming4JC> that's very unfortunate ... :P
[03:31] <Gaming4JC> natty is still supported, I'd like to see someone get assigned. It's a serious blocker to running wine among other things
[03:32] <RAOF> Well, I've added a natty task to the bug.
[03:32] <Gaming4JC> ty :)
[03:33] <RAOF> But ia32-libs is in universe; that's “supported if someone cares enough”.
[03:37] <Gaming4JC> I don't suppose there is any flattr for encouraging devs to care? :P
[05:07] <stokachu> hi, im building a python package which does not use distutils or anything and im trying to exclude certain files from being made executable, http://pastebin.com/C1wM3vX3
[05:08] <stokachu> unfortunately, lintian is complaining about the files in /usr/share/pyshared/sos/plugins/*.py as not being a elf but has executable permissions set
[05:09] <RAOF> How do the files get there?
[05:09] <stokachu> with dh_python2 im using pkg.pyinstall to make sure those files are linked
[05:09] <stokachu> but everything else is through the Makefile for installation
[05:10] <stokachu> and the current mode on those files do not have executable bit nor are they being changed in the Makefile
[06:34] <tumbleweed> stokachu: nothing should make them executable. Are you sure tehy aren't *already*?
[06:34] <tumbleweed> stokachu: you shouldn't be mentioning pyshared in your .pyinstall file
[07:55] <dholbach> good morning
[10:58] <AnAnt> Hello, isn't there a debhelper script for config.guess & config.sub ?
[11:00] <micahg> AnAnt: well, there's dh_autoreconf
[11:00] <AnAnt> micahg: thanks
[11:06] <Rhonda> AnAnt: practically it's just copy over config.guess and config.sub from /usr/share/misc (and Build-Depending on autotools-dev)
[11:06] <Rhonda> Don't forget to remove them in the clean target, though :)
[12:55] <al-maisan> hmm .. did some aspect of "dpkg-source --after-build" change in ubuntu 12.04? I have a package that builds flawlessly on the LP build farm (https://launchpad.net/~openquake/+archive/testing/+build/3260654) but fails in pbuilder on ubuntu 12.04: http://paste.ubuntu.com/869797/
[12:56] <al-maisan> here's the debian/rules file : http://paste.ubuntu.com/869798/
[12:58] <al-maisan> the problem appears to be that the 'override_dh_quilt_unpatch' target in debian/rules is ignored by "dpkg-source --after-build"
[13:04] <tumbleweed> al-maisan: that package is source format 3.0 (quilt) but you are using quilt manually in rules
[13:04] <tumbleweed> pick one or the other
[13:15] <al-maisan> tumbleweed: so what is the appropriate source format when using quilt manually?
[13:16] <tumbleweed> 1.0
[13:17] <al-maisan> tumbleweed: thanks, I am wondering why this mistake of mine was ignored so far..
[13:17] <al-maisan> is the policy being enforced more stricter since 12.04 ?
[13:18] <tumbleweed> al-maisan: no, dpkg just changed its handling of 3.0 (quilt) packages a little
[13:18] <al-maisan> aha, I see. Thank you for looking at this!!
[13:18] <tumbleweed> np
[13:41] <highvoltage> good morning
[13:41] <tumbleweed> hi
[15:33] <alucardni> hello, anybody knows what's the status of libappindicator in Debian?
[15:35] <Laney> alucardni: you should speak to the Debian Ayatana team<EMAIL_ADDRESS>[15:38] <highvoltage> last updated status on http://wiki.debian.org/Ayatana/Packages says that it FTBFS
[15:51] <Laney>  sbuild-build-depends-libappindicator-dummy : Depends: libdbusmenu-glib-dev (>= 0.5.90) but 0.5.0-2 is to be installed
[15:51] <Laney>                                               Depends: libdbusmenu-gtk-dev (>= 0.5.90) but it is not going to be installed
[15:51] <Laney>                                               Depends: libdbusmenu-gtk3-dev (>= 0.5.90) but it is not going to be installed
[16:49] <hrw> ok, time to start motu application
[17:41] <PaoloRotolo> Hi all!
[18:10] <cancer> I wanna contribute to ubuntu
[18:10] <cancer> for gsoc 2012
[18:10] <cancer> any help ??
[18:12] <roaksoax> cancer: ping dholbach, he'll be able to orient you
[18:14] <cancer> but i can't see him online
[18:14] <cancer> how can i ping dholbach
[18:14] <cancer> ?
[18:14] <roaksoax> cancer: he's probably gone for the day, you could try tomorrow morning
[18:14] <roaksoax> cancer: hav eyou seen the wikipage?
[18:15] <cancer> yeah ..
[18:15] <cancer> I am interested in Harvest and Algoritm School
[18:15] <roaksoax> cancer: you might wanna try the mentor too
[18:16] <cancer> I am a student
[18:16] <cancer> i think it would be better for me to first participate as student and then next year as mentor
[18:17] <roaksoax> cancer: I meant, you might wanna try contact the mentor too
[18:20] <valdur55> but... when i am secondary school sutent ... what i shall do ?
[18:20] <cancer> still u can take part
[18:21] <cancer> u should have craving for learning new things and helping opne source community
[21:16] <EvilResistance> whats the syntax for backportpackage's --upload= argument?
[21:16] <broder> anything that dput will accept
[21:16] <EvilResistance> that is to say, in what format should I put the PPA upload destination, ppa:trekcaptainusa-tw/<ppaname> or some other syntax?
[21:16] <EvilResistance> ah, i see
[21:16] <EvilResistance> then that should work
[21:16] <broder> but i think it might choke on anything that's not ppa:foo/bar
[21:17] <EvilResistance> indeed, its going to a PPA, so i dont think it'll whine :P


[16:19] <jrwren> https://blog.system76.com/post/632781631953027072/whats-new-in-popos-2010?utm_source=system76&utm_medium=email&utm_term=Pop!20.10&utm_content=20.10Announcement_Blog&utm_campaign=newsletter
[16:19] <jrwren> YAY!
[16:19] <jrwren> sorry for the tracker flags.
[16:22] <greg-g> s'ok, I know how to delete text ;)
[16:24] <greg-g> that window stacking for tiling is pretty neat
[16:34] <_stink_> oh wow that is awesome.  is that part of upstream GNOME or something special to pop os?
[16:34] <_stink_> i really miss my old tiler, but i just can't justify the setup time because i just fullscreen everything anyway.
[16:37] <greg-g> yeah, mostly the same about 80% of the time. But the other 20% would really benefit from tiling
[16:37] <greg-g> (eg terminals/file browsers/zimwiki/etc)
[17:21] <jrwren> it is popos
[17:21] <jrwren> they do their own WM.. or at least their own  default config
[17:22] <_stink_> cool thank you
[19:40] <jrwren> oh boy... they coming after youtube-dl
[19:42] <cmaloney> noooooooooooooooooooooooooooooooo
[19:43] <cmaloney> I'll unsub from all of the youtube if they do that
[19:43] <jrwren> yes, and of course /i/ don't have a clone of the repo.
[19:43] <jrwren> they already did.
[19:43] <jrwren> it is gone from GH.
[19:43] <jrwren> RIAA issued DMCA takedown
[19:43] <cmaloney> Fuck the RIAA
[19:43] <jrwren> ah: a mirror: https://git.furworks.de/opensourcemirror/youtube-dl
[19:43] <jrwren> YAYA
[19:44] <cmaloney> choosy folks use pip
[19:53] <_stink_> hah i just threw that into a venv like 3 days ago
[19:59] <jrwren> yes but... source?
[20:00] <_stink_> yes.
[20:03] <jrwren> yay!
[20:04] <_stink_> don't tell the RIAA :P
[20:05] <_stink_> oh and in case anyone is wondering, i did not know that it was going to get a takedown notice.  it was coincidence
[20:06] <_stink_> i've been fiddling with sight impared accessibility stuff on an rpi zero, with no X (and no orca).
[20:10] <cmaloney> no worries
[20:10] <cmaloney> we all know it's part of your music streaming service for the latest Kelly Clarkston releases.
[20:10] <cmaloney> no shame in that
[20:12] <_stink_> i just follow the money, what can i say


[01:46] <bluesabre> ochosi, flocculant: pushed a new xfce4-panel to https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xubuntu-staging and a new xfce4-power-manager to https://launchpad.net/~bluesabre/+archive/ubuntu/experimental (since the one in -staging is a higher version number)
[01:47] <bluesabre> xfce4-panel change: https://bugzilla.xfce.org/show_bug.cgi?id=9338
[01:47] <bluesabre> xfce4-power-manager change: http://git.xfce.org/xfce/xfce4-power-manager/commit/?id=6eaf8f868ed9ed8018385e16a92eaacef3c32a9d (ish)
[01:48] <bluesabre> that's probably all I've got for tonight, tomorrow I'll work on appstream
[01:48] <bluesabre> knome, slickymaster, flocculant: oh, and a new xubuntu-docs http://git.xfce.org/xfce/xfce4-power-manager/commit/?id=6eaf8f868ed9ed8018385e16a92eaacef3c32a9d
[01:49] <bluesabre> er
[01:49] <bluesabre> https://launchpad.net/ubuntu/+source/xubuntu-docs/16.04.1
[01:49] <bluesabre> :D
[02:06] <knome> hahah
[06:59] <flocculant> ochosi: I'll add xfpm - but not sure it's worth it if desktop
[07:06] <flocculant> mmm
[07:06] <flocculant> having trouble getting the one from /experimental
[08:19] <flocculant> knome: will we have the updated docs online soon? couldn't care about the user ones - but really would like cont ones there - will be including users in the final beta test call
[08:36] <ochosi> bluesabre: copied the package for wily so i can more easily test it ;)
[09:04] <akxwi-dave> flocculant, re the Language thing, re-did the install.. didn't pop up second time... i'll put it down to a blip, but will keep an eye out in case it happena again.
[10:21] <knome> flocculant, i'll take care of that today
[10:23] <knome> kryten, uh oh, you might have been right with the relative paths
[10:23] <kryten> lol
[10:23] <knome> but tell me
[10:23] <knome> why did the original stuff work for me then?
[10:24] <knome> err, not work
[10:24] <kryten> I take this as a rethoric question. :P
[10:24] <knome> i don't :X
[10:24] <knome> seriously, WOOT
[10:25] <kryten> :D
[10:25]  * knome cries a bit
[10:26]  * knome facepalms
[10:26] <knome> bluesabre....?
[10:26] <knome> :P
[10:27] <knome> anyway, making sure the updated contributor docs are up next
[10:36] <bluesabre> knome: ?
[10:37] <bluesabre> knome: https://www.youtube.com/watch?v=UmnN3eVMWgA
[10:40] <knome> bluesabre, can you do one more docs upload at some point
[10:40] <knome> no string changes, only "bugfixes"
[10:40] <bluesabre> knome: any time
[10:41] <knome> sure, i'll poke you after i've fixed a few more crappy things
[10:41] <bluesabre> k
[10:50] <knome> flocculant, new contributor docs are up
[11:41] <knome> bluesabre, ok, everything is prepared in the branch, including the changelog :)
[11:56] <bluesabre> knome: ok, I can quickly package and upload that if you're ready
[11:57] <knome> yes
[12:03] <bluesabre> knome: https://launchpad.net/ubuntu/+source/xubuntu-docs/16.04.2
[12:04] <bluesabre> be sure to change UNRELEASED to xenial in the branch
[12:04] <bluesabre> heading out, bbl
[12:07] <knome> i will, cheers!
[12:07] <flocculant> hi
[12:08] <flocculant> cya bluesabre
[12:08] <knome> hey flocculant
[12:08] <flocculant> thanks knome :)
[12:08] <flocculant> early break - sneaking 2 in today :p
[12:08] <knome> heh :)
[12:08] <knome> if there's anything fishy in the contributor docs, poke me
[12:08] <knome> they should be fine though
[12:09] <flocculant> ack
[12:09] <knome> lunch, bbl
[12:10] <flocculant> akxwi-dave: re 'users' call - not sure what you meant by size - if you mean content - pointing to http://docs.xubuntu.org/contributors/qa-tester.html should do enough to get them ready
[12:10] <flocculant> as soon as the images are ready I'll follow up with call to everywhere :)
[13:21] <flocculant> went well then ...
[13:21] <knome> kryten, please explain to me why it doesn't work now with the ../../
[13:22] <knome> thing is, the package builds with ../
[13:22] <knome> but not with make
[13:22] <knome> at least here...
[13:25] <knome> er, i eman
[13:25] <knome> why it doesn't work with "../" in the build
[13:26] <kryten> Hah, ok.
[13:26] <knome> it works locally with that
[13:26] <knome> but in the build, it seems to require ../../
[13:27] <knome> should we just introduce some symlinks?
[13:27] <kryten> Nah, that'd be hacky.
[13:28] <knome> i'll let you fix it then
[13:28] <knome> [:
[13:28] <kryten> :D
[13:28] <knome> i know it's hacky, but i don't have any other solution right now
[13:28] <kryten> Well, then just do it like that for now.
[13:28] <knome> sigh
[13:28] <knome> why not fix it right away?
[13:30] <kryten> I mean, in light that we're currently a bit under time pressure there.
[13:30] <knome> it's a bugfix, can land at any time
[13:30] <knome> and a FTBFS fix too
[13:31] <kryten> But we'd rather like to have the current docs included in the Final Beta image, no?
[13:32] <knome> sure, but would your evaluation be that it'd take longer than until monday to figure out the fix?
[13:32] <kryten> And right now I'd not even know where to start looking - plus, *you* are supposed to be the DocBook expert.
[13:33] <knome> this has nothing to do with docbook
[13:33] <knome> fop needs the font metric files to be able to build the PDF; they are simply referred to in the XSL file
[13:34] <knome> it's not a docbook-internal thing
[13:35] <kryten> Also, I'm kind of on the run right now. :P
[13:35] <kryten> But I'll have a look later then.
[13:35] <knome> thanks
[13:35] <knome> i can try to help debug it, if you need
[13:36] <knome> but i'm out of ideas right now
[13:36] <knome> because ../ works locally, not in the build
[13:36] <knome> the opposite with ../../
[13:36] <kryten> :D
[13:36] <knome> ...yeah
[13:36] <knome> the only easy way to fix that which i can think of is a symlink
[13:41] <kryten> Of course, since it worked before, it'd seem like that's a regression in fop.
[13:42] <knome> maybe
[13:42] <knome> maybe it had some path searching magic
[13:42] <knome> though that'd mean our docs were always flawed
[13:50] <kryten> 'fop -q -c ../libs-common/xubuntu-docbook-pdf-fonts.xml ...', and '<font metrics-url="../libs-common/fonts/fontmetric-notosans-regular.xml"' - so...
[13:51] <knome> but how is the build different than make?
[13:53] <kryten> Different environment variables.
[13:53] <knome> right.
[13:53] <knome> but which one would affect this?
[13:56] <knome> anyway, booting the desktop machine up to fix the last issues with the wallpaper contest site, then can look at this too
[15:35] <sidi> Xub packagers, please have a look at #xfce-dev. I suspect either you guys or Corsac made a mistake when packaging libxfce4util
[15:50] <sidi> so, interestingly. debian/patches/ubuntu.series is missed by quilt
[15:50] <sidi> resulting in local changes when attempting to build the package on my Xubuntu machine
[15:51] <sidi> porting the ubuntu.series content to series allowed me to make quilt push everything and to build the package
[17:39] <kryten> knome: There is a least bad hacky solution for that as well - add creation and removal of the needed symlinks to the 'pdf-create.sh' script - keeps it limited to the PDF creation.
[18:07] <flocculant> knome: looked at contest - sent you mail - now I thought it would be better to send to all - can if you want
[18:32] <flocculant> davmor2: following a very very tentative \o/ at the recent upgrade to apt and stuff which fixed one bit - I am now failing at udisks2 - should I report that? vaguely ... or should I just wait for someone more intimately involved - like someone called davmor2 who works for Canonical to say 'hey flocculant - could you see what goes on for you upgrading now?'
[18:33] <flocculant> would this perhaps be better in -release or something ?
[19:04] <davmor2> Hey dude so today I'm busy with silos for phone, However there is a jolly nice man call cyphermox who is starting to concentrate on the upgrade issues currently so you might want to ask him if he would like a fresh report or to keep working on it himself
[19:05] <flocculant> hi davmor2 :)
[19:06] <flocculant> he'll see the ping so I won't repeat it - he know's where I am :p
[19:06] <knome> kryten, i thought about that too..
[19:07] <knome> flocculant, yeah, sure, feel free to send to everybody :)
[19:07] <flocculant> knome: ack
[19:08] <flocculant> done - you'll get another - sorry
[19:08] <knome> np
[19:13] <knome> and replied back
[19:22] <flocculant> and replied
[19:22] <flocculant> ignoring ochosi's mail failures ... Mail quota exceeded.
[19:27] <Unit193> sidi: WFM.
[19:29] <davmor2> flocculant: man you are too easy I'd keep pinging cyphermox till he breaks down and replies ;)
[19:29] <knome> davmor2, it's a different strategy
[19:29] <knome> play like you're not interested in pinging and seeking for him
[19:30] <knome> when he lands one line to the channel, attack him like a hyena
[19:30] <davmor2> hahaha
[19:32] <pjotter> Hi everyone. A question: I have installed pulseaudio in debian 8.3 xfce. But for some reason, some settings that pavucontrol sets are not remembered. Since Xubuntu is kind of like Debian + xfce4 and also has a working paulsaudios sytem+pavucontrol, maybe someone here knows what is going wrong?
[19:33] <knome> pjotter, since my bank account is kind of like yours, maybe you can transfer some of the money to mine?
[19:33] <knome> ;)
[19:33] <flocculant> davmor2: see my plan is to THIS IS NO GOOD FOR UPGRADING FROM 14.04 all over our release stuff and let it hit the fridge next week :p
[19:34] <flocculant> *then* talk to cyphermox :)
[19:34] <pjotter> Hi knome. Sure I've got a negative fortune atm ;)
[19:35] <cyphermox> I'm trying to debug that crasher on upgrade
[19:35] <pjotter> But seriously why is pavucontrol working in Xubuntu but not when I install it on Debian?
[19:35] <cyphermox> it looks very much like it's "just" compiz that is way way way broken
[19:35] <cyphermox> so for now trying to just upgrade compiz, next I'll rip compiz out and upgrade without
[19:35] <flocculant> cyphermox: mmm - but should that affect us in here ?
[19:35] <knome> pjotter, no idea tbh...
[19:35] <cyphermox> flocculant: xubuntu probably still load compositing in many cases?
[19:36] <cyphermox> tbh, I don't know
[19:36] <flocculant> anyway - if you want something other than ubuntu to be tested feel free to ping me :)
[19:36] <pjotter> knome: Np... it's a long shot I know.
[19:36] <flocculant> cyphermox: yea but not compiz
[19:36] <knome> pjotter, maybe it doesn't have all required pulseaudio things
[19:36] <cyphermox> flocculant: if you want to spin up a 14.04.4 and use update-manager -d to upgrade to xenial, that's useful
[19:36] <cyphermox> it would be my next step
[19:36] <cyphermox> but then I also need to do this with servers too
[19:37] <knome> he doesn't want, trust
[19:37] <flocculant> cyphermox: well I update-manager -d -c as per the testcase earlier
[19:37] <knome> me
[19:37] <knome> but he will...
[19:37] <flocculant> cyphermox: and it hung
[19:37] <pjotter> Well, I installed all the pulseaudio things, I could think of. But just pulseaudio and pavucontrol should do the trick, I thought.
[19:37] <cyphermox> flocculant: hung how?
[19:37] <cyphermox> hung as in the whole desktop crashes?
[19:37] <flocculant> cyphermox: hang on - I grabbed a screenshot of where
[19:37] <flocculant> cyphermox: yea - dead as the proverbial
[19:38] <knome> hung like a young lamb at the butchers
[19:38] <pjotter> It's not that it doesn't completely. For the most part, it works. But It doesn't per-application soundcard settings.
[19:38] <cyphermox> well, graphics not changing is very different from the screen going all blank (when it's not stuck behind a screensaver, anyway)
[19:38] <flocculant> cyphermox: http://postimg.org/image/jff7qtz91/ - was in vbox jfyi
[19:39] <ali1234> did the mouse pointer still move?
[19:39] <flocculant> it had been on udisk2 for ~ 30 minutes or so
[19:39] <flocculant> ali1234: nope
[19:39] <ali1234> that's really bad then
[19:39] <flocculant> nor keyboard working
[19:39] <ali1234> mouse pointer is separate from compositing in xfwm
[19:39] <davmor2> cyphermox: I have a feeling it is deeper than just compiz I'm wondering if it is xstack disappears during upgrade and compiz just dies a million deaths
[19:39] <cyphermox> possible, I just haven't made it there yet
[19:40] <cyphermox> davmor2: I'll get to upgrade servers very soon
[19:40] <davmor2> flocculant: man that's cute you still use vbox ;)
[19:40] <flocculant> cyphermox: anyway - that's where I got to - happy to do whatever you want
[19:40] <cyphermox> davmor2: I'm thinking, upgrade a server with no X installed, see if that explodes (it probably doesn't), then upgrade a server on which X has been installed with a very minimal desktop, just enough to run update-manager, and see if that explodes
[19:40] <flocculant> davmor2: I got fed up with kvm root owning the images
[19:41] <cyphermox> if the second fails, it means it's X
[19:41] <flocculant> davmor2: generally I tend to ignore any fails I get with vb and iso's :p
[19:41] <cyphermox> if not, it means it's in some X libs that only do things in some cases (eg. compositing) or something above X
[19:41] <davmor2> cyphermox: sounds like a game plan
[19:41] <cyphermox> it's as scientific as I can think of right now ;)
[19:42] <flocculant> ha ha ha
[19:42] <cyphermox> menus are for restaurants, anyway
[19:42] <flocculant> mmmm
[19:42] <flocculant> food
[19:43] <davmor2> flocculant: yeah vbox died on me one time when I needed it so I switch to kvm + uefi + secureboot + hardware specifics + you get the idea :)
[19:43] <Unit193> cyphermox: Are you the ubiquity guy now, btw?
[19:43] <flocculant> Unit193: I think he has been for some time :)
[19:43] <flocculant> davmor2: I actually only use it to smoketest images and installation
[19:44] <flocculant> I upgrade to 'dev' just after release and run that for us
[19:44] <flocculant> I think I've managed 5 days of using a released version in the last few years
[19:44] <cyphermox> Unit193: yes
[19:47] <davmor2> flocculant: one nice thing for me is I have a cron job that pulls the images daily, and with kvm I can use gvfs to connect to the isos on the server and boot it from there save the hassle of transfers :)
[19:48] <Unit193> cyphermox: Not sure what, but keeps crashing near the end of the install process, not sure what's changed or why it doesn't happen on desktop images: https://bitbucket.org/snippets/unit193/ERyrq
[19:49] <cyphermox> wow cool
[19:49] <cyphermox> you got that for en?
[19:52] <Unit193> en_US in my case, yeah.
[20:13] <ochosi> flocculant: my mail quota is exceeded?
[20:13] <ochosi> you mean @ebt.at?
[20:13] <ochosi> (crap, i should really remove that email address from right about everywhere..)
[20:14] <flocculant> ochosi: yea was ebt
[20:14] <ochosi> :/
[20:14] <flocculant> blame knome ...
[20:14] <ochosi> use any other addr pls
[20:14] <flocculant> I didn't do anymore than reply all :)
[20:15] <flocculant> ochosi: did you get the Wallpaper Contest site testing, part 2 at all?
[20:15] <ochosi> nope
[20:15] <flocculant> I'll forward it then :)
[20:15] <ochosi> ty
[20:16] <flocculant> ochosi: xfce.org ok?
[20:17] <ochosi> sure
[20:17] <flocculant> ochosi: done - included replies so far ( from me ;) )
[20:18] <flocculant> davmor2: I'm generally only interested in *our* ones - so a zsync alias grabs them and removes the .old
[20:19] <flocculant> anything else I get when needed
[20:49] <knome> ochosi, that's the main email for your LP apparently,
[20:49] <knome> ochosi, it was the registered email on the contest site
[20:51] <ochosi> knome: k, not anymore
[20:51] <knome> ochosi, good :P
[20:52] <ochosi> why is the xubuntu bugs team subscribed to issues against "convertall"?
[20:52]  * knome shrugs
[20:52] <knome> maybe somebody tries to convert us to something
[20:52] <ochosi> seems like it
[20:55] <flocculant> maybe Jackson did it
[21:00] <flocculant> no need to be subscribed to abiword or gnumeric next year eventually too I guess
[21:01] <flocculant> ochosi: you likely to be about for friday's meeting?
[21:02] <ochosi> yup, let's drop abiword and gnumeric then
[21:02] <ochosi> flocculant: it's not very likely unfortunately cause we have friends (with baby) over for an evening together
[21:02] <flocculant> ochosi: okey doke - just checking :)
[21:03] <flocculant> would hate to #endmeeting just as you showed up
[21:03]  * knome thinks it would be teh funnee
[21:03] <flocculant> ochosi: I guess xubuntu bug admin has to unsubscribe us - that's you :p
[21:03] <flocculant> knome: lol
[21:04] <flocculant> given that Noskcaj has just responded to that convertall thing - I suspect he subscribed us when subscribing himself
[21:05] <knome> hah :)
[21:09] <ochosi> ok, removed us from convertall
[21:09] <ochosi> thanks for the hint flocculant ;)
[21:09] <ochosi> btw, if there's anything you wanna discuss ahead of tomorrows meeting lemme know
[21:09] <flocculant> :p
[21:10] <ochosi> shall i remove us from abiword and gnumeric too?
[21:10] <flocculant> don't think so
[21:10] <flocculant> bah
[21:10] <ochosi> i mean it's not like we're really going to fix anything there
[21:10] <flocculant> that was re meeting
[21:10] <flocculant> ochosi: no - but perhaps we should stay subscribed till we EOL trusty
[21:10] <ochosi> and 14.04 will soon be superseded (even if not EOL) by 16.04
[21:10] <flocculant> though that is another year I guess
[21:10] <ochosi> alrighty, i guess i can set up an email filter for myself ;)
[21:11] <knome> ochosi, you sure you don't need a secretary for that?
[21:11] <ochosi> knome: why, can you recommend a reliable and affordable one?
[21:11] <knome> yes to former, no to latter
[21:12] <flocculant> ochosi: actually about the meeting - only thing is perhaps your thoughts on core
[21:13] <flocculant> knome and others and I were discussing the other night - perhaps leaving to release on .1 rather than in a few weeks
[21:13] <ochosi> sorry to ask, but what's the status on that?
[21:13] <knome> no official ISOs yet
[21:14] <flocculant> ochosi: no change at the moment
[21:14] <flocculant> to the status of it
[21:14] <flocculant> uninstallable currently as it stands
[21:15] <flocculant> infinity was hoping to get it done before final beta
[21:15] <ochosi> ok, so the naming problem is resolved?
[21:15] <flocculant> yea
[21:15] <ochosi> plus, any other outstanding blockers?
[21:15] <ochosi> (other than not being installable yet)
[21:16] <ochosi> well taht's good to hear
[21:16] <flocculant> ochosi: not that we're aware of
[21:16] <ochosi> so it's only about infinity finding some time to merge..?
[21:16] <flocculant> ochosi: currently with my QA hat on - I am right on the edge now
[21:16] <ochosi> wbat
[21:16] <ochosi> what edge is that?
[21:17] <flocculant> the one seperating perhaps we can get this tested and in for April from there's no way I'm even trying now :)
[21:18] <flocculant> with the desktop stuff - unless something went terribly terribly wrong - I'd be happy to mark it with 1 test
[21:18] <ochosi> mhm
[21:18] <flocculant> not doing that with something this new
[21:19] <ochosi> yeah, but is it really that new? i mean apart from a shorter seed i don't see major differences
[21:19] <ochosi> Unit193: correct me if i'm wrong
[21:19] <flocculant> well
[21:19] <flocculant> I can install the desktop :p
[21:19] <flocculant> and it *does* get tested by more than just a couple of people
[21:20] <flocculant> I've said all along that if it got too close then I'd not be happy
[21:21] <ochosi> :)
[21:21] <flocculant> so don't be surprised that I'm not at week 21 of 26 :p
[21:22] <ochosi> sure sure
[21:22] <flocculant> :D
[21:40] <bluesabre> evening all
[21:41] <flocculant> evening bluesabre :)
[21:44] <knome> 'lo
[21:44] <bluesabre> 'ey 'ome
[21:45] <flocculant> oic
[21:46] <bluesabre> orly?
[21:46] <flocculant> :p
[21:50] <flocculant> night peeps
[22:15] <bluesabre> nighty flocculant
[22:30] <ochosi> night y'all


[08:26] <dholbach> good morning
[09:29] <seb128> hey
[10:04] <seb128> nigelb, hello
[10:04] <seb128> nigelb, is there an url or webpage listing all patches than need review?
[10:26] <dholbach> nigelb: proposed a merge for your tool
[11:51] <vish> seb128: https://bugs.launchpad.net/~ubuntu-reviewers/+subscribedbugs , is a list of sort
[11:53] <seb128> vish, it lists bugs which have been reviewed already though and are tagged waiting on upstream or such
[11:53] <seb128> not very efficient to have a list of things still waiting ;-)
[11:53] <vish> seb128: yeah , it is still a bit confusing workflow :)
[11:53] <seb128> vish, hey btw, how are you?
[11:54] <vish> seb128: good , and you?
[11:54] <seb128> I'm good thanks
[15:18] <james_w> nigelb: http://paste.ubuntu.com/440420/
[16:06] <nigelb> seb128: poke
[16:08] <nigelb> vish: that's not the place to look for bugs to review
[16:09] <nigelb> seb128: https://wiki.ubuntu.com/ReviewersTeam/ReviewGuide#Workflow
[16:09] <nigelb> that query is for new bugs with patches.  I'm still working on getting a list of old bugs, not very sucessful though
[16:09] <nigelb> dholbach: taking a look now :)
[16:10] <nigelb> james_w: thanks :)
[16:12] <nigelb> dholbach: can you modify the description of https://launchpad.net/~ubuntu-reviewers to say "To help review patches, please see https://wiki.ubuntu.com/ReviewersTeam/ReviewGuide#Workflow" ?
[16:13] <dholbach> nigelb: done
[16:13] <nigelb> dholbach: whoa, you're fast :)
[16:15] <nigelb> vish: and um, how is the workflow confusing?  I corrected the wiki long back.
[16:17] <seb128> nigelb, hello
[16:18] <seb128> nigelb, I've been reading this wikipage
[16:18] <seb128> nigelb, the quey lists some 250 patches though
[16:18] <seb128> I though there were 2000 to review
[16:19] <nigelb> seb128: there are 2 lists now, the list of new patches to review and the whole list including the backlog
[16:19] <nigelb> that list isn't complete, I'm having some problem in the script, should be ready by monday
[16:19] <seb128> ok thanks
[16:19] <nigelb> I do have a whole lot clarification to do.  Just I got a little busy with real life :)
[16:54] <nigelb> persia: around
[16:54] <nigelb> I'll be running that script again today to see how it goes :)
[17:16] <vish> nigelb: well , the list of subscribed bugs always increases since we dont subscribe the bugs even after the task is completed , i dont see why we do that
[17:16] <vish> dont unsubscribe*
[17:17] <nigelb> vish: Why should we.  I'd like to know how many bugs were processed through us
[17:17] <nigelb> once you review something it wont come into reivew queue anyway
[17:17] <vish> seemed there was a discussion on that and not sure what the reason was
[17:17] <nigelb> There was a *big* discussion.  It was actually like meh either ways.
[17:18] <nigelb> For statistical reasons, I prefered not unsubscribing.
[17:19] <nigelb> review queue is different from sponsors or other work lists, they have only 2 status "to be done" and "done" while we have a bunch of buckets
[17:22] <vish> nigelb:  hmm , stats for ?
[17:23] <nigelb> vish: stats for what we've done, so far, etc.
[17:23]  * nigelb doesn't remember everything.
[17:23]  * vish  adds more GB to nigelb's brain ;p
[17:24] <nigelb> try playing with php,apache,solr,drupal for 9 hours - its fun
[17:24] <nigelb> I totally can't think of code
[17:27] <vish> nigelb: we could add the query link for new patches :  http://tinyurl.com/3a7lqqr  to the topic ?
[17:27]  * vish adds..
[17:28]  * nigelb cheers


[08:54] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4373 Failed to build
[16:13] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4374 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[16:16] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4336 Proposed pocket (groovy/adcli). Ready to build (groovy/cyrus-sasl2, groovy/sssd)
[16:34] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4374 Pending binary packages (bionic/adcli). Uploading build (bionic/cyrus-sasl2)
[16:54] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4374 Pending binary packages
[18:35] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4374 Diff missing
[21:01] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3840 Failed to build
[21:58] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3840 Generating diffs
[22:46] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3801 Generating diffs
[22:47] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3801 Successfully built
[22:53] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4373 Diff missing
[23:01] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3801 Pending binary packages
[23:14] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4373 Pending binary packages
[23:21] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3840 Successfully built
[23:22] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3801 Successfully built
[23:34] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/4373 Diff missing
[23:41] -queuebot:#ubuntu-ci-eng- rbalint, https://bileto.ubuntu.com/#/ticket/3840 Pending binary packages
[23:55] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4374 Proposed pocket (bionic/cyrus-sasl2). UNAPPROVED queue (bionic/adcli)


[13:35] <topi`> hi, I've got strange behaviour on my .conf scripts, (some of) them will not start at startup even though I've double checked that everything should work. And they also work via manual invocation "initctl start foo"
[13:35] <topi`> system is ubuntu trusty
[13:35] <topi`> I googled and found some ppl asking the same question, but none of those answers seem to help me
[13:35] <topi`> -rw-r--r-- 1 root root 243 Jan 14 13:41 /etc/init/n2n.conf
[13:36] <topi`> I guess the permissions are just fine.
[13:39] <topi`> I wish "initctl" would give me more diagnostics info about *why* a unit did not start even though it has exactly the same "start on ..." stanza as another unit which starts just fine
[13:40] <topi`> init-checkconf says "syntax ok"
[13:41] <topi`> upstart version is 1.12.1-0ubuntu4
[23:38] <supergonkas> Hey anyone around?


[02:53] <UberMusik> hi, so, i "thought" i just successfully created a dual boot winxp/ubuntuStudio configuration on two separate IDE drives, but things haven't gone as well as planned .. i installed xp first on my master 80 gig HD, then i used the latest Ubuntu build DVD to install 12.04 on my 500gig HD .. on the first reboot, i got the menu to select an OS (ubuntu or winxp) .. and i started ubuntu . .then i rebooted and started xp .. all good so far .. now, all my reboot
[02:55] <sambagirl> super music
[03:02] <ailo> UberMusik: A part of your message was missing
[03:03] <ailo> sambagirl: How's your selection of desktop system coming along?
[03:03] <UberMusik> ailo: oh .. thanks .. i'm using adium, which i guess let's me type past the irc character limit . .what were the last 2 words?
[03:03] <ailo> UberMusik: ".. now, all my reboot"
[03:04] <UberMusik> now, all my reboots go direct to XP with no menu to choose an OS .. strange, no? any ideas on what i missed?
[03:04] <UberMusik> once i booted XP for the first time, that's all it sees .. even though i did get the OS menu the first time after installing ubuntu ..
[03:04] <UberMusik> (i chose the "install beside windows" option )
[03:05] <ailo> UberMusik: Did you install grub?
[03:05] <UberMusik> no .. is that a linux util or windows?
[03:05] <ailo> I've never tried "install beside windows", so I don't know how that works
[03:05] <ailo> UberMusik: Grub is the default bootloader for Ubuntu
[03:06] <UberMusik> i thought it was supposed to "just work" (™)
[03:06] <ailo> UberMusik: The boot menu. Did it look Windows, or Linux to you
[03:06] <ailo> If it's Grub, you can press shift while booting, to see the menu
[03:06] <UberMusik> linux .. white text on black background .. i've definitely seen it as a linux boot menu before
[03:06] <ailo> But, Windows should not be default
[03:07] <UberMusik> again, this is two separate IDE drives .. not two partitions on the same drive ..
[03:07] <ailo> UberMusik: May be that you installed boot loaders on both disks
[03:07] <UberMusik> windows is on the master
[03:07] <ailo> UberMusik: Set your bios to boot from the Linux disk.
[03:08] <UberMusik> ailo: my bios isn't seeing my second drive .. that must be the issue .. hmm .. maybe a jumper setting?  how should i have jumpers set for this scenario? i have no jumper on the master, and the secondary IDE drive has a Slave jumper ...
[03:09] <ailo> UberMusik: Set the second to cable select
[03:09] <UberMusik> ailo: hmm .. i think i tried that, and it just got suck on the Dell splash screen
[03:10] <ailo> With cable select it will work it out on its own
[03:10] <UberMusik> i should mention this is a very old machine ..
[03:10] <UberMusik> no jumper on the master?
[03:10] <ailo> UberMusik: If the disk is damaged, bios might get stuck, trying to id the disk
[03:11] <ailo> UberMusik: try one disk at the time, to make sure both work
[03:11] <ailo> Though, I guess they should, since you already installed on both
[03:11] <ailo> But, could be it's unpredictable between boots
[03:11] <UberMusik> ailo: ah .. that's also a possibility .. i have a spare .. so i'll try that … it's just strange that i have been able to boot into both OSs .. but, yes, it's possible one of them is failing ..   ok .. thanks
[03:12] <ailo> UberMusik: You can set both to cable select
[03:12] <ailo> np
[22:30] <heribertorodrigu> hi, does someone can help me to solve the installation of blender 2.64 pls?
[22:31] <heribertorodrigu> am trying to install the package via tarball
[22:32] <heribertorodrigu> I installed the repositories too but it doesn't run the program
[22:42] <heribertorodrigu> well tnx


[20:06] <laek> hey all (o: I've been using pdf2svg converter on Mint, because it outlines fonts and a few other things inkscape doesn't do.. I'm playing with Ubuntu Studio, and pdf2svg isn't in the repo.. When I try to compile it calls for Cairo. Any suggestions?
[20:08] <krytarik> !info pdf2svg
[20:09] <laek> does that mean it -is- in the repository?
[20:09] <krytarik> Yup.
[20:09] <krytarik> Just make sure the 'universe' repo is enabled.
[20:09] <laek> doesn't show up when I search Gnome Software )o:
[20:09] <laek> ahh
[20:10] <laek> thanks for the tip (o:
[20:10] <krytarik> Sure.
[20:14] <laek> krytarik, in Software & Updates | Ubuntu Software? looks like it was checked by default..
[20:16] <krytarik> Just "sudo apt install pdf2svg" then?
[20:17] <laek> aha! back in business (o:
[20:18] <laek> thanks again~
[21:36]  * OvenWerks hates gnome software...


[17:59] <b-man> hi
[18:01] <b-man> i need some help with ltsp-usb
[18:03] <sbalneav> What are you having problems with?
[18:04] <b-man> i didn"t work, so i tried the DebugLocalDev-tutorial
[18:05] <b-man> on step 4 "ssh -X -S /var/run/ldm_socket_vt7_<IP_ADDRESS> <IP_ADDRESS> "/usr/sbin/ltspfsmounter /tmp add" i get authentication failes
[18:05] <b-man> -s+d
[18:05] <b-man> i tried google but found no proper solution
[18:05] <b-man> i set it up on a test-server before and everything worked finde
[18:05] <b-man> fine
[18:06] <b-man> i've no idea why it won't work on the other server
[18:08] <sbalneav> What versiopn of edubuntu are you using?
[18:09] <b-man> i'm using debian :)
[18:09] <b-man> lenny
[18:11] <sbalneav> Well, this really isn't the right channel for that, vagrantc's the fellow you need in #ltsp
[18:11] <sbalneav> he's done the debian port.
[18:11] <b-man> k, thx
[18:11] <b-man> bye


[12:05] <DoeNietWil> Hello Ubuntu user, I came to this irc to ask you a question. We are trying to release a new version of OpenTeacher, and because it is a tool that is very language specific I was wondering if any of you would like to take a couple of minutes and translate it. It really isn't that much work but it would help us a lot. https://translations.launchpad.net/openteacher
[13:17] <DoeNietWil> if you have questions about the project or the translation please go to http://webchat.freenode.net/?channels=openteacher
[13:38] <czajkowski> DoeNietWil: possibly better off using the mailing list to be honest for this kind of thing
[13:38] <DoeNietWil> i'm not the leader of the project, but i will tell them
[13:41] <czajkowski> otherwise it's kinda like spamming irc channels to be honest
[13:43] <DoeNietWil> well, it's not my intention to do that, sorry


[00:00] <neversfelde> apachelogger: no mail yet about the complaint?
[00:04] <apachelogger> neversfelde: no, still waiting if someone else got additional input
[00:04] <apachelogger> but I should eventually push it out by next week
[00:04] <neversfelde> apachelogger: forgot to metion the many bugs about sound, seems to be a jaunty problem
[00:04] <neversfelde> probably not a kubuntu one
[00:04] <apachelogger> well, it happens when pulseaudio gets pulled in
[00:04] <apachelogger> and as I noticed that can happen in the most weird cases
[00:05] <apachelogger> like when you install a make liked build tool for java :P
[00:05] <neversfelde> yes, but purging it is not the solution everytime
[00:05] <apachelogger> bug 370520
[00:05] <apachelogger> well, then it's probably an issue in alsa
[00:05] <apachelogger> neversfelde: ^
[00:06] <neversfelde> apachelogger: didn't you wirte a mail to me about the complaint?
[00:06] <apachelogger> neversfelde: most of the work is really just getting the fixed deployed (i.e. check with debian and prepare SRU) rather than get it done :)
[00:06] <apachelogger> neversfelde: oh... well, yes
[00:06] <neversfelde> will have a look at it
[00:06] <neversfelde> not arrived
[00:06] <apachelogger> neversfelde  ... googlemail .... com
[00:06] <apachelogger> isn't it?
[00:07] <neversfelde> nope, I left google :)
[00:07] <apachelogger> well, it's a google doc...
[00:07] <apachelogger> neversfelde: about the bug: if you don't think that you have time please drop it on the devel list and find someone else to do it
[00:07] <neversfelde> mhh, probably I shoul register again
[00:08] <neversfelde> apachelogger: will do
[00:08] <apachelogger> groupwise is, as I understand, not too unfamous within corporate environments, so having it broken is kinda awful
[00:08] <apachelogger> neversfelde: http://docs.google.com/Doc?id=ajk6csn6c2vn_0c6d8rp6w
[00:10] <neversfelde> apachelogger: bookmarked and will hava a look at it tomorrow evening
[00:10] <apachelogger> okies, thx
[00:11] <apachelogger> Riddell: could you please send mail about meeting schedule + update topic + update wiki + get nixternal to fridge it?
[00:11] <apachelogger> obviously I already forgot what day and time it was :D
[00:14] <neversfelde> ah, there is a thunderstorm on my wallpaper
[00:15]  * neversfelde blames JontheEchidna :)
[00:15]  * apachelogger notes that there was a thunderstorm in his windows a few hours ago
[00:15] <apachelogger> clearly I must blame the weather though
[00:16] <neversfelde> hehe
[00:17] <neversfelde> blame the weather or blame the weatherman, never mid
[01:02] <Riddell> hmm, I'm sure I put it in the topic
[01:03] <neversfelde> mhh
[01:03] <neversfelde> Riddell: what? :)
[01:17] <ryanakca> UTC?
[01:22] <Riddell> it's the only time zone worth considering
[01:23] <Riddell> nixternal: please add to fridge ^^
[01:28] <neversfelde> Would a MOTU have a look at bug 370009
[01:28] <neversfelde> or is it to early in release cycle?
[01:31] <neversfelde> choqok 0.5 is imo worth a backport so it would be good if it passes the line to karmic
[01:35] <shtylman> Riddell: this Wednesday? 18:00 utc? ... I assume in this channel...?
[01:40] <neversfelde> shtylman: meetings normaly take place in #ubuntu-meeting
[01:41] <shtylman> neversfelde: thanks
[01:49]  * Tonio_ packages kaffeine, konversation and latest alpha k3b
[01:49] <Tonio_> kaffeine is impressive, really
[01:49] <Tonio_> can't wait to see it back as the default kubuntu video player
[01:51] <neversfelde> Tonio_: +1
[01:51] <neversfelde> it is a nice app
[01:52] <Tonio_> yup
[01:52] <Tonio_> neversfelde: fancy testing the deb file ?
[01:52] <Tonio_> neversfelde: ppas currently don't build anything :/
[01:53] <Tonio_> ho and also partition manager now has a kcm module, which is pretty cool
[01:53] <neversfelde> Tonio_: I tested a svn snap some days ago
[01:53] <Tonio_> neversfelde: right ;)
[01:53] <neversfelde> I think it was from your ppa
[01:53] <Tonio_> also can't wait for konversation
[01:53]  * neversfelde is a quassel fan :)
[01:53] <Tonio_> I like quassel, but for some reasons it suffers lots of performances issues on my laptop :/
[01:54] <neversfelde> mhh, no problems here
[01:54] <Tonio_> neversfelde: using compositing ?
[01:54] <neversfelde> yes
[01:55] <Tonio_> neversfelde: performances are nice, but it's going very slow when kde compositing is enabled here
[01:55] <neversfelde> NVIDIA Cards all around here, and no probs
[01:56] <Tonio_> ati with the opensource drivers here :)
[01:56] <Tonio_> which also means, at least 2 X.org segfaults a day :/
[01:56] <neversfelde> hehe, that might be the problem
[01:56] <Tonio_> I really hope X.org will stabilize in the next month
[01:56] <neversfelde> we have several reports for ATI in kubunut-de.org forum
[01:57] <Tonio_> I can confirm there is :)
[01:57] <neversfelde> :)
[01:58] <Tonio_> hum, looks like konversation won't let me speak :)
[02:02] <neversfelde> I think I should go to bed, but several tasks left :(
[02:02] <ScottK> Tonio__: Bug or feature?
[02:04] <Tonio_> neversfelde: wasn 't I talking about xorg crashes ? there we go :)
[02:05] <neversfelde> Tonio_: yes, there are a lot of reports like this
[02:05] <neversfelde> gnah :(
[02:08] <Tonio_> wow.... konversation + ati + compositing -> crash
[02:08]  * Tonio_ loves opensources drivers
[02:08] <Tonio_> I remember when the xorg team was complaining...
[02:08] <Tonio_> "want good opensource drivers, please Mr ati and nvidia, release the specs and we'll do them"
[02:08] <Tonio_> what a joke.....
[08:36] <Quintasan> Hiho
[08:37]  * Quintasan is back from trip
[08:38] <bittin> :o
[09:56] <eagles0513875> can someone take a look at the upstream bug of bug 301698 the problem could not be reproduced with qt 4.5.0 r961909
[10:00] <apachelogger> eagles0513875: see ... what do you want to know in this case?
[10:00] <eagles0513875> for instance since it probably needs testing who to assing it to
[10:01] <apachelogger> yourself?
[10:02] <eagles0513875> how woudl i go about testing this bug though
[10:02] <apachelogger> this case is extremly difficult because upstream did not even request data, but just noted that it seems unreproducible in trunk
[10:03] <eagles0513875> gotcha thing is i have never gotten an error like that when posting to launchpad
[10:03] <apachelogger> eagles0513875: apply all patches from qt-copy (in kde svn) to our qt package and rebuild the package, then try if the bug still appears
[10:03]  * eagles0513875 needs to figure out packaging and pbuilder
[10:03] <apachelogger> well
[10:04] <apachelogger> another option is to check the patch names to try find those which might have fixed this issue
[10:04] <apachelogger> or read through the patches themselfs
[10:04] <eagles0513875> ok
[10:04] <apachelogger> as said, difficult to do anything on that bug
[10:05] <eagles0513875> should i ask jon bout how to proceed i know its not nice to lump it on someone else but for right now i think its above me level
[10:05] <apachelogger> you can
[10:05]  * apachelogger wants to note that his trunk build still exposes that bug though
[10:06] <eagles0513875> ahhhh ok
[10:06] <apachelogger> that build is > 1 week old, but I doubt the issue was fixed in the meantime
[10:06] <eagles0513875> i feel bad lumping this on him im still a novice i admit as well that i dont have much time to bug fix i can report bugs upstream but that is about it for now till after 19th of may
[10:08] <eagles0513875> another question not realted to this bug but devel in general im packaging an updated snapshot of kvirc 4.0 would it make it into the kubuntu-experimental ppa or stay just in my personal ppa
[10:12] <apachelogger> technically it should go into karmic and then jaunty-backport
[10:12] <apachelogger> s
[10:13] <eagles0513875> so anythign that gets updated goes into the next release then pushed back to the previous release
[10:13] <apachelogger> well, the backport only happens if the package qualifies for backport
[10:14] <eagles0513875> what would make something get pushed to jaunty as an update
[10:14] <apachelogger> like a KDE beta will probably not qualify for backport as it actually degrades what is in jaunty by default
[10:14] <eagles0513875> for instance an updated kvirc snapshot wouldnt that not hurt anything its just an upgrade to latest version of kvirc which is in jaunty
[10:15] <apachelogger> eagles0513875: well, update != update ... there are stable release updates (minor changes with considerable great impact ... e.g. fixing a crash) ... there are security updates.... and there are backports (which are mostly new versions)
[10:15] <apachelogger> like amarok 2.1.0 will qualify for backports, but not for SRU nor security
[10:15] <eagles0513875> ahhhhh ok that clears up alot of stuff
[10:16] <eagles0513875> backports repos is like the bleeding edge stuff
[10:16] <apachelogger> well, kinda
[10:16] <eagles0513875> would pbuilder work for installing it on the local machine then building the package
[10:17] <apachelogger> eagles0513875: svn snapshot is a different story though, an svn snapshot only would qualify when jaunty included a svn snaphot and when there is no stable release available
[10:17] <eagles0513875> thing is i dunno what was done for jaunty in regards to kvirc 4.0
[10:17] <apachelogger> or when the new snapshot provides considerable improvements over the stable release
[10:17] <apachelogger> eagles0513875: what would you need to know?
[10:18] <eagles0513875> was kvirc for jaunty built from svn
[10:19] <apachelogger> take a look at the version number in jaunty
[10:19] <apachelogger> also, there was no kvirc 4 release yet, so...
[10:20] <eagles0513875> gotcha
[10:20] <eagles0513875> and that is a way outdated version in the repos
[10:20] <eagles0513875> its 3039 and they are on 3190
[10:21] <eagles0513875> another question what would cause an svn version of a program to make a release like kvirc for instance
[10:22] <apachelogger> can't follow
[10:22] <eagles0513875> what cause kvirc which is still in svn what got it to be allowed into jaunty
[10:23] <apachelogger> a horribly broken KDE 3 version I suppose
[10:24] <apachelogger> you should ask the uploader though
[10:24] <eagles0513875> ok
[10:24] <ikonia> it's just common sense surly ?
[10:24] <ikonia> the best available package is taken
[10:25] <eagles0513875> even if its missing alot of features
[10:25] <eagles0513875> for instance themed backgrounds dont work in the version in the repo
[10:25] <ikonia> if it's the best available - it doesn't matter what's in t
[10:25] <ikonia> eagles0513875: does it work on any other versions ?
[10:25] <eagles0513875> on the 3.4.2 it does
[10:26] <eagles0513875> which is stable
[10:26] <ikonia> what is the version in the repo ?
[10:26] <eagles0513875> svn 3039 and they are on svn 3190
[10:27] <ikonia> eagles0513875: has the feature your talking about been removed or is it a bug
[10:27] <ikonia> it's unusual for a feature to be removed in later versions
[10:28] <eagles0513875> i think it hasnt been implemented in the version that is currently in the repo
[10:28] <eagles0513875> i havent installed the latest snapshot
[10:28] <ikonia> is the svn repo a new branch or just an update to the existing?
[10:28] <eagles0513875> i dont understand what you mean
[10:29] <eagles0513875> i got the code from the svn of kvirc
[10:29] <ikonia> is the branch your talking about in the svn repo a brand new branch, or is it building on the existing code base ?
[10:29] <eagles0513875> building on the existing code i think not sure
[10:30] <ikonia> so how can it not have been implmented if it's on the same branch ?
[10:30] <eagles0513875> i see where you are coming from so then its most likely a bug
[10:30] <ikonia> I don't know as I don't use it,
[10:31] <eagles0513875> ill have to compile the latest svn code and see if the issue still exists
[10:32] <ikonia> how are you compiling it, are you using the same options as the existing deb package ?
[10:32] <eagles0513875> i dunno how it was compiled
[10:32] <ikonia> or are you just typing make && make install ?
[10:32] <eagles0513875> no it seems to use cmake so ill be using cmake
[10:32] <eagles0513875> i tried with make and make install but there is no make file to go with
[10:33] <ikonia> ok - but you need to make sure you use the same options as the existing deb package or it's a pointless test that will give miss-leading results
[10:33] <eagles0513875> how can i determine what was used
[10:33] <ikonia> strip the deb
[10:33] <eagles0513875> ok
[10:33] <apachelogger> eagles0513875: see how cmake got invoked in the build log :P
[10:34] <eagles0513875> apachelogger: after stripping it
[10:34] <apachelogger> ikonia: the svn version doesn't have said feature because it gets rewriten for KDE 4
[10:34] <apachelogger> which usually comes down to gets rewrittencompletely
[10:34] <ikonia> apachelogger: which is why I was asking if it was a difference branch or not
[10:34] <eagles0513875> i didnt know :(
[10:35] <eagles0513875> to be honest it looks the same as 3.4.2
[10:35] <ikonia> looks has nothing to do with it
[10:35] <apachelogger> ikonia: amarok 2 is not a different branch and yet has barely any relation to amarok 1's code ;-)
[10:35] <ikonia> hence why I was asking about the code base
[10:35] <eagles0513875> gotcha
[10:35] <ikonia> apachelogger: may not be a different branch in the repo - but it's a fresh branch of code
[10:35] <ikonia> although I don't know amarok at all really
[10:35] <apachelogger> nope
[10:35] <apachelogger> got based upon amarok 1
[10:36] <ikonia> how can it be based on amarok 1 yet be a re-write ?
[10:36] <eagles0513875> hahah just found the cmaake flags
[10:36] <eagles0513875> dont have to strip the deb its under the about kvirc
[10:36] <apachelogger> ikonia: that is what happens when you port, refactor and enhance at the same time :D
[10:37] <ikonia> ok - so it is a seperate branch - it's a new base
[10:37] <apachelogger> it became a new base
[10:37] <apachelogger> however, how would you tell it is
[10:37] <apachelogger> features can also get lost because of the porting alone
[10:37] <ikonia> thats a good point if it's not noted
[10:37] <apachelogger> when there is a non-trivial problem preventing the feature's portation for example
[10:38] <eagles0513875> which in the case of kvirc the theme feature got lost
[10:38] <ikonia> eagles0513875: do you know it's got lost as you just said it looked like a bug ?
[10:38] <ikonia> I don't know - which is why I'm asking
[10:38]  * apachelogger would bet on unfinished porting in this case
[10:38] <eagles0513875> i wont know until i try the updated svn version
[10:39] <eagles0513875> in the about kvirc this is showing this was built on march 7th which is almost 2 months old
[10:40] <ikonia> two months old isn't old
[10:40] <eagles0513875> depending on how active the dev team is alot could change
[10:40] <jussi01> !best
[10:41] <jussi01> or rather
[10:41] <eagles0513875> mornign to you too jussi01
[10:41] <jussi01> !wfm
[10:41] <apachelogger> hm
[10:41] <apachelogger> that clearly doesn't fit SVN 90% of the time
[10:41]  * jussi01 waves in apachelogger's direction
[10:42] <apachelogger> yo jussi01
[10:43]  * eagles0513875 goes and sits in corner and ponders packaging an updated kvirc version to replace the one thats in repos
[10:45] <eagles0513875> do you think its a bad idea to have an updated version of kvirc since its still in svn and also in jaunty
[10:46] <apachelogger> http://brainstorm.ubuntu.com/idea/19358/
[10:47]  * eagles0513875 waits for konqueror to crash
[10:48] <eagles0513875> that got my vote i think it would be kool to have the unique login scree like we do splash screen for kubuntu
[10:51] <apachelogger> maybe I should file an idea "people should stop complaining about kubuntu artwork, but do something about it"
[10:51] <ikonia> I was just about to say there are tons on kde-look, ubuntu-fy one and submit it
[10:53] <apachelogger> well, they would need to fit in
[10:53] <apachelogger> just having a splash doesn't cut the chese
[10:53] <ikonia> of course not,
[10:53] <apachelogger> along with that we'd need a kdm theme and probably a wallpaper
[10:53] <Quintasan> FFFFUUUU
[10:53] <ikonia> ?
[10:53] <apachelogger> Quintasan: you package minion?
[10:54] <Quintasan> apachelogger: what?
[10:54] <apachelogger> are you a packaging minion?
[10:54]  * eagles0513875 wants to eventually become a package minion
[10:54] <Quintasan> apachelogger: looks like :D
[10:54] <apachelogger> Quintasan: anything up on revu to revu?
[10:54] <eagles0513875> i think gnomefreak is as well lol he was packaging seamonkey when he came on lol
[10:54] <Quintasan> currently I'm trying to package new minirok but debuild complains about symbolic links
[10:55] <Quintasan> dunno how to deal with it
[10:55] <gnomefreak> eagles0513875: i finished Seamonkey nightly yesterday
[10:55] <apachelogger> Quintasan: show build log
[10:55] <eagles0513875> ahhh my bad
[10:56] <Quintasan> apachelogger: ok I need a second because I cleared source :P
[10:56] <apachelogger> oi vei!
[10:58] <eagles0513875> koffice has a broken dependency and when installing that dependency first it wants to uninstall my whole kde desktop :(
[10:59] <Quintasan> apachelogger: http://pastebin.com/f66e17ca6
[10:59] <Quintasan> eagles0513875: You are running jaunty?
[10:59] <apachelogger> ah
[11:00] <apachelogger> Quintasan: you seem to have generated binary blop in your source tree
[11:00] <apachelogger> that is preventing dpkg-source from creating the diff and makes it wanna die
[11:00] <eagles0513875> Quintasan: ya i am but stripped it down to kde-base install and building it up that way and when i did this same thing on intrepid the same issue
[11:00] <Quintasan> apachelogger: duuno, I did "git clone"
[11:01] <Quintasan> eagles0513875: Wouldn't it be easier to start with Ubuntu Server and install KDE packages?
[11:01] <apachelogger> ah my fault
[11:01] <apachelogger> Quintasan: dpkg-source: error:   new version is symlink to minirok
[11:01] <apachelogger> dpkg-source: error:   old version is directory
[11:02] <eagles0513875> Quintasan: not a big problem on kubuntu purge kde*
[11:02] <apachelogger> that means minirok-2.0/src is a directory with $content in the tarball
[11:02] <apachelogger> but in your source tree it is a symlink to the directory minirok
[11:02] <eagles0513875> thing is  koffice is really annoying me i cannot install it due to kformula dependency issue and when i try to install kformula it wants to uninstall kde
[11:02] <Quintasan> apachelogger: hmm, I tared and gzipped the git tree I downloaded
[11:02] <apachelogger> so either the tarball is all messed up  or you poluted your source tree :P
[11:03] <apachelogger> Quintasan: well, try to do it again
[11:03] <apachelogger> and make sure you get rid of the .git dir before taring it up
[11:03] <Quintasan> hm ok
[11:04] <eagles0513875> any idea as to why when installing the missing dependency of koffice which is kformula it wants to remove anythign kde that is installed
[11:04] <apachelogger> eagles0513875: #kubuntu
[11:04] <apachelogger> for support
[11:04] <eagles0513875> ok
[11:05] <Quintasan> eagles0513875: use aptitiude, it shows available solutions for dependencies problems
[11:05] <eagles0513875> Quintasan: normally i use apt-get build-dep koffice
[11:05] <eagles0513875> i think there is a bug in the koffice package
[11:06]  * a|wen notes that if aptitude offers less than 180 options, you haven't messed your system up bad enough
[11:06] <Quintasan> lol
[11:07] <eagles0513875> morning a|wen
[11:07] <eagles0513875> ill have to take a look at the koffice source code
[11:07] <Quintasan> Hi a|wen
[11:07] <a|wen> and hi
[11:07] <a|wen> the sad thing was, that none of the 180 options was what i wanted :/
[11:09] <Quintasan> apachelogger: looks like taring didn't preserve symlinks
[11:09] <Quintasan> I wonder how should I do it
[11:10] <eagles0513875> Quintasan: im not a package master but have you tried pbuilder
[11:10] <eagles0513875> it buidls the package using the .dsc file
[11:10] <Quintasan> eagles0513875: I'm using pbuilder
[11:10] <eagles0513875> ahh my bad
[11:11]  * Quintasan wonders how to create karmic pbuilder env
[11:11] <a|wen> Quintasan: make a jaunty one and dist-upgrade
[11:11] <a|wen> and re-creat a fresh one, when we get a debootstrab that supports karmic
[11:12] <Quintasan> a|wen: lol, looks like the best solution is easiest one, thanks :P
[11:12] <a|wen> Quintasan: he :) wish it was always so :P
[11:14]  * a|wen loves his modified pbuilder-dist making all those things easy
[11:15] <Quintasan> ARGH
[11:16]  * Quintasan cloned minirok tree for 30th time
[11:18] <Quintasan> YEAH
[11:18] <Quintasan> I just discovered --preserve option for tar
[11:22] <Quintasan> ....
[11:22] <apachelogger> Quintasan: TBH, there shouldn't be in the source to begin with
[11:23] <apachelogger> you might wanna poke $upstream in the eye
[11:23] <Quintasan> apachelogger: nvm this
[11:23] <Quintasan> apachelogger: It woked
[11:23] <apachelogger> still, go complain
[11:23] <Quintasan> apachelogger: but python-kde4-dev has wrong permissons on pykdeuic.py (no +x) and I can't do "make ui"
[11:24] <apachelogger> again?
[11:24] <Quintasan> and if I don't make it then configuration dialogs don't work
[11:24]  * apachelogger fixed that stuff like 300 times by now
[11:24] <Quintasan> apachelogger: It was just downloaded and installed by pbuilder :/
[11:24] <apachelogger> maybe we should start a suite of QA tests for bindings
[11:24] <apachelogger> that package is regressing like no other
[11:25] <Quintasan> ok so I will leave minrok until this get's fixed
[11:25] <Quintasan> minirok*
[11:28] <apachelogger> Quintasan: meanwhile you can annoy upstream with not creating symlinks though :D
[11:28] <Quintasan> apachelogger: sure I will, such things give me headace :<
[11:32] <Quintasan> woah gcc 4.4
[11:34] <apachelogger> hmmmm
[11:34] <apachelogger> JontheEchidna: ping?
[11:34] <apachelogger> vorian: ping
[11:34] <apachelogger> no one heere
[11:35] <apachelogger> Quintasan: would you happen to know whether we are using pkg-kde-tools yet?
[11:35] <Quintasan> apachelogger: nope :(
[11:35] <apachelogger> :S
[11:36] <a|wen> apachelogger: only in synced packages
[11:36] <apachelogger> a|wen: why not in the others?
[11:36] <apachelogger> that would mean that we have to keep kde4.mk from cdbs and the one in pkg-kde in sync
[11:37] <a|wen> apachelogger: because it places the docs in a dir where they are not found
[11:37] <apachelogger> Riddell is linking isn't he?
[11:37] <apachelogger> anyway, I'll just cdbs for now
[11:37] <apachelogger> but pkg-kde is the longterm target
[11:37] <apachelogger> a|wen: + we can change that pretty easily :P
[11:38] <a|wen> apachelogger: yeah .. but that would lead to half the synced packages FTBFS'ing on us
[11:39] <a|wen> apachelogger: but Riddell will probably do some link-magic in kdelibs ... and the long-term target is to use pkg-kde-tools (and alligning our doc-paths)
[11:40] <apachelogger> well, debian can't align until they dropped kdebase3
[11:40] <a|wen> and that will propably take a while i suppose
[11:41] <a|wen> well if we get the symlink-magic in place, then we should be good
[11:41] <apachelogger> Quintasan: http://revu.ubuntuwire.com/p/plasma-widget-klicker
[11:41] <apachelogger> can you pleas tell me why that changelog lists 3 entries?
[11:42] <Quintasan> dunno, I think it was dropped, let me check
[11:42] <apachelogger> a|wen: it all seems rather weird anyway
[11:43] <apachelogger> neversfelde: bug #364926
[11:44] <Quintasan> apachelogger: looks like it's not going to be developed anymore, could you remove it please?
[11:44] <apachelogger> Quintasan: only revu admins can
[11:45] <apachelogger> you might catch one in #ubuntuwire
[11:57] <ScottK> NCommander: Would you please rescore the kile and alarm-clock srus in Jaunty.
[12:05] <apachelogger> Quintasan: http://revu.ubuntuwire.com/p/plasma-widget-pgame
[12:06] <apachelogger> Quintasan: http://revu.ubuntuwire.com/p/plasma-widget-gxmailnotify
[12:17]  * apachelogger notes that apps using qmake usually are the ones with the worst tarball
[12:46] <Riddell> apachelogger: I am using pkg-kde-tools
[12:46] <Riddell> a|wen: link magic?
[12:55] <apachelogger> Riddell: well, we should start a full migration
[12:56] <Riddell> apachelogger: yep, the merges should migrate it
[12:57] <apachelogger> Riddell: well, I was thinking about not adding new packages with cdbs' kde4.mk
[12:57] <apachelogger> then over time we can move the others to use pkg-kde-tools
[12:59] <Riddell> yes, there shouldn't be a reason to use kde4.mk now
[13:35] <Tonio_> Riddell: I was thinking about replacing k3b and kaffeine by their respective kde4 version in karmic
[13:36] <Tonio_> Riddell: do you think we should do this right now ?
[13:36]  * Tonio_ even thinks we should install kaffeine as default video player
[13:37]  * eagles0513875 thinks we need to find something better the pulse audio to use. i have more problems then its worth. i cant use my hd sound card drivers :(
[13:38] <Lure> do we have qt 4.5.1 and qt-creator 1.1 in some ppa?
[13:38] <Lure> hi Tonio_
[13:38] <Tonio_> Lure: ey !
[13:38]  * Lure wants to try qt-creator after all the positive blog posts
[13:39] <Lure> Tonio_: how are you?
[13:39] <Tonio_> Lure: appart from my eyes, I'm doing well :)
[13:39] <Lure> Tonio_: +1 on getting k3b and kaffeine asap in karmic
[13:39] <Tonio_> Lure: I'm having an eye surgery this summer, little problem on that point :/
[13:40] <Lure> Tonio_: ups, that does not sound that good
[13:40] <Lure> Tonio_: do you plan to come to akademy?
[13:40]  * Lure is considering...
[13:40] <Tonio_> Lure: my company on't pay since I'm leaving my job
[13:40] <Tonio_> hehe
[13:40] <Tonio_> Lure: I probably won't
[13:40] <apachelogger> Tonio_, Riddell: http://aplg.kollide.net/images/osiris/snapshot036.png
[13:40] <apachelogger> partitionmanager beta2
[13:40] <Lure> oh, got something better?
[13:40] <apachelogger> with kcm
[13:40] <apachelogger> hrrhrr
[13:41] <Tonio_> apachelogger: packaged on my ppa fyi
[13:41] <apachelogger> Tonio_: lul, I just updated for karmic :P
[13:41] <Tonio_> apachelogger: ah ;)
[13:41] <eagles0513875> Tonio_: i think they will regret loosing you
[13:41] <Tonio_> apachelogger: I'm not that in what pkg-kde-tool is doing... do we have to stop using kde4.mk ?
[13:42] <apachelogger> you really should create a bug report when you update something and don't upload to $archive right away :P
[13:42] <apachelogger> Tonio_: that is a good question indeed
[13:42] <apachelogger> Riddell: do we have to?
[13:42] <Tonio_> eagles0513875: bah... everyone can be replaced
[13:42] <eagles0513875> Tonio_: but the next guy might not be as good as you then they will regret it
[13:42] <Tonio_> apachelogger: what are the benefits in using pkg-kde-tools ?
[13:43] <apachelogger> there are none
[13:43] <Tonio_> eagles0513875: the only big problem is that I'm the only one to know everything about the french parliament
[13:43] <apachelogger> well, no important ones at least
[13:43] <Tonio_> eagles0513875: I did their distribution mostly alone.... and they'll have to provide support
[13:43] <eagles0513875> Tonio_: then they will be begging to get you back
[13:43] <apachelogger> for one we don't need to update all of cdbs to get our kde stuff sorted
[13:43] <apachelogger> second all the kde related build stuff is in one package
[13:43] <apachelogger> that's about it
[13:43] <MatratzenMatze> qtCreator is an very good program IMHO
[13:44] <Tonio_> eagles0513875: they won't :) cause they know once I've decided something, there's no way I can get back
[13:44] <eagles0513875> Tonio_: sent you pm to not take channel ot
[13:47] <Riddell> Tonio_, apachelogger: pkg-kde-tools is the debian version of kde4.mk, since we don't want to alter from debian for no reason we should use pkg-kde-tools
[13:47] <apachelogger> okies
[13:48] <Riddell> kde4.mk only exists because debian weren't getting round to adding a separate cdbs file, now they have we should use it, it's effectively identicle anyway
[13:48] <Riddell> Tonio_: I've not looked at kaffeine but if we're certain they'll be stable for karmic we should upgrade to the kde 4 versions
[13:49] <Tonio_> Riddell: it's mostly finished right now
[13:50]  * apachelogger updates partitionmanager with pkg-kde
[13:50] <Tonio_> Riddell: target is kde 4.3
[13:51]  * eagles0513875 should get back ot upstreaming bugs but will have to do that when im fedup of revising
[13:54] <Riddell> Tonio_: go for it then
[13:54] <Tonio_> Riddell: kk
[14:43]  * Riddell spots http://www.kubuntu-de.org/english/interview-with-kubuntu-developer-jonathan-thomas
[14:44] <eagles0513875> O_O
[14:44] <eagles0513875> damn that puts me to shame
[14:44] <eagles0513875> im 22 this month and i dotn know how to do jack squat cept upstream bug reporting lol
[14:48] <eagles0513875> Riddell: thanks for pointing that out im learning bout alot of kool stuff in jaunty
[14:49] <apachelogger> Riddell: we should blog, fridge, UWN, NYT ...
[14:52] <eagles0513875> apachelogger: your mentioned in the interview that jon gave
[14:52] <apachelogger> uh
[14:52] <apachelogger> *reads*
[14:52] <eagles0513875> near the bottom bout what a ninja is
[14:52] <eagles0513875> he mentions you in there
[14:53] <apachelogger> hm
[14:53]  * apachelogger thinks that his bug triage work is much more valuable than streamlining the release packaging
[14:53] <eagles0513875> lol
[14:53] <apachelogger> then again who wants to know about how I triaged 500 bugs a day by forwarding everything to jonny :P
[14:54] <eagles0513875> hahahahahaha
[14:54] <eagles0513875> he puts me to shame
[14:55]  * eagles0513875 will be back later to upstream more bugs after a nap and getting fedup of revising
[15:13] <apachelogger> hm
[15:14] <apachelogger> Riddell: I include the kde.mk file, don't I?
[15:14] <apachelogger> Riddell: http://paste.ubuntu.com/162855/
[15:15] <Riddell> or /usr/share/pkg-kde-tools/qt-kde-team/1/debian-qt-kde.mk
[15:15] <Riddell> it's missing debhelper.mk
[15:16] <Riddell> debian-qt-kde.mk brings that in and quilt
[15:17] <apachelogger> ah
[15:17] <apachelogger> thx
[15:26] <apachelogger> Riddell: our magic must be applied so that debian-qt-kde doesn't insist on quilt being installed
[15:27] <Riddell> oh aye forgot about that
[15:27] <Riddell> go ahead if you want to
[15:27] <apachelogger> sure
[15:36] <ScottK> apachelogger: You might want to send that back to Debian qt-kde team.
[16:06] <udoeverything> a|wen: I made the plasma network thingie crash again, but the debug output is not the same as on the link you sent me
[16:32] <eagles0513875> udoeverything: what are you doign to make it crash maybe i can do the same and can confirm you bug
[16:33] <udoeverything> eagles0513875: it right click and pick the crtl+S option (on my german system) and then I just change something and press OK
[16:34] <eagles0513875> well im on english lets me try
[16:34] <udoeverything> eagles0513875: I am running the experimental from the PPA
[16:34] <eagles0513875> i am as well
[16:34] <eagles0513875> but it didnt crash for me
[16:35] <eagles0513875> a|wen: did you change something from the widget that you have in your ppa to the one in kubuntu-experimental
[16:35] <udoeverything> eagles0513875: It didn't for me either .. yesterday. Today it did ..
[16:35] <eagles0513875> have you updating anything
[16:36] <tsimpson> oops
[16:36] <tsimpson> stdbot: part
[16:36] <udoeverything> eagles0513875: I am running Jaunty + normal updates and network plasma widget from the PPA
[16:37] <eagles0513875> same here but on 64bit
[16:37] <udoeverything> eagles0513875: OK, I am 32bit
[16:37] <eagles0513875> strange
[16:37] <udoeverything> eagles0513875: shall I upload the crashlog somewhere?
[16:37] <eagles0513875> udoeverything: pastebin then ping a|wen with it
[16:38] <udoeverything> kk
[16:38] <eagles0513875> hes the one managing that
[16:40] <udoeverything> a|wen: crashlog plasma network widget http://pastebin.com/m34b6a5eb
[16:40] <eagles0513875> udoeverything: just sit and wait
[16:42] <udoeverything> eagles0513875: OK, it doesn't really affect me much. Shakey Xorg on ATI is way worse ;)
[16:43] <eagles0513875> good luck with that i have a really annoying audio problem where alsa seems to want to use the pulse audio driver instead of one of 2 drivers of my hd sound card
[16:45] <udoeverything> yeah, Video and Sound are major construction sites ATM :(
[16:46] <eagles0513875> for me with jaunty im happy that i have direct rendering out of the box with my card which is quite impressive i havent had to install the proprietary driver and im reluctant to
[16:46] <udoeverything> being dependent on Skype stinks too :)
[16:46] <eagles0513875> bah need to get my internal mic and camera working and wacom too
[16:47] <udoeverything> yeah, I have a Intel netbook and a AMD desktop .. both have Issues atm. I had to switch to Fedora on the netbook ( KMS etc are nice )
[16:49] <eagles0513875> udoeverything: see pm
[17:20] <neversfelde> what means /bin/tar: Record size = 8 blocks
[17:20] <neversfelde> after calling lintian?
[17:46] <apachelogger> neversfelde: debian bug 522530
[17:46] <apachelogger> does someone wanna do a cool blog post?
[17:46] <neversfelde> apachelogger: thx
[17:54] <asd> k
[17:54] <Bloggeratti> hello
[17:55] <bittin> hllo
[17:55] <bittin> *hello
[18:10] <eagles0513875> apachelogger: we found our blog minion
[18:12] <Bloggeratti> god darn it , it there not one good blog software that i can use on my KDE desktop, though which i can post to Blogger, proprely!!!!!!!!!!!
[18:15] <neversfelde> Bloggeratti: probably the wrong channel?
[18:17] <Bloggeratti> naah i am a devloper, i was making changes to BloGTK , apprently i still hate it more than everyone else
[18:18] <eagles0513875> lol
[18:23] <apachelogger> hm
[18:23] <apachelogger> where did he go to? :P
[18:24] <eagles0513875> thats your blogger for ya
[18:24] <apachelogger> bilbo is sensible
[18:24]  * apachelogger already blogged
[18:24] <eagles0513875> hes swearing at bloggtk it seems like
[18:24] <neversfelde> #BloGTK-devel probably
[18:24] <neversfelde> :)
[18:24] <apachelogger> http://apachelog.blogspot.com/2009/05/checkinstall-debs-done-cmake-way.html
[18:25] <eagles0513875> is cmake replacing the traditional make make install method
[18:25] <apachelogger> no
[18:25] <a|wen> sebas: crash in the widget rev 961845 (so less than a day old) http://pastebin.com/m34b6a5eb
[18:25] <apachelogger> it is replacing configure and all the asorted stuff
[18:27]  * txwikinger hates nvidia
[18:27] <eagles0513875> hi txwikinger whats wrong
[18:27] <apachelogger> nvidia
[18:27] <apachelogger> that is wrong :P
[18:27] <eagles0513875> i have direct rendering without having the proprietary driver installed which is funny
[18:27] <eagles0513875> ati is mroe wrong the nvidia
[18:28] <apachelogger> nope, ati specs are available which makes it less wrong
[18:28] <txwikinger> everytime I upgrade kubuntu the nvidia is playing up
[18:28] <txwikinger> I am tired of it
[18:28] <txwikinger> I will never buy nvidia again
[18:28] <sebas> a|wen: that's one weird crash, the offending line goes:
[18:28] <sebas> She'll join us for dinner at 2000 it seems
[18:28] <sebas> Ah.
[18:28] <eagles0513875> txwikinger: purge it and reinstall the driver
[18:28] <sebas> Hmpf.
[18:28] <sebas>     int old = m_numberOfWlans;
[18:28] <sebas> that one :)
[18:28]  * apachelogger scratches head
[18:28] <txwikinger> eagles0513875: Already done
[18:28] <sebas> And m_numberOfWlans is 99 as the bt says
[18:28] <apachelogger> that is one weird code right there
[18:29] <eagles0513875> txwikinger: still same issues
[18:29] <txwikinger> apachelogger: No wonder if you wrote it :p
[18:29] <apachelogger> nah, sebas did :P
[18:29]  * apachelogger only writes weird code when writing ruby, though that might be due to ruby
[18:29] <a|wen> apachelogger: lol
[18:30]  * sebas only wrote the Plasma bits
[18:30] <txwikinger> a language that is name ruby must be an issue in the first place
[18:30] <sebas> a|wen: is that a reproducable crash?
[18:30] <apachelogger> hm, italy buys $world
[18:31] <apachelogger> at least in a $carworld POV
[18:31] <eagles0513875> a|wen: did you see the paste bin of crash that someone got earlier with network manager im on 64bit and was unable to reproduce it
[18:31] <a|wen> eagles0513875: do you have the version from kubuntu-experimental?
[18:32] <a|wen> sebas: i'm testing it in a few moments ... snapshot is only a few hours old, so wasn't built when i last was at the pc
[18:32] <sebas> Aight, I'll be out for dinner in 20 minutes though
[18:33] <sebas> Likely to return back online later on though
[18:34] <a|wen> sebas: not reproducable here
[18:34] <sebas> Ok, weird, but I can't do anything about it.
[18:36] <a|wen> sebas: okay ... there looks to have been a lot of reordering today; so i'll see if it appears after that is finished
[18:36] <sebas> We've been polishing things and hacking on it for the afternoon
[18:36] <a|wen> so i could see :)
[18:36] <sebas> I'm at the Amarok sprint at our office in Berlin right now
[18:36] <sebas> We didn't write new crashes though ;)
[18:37] <a|wen> hehe ... you wrote them out of the code instead :)
[18:38] <apachelogger> just commeneted out .... for later use :P
[18:38] <a|wen> :P
[18:40] <apachelogger> neversfelde: fancytasks?
[18:40] <apachelogger> oh dear
[18:40] <neversfelde> apachelogger: Apple feeling :)
[18:40] <apachelogger> Riddell: is there some gui to taskel .. maybe we should make the plasmoids group-installable via taskel?
[18:40] <apachelogger> neversfelde: missing launchpad bug
[18:40] <ScottK> apachelogger: I think just a metapackage for Universe widgets.
[18:41] <neversfelde> apachelogger: there is no bug, shall I create it by myself?
[18:41] <apachelogger> neversfelde: don't package without launchpad bug, you see where that goes with fotowall  :P
[18:41] <apachelogger> neversfelde: yes
[18:41] <neversfelde> mhh, ok
[18:41] <a|wen> neversfelde: looked like fotowall was on it's way to debian?
[18:42] <apachelogger> ScottK: dpkg should have a more sensible thing for that
[18:42] <ScottK> apachelogger: Could be, but once you have them installed, they show up in the widget selector, so that's enough.
[18:43] <apachelogger> sure, but it's a PITA ... there should be a way to mark plasmoids as such within the packaging itself
[18:43] <apachelogger> and then $apt gui should be able to install them
[18:43] <apachelogger> or any $group for that matter
[18:45] <neversfelde> a|wen: where can I check this? Anyway Alessandro was faster than me, so seems that I am out :)
[18:45] <apachelogger> neversfelde: please use pkg-kde-tools
[18:45] <apachelogger> include /usr/share/pkg-kde-tools/qt-kde-team/1/debian-qt-kde.mk
[18:45] <a|wen> neversfelde: the ubuntu bug was linked to a debian RFC-bug, that now was renamed to ITP
[18:46] <apachelogger> ITP is far away from "on it's way" :P
[18:46] <apachelogger> even "on it's way" is far away from "arrived"
[18:46] <neversfelde> :)
[18:47] <ScottK> It wouldn't hurt to mail the owner of the ITP to volunteer to collaborate or see how close they are.
[18:47] <a|wen> apachelogger: then let's call it "first step"
[18:47] <apachelogger> ScottK: agreed
[18:48] <apachelogger> a|wen: http://revu.ubuntuwire.com/p/plasma-widget-fancytasks
[18:49] <apachelogger> a|wen: complained about missing packaging bug and pkg-kde-tools for the .mk
[18:51]  * a|wen looks
[18:52] <neversfelde> so pkg-kde-tools is for the make process?
[18:52] <neversfelde> I opened a [needs packaging bug] for that and will upload another version
[18:52] <apachelogger> neversfelde: yes
[18:52] <apachelogger> neversfelde: you shouldn't use kde4.mk from cdbs anymore
[18:53] <neversfelde> mhh
[18:53] <neversfelde> so only debhelper.mk
[18:54] <neversfelde> and a build dep on pkg-kde-tools?
[18:57] <apachelogger> neversfelde: no
[18:57] <apachelogger> neversfelde: the include I pasted enough
[18:57] <apachelogger> s/enough/above
[18:58] <apachelogger> instead of the kde4.mk one
[18:59] <neversfelde> sorry, did not notice this line
[18:59] <apachelogger> hm
[18:59] <apachelogger> hmmmmmmmmmm
[18:59] <apachelogger> neversfelde: IMHO that plasmoid should have been implemented as a panel containment
[19:00] <neversfelde> mhh?
[19:01] <a|wen> neversfelde: i can't see any other problems apart from those already covered by apachelogger
[19:01] <neversfelde> ok, I will upload a corrected version, thx
[19:02] <apachelogger> neversfelde: it should be an alternative panel implementation rather than a plasmoid
[19:02] <neversfelde> apachelogger: it is more a task manager replacement than a whole panel, I think
[19:03] <apachelogger> well
[19:03] <apachelogger> it is both
[19:04] <apachelogger> or rather, it needs both
[19:04] <apachelogger> just having it live in a default panel is awkward
[19:04] <apachelogger> not having it there takes away all the features a panel has
[19:04] <neversfelde> probably it will be a new kooldock someday, but I can't see that it is now
[19:05] <apachelogger> so IMHO it needs to be a panel implementation with hardcoded taskmanager
[19:05] <apachelogger> neversfelde: kooldock was a workaround
[19:05] <apachelogger> and if it becomes that it is a pastard application as it doesn't use the fancy plasma capabilities
[19:06] <neversfelde> should I rename it somehow?
[19:08] <neversfelde> mhh, I used kde4.mk for plasma-widget-stasks, so I should correct it
[19:14] <apachelogger> neversfelde: don't forget to take a look at the groupwise issue :P
[19:15] <apachelogger> bug 336626
[19:16] <apachelogger> akonaditray is autostart?
[19:18] <neversfelde> apachelogger: I had a look at it a few minutes ago and I think I understood the problem. But it seems to be a big task and my time is very limited these days, I hope I can get in touch with it soon
[19:19] <apachelogger> well, it's really just politics ;-)
[19:19] <apachelogger> you don't need to QA the SRU yourself
[19:19] <apachelogger> doubting that you have a groupwise server that would be difficult anyway
[19:21] <neversfelde> well, first I have to find out, what a SRU is :)
[19:28] <apachelogger> neversfelde: there is a pretty nice page in the wiki
[19:28] <apachelogger> with step-by-step guide
[19:28] <neversfelde> ok, will have a look at it
[19:29] <neversfelde> reuploaded that fancy thing
[19:29] <neversfelde> ist it possible to create a watch file for kde-look?
[19:30] <a|wen> afaik no
[19:30] <apachelogger> a|wen: ah
[19:30] <neversfelde> ok, thanks
[19:30] <apachelogger> do an ack
[19:31] <apachelogger> oh dear oh dear
[19:31] <apachelogger> neversfelde: did you testbuild?
[19:31] <neversfelde> apachelogger: yes
[19:31] <apachelogger> I don't trust you :P
[19:31]  * apachelogger invokes pbuild
[19:31] <neversfelde> hehe
[19:32]  * a|wen looks at fancytasks again
[19:37] <apachelogger> hmmmmmmmm
[19:37] <apachelogger> a|wen: builds and looks good
[19:37] <apachelogger> I am ready to upload if you are ok
[19:37] <apachelogger> wth
[19:38] <apachelogger> do launchpad cookies not stick with qwebkit anymore?
[19:38] <a|wen> i'm okay with the look of it ... but i was just going to testbuild it first
[19:38] <apachelogger> a|wen: already did :P
[19:38] <apachelogger> + neversfelde as well if you chose to trust him :P
[19:38] <neversfelde> seems that noone is trusting me :)
[19:39]  * a|wen wonders if he can trust apachelogger ;P
[19:39] <neversfelde> lol
[19:39] <apachelogger> hehe, young motus always so overly eager to testbuild :P
[19:39] <a|wen> apachelogger: so you want an ack in REVU, or is it okay for me to just give it here?
[19:39] <apachelogger> just here
[19:39] <apachelogger> I'll mention it on revu
[19:40] <apachelogger> time saver :D
[19:40] <a|wen> :)
[19:40] <a|wen> apachelogger: go ahead
[19:41] <apachelogger>   Uploading plasma-widget-fancytasks_0.8.1-0ubuntu1_source.changes: done.
[19:41] <apachelogger> Successfully uploaded packages.
[19:41] <apachelogger> a|wen, neversfelde: thx
[19:42] <neversfelde> apachelogger: thank yoiu
[19:42] <neversfelde> -i
[19:42] <apachelogger> a|wen: wanna write a mail about pkg-kde-tools?
[19:42] <apachelogger> we probably should inform (k)ubuntu-devel
[19:42] <a|wen> apachelogger: eh?
[19:42] <apachelogger> that we now prefer pkg-kde-tools over kde4.mk in cdbs
[19:42] <a|wen> ahh, use pkg-kde-tools instead of kde4.mk
[19:43] <apachelogger> so that a) everyone changes packags and b) that no one lets new kde4.mk packages in
[19:44] <Tonio_> hum stupid question but why do we have both a kdewallpapers and a kdebase-workspace-wallpapers ?
[19:45] <Tonio_> isn't that a bit.... nasty ?
[19:45] <apachelogger> possibly
[19:45] <a|wen> apachelogger: i'll write op a short notice
[19:45] <apachelogger> !info kdewallpapers
[19:45] <apachelogger> ah
[19:45] <apachelogger> right
[19:46] <apachelogger> Tonio_: artists need to rediscover kdeartwork
[19:46] <apachelogger> as Riddell put the slogan
[19:46] <apachelogger> a|wen: k,thx
[19:46] <Tonio_> apachelogger: so it's just upstream stupid duplication ? :)
[19:46] <Tonio_> how stupid
[19:47] <apachelogger> well, upstream just doesn't get that no one needs some 10 wallpapers with an overall size of 50mib
[19:50] <eagles0513875> O_O
[19:50]  * eagles0513875 rubs eyes andl ooks again at the siz
[19:51]  * apachelogger redy ruby eys
[19:51] <apachelogger> +e
[19:51] <Tonio_> apachelogger: shouldn't we rename kdebase-workspace-wallpapers to kdewallpapers-extra ?
[19:51] <Tonio_> apachelogger: that would make it more clear isn't it ?
[19:51] <Tonio_> or at least provide it
[19:51] <apachelogger> well
[19:51] <apachelogger> it is extra to kdebase-workspace
[19:51] <apachelogger> so kdewallpapers shoudl be k-w-w-extra
[19:52] <apachelogger> if that at all
[19:52] <Tonio_> hum, yeah
[19:52] <Tonio_> well whatever the one to rename, the current different naming is really strange
[19:52]  * Tonio_ notes this to fix
[19:53] <apachelogger> Tonio_: probably needs discussion with debian and/or upstream
[19:53] <Tonio_> yup yup
[19:56] <apachelogger> uhh
[19:57] <apachelogger> no apachelogger at linuxtag
[19:57] <apachelogger> how sad is that
[20:05] <a|wen> apachelogger: http://pastebin.ca/1410581 ... something I've swallowed completely wrong here; or something i should change/add/remove?
[20:06] <apachelogger> a|wen: IMHO it indicates that one should upload to get that changed
[20:06] <apachelogger> which is not what people should do
[20:07] <apachelogger> at least I don't think so :D
[20:07] <apachelogger> rather update if/when you merge or if/when you upload a new upstream version
[20:07] <apachelogger> there is no need to flood the archives with uploads just to get that minor change done
[20:08] <a|wen> apachelogger: we agree there ... i'll adjust wordings :)
[20:08] <apachelogger> ok, thx, lookgs good otherwise
[20:09] <apachelogger> must by typo day again
[20:10] <a|wen> he
[20:11] <a|wen> apachelogger: change that paragraph to: "If you care for a KDE4(-based) application, please help by changing it to use pkg-kde-tools when a new upstream version is uploaded. If the (KDE4-version) of the package is in Debian you should hopefully be able to do that by a merge."
[20:11] <apachelogger> aye, good with me
[20:12] <a|wen> apachelogger: good; i'll send it to kubuntu-devel as well as ubuntu-devel ?
[20:13] <apachelogger> a|wen: aye, maybe also motu
[20:13] <a|wen> i'll add motu as well ... then we'll hopefully hit everyone
[20:20] <apachelogger> very good
[20:20] <apachelogger> a|wen++
[20:22] <a|wen> if not in anything else; then i can always be the secretary writing the mails :P
[20:22] <apachelogger> true
[20:23]  * apachelogger would need a mail minion anyway :P
[20:23] <apachelogger> a|wen: btw, did you take a look at the l10n paper?
[20:23] <seele> blah, that intel video driver update doesnt seem to have helped much
[20:23] <a|wen> apachelogger: uh, which one?
[20:23] <apachelogger> sec
[20:24] <apachelogger> a|wen: http://docs.google.com/Doc?id=ajk6csn6c2vn_0c6d8rp6w
[20:24] <apachelogger> this one
[20:30] <a|wen> apachelogger: looks pretty sensible to me
[20:32] <apachelogger> a|wen: any additions you can think of?
[20:34] <a|wen> apachelogger: no, can't think of anything missing ... looks very well thought through
[20:34] <apachelogger> okies, thanks
[21:30] <nielsslot> can someone tell me when the first KDE 4.3 beta packages should appear for Jaunty?
[21:33] <a|wen> nielsslot: we need kde to release the beta first :)
[21:34] <nielsslot> it's going to be released on May 12
[21:34] <nielsslot> i'm wondering if there are going to be packages around May 16
[21:35] <a|wen> nielsslot: the plan is to have PPA packages not to far after the release ... but if that is before may 16 is not known
[21:36] <nielsslot> a|wen: ok, thanks
[21:37] <a|wen> nielsslot: is it for demonstrational use on that date?
[21:37] <nielsslot> kdegames is planning at test day in that weekend
[21:38] <a|wen> nielsslot: specifically for the 4.3 branch or for trunk?
[21:39] <nielsslot> not sure.. shouldn't be that much of a difference..
[21:39] <nielsslot> a|wen: ^^
[21:40] <a|wen> nielsslot: right ... oh project-neon doesn't have packages for jaunty yet; so no idea in suggesting that
[21:41] <nielsslot> a|wen: i noticed that already, that's why i asked..
[21:42] <a|wen> nielsslot: ahh ... well, now i'm also up-to-date on that :)
[21:43] <a|wen> apachelogger: any plans for project-neon on jaunty?
[21:47] <a|wen> nielsslot: haven't seen you in here before?
[21:53] <neversfelde> apachelogger: so there is no kdepim-dev.install in Debian, seems to be a kubuntu problem.
[21:57] <neversfelde> yes, it is a difference "    - Keep our kdepim-dev package
[22:25] <ScottK> Somewhere in there is a changelog entry that goes something like "make kdepim-dev actually useful"
[22:25] <imbrandon> afternoon all
[22:31] <apachelogger> a|wen: already staging
[22:32] <apachelogger> actually already done
[22:32] <apachelogger> but I am doing a new rebuild
[22:32] <apachelogger> with new qt and all
[22:42] <nhandler> JontheEchidna: Aren't we meant to switch to pkg-kde-tools when we do new upstream releases now?
[22:44] <imbrandon> nhandler: yes
[22:46] <nielsslot> a|wen: i'm one of the KTurtle developers.. not very active on IRC though..
[22:48] <a|wen> nielsslot: okay ... but welcome then :)
[22:48] <nielsslot> a|wen: thanks :)
[22:49] <a|wen> nielsslot: just thought the name looked very homely
[22:50] <nielsslot> a|wen: 'homely'?
[22:50] <a|wen> nielsslot: nordic at least (DK)
[22:51] <nielsslot> a|wen: i'm dutch
[22:51] <a|wen> nielsslot: well, we get mixed up with that all the time in any case :)
[22:58] <ghostcube_> oha ein holländer
[22:59] <ghostcube_> :)
[23:10] <a|wen> well... fancytasks is great if it could stop randomly crashing plasma for me
[23:18] <a|wen> neversfelde: i hope you are ready to package when a new version arrives :)
[23:21] <a|wen> oh well, i suppose i wanted them grouped; can't change it back again
[23:50] <neversfelde> a|wen: sure :)
[23:50] <a|wen> neversfelde: perfect :) ... one advice; don't enable grouping if you don't want that ;)
[23:51] <neversfelde> :)