[00:19] <ScottK> yofel and Riddell: I added all the ones that are in the archive to the packageset (zeroconf-ioslave is not).
[00:57]  * ahoneybun updates his macbook to beta 2
[03:01] <SonikkuAmerica> Quick question: How long is 14.04 being supported for, 3 years or 5?
[03:02] <ScottK> SonikkuAmerica: 5
[03:02] <SonikkuAmerica> ScottK: Thank you
[03:02] <SonikkuAmerica> Also, do you know about our new one-stop page in development, KubuntuLinks?
[03:07] <SonikkuAmerica> https://wiki.kubuntu.org/Kubuntu/KubuntuLinks <<< We're building a one-page landing where we have a jumping-off place for all things Kubuntu. You can check on what we're trying to build off off at LubuntuLinks and the Ubuntu GNOME One Stop Page (links are on the KubuntuLinks page)
[08:38] <apachelogger> shadeslayer: bug 1297139
[09:35] <shadeslayer> apachelogger: ack
[09:35] <kubotu> ::workspace-bugs:: [1297139] startkde qdbus invocation broken when both qt4 and qt5 are installed @ https://bugs.launchpad.net/bugs/1297139 (by Harald Sitter)
[09:44] <apachelogger> shadeslayer: you know, had you written a model for drivermanager it probably would have needed no refactoring xD
[09:44] <shadeslayer> k
[09:44] <apachelogger> what I am doing is moving the management components out of module.cpp
[09:45] <apachelogger> so really, we should just have initially gone with a model then that would have been separate all along ^^
[09:53] <shadeslayer> apachelogger: http://paste.ubuntu.com/7150443/
[09:53] <shadeslayer> better?
[09:56] <apachelogger> shadeslayer: why two lines?
[09:57] <shadeslayer> standard convention in startkde as I see
[09:57] <shadeslayer>         XCURSOR_THEME=default
[09:57] <shadeslayer>         export XCURSOR_THEME
[09:58] <kdeuser56> have a look at that trace of kdeinit4: http://pastebin.com/ubvcXtKw
[09:58] <kdeuser56> very weird ... looks like kcrash also crashed? 
[09:59] <apachelogger> shadeslayer: so you are upstreaming?
[09:59] <shadeslayer> apachelogger: this patch? lolno
[09:59] <apachelogger> what does it matter then? :P
[09:59] <shadeslayer> some variation of this probably
[09:59] <shadeslayer> *shrug* fine 
[09:59] <shadeslayer> I don't care if its one way or the other
[10:00] <apachelogger> it's not like that script is a shining example of consistent or good shell practise ;)
[10:00] <shadeslayer> I just thought it'd be better to have it consistend with the rest of startkde
[10:00] <shadeslayer> *consistent
[10:00] <apachelogger> shadeslayer: like that other patch we do one-line export in? ^^
[10:00] <apachelogger>     export KDEDIRS=/usr/share/kubuntu-mobile-default-settings/:/usr/share/kubuntu-default-settings/kde4-profile/default/
[10:01] <shadeslayer> apachelogger: http://paste.ubuntu.com/7150476/
[10:01] <shadeslayer> heh
[10:01] <apachelogger> I am not even sure why it does it over two lines, when I implemented a shell some years ago I think the posix spec even said that export will set the variable
[10:03] <apachelogger> so, in terms of a posix shell export foo=bar is equal to foo=bar, export just adds the additional feature of the variable being replicated into children's envrionment
[10:03] <shadeslayer> k
[10:03] <apachelogger> maybe I am misremebering, who knows
[10:05] <shadeslayer> apachelogger: uploaded
[10:05] <apachelogger> Variables shall be initialized from the environment (as defined by XBD Environment Variables and the exec function in the System Interfaces volume of POSIX.1-2008) and can be given new values with variable assignment commands. If a variable is initialized from the environment, it shall be marked for export immediately; see the export special built-in. New variables can be defined and initialized with variable assignments, with the read or 
[10:05] <apachelogger> getopts utilities, with the name parameter in a for loop, with the ${ name= word} expansion, or with other mechanisms provided as implementation extensions.
[10:05] <apachelogger> The shell shall give the export attribute to the variables corresponding to the specified names, which shall cause them to be in the environment of subsequently executed commands. If the name of a variable is followed by = word, then the value of that variable shall be set to word.
[10:05] <apachelogger> If a variable assignment precedes the command name of export but that variable is not also listed as an operand of export, then that variable shall be set in the current shell execution environment after the completion of the export command, but it is unspecified whether that variable is marked for export.
[10:06] <shadeslayer> Riddell: ScottK: can you approve kde-workspace ?
[10:06] <apachelogger> so yeah, foo=bar\n export foo is a bit of a silly way to write it
[10:07] <apachelogger> "the shell shall" is fancy tho ^^
[10:08] <apachelogger> anyway, complete read in case someone is interested http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html
[10:09] <apachelogger> shadeslayer: I am wondering whether it would be worth equipping the class Driver with a Package *
[10:09] <apachelogger> thus removing all QApt interaction from DriverWidget
[10:09] <shadeslayer> Package * ?
[10:09] <apachelogger> A package pointer
[10:10] <apachelogger> also move the is active logic outside
[10:10] <apachelogger> so driverwidget really just needs to iter all drivers and create appropriate widgets
[10:12] <shadeslayer> quite a bit of refactoring
[10:13] <Riddell> shadeslayer: what's new?
[10:13] <shadeslayer> Riddell: fix for bug 1297139
[10:13] <apachelogger> shadeslayer: you made the driverwidget contain processing logic :P
[10:13] <apachelogger> actually it isn't much though
[10:13] <apachelogger> DW::isActive goes away, moves outside class, ctor gets changed to not use qapt, but instead do a property check
[10:14] <shadeslayer> k
[10:23] <apachelogger> hm
[10:23] <apachelogger> shadeslayer: are you sure that driverwidget currently contains the same logic to find the active driver as the gtk gui?
[10:24] <shadeslayer> not exactly the same I think
[10:24]  * apachelogger thought that used an order rather than a first-match
[10:24] <shadeslayer> but quite close
[10:24] <shadeslayer> and mine uses an order too
[10:24] <apachelogger> oh?
[10:25] <apachelogger> ah yeah, manualinstall always trumps
[10:25] <shadeslayer> yes
[10:26] <shadeslayer> manualinstall > proprietary > opensource
[10:26] <apachelogger> shadeslayer: why is manual bound to qapt finding a package though?
[10:27] <apachelogger> you don't trust the backend? :P
[10:27] <shadeslayer> is it?
[10:28] <shadeslayer> hm
[10:28] <apachelogger> if package {} else { if (driver.manual) }
[10:28] <shadeslayer> apachelogger: yeah I suppose it could be done like : if package && !driver.manual
[10:30] <apachelogger> but why is that dependent on package at all?
[10:30] <shadeslayer> because QApt sometimes returns null ptrs to packages
[10:31] <apachelogger> yes, but what does that have to do with whether the driver the is manual or not
[10:32] <shadeslayer> ah so you mean if driver.manual { } else if package {}
[10:38] <apachelogger> shadeslayer: yeah
[10:39] <shadeslayer> sure, looks fine
[10:50] <apachelogger> http://paste.ubuntu.com/7150634/
[10:50] <apachelogger> much fun has been had
[10:55] <apachelogger> oh 
[10:55] <apachelogger> I just got reminded that chose to ignore broken l10n
[10:55] <apachelogger> hawt
[10:57] <apachelogger> oho
[10:57] <apachelogger> shadeslayer: http://paste.ubuntu.com/7150658/ that does not work btw
[10:58] <apachelogger> there's langauges that parse right-to-left ;)
[10:58] <shadeslayer> >.>
[10:58] <apachelogger> so you appending on the right will make for silly localization
[11:19] <apachelogger> shadeslayer: what's supposed to happen when a driver is not installed manual but qapt still doesn't manage to find a package?
[11:20] <apachelogger> not create a button?
[11:20] <shadeslayer> yep
[11:21] <shadeslayer> because it would be impossible to do anything with it
[11:21] <shadeslayer> apachelogger: while you're refactoring, maybe you could come up with a sane way to handle the case where there is exactly one driver for the device
[11:23] <apachelogger> shadeslayer: does that happen?
[11:23] <apachelogger> I'd rather think that would be handled in ubuntu-drivers-common
[11:23] <shadeslayer> yes
[11:24] <apachelogger> shadeslayer: tell the pitti to not report such devices :P
[11:25] <apachelogger> its a pointless
[11:25] <shadeslayer> how so
[11:25] <shadeslayer> apachelogger: actually, I think it's a bug that my device only reports one driver
[11:25] <shadeslayer> when infact it has 2
[11:25] <kubotu> ::qt-bugs:: [1254276] qt4-linguist-tools should depend on qtchooser @ https://bugs.launchpad.net/bugs/1254276 (by Daniel Lintott)
[11:26] <shadeslayer> linux-firmware-nonfree and b43
[11:26] <apachelogger> maybe qapt scrus up
[11:26] <shadeslayer> nope
[11:26] <shadeslayer> ubuntu-driver list only shows one
[11:26] <apachelogger> kcmshell(7874) DriverWidget::DriverWidget: encountered invalid driver 0x0 false for "GK104 [GeForce GTX 660 OEM]" 
[11:26] <apachelogger> I broke it
[11:26] <apachelogger> ololo
[11:27] <shadeslayer> staph breaking it :(
[11:27] <apachelogger> shadeslayer: well, bug in the commons thing then
[11:27] <apachelogger> oh lol, I know why ^^
[11:30] <apachelogger> foreaching is quite the pain without pointers :'<
[11:34] <apachelogger> I think the refactored code might need a refactoring ^^
[11:34] <apachelogger> that got spooky very quickly
[11:35] <apachelogger> on the plus side it's working as expected and didn't need pointers
[11:39] <apachelogger> why the qapt includes are in LibQApt/ rather than QApt/ is the greatest question of all time
[11:44] <BluesKaj> 'Morning folks
[11:47] <Riddell> anyone got amarok working with gstreamer 1.0 backend?
[11:50] <Riddell> ah yes got it working
[11:57] <yofel> worked for me after I got the new qtwebkit
[12:07] <apachelogger> shadeslayer: Q: why are xapian failures handled seperately from init errors in terms of the UI?
[12:13] <apachelogger> shaaaaaaaaaaaaaaadeslaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaay0r
[12:13] <apachelogger> must be at lunchen
[12:13]  * apachelogger waves the fist
[12:35] <sgclark> Riddell: any tasks for me today?
[12:37] <Riddell> sgclark: whole new calligra for the packaging if you think you can handle it
[12:38] <Riddell> sgclark: including backporting to saucy
[12:38] <sgclark> Riddell: only one way to learn :) will need help with backport bit
[12:40] <sgclark> In debian/watch no matching files for watch line , where is it?
[12:41] <sgclark> Riddell: ^
[12:44] <Riddell> sgclark: oh it's probably still not public
[12:45] <sgclark> depot?
[12:45] <Riddell> sgclark: scp ftpubuntu@depot.kde.org:stable/calligra-2.8.1/*xz .
[12:45] <sgclark> thanks!
[12:45] <Riddell> also calligra-l10n to be packaged too, which is a real fiddle
[12:45] <jussi> Im getting browser-plugin-vlc crashes on 14.04 - anyone else getting those? 
[12:49] <Riddell> um, shouldn't do?
[12:50] <jussi> annoying thing is it doesnt give me apport or anything to report the bug
[12:56] <apachelogger> jussi: activate apport notifications then :P
[12:56] <jussi> apachelogger: how? 
[12:56] <apachelogger> the opposite of how you deactivated them I guess
[12:58] <jussi> apachelogger: its a pretty much brand new install...
[13:03] <shadeslayer> apachelogger: yeah, went off for lunch
[13:03] <shadeslayer> apachelogger: no real reason, just being verbose I guess
[13:04] <apachelogger> jussi: something must be astray then
[13:04] <apachelogger> jussi: are you sure apport is enabled though? /etc/default/apport
[13:04] <apachelogger> shadeslayer: btw, you can connect signals to signals ;)
[13:05] <jussi> apachelogger: Ill look
[13:05] <shadeslayer> Riddell: btw moving to gst 1.0 will break ktp call ui
[13:05] <apachelogger> shadeslayer: changed tracking is epically broken btw
[13:06] <shadeslayer> s/will/might/
[13:06] <kubotu> shadeslayer meant: "Riddell: btw moving to gst 1.0 might break ktp call ui"
[13:06] <shadeslayer> apachelogger: yes :(
[13:06] <apachelogger> the slot checking for changedness in driverwidget actually changes the reference value, as though it was saved which of course it wasnt
[13:06] <apachelogger> most peculiar
[13:07] <Riddell> shadeslayer: hmm so it's a choice of auto-install + ktp call ui  vs  ugly codecs ?
[13:08]  * apachelogger broke sorting somehow
[13:09] <shadeslayer> Riddell: no it's a choice between : having a untested port , which might cause applications like call ui to stop working but gets us out of the codec situation vs a codec situation vs landing pvlc 
[13:09] <shadeslayer> take your pick
[13:09] <ScottK> shadeslayer: I'll be offline ~all day, so don't count on me to approve anything for at least 10 hours.
[13:09] <shadeslayer> ScottK: ok
[13:14] <jussi> apachelogger: its enabled (set to 1)
[13:15] <apachelogger> then I dunno
[13:15] <apachelogger> jussi: do you have a crash file in /var/crash
[13:16] <jussi> apachelogger: actually, yes, I do
[13:17] <apachelogger> then it should have a notification
[13:17]  * apachelogger cries
[13:18] <jussi> so by crashing something else Ive triggered another bug? 
[13:18]  * jussi cries
[13:18] <apachelogger> jussi: kdebugdialog -> enable all -> logout -> login -> wait a minute -> paste .cache/upstart/startkde.log
[13:18] <apachelogger> jussi: also
[13:19] <apachelogger> does the crash file have a file with the same name and .upload or .uploaded appended?
[13:19] <jussi> no
[13:19] <apachelogger> k
[13:19] <jussi> only 1 file in /var/crash
[13:23] <jussi> apachelogger: pm'ed it to you
[13:24] <apachelogger> arrr
[13:25] <apachelogger> shadeslayer: Q: what exactly happnes if I have nvidia binarily installed and switch to nuvoulyuluo
[13:26] <apachelogger> jussi: well, the good news is there is no output, the bad news is there is no output
[13:26] <shadeslayer> apachelogger: it installs the nouveau driver .... but doesn't remove the nvidia one
[13:26] <apachelogger> jussi: oh, actually, you might have to wait up to 5 minutes
[13:26] <apachelogger> there's a timer somewhere
[13:26] <shadeslayer> I suspect it keeps nvida active in that case :/
[13:26] <shadeslayer> lets try
[13:26] <apachelogger> shadeslayer: #logicfail
[13:27] <shadeslayer> oh wait, my kcm is still broken
[13:27] <shadeslayer> apachelogger: yes :/
[13:29] <apachelogger> row row row ye boat gently over the seas, and if you see a kraken spawn don't forget to scream
[13:29] <apachelogger> shadeslayer: what does the gtk thingum do
[13:29] <shadeslayer> gtk thingum?
[13:29] <apachelogger> the gtk gui
[13:29] <shadeslayer> don't remember off the top of my head
[13:30]  * shadeslayer looks
[13:31] <jussi> apachelogger: any better? 
[13:32] <apachelogger> jussi: nay
[13:32] <jussi> :/
[13:32] <apachelogger> jussi: alt-f2 -> kded -> in the bottom list make sure notifiction helper is actually started
[13:32] <apachelogger> alas, I think it creates no output if there's nothing to talk about
[13:32] <apachelogger> so it may simply not want to process the file
[13:33] <apachelogger> !info kubuntu-driver-manager trusty
[13:33] <shadeslayer> apachelogger: http://paste.kde.org/pdnrvs0qk
[13:33] <jussi> notification helper is started
[13:33] <apachelogger> shadeslayer: right
[13:34] <shadeslayer> so removes the package
[13:37]  * shadeslayer rages at pam
[13:39] <apachelogger> jussi: paste again
[13:39] <apachelogger> jussi: are you sure you enabled everything in kdebugdialog?
[13:39] <apachelogger> ohohoh
[13:39] <apachelogger> jussi: you are on trusty, right?
[13:39] <apachelogger> !info kubuntu-notification-helper trusty
[13:40] <jussi> apachelogger: yes
[13:40] <apachelogger>     kDebug() << "ApportEvent ::"
[13:40] <apachelogger> there should be debug output regardless of whether it actually will process the files
[13:44] <shadeslayer> hm
[13:44] <shadeslayer> Riddell: can you reset my password on qa.kubuntu.co.uk?
[13:45] <apachelogger> shadeslayer: please test the master
[13:45] <apachelogger> still doesn't remove stuff yet
[13:47] <shadeslayer> apachelogger:   driver("nvidia-331-updates" recommended[false] free[false] fromDistro[true] builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
[13:47] <shadeslayer> that 0x0 doesn't look good
[13:47] <shadeslayer> clicking apply doesn't do anything
[13:49] <kubotu> ::workspace-bugs:: [1297139] startkde qdbus invocation broken when both qt4 and qt5 are installed @ https://bugs.launchpad.net/bugs/1297139 (by Harald Sitter)
[13:51] <apachelogger> shadeslayer: huh
[13:51] <apachelogger> shadeslayer: doesn't want to change anything then :P
[13:52] <shadeslayer> wat
[13:57] <jussi> apachelogger: err, what is it you want me to do? 
[13:57] <apachelogger> shadeslayer: oh, me stupid
[13:57] <apachelogger> shadeslayer: forgot to actually the function ^^
[13:57] <apachelogger> jussi: wait for the log to contain ApportEvent
[13:58] <apachelogger> if it doesn't then your setup is broken somehow
[14:09] <apachelogger> shadeslayer: pull
[14:09] <shadeslayer> yeah works now
[14:10] <shadeslayer> "fix the actual, ehm, management, the manager is, ehm, supposed to do.." :P
[14:13] <shadeslayer> apachelogger: btw what does kubuntu-notification-helper check for reboots?
[14:16] <apachelogger> an asortment of files
[14:16] <apachelogger> well
[14:16] <apachelogger> two
[14:16] <shadeslayer> ^^
[14:16] <shadeslayer> which ones
[14:16] <apachelogger> read the source
[14:16] <shadeslayer> pft
[14:17] <apachelogger> src/daemon/rebootevent/rebootevent.cpp:    if (!QFile::exists("/var/run/reboot-required") && !kdelibsChanged)
[14:17] <apachelogger> src/daemon/rebootevent/rebootevent.cpp:    QFile file("/var/run/reboot-required-kdelibs");
[14:18] <apachelogger> that was very hard
[14:18] <apachelogger> took me one cd and a grep
[14:18] <apachelogger> geez
[14:18] <apachelogger> shadeslayer: give that kcm a testero please
[14:18] <apachelogger> I cannot test debconf etc.
[14:18] <shadeslayer> apachelogger: works on nvidia machine
[14:19] <shadeslayer> I can change drivers, shows correct drivers after change
[14:19] <shadeslayer> apachelogger: I vaguely recal that it used to inform the user via the kcm to reboot
[14:21] <apachelogger> shadeslayer: what? no?
[14:21] <shadeslayer> ok
[14:21] <apachelogger> phonon kcm tells the user to logout and login
[14:21] <apachelogger> but I don't think there is any KCM that notifies about reboots
[14:21] <apachelogger> considering that's a system level thing I doubt KCMs have much business talking about that :P
[14:24] <apachelogger> hm
[14:24] <apachelogger> is launchpad broken?
[14:24] <shadeslayer> why?
[14:25] <apachelogger> I have a number of builds stuck in queue for 6 hours
[14:25] <apachelogger> and they keep saying they will start in like 30 minutes
[14:25] <shadeslayer> I uploaded KDE 4.13 for Saucy
[14:25] <shadeslayer> which would explain it
[14:25] <shadeslayer> s/would/might
[14:25] <apachelogger> ah, I guess
[14:25] <shadeslayer> on that note
[14:25] <apachelogger> still odd that the queue estimate is so rubbish
[14:25] <shadeslayer> Riddell: can you plz change my password for qa.kubuntu.co.uk
[14:26] <apachelogger> I mean "starting in 30 minutes" for 6 hours I have not seen before ^^
[14:26] <apachelogger> "starting in 6 hours" OTOH I have seen :P
[14:26] <shadeslayer> I see > 700 jobs for 25 builders
[14:26] <apachelogger> shadeslayer: whats your user
[14:26] <shadeslayer> shadeslayer
[14:31] <shadeslayer> so I have PAM somewhat working, I've figured out where all the configs and what not go
[14:31] <shadeslayer> but there be bugs
[14:35] <apachelogger> shadeslayer: what I don't get, why can the kmessagewidgets be closed
[14:35] <apachelogger> it's not like the user would get anything from closing them as they go away on their own anyway
[14:36] <apachelogger> shadeslayer: please be releasing master
[14:38] <shadeslayer> okay
[14:38] <shadeslayer> PAM is blocked till next week
[14:42] <shadeslayer> Riddell: might want to approve kubuntu-driver-manager
[14:44] <shadeslayer> also, FYI http://qa.kubuntu.co.uk/ninjas-status/build_status_4.12.95_saucy.html
[14:46] <apachelogger> actually I think driver-manager can wait
[14:46] <shadeslayer> already uploaded
[14:46] <apachelogger> not critical for b2 IMO
[14:47] <apachelogger> shadeslayer: yeah, it can sit in the queue
[14:47] <shadeslayer> okay
[14:47] <shadeslayer> apachelogger: fwiw we still don't have ISO's
[14:47] <shadeslayer> so I think it's fine
[14:47] <apachelogger> whatever works :P
[14:48] <apachelogger> ovidiu-florin: in case I forgot to ask last week, where are we on the wordpress migration ;)
[14:48] <shadeslayer> +        //  b) set driver.fuzzyActive, see blow
[14:48] <shadeslayer> :D
[14:49] <apachelogger> ?
[14:49]  * apachelogger wonders what to write about 4.13b1
[14:49] <shadeslayer> it's magic
[14:50] <apachelogger> how? :P
[14:50] <apachelogger> there's a whole comment block explaining how the activity order works :P
[14:50] <shadeslayer> apachelogger: https://www.youtube.com/watch?v=N7-fZJaJUv8
[14:50] <apachelogger> do we have ktp 0.8 final yet?
[14:50] <shadeslayer> magic ^^
[14:52] <apachelogger> lol
[14:53] <apachelogger> shadeslayer: that's what you get for not sticking to your original design
[14:54] <apachelogger> plasma is not a file manager, neither is the folderview plasmoid, allowing it to go anywhere near the domain of doing file management is shooting yourself in the foot
[14:54] <apachelogger> so that's why there's that video
[14:55] <apachelogger> because people have grand design ideas, then don't stick to them and then stuff ends up being weirdly patched together nonesense because it was not in the original grand design ideas
[14:55] <apachelogger> q.e.d.
[14:55]  * apachelogger looks for something to eat
[14:56] <shadeslayer> plasma's design looks delicious :P
[15:03] <shadeslayer> apachelogger: http://download.kde.org/stable/kde-telepathy/0.8.0/src/
[15:03] <shadeslayer> been up for a week
[15:08] <apachelogger> shadeslayer: do we have it in the archive tho?
[15:08] <apachelogger> parently not 
[15:08] <apachelogger> Version: 0.7.80ubuntu1
[15:09] <apachelogger> kubotu: newversion kde-telepathy 0.8.0
[15:09] <kubotu> Package kde-telepathy doesn't exist yet!
[15:09] <apachelogger> kubotu: newversion meta-kde-telepathy 0.8.0
[15:09] <kubotu> https://bugs.launchpad.net/bugs/1297351
[15:10] <shadeslayer> nope
[15:11] <shadeslayer> there was no announcement
[15:20] <apachelogger> well that is rude
[15:20] <apachelogger> d_ed: is there a reason ktp 0.8 was not announced?
[15:21] <shadeslayer> d_ed was on vacation
[15:21] <shadeslayer> poke mck182
[15:27] <apachelogger> Sput: when is 0.10 final due?
[15:40] <apachelogger> shadeslayer, Riddell: beta2 updated https://wiki.ubuntu.com/TrustyTahr/Beta2/Kubuntu
[15:40] <apachelogger> I pulled the 4.13 description out of my nose
[15:40] <apachelogger> bug section will need doing
[15:41] <apachelogger> although to be honest, I think listing the bugs when there is a link to the lunchpad filter seems a bit of a waste of time
[15:42] <shadeslayer> https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1292471/comments/1
[15:42] <shadeslayer> :D
[16:04] <sgclark> Can I put stuff in http://bazaar.launchpad.net/~kubuntu-packagers/+junk/kubuntu-automation/view/head:/lintian-ignore.json lintian overrides to clean up? 
[16:04] <sgclark> Riddell: or anyone with answer
[16:10] <shadeslayer> sgclark: sure, but what do you want to clear up?
[16:15] <sgclark> shadeslayer: rebuilding, will paste the list for approval before I make the overrides
[16:16] <shadeslayer> okay
[16:17] <shadeslayer> apachelogger: anything off the top of your head that needs doing?
[17:20] <Riddell> apachelogger: lovely, thanks
[17:20] <Riddell> shadeslayer: beta testing!
[17:20] <Riddell> shadeslayer: can't you change your own password on qa.kubuntu.co.uk ?
[17:30] <Riddell> sgclark: getting on ok?
[17:31] <sgclark> Riddell: yep :0 I need to know if these are ok to put in overrides or need investigation: http://paste.ubuntu.com/7152244/
[17:33] <sgclark> Riddell: also http://paste.ubuntu.com/7152258/
[17:34]  * Riddell looks
[17:37] <Riddell> sgclark: for the first one http://paste.ubuntu.com/7152244/ the only one I think I'd not include is icon-size-and-directory-name-mismatch since I would like those fixed upstream
[17:38] <sgclark> Riddell: ok, I can fix those in my off time as well.
[17:38] <Riddell> sgclark: thanks :)
[17:39] <Riddell> sgclark: libkdeinit4_calligrawords.so I'm not really sure but it seems to be listed in both calligrawords-common.install and calligrawords.install when it shouldn't be in either
[17:39] <Riddell> but maybe it's listed in both because dh_movelibkdeinit doesn't handle it
[17:40] <Riddell> I'd remove it from calligrawords-common.install at least
[17:40] <Riddell> and see if it sorts itself when removed from calligrawords.install
[17:40] <sgclark> ok
[17:40] <Riddell> although that would need another compile which will take another age to do so don't worry if it's too much
[17:40] <sgclark> I really don't mind at all
[17:44] <sgclark> Riddell: anything else need attention?
[17:45] <sgclark> Riddell: image-file-in-usr-lib ok to override?
[17:46] <soee> i se gstreamer in updates and it is going to ne installed not update it wasnt here by default before ?
[17:52] <Riddell> sgclark: yeah I think that's what we have to do with QML
[17:52] <Riddell> soee: now gstreamer1.0 not gstreamer0.10
[17:53] <soee> Riddell: any important chnage sor just version number ?
[17:54] <Riddell> whole different API
[17:54] <Riddell> soee: so do test it
[17:56] <sgclark> Riddell: all these package-name-doesnt-match-sonames safe to override?
[17:57] <Riddell> sgclark: yes I think so, lintian likes a library to be in its own package but often that's overkill
[17:57] <Riddell> and since we don't install the library headers nothing can use it anyway
[17:57] <sgclark> lol yeah, that would certainly be the case here
[18:05] <Riddell> sgclark: by the way new KF5 due on Friday
[18:05] <Riddell> sgclark: then the Plasma release which was due a couple of weeks ago is now due next week (and I think I'm the release manager)
[18:06] <sgclark> Riddell: ok, I will be out of town Saturday -Monday, will bring my laptop and try to do some. Can't promise though have no idea on connection.
[18:06] <sgclark> Riddell: will be fully available Tues+ though
[18:07] <Riddell> sgclark: lovely
[18:08] <sgclark> looking forward to plasma :)
[18:12] <sgclark> Riddell: how about these? calligraplan: unusual-interpreter #!kross
[18:13] <Riddell> sgclark: kross is an unusual interpreter but a perfectly valid one :)
[18:13] <sgclark> ok
[18:14] <Riddell> it's part of kdelibs and makes it easy to add scripting interfaces to your apps that can be used from python, ruby etc
[18:14] <Riddell> but I think only calligra uses it
[18:15] <sgclark> Riddell: this one? calligraplan: jar-not-in-usr-share 
[18:16] <sgclark> Riddell: and finally: 4 outdated-autotools-helper-file 3rdparty/google-breakpad
[18:16] <yofel> architecture independent files should usually be in /usr/share/ and as java isn't fully compiled that counts for jars too - not really important though
[18:17] <Riddell> sgclark: fixing the jar issue would mean working out how that calligra plugin looks and find the .jar file and fixing it, beyond what I want to do since it doesn't cause any problems having it in /usr/lib
[18:18] <sgclark> Riddell: ok I will leave as lintian error in case someone wants to look at it at a later time. 
[18:18] <sgclark> what about the last outdated-autotools
[18:19] <Riddell> sgclark: and we can't really update those autotool files since it's just a fork of a 3rd party project, would need to get google-breakpad to update its files but I presume there's a reason they need to work it like google-breakpad not being a very open project
[18:19] <sgclark> ok, leaving that as well
[18:19] <sgclark> Thanks! rebuilding now
[18:22] <sgclark> Riddell: or yofel: err one last item: http://paste.ubuntu.com/7152438/
[18:31] <shadeslayer> Riddell: I forgot my current password
[18:31] <shadeslayer> I had it stored as a encrypted file on my disk
[18:32] <shadeslayer> but Apple formatted my computer
[18:32] <yofel> sgclark: that should preferably be fixed... even if it won't cause problems most of the time
[18:33] <yofel> shadeslayer: I know I probably sound totally annoying, but ever heard of "backups" =P
[18:33] <shadeslayer> I forgot to back that particular thing up :P
[18:33] <yofel> lol
[18:33] <shadeslayer> I have everything else
[18:33] <shadeslayer> apart from .zshrc and some passwords
[18:33] <yofel> oh well, that's something at least ^^
[18:34] <shadeslayer> oh right, no .pbuilderrc too xD
[18:35] <Riddell> shadeslayer: don't you have an ssh key?
[18:35] <shadeslayer> Riddell: yes, but required sudo priviliges to switch to the kubuntu user
[18:42] <Sput> apachelogger: today
[18:42] <shadeslayer> I shall do testing tomorrow
[18:42] <shadeslayer> if there's testing to be done :)
[18:45] <Sput> apachelogger: tagging and tarballing at least; don't think I feel like writing release announcements tonight :P
[18:45] <Riddell> shadeslayer: lots of beta testing needed, although a respin needed first for your driver-manager update
[23:05] <Sput> apachelogger: http://quassel-irc.org/pub/quassel-0.9.3.tar.bz2 http://quassel-irc.org/pub/quassel-0.10.0.tar.bz2 and ScottK pinged
[23:06] <ScottK> It will be later tonight before I can look.
[23:07] <ScottK> Riddell: If you want ^^^ in for beta 2, someone else will probably need to package it.
[23:11] <Sput> ScottK: yeah, sorry, took a few hours longer than I hoped :/
[23:12] <Sput> then again, should still be two days until the freeze?
[23:52] <Riddell> Sput: what's the difference between the two
[23:55] <Sput> Riddell: 0.10.0 is a feature release, and the other one is the last bugfix release for 0.9 (it contains the fixes from 0.10, but no new features)
[23:56] <Sput> 0.9.3 is useful for distros which believe in this stable release and feature freeze thingy :)