[05:48] <ovidiu-florin> ahoneybun: pong
[05:48] <ovidiu-florin> ahoneybun: anything else than what we talked in Hangouts?
[08:53] <sitter> https://bugs.launchpad.net/bugs/1496121
[08:53] <sitter> Riddell: did plasmanm not get a rebuild?
[08:54] <Riddell> dunno, I've not looked at how the rebuild went yet
[09:16] <clivejo> Riddell yofel: missing files in Baloo - https://paste.kde.org/pfzzcbxmz - where do I put them?
[09:17] <clivejo> are the all dev files to go in not-installed?
[09:19] <Riddell> those dbus interfaces can go in the -dev package and the .mo files are translations and should probably go in baloo-kf5.install
[09:20] <clivejo> so I see :) - http://anonscm.debian.org/cgit/pkg-kde/frameworks/baloo.git/commit/?id=d64f2679761701285c2d0d7f1732edbd92295fd0
[09:21] <clivejo> maxy is a helpful chappie
[09:26] <sitter> [11:25] <kubuntu-ci> Project merger_baloo build #42: FAILURE in 6.7 sec: http://kci.pangea.pub/job/merger_baloo/42/
[09:27] <clivejo> sitter: it has missing files, Ive just uploaded a fix
[09:27] <sitter> you fix just broke the merger
[09:28] <clivejo> can you explain? :/
[09:28] <sitter> Riddell: ^
[09:31] <clivejo> how do I fix what I broke?
[09:32] <Riddell> one sec
[09:33] <yofel> clivejo: see http://kci.pangea.pub/job/merger_baloo/42/console
[09:33] <yofel> you'll have to manually merge kubuntu_wily_archive into kubuntu_unstable
[09:34] <yofel> ah right
[09:35] <yofel> sitter: could you please reset my CI login? I can't get in
[09:35]  * sitter has been thinking about wiring it to launchpad logins but ETOOLAZY
[09:35] <yofel> ^^
[09:37] <Riddell> clivejo: yep do the merge yourself, it was already fixed in a slightly different way in unstable branch
[09:37] <clivejo> I dont understand how I broke it
[09:37] <Riddell> clivejo: git pull; git checkout kubuntu_unstable; git merge kubuntu_wily_archive
[09:38] <Riddell> clivejo: when you commit to kubuntu_wily_archive the CI system will automatically try to merge that change into kubuntu_unstable
[09:38] <Riddell> if there's a clash in that merge you'll get a poke
[09:38] <Riddell> and you need to do it manually
[09:38] <kubuntu-ci> Yippee, build fixed!
[09:38] <kubuntu-ci> Project vivid_unstable_kaccounts-integration build #85: FIXED in 13 min: http://kci.pangea.pub/job/vivid_unstable_kaccounts-integration/85/
[09:38] <clivejo> but why did it fail?
[09:39] <clivejo> how was it slighty fixed in a different way?
[09:39] <Riddell> clivejo: do the merge and you'll see
[09:39] <kubuntu-ci> Yippee, build fixed!
[09:39] <kubuntu-ci> Project wily_unstable_dolphin-plugins build #10: FIXED in 17 min: http://kci.pangea.pub/job/wily_unstable_dolphin-plugins/10/
[09:39] <kubuntu-ci> Project vivid_unstable_kdeconnect-plasma build #98: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/vivid_unstable_kdeconnect-plasma/98/
[09:40] <clivejo> CONFLICT (content): Merge conflict in debian/baloo-kf5-dev.install
[09:41] <yofel> right, now edit the file
[09:41] <clivejo> ok
[09:41] <clivejo> someone added them file by file
[09:41] <clivejo> and I followed maxy by adding the folder
[09:42] <Riddell> go with your way then
[09:42] <Riddell> edit that file manually
[09:42] <Riddell> git add it then git commit it then git p ush it
[09:42] <clivejo> can I use git gui?
[09:43] <Riddell> dunno, probably, I use qgit sometimes but not usually for commits
[09:44] <clivejo> ok I think thats done it
[09:45] <clivejo> and baloo is green on qa - happy days
[09:58] <clivejo> are you guys working on apps?
[10:00] <Riddell> nobody is so far
[10:01] <clivejo> Riddell: http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.14.0_wily.html
[10:01] <clivejo> would you cast your expert eye over them please
[10:02] <clivejo> Riddell: yofel was doing them last night, but couldnt get login to pause CI
[10:03] <yofel> I did nothing
[10:03] <clivejo> in fear of sitter shouting and the time of night he left it :)
[10:03] <Riddell> clivejo: khtml could do with symbols being updated
[10:03]  * sitter pets yofel
[10:04] <sitter> on that note
[10:04] <Riddell> kitemmodels too
[10:04] <sitter> I am going to enable symbol tracking in CI again
[10:04] <Riddell> clivejo:  kwidgetsaddons three
[10:05] <clivejo> ok
[10:08] <clivejo> yofel is is going to implement my new idea, DUS
[10:09] <yofel> I never said that
[10:09] <yofel> and the parser is perl
[10:09] <clivejo> LOL
[10:11] <sitter> do not touch the pyrl
[10:11] <sitter> it's dangerous
[10:12] <clivejo> dont worry sitter, I is an expert ;)
[10:13] <sitter> I presume we are talking symbols management?
[10:14] <clivejo> yeah, but Im only joking
[10:14] <sitter> because the much bigger problem with that is that it has no autotests so any change might randomly break things
[10:14] <sitter> which seems slightly undesirable with symbols :)
[10:31] <clivejo> Riddell: hows that?
[10:31] <Riddell> clivejo: how's what?
[10:32] <clivejo> those three are done, the qa list
[10:33] <Riddell> clivejo: foo khtml broke on amd64
[10:34] <Riddell> I guess it needs some fancy use of that symbol update script for both arches
[10:34] <Riddell> sitter: any thoughts on what's up with this? http://mobile.kci.pangea.pub:8080/job/vivid_unstable_solid_pub/
[10:34] <yofel> that's not fancy, that's what you should always do
[10:35] <sitter> Riddell: yes, read the mail I sent to bluesystems list about exactly this
[10:35] <yofel> fixing architecture mismatches later on is a lot more work
[10:35] <clivejo> yofel: will you teach me how?
[10:35] <yofel> clivejo: you feed all buildlogs into batchpatch
[10:36] <clivejo> so download both the buildlogs and run it against each of them in turn?
[10:36] <yofel> no, pass all of them in one command
[10:36] <yofel> just do something like buildlog* at the end
[10:36] <clivejo> can you show me an example of the command you run?
[10:37] <sitter> yofel: that's not gonna work
[10:37] <sitter> the logs need to be in order
[10:37] <yofel> in what order?
[10:37] <sitter> at least if you explicitly define the architecture list
[10:37] <yofel> ah, I never do that
[10:38] <sitter> in that case I'll shut up :P
[10:38] <yofel> ^^
[10:38] <clivejo> sitter: how would you do it?
[10:38] <sitter> hm
[10:38] <sitter> ubottu: info libtelepathy-qt5-dev
[10:39] <sitter> http://people.ubuntu.com/~apachelogger/tmp/symbol/symbolpatch
[10:39] <sitter> ubottu: find libtelepathy-qt5-dev
[10:39] <clivejo> *coughs*
[10:39] <sitter> that bot doesn't like me :(
[10:40] <sitter> pft
[10:40] <sitter> Riddell: our telepathyqt is too old for kdeconnect master :(
[10:40] <sitter> someone should talk to apolo about this ;)
[10:41]  * yofel -> lunch
[10:42] <clivejo> ah lunch, that reminds me I must fill the cattle drinker
[10:42] <sitter> Riddell: is it possible that you didn't symlink plasma-mediacenter from kde-extras to plasma?
[10:43] <Riddell> sitter: in debian git ?
[10:44] <sitter> yes
[10:46] <BluesKaj> Hiyas all
[10:49] <Riddell> sitter: I did not, I'll do that now
[10:52] <Riddell> sitter: symlink added
[11:02] <sitter> Riddell: have you given any thought how to do builds in jenkins without CI?
[11:03] <Riddell> sitter: I don't understand, you mean with tars?
[11:03] <sitter> yep
[11:04] <Riddell> sitter: replace the _src job with one that uses uscan?
[11:04] <sitter> well yes but how :P
[11:04] <Riddell> although I guess that wouldn't work with hidden tars on kde server but not on download yet
[11:04] <sitter> also what if uscan isn't enough?
[11:04] <sitter> e.g. kde releases that aren't public yet
[11:05] <Riddell> let it fall back to using ssh
[11:05] <sitter> that needs code abstraction somewhere tough
[11:06] <Riddell> why would it be any harder than working out how to check it out of git?
[11:06] <Riddell> I guess checking it out of git is built into jenkins somewhat?
[11:06] <sitter> actually this is a bit shitty because we handle git-source in jenkins but we'd be doing the others in ruby
[11:06] <sitter> so yeah, the separation hurts a bit from an architecture POV
[11:06] <Riddell> or python.  it could be written in python.
[11:06] <sitter> it can't
[11:06] <Riddell> oh
[11:07] <Riddell> por que no?
[11:07] <sitter> because it's a shit language
[11:07] <sitter> that's why
[11:07] <Riddell> ah I see
[11:07] <sitter> also on the more practical side we have no provisioning for python deps
[11:08] <sitter> eitherway that doesn't matter
[11:09] <sitter> so on the jenkins job side we already have tech in place that can sort of tell apart a packaging repo from an upstream repo IIRC and will simply work with only packaging but no upstream
[11:09] <sitter> so it would only use the packaging repo and then hand over to ruby or whatever
[11:10] <sitter> inside there we'd have a couple of steps to generate the source: 1. get the source and tar if necessary -> 2. merge packaging into source- > 3. mangle packaging to CI -> 4. buildpackage -S
[11:11] <sitter> 3 must not really happen for non CI builds
[11:11] <Riddell> this sounds good
[11:13] <sitter> and 1 would need to have different classes with a factory GitSource(copy from clone dir, gen orig.tar), TarSource (uscan > arbitrary code stored somewhere for ssh)
[11:13] <sitter> former would eventually run through releasme to get l10n
[11:14] <Riddell> I know that's been your hope for a long time but I would guess it's still a bit long term
[11:15] <Riddell> releaseme still needs extra stuff added, like all the plasma scripts I have
[11:15] <Riddell> and not everything uses releaseme
[11:16] <sitter> well
[11:16] <sitter> first step is using releasme's l10n classes to get l10n for our clones :P
[11:16] <sitter> which should be somewhat trivial
[11:17] <sitter> albeit super low priority
[11:20] <Riddell> and super slow
[11:20] <Riddell> it's still a good chunk of the plasma release process getting l10n
[11:21] <sitter> Riddell: didn't we make it fast?
[11:21] <Riddell> sitter: sure it's lots better than before
[11:21] <Riddell> takes an hour rather than 4 hours
[11:21] <sitter> an hour seems a bit extreme though
[11:21] <sitter> ah
[11:21] <sitter> including sources
[11:21] <Riddell> but if you have everything in CI doing that it'll take quite a while
[11:21] <sitter> well
[11:22] <sitter> you've got some 30 sources in plasma?
[11:22] <Riddell> yes
[11:23] <sitter> that's 2 minutes per source. seems pretty reasonable TBH
[11:23] <sitter> so say 1 minute for l10n which is pretty reaosnable
[11:23] <Riddell> ok, you know CI better than me
[11:23] <sitter> the thing with CI is that it would be somewhat parallel
[11:24] <sitter> so it wouldn't be idle building sources for 60 minutes but more evenly spread it out
[11:25] <Riddell> right
[11:25] <sitter> kci going down for maintenance in ~15 minutes
[11:49] <shadeslayer> sitter: Isnt vcsbuilder exactly what you described above?
[11:50] <sitter> no
[11:51] <sitter> it abstracts on the concept of source building
[11:51] <sitter> which is actually too high
[11:51] <sitter> as I said, there's 4 steps only 2 deviate between source types
[12:01] <shadeslayer> I thought that's what vcsbuilder was going to become, hmm ...
[12:02] <sitter> so did I, but it's not quite what we need :P
[12:02] <shadeslayer> :)
[12:02] <sitter> or maybe it is, but then we still need a base of sorts to contain the shared 2 steps
[12:02] <shadeslayer> *nod*
[12:02] <sitter> logic abstraction generally is nicer to read than design abstraction though
[12:03] <shadeslayer> sitter: BTW where do I move that mgmt folder out to?
[12:03] <sitter> so we have one source class it just has behavior properties that change depending on the environment it is used in or something
[12:03] <shadeslayer> ci/mgmt ?
[12:03] <sitter> shadeslayer: mgmt/
[12:03] <sitter> don't matter much I guess
[12:08] <sitter>     @data = YAML.load_file("#{File.dirname(__FILE__)}/data/maintainer.yaml")
[12:08] <sitter> shadeslayer: that's wrong I think btw
[12:08] <sitter> in build_source
[12:08] <sitter> oh wait it is in there
[12:08] <sitter> not a fan of data in lib/ :P
[12:31] <shadeslayer> sitter: added to list of things to fix
[12:47] <sitter> Riddell, yofel: shouldn't marble-qt be dead?
[12:47] <sitter> 00:00:49.506 KCI-W :: W: marble-qt: empty-binary-package
[12:47] <Riddell> sitter: who says it's empty? it gets built when I build it
[12:48] <sitter> CI says
[12:48] <sitter> it also has no install file
[12:48] <sitter> so I don't see how it can contain anything
[12:48] <yofel> The original plan was to kill it, but I never finished that - and someone said that it might still be useful
[12:49] <Riddell> I did have to add one I remember
[12:49] <sitter> debian/not-installed:# marble-qt
[12:49] <sitter> debian/not-installed:./usr/bin/marble-qt
[12:49] <yofel> but I'm not quite sure if QTONLY needs a double build
[12:49] <sitter> Riddell: you did not push then
[12:51] <Riddell> sitter: debian/marble-qt.install is in kubuntu_unstable
[12:51] <Riddell> sitter: which branch are you on?
[12:51] <sitter> wily_archive Oo
[12:52] <sitter> [remote "origin"]
[12:52] <sitter>         url = debian:applications/marble
[12:53] <sitter> Riddell: http://anonscm.debian.org/cgit/pkg-kde/applications/marble.git/commit/?h=kubuntu_unstable&id=c5615d60b1debe15c3255cd23085e4b174c32690
[12:53] <sitter> I would say something about the fact that there is stuff in the commit that has nothing to do with the changelog but I'll just pretend I dont' care anymore
[12:58] <Riddell> pushed marble-qt.install to wily_archive, it'll get updated when someone does applications 15.08.1
[13:00] <sitter> ok
[14:22] <yofel> when I read lp 1496121 I wonder why we put so much effort in symbol tracking if other people end up braking stuff anyway.. *sigh*
[14:22] <yofel> *breaking
[14:24] <yofel> actually, perfect example
[14:24] <yofel> clivejo: THAT ^ is the reason why we have symbol files
[14:47] <sitter> that's why we need ACC ADT, no? :P
[14:48] <sitter> symbols files we need to do precise link dependencies
[14:51] <yofel> well, true, for c++ we really need ACC
[15:07] <tsdgeos> we need AC/DC!
[15:09] <yofel> lol
[15:10]  * clivejo pictures sitter head banging to AC/DC
[15:11]  * clivejo giggles
[16:24] <ovidiu-florin> yofel: ping
[16:30] <ovidiu-florin> anyone here?
[17:10] <yofel> ovidiu-florin: HM?
[17:10] <yofel> oops
[17:12] <yofel> drat, back in a few mins
[17:50] <soee> new frameworks almost ready ? :)
[18:07] <soee> Riddell: shouldn't Frameworks 5.12 for vivid be removed already from stagin ppa (https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks/+packages) as they were released ?
[18:24] <clivejo> soee: nope they arent ready, symbol issues
[18:48]  * ahoneybun has rebuilt his linode server
[18:50] <clivejo> what happened to it?
[18:57] <ahoneybun> when I made it I did it wrong or something
[18:57] <clivejo> oh
[19:36] <clivejo> have apps 15.08.1 been uploaded yet?
[19:42] <clivejo> yofel Riddell ^
[19:55] <ahoneybun> weird Plasma does not like you using TWRP
[19:55] <ahoneybun> I crashed it lol
[19:57] <clivejo> how do I fix khtml?
[19:58] <clivejo> can I just copy debian's soluation?
[20:09] <yofel> sounds reasonable
[20:10] <clivejo> yofel: how would I do a revert of my commit
[20:10] <yofel> I wouldn't revert anything but just copy&paste that line from master into your file
[20:10] <clivejo> I would like to do it properly
[20:11] <clivejo> for practice
[20:11] <clivejo> revert the commit, grab the two build logs and feed them into pkgkde-symbolshelper
[20:12] <clivejo> you think Im crazy?
[20:12] <yofel> no, just it'll take about half an hour if you want to leave the builds to launchpad until we're done...
[20:13] <yofel> and it won't even work in the archive because armhf and powerpc will be missing from the symbol annotation
[20:13] <yofel> hm...
[20:14] <clivejo> what should I do?
[20:14] <yofel> I just noticed another thing
[20:14] <yofel> _ZNK3KJS7JSValue9getNumberEv@Base 5.14
[20:15] <yofel> the upstream version is 5.14.0, not 5.14. Has no real impact in this case, but please try to use the *exact* version next time
[20:16] <yofel> clivejo: what *I* would do is: take the symbol from the debian file, put that into ours, fix the version to say 5.14.0 just to match what we're doing and remove any architectures we don't have
[20:19] <clivejo> how did I introduce that, by using pkgkde-symbolshelper batchpatch -v 15.14 khtml*.build?
[20:20] <yofel> probably
[20:20] <yofel> actually, you only gave it the i386 build log
[20:20] <yofel> # SymbolsHelper-Confirmed: 5.14 i386
[20:21] <yofel> shows that
[20:22] <clivejo> I give it the amd64 first, then the i386 failed to build so I gave it the i386 buildlog
[20:22] <clivejo> didnt realise that sometimes you have to give it the two buildlogs
[20:23] <clivejo> I have the 386 one so if I download the amd64 and apply both would that fix it?
[20:24] <yofel> always try to feed it all build logs. symoblshelper can only determine information for the logs it has, so as it saw a symbol missing on i386, but didn't have the amd64 log which said that no symbols are missing, it couldn't figure out that the symbol is architecure-specific
[20:26] <clivejo> it is failing on the amd64, so if I feed it with the amd64 buildlog will it remove the i386 symbols?
[20:27] <yofel> if you do that, you'll again have a symbol diff on i386 with an added symbol
[20:27] <yofel> you need to feed it ALL logs
[20:28] <clivejo> ok
[20:29] <clivejo> grabbing amd64 now
[20:30] <clivejo> so use -v 5.14.0 ?
[20:30] <yofel> yes please
[20:30] <clivejo> or should I leave it and "learn"
[20:30] <yofel> nah, if you're already at it finish it
[20:32] <clivejo> pkgkde-symbolshelper: warning: * patch 'libkf5khtml5_5.14.0-0ubuntu1~ubuntu15.10~ppa1_i386 (--- debian/libkf5khtml5.symbols)' for i386 ... FAILED.
[20:32] <clivejo> so that is expected as I had already applied the i386 buildlog?
[20:33] <clivejo>  (arch=i386)_ZNK3KJS7JSValue9getNumberEv@Base 5.14 (was arch=)
[20:34] <yofel> well, it did the right thing at the end
[20:34] <clivejo> you reckon thats fixed it?
[20:34] <yofel> for the PPA yeah
[20:35] <yofel> will most likey throw warnings in the archive, but we can fix that later
[20:35] <clivejo> so commit, push and rebuild?
[20:35] <yofel> yep
[20:35] <clivejo> there is another file has changed in git gui
[20:36] <yofel> huh?
[20:36] <clivejo> a .orig file
[20:36] <clivejo> is that a git file?
[20:36] <yofel> uhm, no
[20:36] <yofel> something might've gone wrong when applying the diff
[20:37] <clivejo> libkf5khtml5_patched.symbolsJ212jy,orig
[20:37] <yofel> any errors in the real symbol file?
[20:37] <clivejo> nope just two diffs
[20:37] <yofel> then delete the file
[20:37] <clivejo> +# SymbolsHelper-Confirmed: 5.14 amd64 i386
[20:38] <clivejo> and + (arch=i386)_ZNK3KJS7JSValue9getNumberEv@Base 5.14
[20:38] <clivejo> if I just ignore it and dont stage it
[20:41] <clivejo> is there an easy way to download the buildlogs?
[20:43] <yofel> I personally go to the status page, right click on arch > copy link address, then wget the file
[20:43] <clivejo> thats the way I been doing it
[20:43] <yofel> we could write a script that does that, and we have one for the archive, but so far nobody bothered
[20:46] <clivejo> yofel: did you get your CI login sorted?
[20:46] <yofel> yep
[20:46] <clivejo> upload apps?
[20:46] <yofel> no motivation...
[20:47] <clivejo> oh?
[20:47] <clivejo> can I?
[20:47] <yofel> uh.. lets see if I can figure out where the pause button is
[20:48] <clivejo> http://kci.pangea.pub/view/mgmt/job/mgmt_pause_integration/ ?
[20:49] <yofel> there
[20:49] <clivejo> you did something :)
[20:50] <yofel> I clicked on a button :P
[20:50] <clivejo> I clicked the button too, but it doesnt know who I am :P
[20:50] <yofel> ok, so if you want to upload apps go ahead
[20:51] <clivejo> you sure you dont want to?
[20:51] <yofel> yes
[20:51] <clivejo> dont want to fall out over it :P
[20:52] <yofel> you know the git script better than I do, and I don't want to involve myself into something long-running right now
[20:53] <yofel> just remember to put the bottom of the upload script output with the errors on the pad
[20:53] <clivejo> so bzr merge to refresh my kubuntu-automation folder?
[20:54] <yofel> probably not needed, but do it anyway to be on the safe side
[20:55] <clivejo> someone has modified ppa-build-status
[20:55] <clivejo> was that you on weegie?
[20:56] <yofel> yep, the log would tell you that as well :P
[20:56] <clivejo> I didnt see the log
[20:56] <yofel> bzr log --limit 1
[20:56] <clivejo> so I need to commit that to my personal branch?
[20:57] <clivejo> Im only seeing myself!
[20:57] <yofel> I guess? I'm not too familiar with the branched bzr workflow
[20:58] <clivejo> weird Im not seeing that you made that change
[20:58] <clivejo> would you make it as Riddell?
[20:59] <clivejo> maybe I should delete my local folder and pull it from bzr
[20:59] <yofel> does 'bzr log -n 0' show it?
[21:01] <clivejo> nope
[21:01] <yofel> did you do a bzr pull?
[21:01] <clivejo> nothing to pull
[21:02] <clivejo> this is weird
[21:02] <yofel> no idea then. As I said, I don't really know how to use bzr like that
[21:02] <clivejo> me enither
[21:03] <clivejo> you are definately there - http://bazaar.launchpad.net/~kubuntu-packagers/+junk/kubuntu-automation/changes/616?start_revid=616
[21:05] <clivejo> rm it and recreated
[21:05] <clivejo> you are there now!
[21:09] <clivejo> humm it wants to remove libkexiv2 from the list
[21:09] <yofel> yeah, dunno why
[21:11] <clivejo> if I add it back into the applications-wily will it break it?
[21:13] <yofel> no, the tarball is on depot from what I see
[21:17] <clivejo> something badly worng
[21:17] <clivejo> [21:18] <yofel>  akonadi-15.08.1.tar.xz
[21:18] <yofel> it's there
[21:18] <clivejo> I know
[21:18] <clivejo> but the script cant see it
[21:19] <yofel> anyway, I'm off for the evening
[21:19] <yofel> gn
[21:19] <clivejo> ok, have a good evening
[21:19] <clivejo> O/
[21:41] <clivejo> Riddell: ping
[21:53] <Riddell> hi clivejo
[21:57] <clivejo> howdy
[21:57] <clivejo> is the staging ppa ready for these apps (15.08.1)
[21:58] <clivejo> Riddell: ^
[21:58] <Riddell> clivejo: as ready as it'll ever be :)
[21:58] <Riddell> clivejo: have you got them ready to upload?
[21:58] <Riddell> clivejo: how's frameworks doing?
[21:59] <clivejo> yodel helped me fix khtml earlier
[21:59] <clivejo> I think its good to go ?
[21:59] <clivejo> yofel even
[21:59] <Riddell> lovely
[22:00] <clivejo> I see 15.08.1 fixes that problem in ark
[22:00] <Riddell> clivejo: if you want to do the next step of uploading it to ubuntu you can run the comment "./ubuntu-archive-upload -v 5.3.2 -t ~/src/plasma/ -r plasma" (but with bits changed as relevant)
[22:00] <Riddell> then send a tar of all the .changes files to me or someone to sign them
[22:00] <Riddell> or I'll just do it tomorrow
[22:01] <clivejo> Riddell: there was talk that it cant go into wily?
[22:01] <clivejo> due to feature freeze?
[22:01] <Riddell> clivejo: you could also file a feature freeze exception bug request
[22:01] <clivejo> doesnt bother me
[22:02] <clivejo> surely it should come from someone on KC?
[22:02] <clivejo> but needs testing 
[22:02] <clivejo> god knows what mistakes Ive made with the symbols
[22:03] <Riddell> clivejo: nope it should come from any packager and be approved by someone on release team (like me)
[22:03] <Riddell> and yes you should install and test frameworks indeed
[22:04] <clivejo> Im keen to test apps
[22:05] <Riddell> and upload that to the staging-applications PPS
[22:05] <Riddell> PPA
[22:05] <Riddell> my head is collapsing, I need to sleep
[22:05] <clivejo> Riddell: do you know why it wants to remove libkexiv2 from the packaging list
[22:05] <clivejo> it being the script
[22:06] <Riddell> no idea, it is in there http://download.kde.org/stable/applications/15.08.1/src/
[22:06]  * Riddell snoozes
[22:06] <clivejo> night night