[00:37] <dodger> valorie: from what some of my czech colleagues were saying that should be around 35 euros depending on which stations you leave from and go to
[01:37] <valorie> thanks, dodger
[01:38] <valorie> effing flash in chrome slowed my whole box to a crawl, so I had to quit
[01:38] <valorie> the day of a flash update it always seems to be squiffy
[01:40] <valorie> and the bus website itself was what caused the problem I think
[01:42] <valorie> seems best to fly to Vienna and take the bus from there, rather than trying to fly into brno itself
[02:21] <ScottK> We didn't talk about Qt5 5.2 or 5.3 for this cycle. 
[02:31] <dodger> valorie: are you looking at this one for the bus?
[02:31] <dodger> http://czech-transport.com/index.php?id=12755
[02:32] <valorie> no, it was different page
[02:32] <valorie> student something
[02:32] <valorie> looks like the same bus though
[02:32] <dodger> there's also a train from vienna to brno, which is probably quicker and more comfortable
[02:33] <valorie> hmmm, people say that the bus is better because of wifi?
[02:33] <dodger> yeah, there is the wifi situaiton
[02:33] <dodger> but even on the bus you only get wifi during the travel time in the czech republic, according to the website
[02:33] <valorie> anyway, I don't have to decide now
[02:34] <valorie> I just wanted to ask Canonical for the money
[02:34] <valorie> now I've sent the form, so thank you for the information
[02:34] <dodger> let me know if they do it
[02:35] <valorie> cool
[02:35] <dodger> if not, i'll be happy to pitch in and sponsor you for the bus or train ticket :)
[02:35] <valorie> now to find someone I know in Vienna
[02:35] <valorie> to hang out with for a day or so
[02:36] <valorie> aren't you sweet!
[02:38] <valorie> dodger: do you live in the Czech Rep. ?
[02:38] <dodger> no, I'm originally from Germany, but live in California
[02:39] <dodger> until next week, which is when I'm moving to North Carolina
[02:39] <valorie> wow, that will be a culture change!
[02:40] <valorie> weather change, too
[02:40] <dodger> a bit, yes :P 
[02:40] <dodger> i've lived in texas and florida before, so i'm familiar with both culture and weather :P
[02:40] <valorie> do you live in SoCal, or in the north?
[02:40] <ScottK> Fewer earthquakes though. 
[02:40] <dodger> about 35 miles north of san francisco, close to santa rosa
[02:40] <valorie> oh, pretty
[02:41] <valorie> ScottK: so true
[02:41] <dodger> love the area... leaving makes me a bit sad
[02:41] <dodger> but i'll take a 5% salary hike combined with a 40% reduction in cost of living
[02:41] <valorie> whole left coast is gonna shake right into the ocean one of these millenia
[02:41] <valorie> oh, well worth it then!
[02:42] <dodger> yeah, i'm moving for a job... i think it's worth it just because of the new employer
[02:43] <dodger> although i'm not looking forward to moving per se, hate doing that
[02:43] <valorie> ah, I like moving
[02:43] <valorie> but then I've not done it often
[02:43] <dodger> i like the sort of personal adventure part of it
[02:43] <valorie> chance for a fresh start, with fresh paint
[02:44] <valorie> good time to pitch extra belongings, etc.
[02:44] <dodger> but loathe the logistics
[02:44] <dodger> i've moved 7 times over the last 14 years... i'm about ready to stop
[02:44] <valorie> yes, it's a bit of a pain
[02:45] <dodger> oh ain't it true! it's amazing how much unnecessary stuff we accumulated over a few years
[02:45] <valorie> I've only moved 5 times total
[02:46] <valorie> trying to slim down the stuff in this house to make the next move easier, if it ever happens
[02:46] <dodger> the worst is packing everything and then not knowing where stuff is
[02:46] <valorie> write on every box!
[02:46] <dodger> luckily this time a bunch of people will just show up, pack everything, ship it, and unpack it again
[02:47] <valorie> oh nice
[02:47] <dodger> can't tell you how happy i am about that part :P
[02:51] <valorie> I've never had professional help, but it does sound much more worry-free
[02:52] <dodger> there's always the time after when you've got 80% of the stuff unpacked and are left with 30 boxes, none of which get unpacked for two years
[02:52] <valorie> oh god yes
[02:53] <dodger> i say  if we haven't looked at it for two years, it might as well just disappear
[02:53] <valorie> right, and that "30 boxes" is what I want to unload NOW
[02:53] <valorie> so it never has to be moved anywhere but Value Village or the dump
[02:54] <valorie> ok, I need to get afk and walk for a bit
[02:54] <valorie> good to talk with you dodger, and thanks for the help and generous offer
[02:55] <dodger> enjoy your walk, and let me know - i meant it
[03:47] <ScottK> shadeslayer: Still needs some kind of "here's now you test it" in the libkscreen SRU.
[06:10] <soee> good morning
[06:44] <lordievader> Good morning.
[06:44] <soee> good morning lordievader
[06:46] <lordievader> Hey soee, how are you?
[06:47] <soee> lordievader: im fine, second rainy day here in PL though :) how are you ?
[06:47] <lordievader> Doing all right :)
[06:48] <soee> :)
[06:48] <jussi> o/
[06:49] <lordievader> Hey jussi, how are you doing?
[06:49] <jussi> lordievader: alive...
[06:50] <valorie> more {{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}}}}}} for jussi
[06:50] <valorie> alive does beat the alternative
[06:50] <valorie> just remember that
[06:51] <lordievader> It starts with being alive ;)
[06:52] <valorie> it does
[09:49] <shadeslayer> ScottK: re libkscreen done
[09:50] <shadeslayer> https://bugs.launchpad.net/ubuntu/+source/libkscreen/+bug/1319084
[10:12] <shadeslayer> Riddell: I don't see a plasma 5 release yet :)
[10:16] <Riddell> shadeslayer: you don't? where are you looking?
[10:16] <Riddell> http://dot.kde.org/2014/05/13/plasma-next-beta-ready-testing
[10:17] <Riddell> http://kde.org/announcements/announce-frameworks5-beta1.php
[10:17] <shadeslayer> second one still has double panels?
[10:19] <Riddell> wait, I mean http://kde.org/announcements/announce-plasma-next-beta1.php
[10:19] <Riddell> no double panels on that
[10:19] <shadeslayer> Riddell: http://kde.org/announcements/plasma-next-beta/ss-wallies.png
[10:19] <shadeslayer> double panel
[10:20] <Riddell> hmm
[10:20] <Riddell> shadeslayer: press F5
[10:20] <shadeslayer> cheers :)
[10:22] <soee> this beta is/will be somehow available for kubuntu through ppa ?
[10:22] <Riddell> soee: yep, it's going into the experimental PPA, still lots of work to be done though
[10:23] <soee> ah thought so, is it buggy atm or usable ?
[10:24] <Riddell> both I'd say
[10:26] <soee> ok good to know ;) thank you
[10:59] <BluesKaj> 'Morning folks
[11:24] <ScottK> shadeslayer: Thanks.  Accepted.
[11:33] <sgclark> where are these merges suppose to go?
[11:33] <Riddell> sgclark: into the ubuntu archive
[11:33] <sgclark> requestsync hates me
[11:33] <Riddell> sgclark: so if you have a merged package just pass it onto someone who can check and upload it
[11:34] <sgclark> so the kubuntu version is newer, it complains that that version does not exist in sid
[11:34] <sgclark> Riddell: gwenview https://launchpad.net/~scarlett-7/+archive/kubuntu-ppa
[11:36] <ScottK> Riddell: Do we want to push for Qt 5.3 in Utopic?  We forgot to discuss on the call (at least when I was there).
[11:36] <sgclark> Riddell: also libksysguard and kinfocenter are ready for you in bzr
[11:36] <Riddell> ScottK: yes we do, I was taking that as assumed
[11:36] <Riddell> sgclark: lovely, I uploaded  and kinfocenter yesterday
[11:37] <ScottK> We'll probably need to wrestle Canonical over it.
[11:37] <ScottK> I'll write a mail.
[11:38] <sgclark> Riddell: I set up another computer for packaging, so I will work on one of each again
[11:39] <Riddell> ScottK: do they not want it?
[11:39] <ScottK> Don't know for sure.
[11:39] <ScottK> The were reluctant upgraders last time.
[11:42] <rawi> Hi, folks, just coming from #kubuntu to you, the devs, with a big problem
[11:42] <rawi> I'm on kubuntu 14.04 with kde-ppa and backports enabled
[11:42] <rawi> I got today almost the whole kde updated
[11:43] <rawi> after that I'm not able any more to copy/paste a file to a mounted samba share, neider with Krusader, nor Dolphin, nor Konqueror
[11:44] <Riddell> yofel: ↑
[11:44] <shadeslayer> Riddell: actually not in the archive
[11:44] <shadeslayer> re mrege
[11:44] <shadeslayer> Riddell: because I thought we wanted to wait for 4.13.80
[11:44] <yofel> I don't remember touching anything related to samba
[11:45] <rawi> I see the Share listings, I can open und edit files and I can even create new files with rightklick+Neew_File
[11:45] <yofel> lets see if I can mount something here
[11:46] <rawi> trying to copy/paste files gives error "Disk full"
[11:47] <rawi> and Krusader shows above the panel Mt.Man: working...
[11:47] <rawi> like here http://imagebin.org/310804
[11:48] <alket> why did you switch from rekonq to firefox ? 
[11:48] <yofel> hm, copying to and from smb:// works for me here
[11:49] <yofel> alket: mostly because qtwebkit (which is used by rekonq) is a security support nightmare
[11:49] <rawi> oh, I usualy mount the shares befor from commandline
[11:50] <yofel> ok, I have that to, let me check
[11:50] <yofel> *too
[11:50] <Riddell> shadeslayer: what's not in the archive?
[11:50] <alket> yofel: thank you , firefox crashes for me often , but in rekonq seems many things don't work like adblock etc.
[11:51] <alket> what about konqueror ? is it any good ?
[11:51] <shadeslayer> Riddell: the merges, please don't push them to the archive just yet
[11:51] <alket> from security side ?
[11:51] <shadeslayer> alket: hah, probably worse than qtwebkit
[11:51] <shadeslayer> Riddell: the idea was to wait for 4.13.80
[11:51] <alket> so any good KDE web browser ?
[11:52] <yofel> rawi: there we go, error
[11:52] <shadeslayer> none that I am aware of
[11:52] <Riddell> shadeslayer: wait until 4.13.80 before doing any merges? I thought you wanted to do all the merges before 4.14 alphas
[11:52] <shadeslayer> Riddell: wait till 4.13.80 to do uploads
[11:53] <rawi> yofel: I just tryed with direct protocol smb:// and it works that way
[11:53] <Riddell> shadeslayer: so you want to merge it in bzr but not upload? why?
[11:53] <rawi> only not if the shares were already mounted before
[11:53] <yofel> right, here too, lets see if the logs tell anything
[11:54] <ScottK> alket: We decided having a browser with reasonable security support was more important than having a KDE based browser.  There are zero choices that are both.
[11:54] <alket> ok , thank you all 
[11:54] <yofel>  29 13:51:26 dolphin(9005)/kio (KIOJob)^[[0;34m KIO::CopyJobPrivate::statCurrentSrc^[[0m: Stating finished. To copy: 125920 , available: 0
[11:55] <yofel> looks like kio is doing something wrong
[11:56] <rawi> yofel: sorry, this is a bit to high for me, but I'm glad that you could see it
[11:58] <shadeslayer> yofel: mind sending it upstream if you can reproduce it?
[11:58] <yofel> shadeslayer: I'm already looking though b.k.o
[11:58] <shadeslayer> cheerio
[11:58] <ScottK> Riddell: Mail sent re Qt5 5.3.  Let's see what people say.  It may turn out to be easy.
[12:03] <shadeslayer> kubotu: newversion kdeconnect 0.5.2
[12:03] <kubotu> https://bugs.launchpad.net/bugs/1319365
[12:07] <shadeslayer> argh :(
[12:07] <shadeslayer> kdeconnect_0.5.2-0ubuntu1_source.changes rejected
[12:11] <rawi> yofel: is anything I could help with in the kio issue?
[12:12] <yofel> I don't think so, I'll give you the report after I'm done filing it if you have anything to add
[12:13] <rawi> yofel: thank you very much!
[12:13] <yofel> rawi: kde 334761
[12:21] <rawi> yofel: would it help to say, that the same is happening in Krusader and Konqueror as well? Probably not, because is the same infrastructure...
[12:21] <yofel> well, won't hurt if you do, but I would assume they all use kio
[12:21] <rawi> thanks again
[12:27] <shadeslayer> apachelogger: http://people.ubuntu.com/~rohangarg/upload/kdeconnect/trusty/kdeconnect_0.5.2-0ubuntu0.1.dsc && http://people.ubuntu.com/~rohangarg/upload/kdeconnect/utopic/kdeconnect_0.5.2-0ubuntu1.dsc
[12:27] <shadeslayer> plz
[12:29] <apachelogger> no
[12:29] <apachelogger> shadeslayer: apply for motu
[12:29] <shadeslayer> plzzzz
[12:29] <apachelogger> shadeslayer: apply for motu
[12:34] <shadeslayer> ScottK: ^^ plz
[12:34] <shadeslayer> oh
[12:34] <shadeslayer> won't work
[12:34] <apachelogger> don't
[12:34] <shadeslayer> who's going to approve then :P
[12:34] <apachelogger> shadeslayer: apply for motu
[12:34] <shadeslayer> Riddell: plzz ^^
[12:34] <apachelogger> don't
[12:34] <apachelogger> shadeslayer: apply for motu
[12:34] <shadeslayer> won't become one in 1 hour
[12:35] <apachelogger> if you apply for motu now, I may feel more like uploading that package
[12:35] <shadeslayer> I shall apply tomorrow?
[12:35] <apachelogger> no
[12:35] <apachelogger> now
[12:36] <Riddell> shadeslayer: what what?
[12:41] <shadeslayer> apachelogger: I'll have to write a wiki page ufff
[12:41] <shadeslayer> apachelogger: how about I do this when I have time tomorrow
[12:41] <shadeslayer> I'd rather be packaging sddm for neon now :P
[12:42] <shadeslayer> ohm
[12:42] <shadeslayer> apachelogger: plus, I've missed the 1 week window for the meeting on the 19th
[12:43] <apachelogger> I am sure you can ask nicely
[12:44] <shadeslayer> rawi: fwiw imagebin is on the badware blacklist
[12:47] <rawi> shadeslayer: sorry, I'm new to IRC and that's what ubottu in #kubuntu recomended to me...
[12:48] <shadeslayer> :)
[13:50] <shadeslayer> https://bugs.launchpad.net/ubuntu/+source/ktp-contact-list/+bug/1319085
[13:50] <shadeslayer> could someone check if that's fixed in trusty for them ^^
[13:57] <shadeslayer> apachelogger: ^^
[13:59] <shadeslayer> apachelogger: dude, did you see the amarok valgrind I sent you yesterday
[14:00] <apachelogger> shadeslayer: I did not because the paste was deleted
[14:00] <apachelogger> ALSO I remembered that I saw this crash too
[14:00] <shadeslayer> :O
[14:00] <apachelogger> it's fairly reproducible when quickly switching through equalizer presets
[14:00] <shadeslayer> apachelogger: http://paste.kde.org/phfkfgjhg
[14:01] <apachelogger> considering it doesn't crash with gst0.10 I'd say it is a gst bug, OTOH gst could also fall apart because pgst is shit
[14:01] <apachelogger> dem debug symbols
[14:01] <shadeslayer> apachelogger: yeah, afaict there's nothing in there about pgst, however, could be that pgst is being mental
[14:01] <apachelogger> shadeslayer: the grind looks useless
[14:02] <shadeslayer> needs debug symbols?
[14:03] <apachelogger> no, I don't see where it crashes
[14:03] <apachelogger> plus it does not list any bogus mem access, whereas one of the pastes was talking about writing to unalloced memory or some such business
[14:04] <apachelogger> generally I guess it would help the grinding to turn off all amarok scripts though
[14:04] <apachelogger> (that way the qtscript rubbish should be less or gone complete)
[14:04] <shadeslayer> apachelogger: line 855
[14:04] <shadeslayer>  Address 0x384bd000 is not stack'd, malloc'd or (recently) free'd
[14:05] <shadeslayer> bogus mem access right there?
[14:05] <apachelogger> that's in qtscript though
[14:05] <apachelogger> plus that seems to be normal
[14:05] <shadeslayer> well it crashes shortly afterwards, which is why I thought that's what you were looking for
[14:06] <apachelogger> it's not impossible
[14:06] <apachelogger> that would be a different crash then though
[14:06] <shadeslayer> right
[14:06] <shadeslayer> apachelogger: so what else do you need
[14:06] <apachelogger> as I said, grinding without scripts would help
[14:06] <shadeslayer> disable amarok scripts
[14:06] <shadeslayer> anything else?
[14:07] <apachelogger> a backtrace from the grinded crash xD
[14:07] <apachelogger> because that grind suggests another bt
[14:07]  * shadeslayer will ask the user who can reproduce the crash reliably to join here :P
[14:08] <apachelogger> they should just file a flipping bug report
[14:09] <shadeslayer> on bugs.kde.org?
[14:09] <apachelogger> I guess
[14:09] <apachelogger> the endless pit of pgst is not really cared for \o/
[14:09] <shadeslayer> I need to figure out what to do with the bugzilla for pgst
[14:10] <shadeslayer> flipping mental it is
[14:10] <apachelogger> someone shoudl rewrite pgst in ruby
[14:11]  * shadeslayer would rather everyone just use Qt MM
[14:11] <apachelogger> because that makes gstreamer less crashy? :P
[14:12] <shadeslayer> DarthFrog: ok, please provide a valgrind log with amarok scripts disabled here, or just report a bug on bugs.kde.org
[14:14] <DarthFrog> shadeslayer:  so that would be "valgrind amarok  2>output.txt"?
[14:14] <shadeslayer> yeah
[14:14] <apachelogger> --nofork
[14:14] <shadeslayer> ^^
[14:14] <apachelogger> no, I mean you need to run amarok with --nofork
[14:16] <DarthFrog> so "valgrind amarok --nofork"?
[14:18] <DarthFrog> http://paste.ubuntu.com/7462937/
[14:19] <DarthFrog> Amarok didn't launch, only that output.
[14:21] <apachelogger> DarthFrog: it's already running, you need to quit it and then run valgrind
[14:22] <DarthFrog> apachelogger:  Please give me the sequence of commands that I would enter at the console.
[14:24] <DarthFrog> I killed the existing amarok instance and am running "valgrind amarok --nofork 2>out.txt".
[14:29] <DarthFrog> Nothing.  No return to the command prompt, no amarok window.
[14:30] <shadeslayer> probably going to take a while
[14:31] <DarthFrog> shadeslayer: No, it just launched to the systray. :-) 
[14:32] <DarthFrog> However, now using the equaliser doesn't crash it.  I did turn off all scripts. 
[14:39] <apachelogger> I guess it could be a qtscript issue after all then
[14:48] <DarthFrog> Oh lovely.  Now restarting Amarok crashed my session, kicking me back to the display manager login screen. :-(
[14:49] <DarthFrog> I'm re-enabling scripts, one at a time.
[14:50] <DarthFrog> That one did it! 
[14:50] <DarthFrog> (amarok:24283): GStreamer-CRITICAL **: write map requested on non-writable buffer
[14:52] <DarthFrog> The BBC Radio Streams is at least one of the guilty parties.
[14:52] <DarthFrog> at least, it is with Script Console and Lyrics enabled.
[14:53] <DarthFrog> LyricWiki, I mean.
[14:54] <DarthFrog> Hmm, not so quick there.  It still crashes after disabling the BBC script.
[14:56] <DarthFrog> All scripts disabled and it still crashes.  
[14:59] <kdeuser56> yofel: Do you recommend using the neon iso or will the normal isos together with the neon ppa do as well?
[14:59] <kdeuser56> (in order to get plasma next)
[15:00] <yofel> the iso should provide a better experience as restarting the session on live is a pain
[15:00] <yofel> shadeslayer will know more
[15:00] <kdeuser56> I did not understand your first sentence
[15:01] <kdeuser56> session on live = session on neon live cd?
[15:01] <kdeuser56> yofel: the iso ... which iso? :D
[15:02] <yofel> well, != obviously as plasma next is not plasma current
[15:03] <kdeuser56> am I drunk?  ... I do not get you at all sorry
[15:04] <kdeuser56> of course I know that the utopic daily iso ships current plasma while the neon iso ships plasma next
[15:04] <kdeuser56> you said restarting a session is a pain ... where is it a pain?
[15:05] <kdeuser56> My initial question was the following: I want to use plasma next in production, but I want my system to be based on uptopic and not on trusty, so I am thinking of adding the neon ppa to utopic ... what I wanted to know was if that will end in a mess so that I should probably use the neon isos?
[15:06] <apachelogger> neon5 doesn't support utopic
[15:08] <kdeuser56> oh okay ... pitty :-(
[15:09] <kdeuser56> the current neon iso lags extremly on nouveau for me ... repaint issues all the time ... now the question is, if its kwin or plasma next ...
[15:10] <mgraesslin> kdeuser56: use nvidia
[15:10] <kdeuser56> mgraesslin: the blob? 
[15:10] <mgraesslin> yes
[15:11] <kdeuser56> is the nouveau performance regression a known issue?
[15:12] <kdeuser56> mgraesslin: or do you just recommend me to try it with the blob and see if the problem persists? 
[15:13] <mgraesslin> we (kwin devs) do not recommend to use nouveau
[15:14] <kdeuser56> in general? 
[15:14] <kdeuser56> for kwin4 everything is fine with nouveau
[15:22] <shadeslayer> apachelogger: http://paste.ubuntu.com/7463252/
[15:26] <shadeslayer> ScottK: http://paste.ubuntu.com/7463274/
[15:26] <shadeslayer> better?
[15:26] <sgclark> Riddell: or shadeslayer: amor merge https://launchpad.net/~scarlett-7/+archive/kubuntu-ppa/+packages
[15:30] <sgclark> Riddell: http://paste.ubuntu.com/7463301/
[15:46] <Riddell> sgclark: binary-without-manpage we can ignore (it's debian policy but we're not too fussed about it in ubuntu)
[15:47] <Riddell> sgclark: and the kdeinit ones I know needs to be fixed, dh_movelibkdeinit needs adapted for kdeinit5 but live with it for now
[15:47] <Riddell> shadeslayer: so what was that about not uploading merges? surely we should upload merges now, the issue I've always been worried about is trying to merge at the same time as updating to the new version which is excessively complex
[15:48] <Riddell> agateau: on https://code.launchpad.net/~agateau/ubiquity/kde-fix-keyboard-selection-glitch/+merge/218569 I'm afraid I don't understand the problem, it seems to work ok with keyboard navigation, and I don't see any difference after applying your patch
[15:48] <Etriaph> What TZ is ovidiu-florin in?
[15:48] <Riddell> Etriaph: UTC+3
[15:48] <Etriaph> Riddell: Ah, OK
[15:53] <shadeslayer> Riddell: <yofel> well, as I told you, we'll have to bump breaks/replaces when we do a new version, so going straight to << 4.13.80 would be easiest
[15:55] <agateau> Riddell: you can reproduce the bug by selecting a keyboard layout with the keyboard, then pressing the down arrow key
[15:56] <yofel> well, I don't mind either way, but if we upload now we'll break the dev release upgrade for anyone that's running 4.13.1 in trusty right now
[15:56] <agateau> Riddell: it should select the next layout and immediatly come back to the previous one
[15:56] <yofel> and I don't see how that's complex, it's 2 different work items
[15:56] <yofel> you don't do both at the same time
[15:57]  * yofel throws keyboards at joomla in the meantime
[15:57] <shadeslayer> joomla .. hahaha
[16:00] <shadeslayer> Riddell: can you upload kdeconnect for me
[16:00] <shadeslayer> Riddell: http://people.ubuntu.com/~rohangarg/upload/kdeconnect/trusty/kdeconnect_0.5.2-0ubuntu0.1.dsc && http://people.ubuntu.com/~rohangarg/upload/kdeconnect/utopic/kdeconnect_0.5.2-0ubuntu1.dsc
[16:03] <shadeslayer> sgclark: you dropped the dbg package?
[16:04] <sgclark> not me personally, perhaps debian did? Still  not confident on merges
[16:04] <sgclark> shadeslayer ^
[16:05] <shadeslayer> right debian doesn't have the dbg package, but the question is, do we want to drop it?
[16:08]  * Etriaph is a fan of dbg packages
[16:09] <sgclark> I am guessing no? so do I add those back in all the packages and add to remeaing changes? I did not realize they do not have those.
[16:09] <sgclark> shadeslayer ^
[16:09] <Riddell> shadeslayer: we don't want it if debian doesn't have it
[16:10] <sgclark> how many bugs can a floating ball of sunshine have? :)
[16:10] <Etriaph> It depends on how many programmers it took to build the floating ball of sunshine :)
[16:10] <sgclark> lol
[16:10] <Riddell> amor is a work of programmatic perfection
[16:11] <Etriaph> The most amazing code, in any language, I ever read, is Rails.
[16:12] <Riddell> cor, ubuntu forking itself https://lists.ubuntu.com/archives/ubuntu-release/2014-May/002859.html
[16:12] <Riddell> not unlike kubuntu I guess :)
[16:12] <shadeslayer> my thoughts exactly
[16:12] <Riddell> they stole our idea!
[16:13] <shadeslayer> my thoughts exactly
[16:15] <sgclark> ok so, what is the verdict on dbg package
[16:15] <shadeslayer> *shrug* drop it
[16:15] <Riddell> in merges, if in doubt: follow debian
[16:16] <shadeslayer> it's fine
[16:16] <shadeslayer> Riddell: kdeconnect uploaded ? :P
[16:16] <Etriaph> Would someone still be able to produce the bugging symbols from the source package?
[16:16] <shadeslayer> Riddell: also, https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1319365 < please accept nominations
[16:16] <Etriaph> Just curious as to how this is put together.
[16:16] <shadeslayer> Etriaph: my guess would be that LP creates dbgsym packages
[16:17]  * Etriaph nods.
[16:18] <Riddell> shadeslayer: is there a MRE for kdeconnect? or how do you plan to get it into trusty?
[16:18] <BluesKaj> yeah Unity8 sounds too much like MS desktop clone
[16:19] <shadeslayer> Riddell: well, talked to upstream and checked the diff, code has some new features, but cmake isn't installing those things
[16:19] <shadeslayer> so we're good
[16:19] <shadeslayer> everything else is bug fixes
[16:19] <shadeslayer> so it should be fine?
[16:19] <Riddell> shadeslayer: I'll let you fight that out with the archive admins then :)
[16:19] <shadeslayer> :)
[16:19] <Riddell> shadeslayer: uploaded!
[16:19] <shadeslayer> thx
[16:23] <Riddell> on merges I think we can do a mass update of breaks/replaces/conflicts if that's what is needed
[16:23] <Riddell> I don't think we should wait for merges, get them over with quickly is best
[16:25] <Riddell> shadeslayer: will you look at sgclark's merges or shall I?
[16:25] <shadeslayer> Riddell: please go through them
[16:32] <Riddell> shadeslayer: do you know what you need to do to get permissions to nominate bugs for series?
[16:33] <Riddell> that seems like a slightly weird thing to restrict
[16:33] <Riddell> would applying for MOTU help?
[16:36] <yofel> bug control can noimnate IIRC, any dev with upload permissions can then accept the task
[16:39] <Riddell> yep, so apply for MOTU shadeslayer!
[16:48] <Riddell> sgclark: looking at amor I think you can drop both those changes
[16:49] <Riddell> sgclark: the exact versions in build-deps doesn't matter too much for kde depends as long as kde-sc-dev-latest is updated (which I see it isn't)
[16:50] <Riddell> sgclark: and installing a manpage with .install rather than with .manpages might be mildly less elegant but makes no real difference
[16:50] <Riddell> and it's always best to remove any changes compared to debian where there's no real advantage (make them do all the work so we don't have to)
[16:50] <Riddell> alas we can't sync it as there's no 4.13 package in debian
[16:51] <Riddell> sgclark: so yeah, no changes need kept there
[16:52] <Riddell> sgclark: gwenview same thing, just keep the debian build-dep versions
[16:52] <Riddell> sgclark: also your changelog entry should mention that we add kubuntu_install_kipi_plugins.patch
[16:55] <sgclark> Riddell: yes I am a bit confused as most of these I am doing , we are at 4.13 and they are at 4.12
[16:58] <Riddell> sgclark: right, which means we can't just simply sync the packages, but we can still drop any unnecessary changes
[16:58] <sgclark> ok
[17:03] <Riddell> sgclark: for membership, go for it, write yourself a wee wiki page then make a doodle poll with some dates and times on it so we can get a meeting of kubuntu council
[17:03] <sgclark> ok ty
[17:04] <sgclark> Riddell: ok so if debian has a newer version than we have in depends, I do what?
[17:04] <Riddell> sgclark: just stick with whatever debian has unless there's a reason not to
[17:05] <Riddell> stick with the newer version if that's what they have yes
[17:05] <sgclark> I can't build it because that version is not yet in kubuntu
[17:05] <Riddell> ah well there's an issue :)
[17:05] <Riddell> sgclark: what's the package?
[17:05] <sgclark> kde-sc-dev-latest they have -v 4:4.12
[17:06] <Riddell> ah hah, so we need kde-sc-dev-latest merged
[17:06] <sgclark> ok
[17:06] <sgclark> want me to try that?
[17:06] <Riddell> sgclark: take it on if you want to yes
[17:07] <sgclark> on it
[17:07] <Riddell> I quite forget what the delta is in that
[17:08] <Riddell> we can't rely on kde-sc-dev-latest to bring in the latest versions as debian do because launchpad is a bit crap at knowing when to set off a rebuild in that case, but for merges I don't think that's important, it's only an issue when doing a KDE SC mass upload
[17:11] <shadeslayer> Riddell: yeah will do tomorrow
[17:13]  * Riddell out for a few hours
[17:15] <shadeslayer> Riddell: btw do you think we should send out a similar request as the Unity 8 flavor ?
[17:28] <sgclark> Can anyone tell me if this still stand true for kde-sc-dev-latest: http://paste.ubuntu.com/7463828/
[17:29] <sgclark> and this: http://paste.ubuntu.com/7463837/
[17:29] <TheFakeazneD525> will Kubu 14.10 ship with KDE SC KF5 KDE5 5 or whatever it's called?
[17:31] <sgclark> pretty sure that is still in discussion
[17:32] <shadeslayer> TheFakeazneD525: probably as a separate ISO
[17:32] <TheFakeazneD525> Hmm, another question
[17:33] <TheFakeazneD525> KDE now has the Oxygen font, will Kubu ship with that in the future?
[17:38] <apachelogger> probably on a separate ISO
[18:05] <TheFakeazneD525> ah, thanks for clearing this up
[18:05] <TheFakeazneD525> take care guys~
[18:16] <ScottK> shadeslayer: What's a "KDE desktop"?
[18:17] <ScottK> Also baloo should not be a user facing thing.
[18:59] <ScottK> shadeslayer: This kdeconnnect release is not a bugfix release.
[19:00] <ScottK> Did we ever explicitly include kdeconnect in our MRE?
[19:38] <shadeslayer> ScottK: re kdeconnect MRE not that I know of, no, and can you give me a reason why it's not a bugfix release?
[19:38] <ScottK> shadeslayer: Did you look at the diff?  New cli capability.
[19:38] <ScottK> Definitely not bugfix.
[19:38] <shadeslayer> ScottK: not installed anywhere
[19:39]  * shadeslayer double checks
[19:40] <shadeslayer> argh, my internets is so slow :/
[19:47] <shadeslayer> ScottK: okay, I was wrong, so, if I remove the kdeconnect-cli binary, what other problems would there be?
[19:47] <shadeslayer> should be relatively easy to do that
[19:48] <ScottK> shadeslayer: Since there's no MRE for this, please go through the rest and figure out what fixes actual bugs.
[19:48] <shadeslayer> roger, looking through https://launchpadlibrarian.net/175544677/changelog
[19:48] <ScottK> I think it'd be more sensible to do a patch update to the current version then do the new version with stuff wripped out.
[19:49] <ScottK> You'll need to review the diff in detail too.
[19:49] <shadeslayer> ofcourse
[19:50] <shadeslayer> ScottK: actually this is weird
[19:50] <shadeslayer> commit log talks about disabling it
[19:51] <ScottK> Didn't look disabled when I looked at the diff.
[19:51] <shadeslayer> yeah
[19:51] <shadeslayer> talking to upstream now
[19:51] <ScottK> In any case the fact that it's there tells me they don't have a release strategy that's compatible with MRE.
[19:52] <shadeslayer> ScottK: roger, I'll talk to upstream and sort it out
[19:52] <shadeslayer> thanks
[19:54] <ScottK> shadeslayer: You might point them to http://techbase.kde.org/Policies/Minor_Point_Release_Policy for a good example of what to follow.
[19:55] <ScottK> Of course it'd be nice if KDE itself hadn't abandoned that for KF5.
[20:07] <shadeslayer> ScottK: passed on to upstream, he's fixing the tarball
[20:07] <ScottK> Please he gives it a new number.
[20:08] <yofel> ... by not appending -1 or so
[20:08] <ScottK> shadeslayer: 0.5.2 is already used in the archive, so how about 0.5.1.1.
[20:11] <shadeslayer> or 5.2.1
[20:11] <shadeslayer> *0.5.2.1
[20:13] <shadeslayer> ScottK: ^^
[20:14] <ScottK> Then you upload that to uptopic too.
[20:14] <ScottK> That'd be fine.
[20:14] <shadeslayer> yeah, was going to do that
[20:14] <ScottK> May as well doe 0.5.3 at that point though.
[20:20] <ScottK> Instead of a PPA for Plasma 5, could we just do something like this: https://lists.ubuntu.com/archives/ubuntu-release/2014-May/002859.html
[20:25] <yofel> wasn't the reason for the PPA easier updatability? Otherwise that's pretty  much what we're trying to do
[20:26] <ScottK> Will we care about post-release updates?
[20:27] <shadeslayer> if we don't want to give a bad rep, yes
[20:27] <ScottK> We can get an FFe all the way up to release.
[20:27] <shadeslayer> and a faster release cycle is why we wanted to use a PPA AFAIK
[20:28] <ScottK> You probably won't be able to keep updating anyway.
[20:28] <ScottK> KF5 will keep updating and P5 will use stuff from the new KF5.
[20:36] <soee> driver manager after installing 337 http://wstaw.org/m/2014/05/14/driver_manager.jpg
[20:37] <shadeslayer> 0.i
[20:37] <shadeslayer> 0.o
[20:37] <shadeslayer> that's still happening?
[20:38] <soee> but with xorg edgers ppa
[20:39] <soee> i had all fine, than i installed 337 and this showed up, after list refresh i have one list again as it should be
[20:39] <soee> and 337 marked as installed
[20:39] <soee> brb reboot
[20:40] <shadeslayer> apachelogger: ^^
[20:41] <shadeslayer> ScottK: not necessarily
[20:41] <shadeslayer> ScottK: though I reckon there might be problems which are fixed in KF5 and then cause issues in PN5
[20:44] <ScottK> shadeslayer: There is zero indication that upstream really cares about distros in their release policy.  So I think it's safe to assume at this point we'll get screwed.
[20:44] <soee> back
[20:45] <ScottK> As nearly as I can tell every single distro pushed back on the KF5 release plan and the most it got in feedback is maybe we should make some stable branches.
[20:46] <ScottK> If they want stuff to get updated, then they ought to release stuff we can update with.