[07:33] <lordievader> Good morning
[07:35] <soee_> ohaio lordievader o/
[07:35] <lordievader> Hey soee_, how are you doing?
[07:36] <soee_> lordievader: fine, waiting for new plasma release :) You?
[07:36] <lordievader> Doing good here :)
[07:36] <soee_> :)
[07:37] <acheronuk> Morning :)
[07:37] <lordievader> Hey acheronuk 
[07:38] <soee_> https://www.youtube.com/watch?v=RdQkKc5egIg
[09:08] <aektzim> good morning! :) (jimarvan)
 Mparillo apps is at 16.04.2 for YY and XX in staging
[11:19] <aektzim>  :D
[11:19] <clivejo> is Plasma 5.6.5 not in landing?
[11:20] <clivejo> maybe even backports for XX?
[11:20] <yofel> yes
[11:20] <yofel> and yes
[11:20] <clivejo> FW too?
[11:20] <yofel> and yes ^^
[11:20] <clivejo> LOL
[11:21] <aektzim> hmm
[11:21] <yofel> apps you know what's the case
[11:21] <aektzim> clivejo: reinstalling 16.04 so I can continue the testing
[11:21] <clivejo> yofel: RE: Apps I have copied KCI version of ffmpegthumbs and kdeconnect into the apps-staging
[11:22] <yofel> git too?
[11:22] <clivejo> kdeconnect havent copied the git
[11:23] <clivejo> the reason being that I think we should follow debian and use the previous packaing
[11:23] <clivejo> ie kdeconnect rather than kdeconnect-plasma
[11:23] <clivejo> need to talk to you regarding that
[11:24] <yofel> if you say that then I'll belive you, otherwise I would have to read through the packaging myself again
[11:26] <mparillo> Does that mean that we need a quick test on Apps 16.04.2?
[11:26] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/kde-extras/kdeconnect.git/tree/debian/changelog
[11:27] <clivejo> mparillo: yes, please test apps 16.04.2
[11:27] <yofel> ah, debian doesn't even have kdeconnect-plasma
[11:28] <clivejo> nope, thats was a kubuntu thing
[11:28] <clivejo> how do we deal with that?
[11:29] <clivejo> just mirror kdeconnect debian git into LP and pretend nothing happened?
[11:29] <yofel> removal request for kdeconnect-plasma and me doing a force-sync for kdeconnect IMO
[11:30] <aektzim> :(
[11:30] <yofel> needs checking whether that gets properly replaced for users though
[11:30] <clivejo> sounds complicated 
[11:30] <yofel> otherwise merge kdeconnect with debian and add transitional packages / breaks / etc.
[11:31] <yofel> the removal for kdeconnect-plasma should happen though
[11:31] <clivejo> do we need to keep kdeconnect-plasma as a transitional package for a while?
[11:31] <yofel> the force-sync is one command, so not an issue. Checking whether something breaks is the part that requires work
[11:33] <yofel> dunno if we need *that*, we need whatever is needed to properly replace the packages for users
[11:33] <yofel> might be that
[11:34] <yofel> where "for a while" means: until 18.10
[11:35] <clivejo> kdeconnect really should be part of plasma release
[11:35] <clivejo> IMO
[11:35] <yofel> talk that out with upstream. Doesn't make much of a difference for us
[11:38] <mparillo> clivejo: sudo add-apt-repository ppa:kubuntu-ppa/staging-kdeapplications ?
[11:39] <clivejo> looks ok
[11:39] <jimarvan2> mparillo: thanks was look for that ;)
[11:39] <jimarvan2> *looking
[11:39] <clivejo> please report back any installation oddness
[11:40] <jimarvan2> ok
[11:59] <mparillo> Updates appeared to all be successful...re-booting.
[12:16] <mparillo> Dolphin and Kate both report 16.04.2 and seem to operate normally. Rekonq and Kinfocenter seem to work also.
[12:16] <BluesKaj> Hey all
[12:17] <hegemon8> Hey BluesKaj :)
[12:18] <BluesKaj> Hi hegemon8 , what's happening ?
[12:19] <hegemon8> trying to make airtime 2.5.2.1 work on my kubu, and You? :)
[12:19] <mparillo> BluesKaj: clivejo has announced that apps 16.04.2 is available. sudo add-apt-repository ppa:kubuntu-ppa/staging-kdeapplications and nothing seemed wrong to me.
[12:20] <BluesKaj> hegemon8,  not much, first morning coffee atm
[12:20] <hegemon8> clivejo:  announced apps? I want to try :)
[12:20] <jimarvan2> go go install repo :)
[12:21] <BluesKaj> mparillo,  thanks I'll run that on my laptop later on 
[12:22] <BluesKaj> or did I already ...my poor memory fails me this morning
[12:22] <hegemon8> upgrading now jimarvan2
[12:22] <jimarvan2> everyone experiences the same issue on VBox when installing 16.04?
[12:22] <hegemon8> ^^
[12:22] <jimarvan2> i get that wierd screen with colorful letters/numbers puzzle
[12:23] <hegemon8> jimarvan2: had probs with initial release, but now when got it from daily iso on bare metal works fine to me 
[12:24] <hegemon8> i've got recent plasma 5.6.x from backports ppa, so i'll wonder how will it work after upgrade :)
[12:24] <jimarvan2> ye but I thought we are supposed to install the staging kde apps from initial 16.04 iso, no?
[12:24] <jimarvan2> am I wrong? should I install the backports too?
[12:25] <hegemon8> don't know tbh, i did earlier on (4 days ago) so... apps? why not :) i like new shiny things on my desktop :)
[12:25] <jimarvan2> nah I will test it as a normal user would, use what is available on official repos
[12:25] <jimarvan2> and see how it goes
[12:25] <jimarvan2> VBox snapshoting helps there  to revoke changes ;)
[12:26] <mparillo> I installed staging apps (sudo add-apt-repository ppa:kubuntu-ppa/staging-kdeapplications) to YY. I assumed it was going there first. It certainly was there.
[12:26] <hegemon8> true :) i'm crazy one, i test it on my only laptop, that makes sure i'll notice bugs more likely then when test it every now and then
[12:26] <mparillo> clivejo: Are the KDE Apps 16.04.2 also on XX?
[12:27] <mparillo> hegemon8: Way to live on the edge! I only do that when it contains a fix for some known annoyance of mine. Otherwise (like today) it goes in a VM first.
[12:28] <jimarvan2> installing kdeapplications now :)
[12:28] <jimarvan2> mparillo dist-upgrade or full-upgrade?
[12:28] <jimarvan2> any of the two?
[12:28] <hegemon8> mparillo: smart way to do it... i'm just like a kido in candy store... new apps You say? .... ^^
[12:29] <hegemon8> it got me into troubles not once :)
[12:30] <hegemon8> BluesKaj: just enjoying my coffee myself... black gold :)
[12:31] <BluesKaj> hegemon8,  yeah , western dark roast here  :-)
[12:31] <hegemon8> lavazza here BluesKaj :)
[12:32] <jimarvan2> clivejo: mparillo: https://s31.postimg.org/o9rvmwrcb/Screenshot_20160705_132933.png
[12:32] <jimarvan2> this is what I get after fresh installing 16.04, updating, then adding the kdeapps repository
[12:32] <jimarvan2> is there something missing?
[12:33] <jimarvan2> should I add the backports repository?
[12:35] <mparillo> jimarvan2: I have been doing a full-upgrade. There is a subtle difference between the older dist-upgrade and full-upgrade, but I am not competent to distinguish them.
[12:35] <jimarvan2> ok I have not done it yet
[12:35] <hegemon8> jimarvan2: will tell You as it go when download will finish, i have backports enabled...
[12:36] <jimarvan2> so to be clear, mparillo, you used an updated 16.04 (no backports) and did full-upgrade
[12:36] <jimarvan2> correct?
[12:36] <BluesKaj> mparillo,  just ran the above ppa and rebooted the lapyop, and all is well , there just 2 changes, gwenview upgrade and kde-connect
[12:36] <mparillo> No, I used YY
[12:36] <mparillo> YY will be released as 16.10
[12:37] <jimarvan2> ye clivejo asked me to test them on xenial
[12:37] <jimarvan2> so there you have it, some of the packages are been kept back on xenial! :)
[12:38] <hegemon8> mparillo: You're hardcore :)   i'll wait a bit as after upgrade from 15.10 to 16.04 i've ended up with fresh daily iso reinstall.
[12:38] <mparillo> I think that since Apps will only land in backports on XX, maybe it makes sense to add that repo also.
[12:39] <jimarvan2> ye
[12:39] <mparillo> If then you have no held back packages, then you have an additional bit of data to report.
[12:39] <jimarvan2> doing so, saving a VBox snapshot too
[12:39] <jimarvan2> will report soon
[12:40] <jimarvan2> official backports right? not any staging ind
[12:40] <jimarvan2> *kind
[12:40] <jimarvan2> ppa:kubuntu-ppa/backports 
[12:41] <jimarvan2> that was it!!!
[12:41] <jimarvan2> no more held packages :D
[12:41] <hegemon8> did it worked then?
[12:42] <jimarvan2> still installing
[12:42] <hegemon8> pure accident i've found backports earlier in announcements on  kubuntu website that plasma 5.6.x was released to public :)
[12:43] <mparillo> Also have a question that jimarvan2 got me thinking about. Does Muon Update Manager do an upgrade, dist-upgrade, or a full-upgrade?
[12:43] <jimarvan2> good question...
[12:44] <jimarvan2> it does not do a dist-upgrade because it is hinting it if a dist upgrade is available
[12:45] <BluesKaj> the staging-kdeapplications ppa just upgrades kdeconnect-plasma and krdc on YY/16.10, mparillo, clivejo
[12:46] <jimarvan2> installation went absolutely smooth
[12:46] <jimarvan2> rebooting and trying it out
[12:46] <hegemon8> let us know pls
[12:48] <mparillo> BluesKaj: Funny, can you check the version numbers of Kate and Dolphin (and maybe konversation). I would have thought they would also show 16.04.2
[12:48] <hegemon8> maybe my try of install airtime will succeed after that. (dependencies not met issue)
[12:50] <acheronuk> staging-kdeapplications ppa has backports ppa as a dependancy, so have to be use together
[12:51] <acheronuk> on XX anyway
[12:51] <jimarvan2> OK report time: staging-kdeapplications work PERFECTLY on 16.04 image with backports
[12:51] <jimarvan2> i tested almost all apps no issues
[12:52] <acheronuk> kdePIM ok? had to re-do akonadi yesterday
[12:52] <hegemon8> great! (mine is installing now... Would be faster if i wouldn't install most of apps from repo earlier to test what works^^)
[12:54] <jimarvan2> acheronuk: i will try now to use it
[12:54] <BluesKaj> mparillo, yes dolphin is Version 16.04.2 on YY/16.10
[12:54] <BluesKaj> here
[12:56] <hegemon8> reboot
[12:57] <jimarvan2> acheronuk: seems OK
[12:57] <BluesKaj> mparillo,  Version 16.04.2 on XX/16.04 here as well
[12:58] <jimarvan2> I see no issues with kdePIM
[13:02] <acheronuk> jimarvan2: Good. Should be OK, but nice to have that confirmed
[13:03] <acheronuk> https://www.kde.org/announcements/plasma-5.7.0.php
[13:04] <jimarvan2> in fact I am going to upgrade my production laptop right away
[13:04] <jimarvan2> :>
[13:06] <hegemon8> okay, booted well, lets see how it works :)
[13:28] <clivejo> with apps on XX, make sure you also have backports enabled
[13:30] <jimarvan2> damn i  hoped the updated ffmpegthumbs would allow dolphin to show mp4 preview :(
[13:30] <clivejo> jimarvan2: it should
[13:30] <clivejo> have you it switched on in the dolphin settings?
[13:31] <acheronuk> and clicked the preview button?
[13:31] <jimarvan2> you mean press preview?
[13:31] <jimarvan2> i only clicked preview button
[13:31] <jimarvan2> is there a setting on dolphin?
[13:31] <acheronuk> yes, there is a setting
[13:32] <clivejo> Settings > Configure > Previews > video thumbs
[13:32] <jimarvan2> yeap got it remembered
[13:33] <jimarvan2> I do not see video thumbs option available\
[13:33] <clivejo> have you ffmpegthumbs installed?
[13:33] <acheronuk> http://i.imgur.com/nty9Ve2.png
[13:34] <jimarvan2> hmm let me check
[13:34] <jimarvan2> probably not because i only upgraded
[13:35] <clivejo> is it not enabled by default?
[13:35] <jimarvan2> no
[13:35] <jimarvan2> i am installing now
[13:35] <clivejo> humm
[13:36] <BluesKaj> clivejo,  i get the not available message, "Package ffmpegthumbs is not available, but is referred to by another package"
[13:36] <jimarvan2> success!
[13:36] <jimarvan2> now i can see previews :D <3 u all
[13:36] <clivejo> its available from the apps staging ppa
[13:37] <jimarvan2> also the bug for deleting a user from User Accounts, and still showing up on the login screen is gone
[13:38] <jimarvan2> amarok still has issues with internet online services, but that is because it is not updated for a long time :P
[13:38] <jimarvan2> hmm what else to check
[13:38] <jimarvan2> any ideas? what else should I try?
[13:38] <jimarvan2> kdeconnect?\
[13:39] <jimarvan2> that would be challenging through VBox but I could give it a go
[14:03] <clivejo> as long as they both on same network it should work
[14:31] <sheytan> Hey, again me with *that* question. When 5.7 will be ready for kubuntu? :D
[14:33] <clivejo> sheytan: how long is a piece of string?
[14:35] <jimarvan2> :D
[14:35] <jimarvan2> i will go with 1 cm :P
[14:37] <jimarvan2> see you in the evening guys, wrapping up here for my karate session, ciao!
[14:46] <acheronuk> clivejo http://www.omgubuntu.co.uk/2016/07/plasma-5-7
[14:47] <acheronuk> "Want to install Plasma 5.7 on Ubuntu 16.04 LTS? You won’t have to wait long. Plasma 5.7 will be available to install on Kubuntu 16.04 LTS through the Kubuntu Backports PPA at some point in the very near future."
[14:47] <clivejo> hummm
[14:47] <yofel> does it help to suggest that omgubuntu is a really bad source for information?
[14:47] <clivejo> Ive written to that Joey fella before about jumping the gun!
[14:48] <acheronuk> yofel: yes, I know. but it still irks me
[14:49] <clivejo> click baiting
[14:49] <mparillo> Maybe he knows something about Qt 5.7 landing in the archive backports?
[14:49] <clivejo> he knows more than us then!
[14:49] <acheronuk> mparillo: has it? news to me!
[14:50] <yofel> you mean 5.6 I guess
[14:51]  * yofel wonders if you can set a default output in the volume applet now
[14:52] <BluesKaj> just looking for traffic to his site... seems he has no clue when 5.7 will be available , clivejo, click baiting is exsactly what he's dong
[14:52] <yofel> well, I guess 18.04 will be awesome if I look at that feature list
[14:53] <clivejo> Im looking forward to Yakkety
[14:53] <mparillo> What I meant was that Kubuntu cannot backport Plasma 5.7 until the larger Ubuntu project backports Qt 5.7, or am I incorrect?
[14:53] <clivejo> its the most stable Ive ever seen it
[14:53] <yofel> mparillo: we can very much backport 5.6 ourselves, and we will have to do that
[14:53] <clivejo> mparillo: plasma 5.7 needs Qt 5.6.1 or better
[14:54] <clivejo> acheronuk has been working on that
[14:54] <mamarley> Isn't Qt 5.6.1 already in the frameworks-staging PPA?
[14:54] <clivejo> only for Yakkety
[14:57] <mparillo> TY for the correction
[15:02] <clivejo> yofel: would you have time to do kde-l10n?
[15:02] <yofel> for?
[15:02] <clivejo> 16.04.3
[15:02] <yofel> can do, where to?
[15:03] <clivejo> its a huge download and not sure if I have the quota :(
[15:03] <clivejo> apps staging?
[15:03] <yofel> for Y?
[15:03] <clivejo> I dont understand the question
[15:03] <yofel> yakkety
[15:03] <clivejo> both YY and XX
[15:03] <yofel> ack
[15:03] <clivejo> should be easy to backport when the SC is on your machine
[15:04] <yofel> that's not how it works, so I have to do 2 sepeare l10n runs anyway
[15:04] <clivejo> eak
[15:04] <yofel> typo day
[15:04] <clivejo> lot of downloading
[15:04] <yofel> indeed
[15:04] <clivejo> and uploading
[15:05] <clivejo> unfortunately I’m metered both ways 
[15:05] <yofel> that's what servers are for ^^. It's not like I'm running it on my work PC here either.
[15:06] <clivejo> ah
[15:15] <yofel> hm, 16.04.3 isn't a thing, I'll take 16.04.2
[15:15] <clivejo> oupps sorry
[15:15] <yofel> ^^
[15:15] <clivejo> I keep doing that
[15:21] <BluesKaj> installed the new frameworks on YY, now when opening dolphin this red error pops up,  Could not start process Unable to create io-slave:klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'.
[15:21] <BluesKaj> .
[15:29] <yofel> oh damnit, I forgot that i18n script
[15:30] <yofel> clivejo: could you please merge the libkf5i18n changes from xenial backports into yakkety archive? I forgot that
[15:30] <yofel> I'll do the l10n side
[15:31] <clivejo> this => https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ki18n/commit/?id=6da2ac43443f280ffc28f475c2141a12c9519f74
[15:45] <clivejo> https://www.digikam.org/node/755
[15:46] <clivejo> digiKam 5 out today
[15:46] <yofel> clivejo: yes, that, just put "4:16.04.2" as firstversion instead
[15:46] <clivejo> oups
[15:47] <clivejo> I merged and uploaded to frameworks staging PPA
[15:47] <yofel> ah sorry, forgot about that :P
[15:47] <acheronuk> hmmm. just looking at that kde-l10n stuff, and looks a pain to do
[15:48] <yofel> not really, that's like 99% scripted
[15:48] <clivejo> so change it to "l10npkgs_firstversion_ok := 4:16.04.2"
[15:48] <yofel> right
[15:49] <acheronuk> this? https://community.kde.org/Kubuntu/Packaging/L10nOperatorGuide
[15:49] <clivejo> ok pushed
[15:49] <yofel> acheronuk: that
[15:49] <clivejo> generating ppa22
[15:50] <clivejo> and uploaded to PPA
[15:50] <acheronuk> tried running the script for the hell of it, and got the "Permission denied (publickey).ls: cannot access 'kde-l10n-*.tar.xz'" message
[15:50] <clivejo> you got a KDE account?
[15:50] <yofel> ah yeah, you need depot access for that
[15:50] <acheronuk> I think I must get my kde identity account upgraded
[15:51] <yofel> no, it's just adding your ssh key for depot, we can do that
[15:52] <acheronuk> so I don't need to do this yet then? https://identity.kde.org/index.php?r=developerApplication
[15:52] <yofel> no, that's for write access to git.kde.org
[15:53] <acheronuk> err. no. don't quite need that yet!
[15:54] <acheronuk> maybe some day, but certainly not now
[16:12] <yofel> acheronuk: your ssh key is on ftpubuntu@depot.kde.org now
[16:13] <yofel> that's the pre-publish server before download.kde.org where you find the not-yet-released tarballs
[16:13] <acheronuk> that you yofel. That is great.
[16:13] <soee> :)
[16:13] <acheronuk> helps if I can at least run through some of the scripts further, to get a better grip on what they do and how
[16:14] <yofel> the automation tooling recommends setting the user for that host in ~/.ssh/config, you should do that (at least some scripts rely on that)
[16:14] <clivejo> acheronuk: are you still taking notes on the process so far?
[16:15] <acheronuk> sort of. a fair bit is in memory at the moment, so I must do a bit more self documentation
[16:16] <clivejo> remember this document - https://notes.kde.org/p/kubuntu-packaging
[16:16] <acheronuk> yes, I keep popping back top that
[16:16] <clivejo> we are trying to put together a newbie guide
[16:16] <clivejo> if you see anything wrong on that, let us know
[16:17] <acheronuk> will do
[16:17] <clivejo> also this is the ninja's note pad
[16:17] <clivejo> https://notes.kde.org/p/kubuntu-ninjas
[16:18] <clivejo> when there are 2 or more people working, it helps us co-ordinate
[16:18] <clivejo> so we dont step on each others toes
[16:19] <acheronuk> yep, I get the idea
[16:19] <clivejo> whats the general feeling on apps 16.04.2?
[16:20] <clivejo> I think they should go to testing PPA
[16:22] <acheronuk> as they want further 'testing' they probably should?
[16:23] <clivejo> I was concerned about that akonadi installation issue, but I think thats resolved now
[16:25] <acheronuk> more testing would give more certainly on that...
[16:25] <acheronuk> *certainty
[16:25] <clivejo> indeed
[16:25] <clivejo> yofel: WWYD ?
[16:26]  * clivejo goes off in search of food
[16:27] <yofel> move it. If you can find no more issues in the easy reproducable test upgrades then it's good enough for testing
[16:27] <yofel> actually releasing it requires looking into all the corner cases
[16:27] <yofel> but wait for l10n, I'm still working on that
[16:27] <yofel> yakkety batch #2 is up, now to x
[16:27] <clivejo> :)
[16:47] <soee> digiKam 5.0.0 is published... (https://www.digikam.org/node/755)
[16:50] <yofel> that would be sweet to have. 
[16:51] <yofel> hm, I need to read that i386 discussion...
[16:52] <yofel> out of curiosity: any 32bit users around?
[16:54] <soee> dunno :)
[17:00] <acheronuk> no 32bit here
[17:03]  * acheronuk watches the build-l10n.sh script do it's stuff
[17:03] <acheronuk> that's quite neat :)
[17:04]  * yofel off to find some dinner, bbl
[17:24] <mamarley> yofel: My grandmother has an old Core Duo laptop that (necessarily) runs the 32-bit version of Kubuntu.
[17:25] <genii> I thought C2D is 64 bit cpu
[17:25] <mamarley> genii: It is.  I said Core Duo, not Core 2 Duo.
[17:26] <genii> mamarley: Ah, mis-read :)
[18:16] <BluesKaj_> my desktop is kinda messed up after the frameworks ppa upgrade...a reinstall from the daily is in orderb
[18:16] <BluesKaj_>  for the desktop pc
[18:16] <acheronuk> BluesKaj_: was that on YY?
[18:17] <BluesKaj_> yeah
[18:17] <clivejo> Id reckon so
[18:17] <clivejo> only thing in frameworks was that test build on Qt5.6.1
[18:17] <clivejo> which didnt go to plan
[18:18] <acheronuk> well, it hit bumps that you might expect
[18:18] <BluesKaj_> well, it wasn't a true kubuntu install anyway ..used the ubuntu-server then installed the desktops 
[18:19] <clivejo> BluesKaj_: if you can, download the iso and install from that
[18:19] <clivejo> it needs testing
[18:20] <BluesKaj_> downloading the the YY daily since the slideshow was removed, is that correct?
[18:23] <BluesKaj_> ubiquity won't crash?
[18:24] <BluesKaj_> I'll be installing to / and /home is on a separate partition
[18:25] <clivejo> it shouldnt crash
[18:26] <clivejo> but not promising anything!
[18:26] <BluesKaj_> ok good
[18:27] <BluesKaj_> hehe, np clivejo we all take our chances :-)
[18:30] <BluesKaj_> interesting, I ended up wirh some kind of hydrid desktop withe unity like panel ath the top with green patterned backaground and the application icons set in a grid pattern on the desktop
[18:31] <clivejo> ewww Unity, spawn of the devil!
[18:32] <genii> BluesKaj_: Can you take a screenshot of that? Sounds pretty weird
[18:33] <BluesKaj_> I'll fix it as soon as possible...dunno if a screenshot is possible, ...checking
[18:41] <BluesKaj_> afraid the scrnshot app crashes
[18:41] <clivejo> what are you using to screenshot?
[18:42] <BluesKaj_> prntscrn key
[18:42] <clivejo> install kde-spectacle manually and run it from kick off menu
[18:43] <clivejo> just type spectacle to run it
[18:43] <BluesKaj_> there is no kickoff
[18:44] <clivejo> krunner?
[18:49] <BluesKaj_> it only captures the background without any icons on the grid
[18:49] <clivejo> have you a smart phone to take a photo of the screen?
[18:51] <BluesKaj_> tried that the screen is too bright, overwhelms the phone
[18:52] <genii> Ah, oh well :(
[18:52] <clivejo> not meant to be
[18:54] <BluesKaj_> think i got aphoto that might work
[19:06] <BluesKaj_> now kde connect doesn't work at all on this laptop
[19:15] <BluesKaj_> installing imgur on my phone ...should have it posted in a few mins
[19:38] <BluesKaj_> clivejo, http://imgur.com/vWi7QBq
[19:39] <BluesKaj_> took a while, but i managed 
[19:44] <clivejo> looks like Gnome to me
[19:44] <clivejo> I dont see any Unity?
[19:45] <clivejo> LOL
[19:45] <clivejo> interesting comments
[19:45] <clivejo> Why do people take cell phone shots of their desktop... Don't they realize they can use the print screen button. CMON LINUX USER.
[19:46] <clivejo> why cant people mind their own business!
[19:49] <acheronuk> that is gnome!
[19:50] <BluesKaj_> prntscn didn't work
[19:53] <BluesKaj_> dunno what gnome looks like, I haven't used it intentionally in many yrs :-)
[19:58] <BluesKaj_> another thing, K3b fails to write every time i try it...errors out, "look at the log"...to hell with logs it's been broken for 2 yrs on my machines, but doesn't seem to be getting much attn , I can't be the only one
[20:03] <BluesKaj_> wodim to the rescue
[20:05] <clivejo> in k3b use the other write method
[20:06] <yofel> acheronuk: customery question: are you evil? ^^
[20:07] <acheronuk> only on fridays
[20:07] <acheronuk> err... no
[20:07] <BluesKaj_> which other write method?
[20:07] <yofel> well, that'll work
[20:07] <yofel> acheronuk: you have been promoted
[20:08] <acheronuk> I have? That has been mixed blessings in the past!
[20:08] <yofel> lol, well, you're an official ninja now, so you can save yourself the merge requests now
[20:09] <yofel> you also have write permissions to ~kubuntu-ppa, please be careful with that
[20:10] <acheronuk> I will be exceptionally careful. Thank you :)
[20:11] <clivejo> yofel: will you teach us how to tag?
[20:11] <BluesKaj_> ok other stuff to do ...later, take care
[20:13] <yofel> clivejo: the official way to do so, is to run ubuntu-archive-upload. If you don't want to run that, you can imitate the behavior by running dch -r I believe and git-tagpkg with do-all
[20:14] <clivejo> wont it fail cause I dont have archive upload rights?
[20:14] <yofel> it only prepares the sources, it doesn't upload anything. It doesn't push git either
[20:17] <clivejo> good to know
[20:18] <yofel> originally it did everything, later on that turned out to not be such a good idea ^^
[20:18] <clivejo> I wonder why 
[20:19] <yofel> the script does like to crash halfway every now and then. And re-running it - while not as bad as staging-upload - doesn't quite work
[20:22] <yofel> well, *didn't* quite work
[20:36] <clivejo> acheronuk: see ^^^
[20:37] <acheronuk> clivejo: where?
[20:37] <clivejo> :P 
[20:37] <clivejo> http://kci.pangea.pub/job/merger_kinit/624/console
[20:38] <clivejo> 'Merging remotes/origin/kubuntu_yakkety_archive into kubuntu_unstable.' 'remotes/origin/kubuntu_yakkety_archive'  2>&1:Auto-merging debian/changelog (Git::GitExecuteError)
[20:38] <clivejo> CONFLICT (content): Merge conflict in debian/changelog
[20:38] <acheronuk> oh, you ran it through KCI. duh!
[20:38] <clivejo> yeah, its useful for some things!
[20:40] <acheronuk> "Sending notification to suspect: clivejo"
[20:40] <acheronuk> LOL
[20:40] <clivejo> have you setup git for merging changelogs on your machine?
[20:40] <clivejo> it always blames me :(
[20:40] <clivejo> usually cause I broke it
[20:40] <yofel> I really wonder where it reads that from..
[20:40] <clivejo> but thats a different story
[20:41] <acheronuk> clive: I thought I had ssh set up enough, but that was slightly wrong, so not suer
[20:42] <clivejo> in your ~/.gitconfig
[20:42] <clivejo> do you have the merge driver for changelogs
[20:42] <acheronuk> nope
[20:43] <clivejo> [merge "dpkg-mergechangelogs"]
[20:43] <clivejo>     name = debian/changelog merge driver
[20:43] <clivejo>     driver = dpkg-mergechangelogs -m %O %A %B %A
[20:43] <clivejo> yofel: do you have the link explaining that? ^
[20:43]  * clivejo cant find it
[20:43] <yofel> not at hand
[20:44] <acheronuk> 1st time I've seen it
[20:44] <clivejo> http://manpages.ubuntu.com/manpages/trusty/man1/dpkg-mergechangelogs.1.html
[20:44] <acheronuk> now it's in there
[20:45] <clivejo> good enough explanation for now!
[20:45] <clivejo> run dpkg-mergechangelogs from terminal to check its installed ok
[20:46] <clivejo> should get an error "dpkg-mergechangelogs: error: needs at least three arguments"
[20:46] <acheronuk> yes, I do
[20:46] <clivejo> good good
[20:47] <clivejo> now get yourself a clean folder
[20:47] <clivejo> eg ~/kubuntu/kinit 
[20:47] <acheronuk> yep
[20:47] <clivejo> move into it and do "git clone kubuntu:kinit"
[20:48] <acheronuk> done
[20:48] <clivejo> then cd into the new kinit folder
[20:49] <clivejo> git checkout kubuntu_yakkety_archive
[20:49] <acheronuk> ok..
[20:49] <clivejo> git checkout kubuntu_unstable
[20:49] <clivejo> git merge kubuntu_yakkety_archive
[20:49] <clivejo> and you get a CONFLICT (content): Merge conflict in debian/changelog
[20:50] <acheronuk> indeed I do
[20:50] <clivejo> open debian/changelog in your favourite editor
[20:50] <acheronuk> already have
[20:51] <clivejo> <<<<<<< is the start of the merge conflict
[20:51] <clivejo> one changelog has the line   * Adding postinst-must-call-ldconfig lintian override the other does not
[20:52] <acheronuk> yep, so just that line before the divider
[20:53] <clivejo> So remove lines 6, 8 and 10
[20:53] <acheronuk> done
[20:53] <clivejo> save
[20:54] <acheronuk> &
[20:54] <clivejo> git commit it
[20:54] <clivejo> and git push it
[20:55] <acheronuk> just that?
[20:55] <clivejo> Im not sure how you use git
[20:55] <clivejo> I use git gui
[20:56] <acheronuk> so git add
[20:56] <acheronuk> then commit
[20:57] <acheronuk> I think
[20:57] <clivejo> and give it your own commit message
[20:57] <clivejo> it will probably default to "Merge branch 'kubuntu_yakkety_archive' into kubuntu_unstable"
[20:58] <acheronuk> it will?
[20:58] <clivejo> a merge usually generates a message to that affect
[20:58] <acheronuk> it did
[20:59] <acheronuk> then push?
[20:59] <clivejo> as i say I use git gui as it works better for me
[20:59] <clivejo> so I dont forget git add files etc
[20:59] <acheronuk> I may try that, but I would like to know the nuts and bolts first
[21:00] <clivejo> yeah push that commit
[21:00] <acheronuk> done
[21:00] <clivejo> wait for it
[21:01] <clivejo> ...
[21:01] <acheronuk> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kinit/commit/?h=kubuntu_unstable&id=4bf33993b91dd050268ef73a2071032cb024d6ce
[21:02] <clivejo> hummm
[21:02] <yofel> if kci is slow, blame me. I tried opening the configuration, and now jenkins seems stuck
[21:03] <clivejo> your commit should have triggered KCI
[21:03] <clivejo> ah
[21:03] <yofel> oh great, I killed the bot -.-
[21:03] <yofel> I think our CI has some scalability issues....
[21:04] <clivejo> acheronuk: normally your commit should have triggered KCI into doing a merge
[21:04] <clivejo> then it that merge would trigger new builds
[21:04] <clivejo> but Phil has killed it!
[21:04] <yofel>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                                                                                                                             
[21:04] <yofel>  1284 jenkins   20   0 3243920 1.120g   5516 S 195.1 30.6   3034:59 /usr/bin/java -Djava.awt.headless=true -Dorg.jenkinsci.plugins.gitclient.Git.timeOut=120 -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1        
[21:04] <acheronuk> it seemed half dead anyway
[21:05] <yofel> seriously, what is that thing doing..
[21:05] <clivejo> The UI wont load for me
[21:05] <clivejo> cant kick it manually
[21:06] <yofel> yes, it's stuck it loading the settings screen it seems o.O?
[21:06] <yofel> *at loading
[21:07] <clivejo> Im getting proxy error
[21:08] <yofel> yes, the proxy is timing out
[21:09] <acheronuk> back in a short while
[21:09] <clivejo> acheronuk: did you see what happened in that package?
[21:10] <clivejo> no prob
[21:10] <clivejo> yofel: does KCI write back to LP git?
[21:10] <yofel> yes
[21:11] <yofel> to _(un)stable
[21:11] <clivejo> so if it was working that merge would have been automatic?
[21:11] <yofel> the merger always tries automatic merges. It will just fail if there's conflicts
[21:11] <valorie> hi folks, my son pronounced my old broken testing laptop as well and truly dead, so I'm going to install vbox and put the daily ISO on it 
[21:12] <valorie> couple of questions: how much memory is good to assign to it?
[21:12] <yofel> 2G if you can afford it
[21:12] <clivejo> how is it dead?
[21:12] <valorie> and is it true I can mount the iso without writing it to a USB?
[21:13] <jimarvan> ;)
[21:13] <valorie> he said that when it tries to start, it just exits with no error message
[21:13] <valorie> no startx, etc
[21:13] <valorie> which was my experience as well
[21:13] <clivejo> cant you just format and start again?
[21:13]  * yofel killed jenkins
[21:13] <valorie> the broken hinge seems to have disconnected something essential to the display
[21:14] <yofel> restarting
[21:14] <clivejo> valorie: you need to scold yofel !!
[21:15] <valorie> yofel isn't the one that dropped that laptop onto the floor
[21:15] <valorie> that would be my husband
[21:15] <valorie> :(
[21:15] <valorie> anyway, this laptop is nice and beefy
[21:15] <clivejo> no, but he broke KCI!
[21:15] <yofel> oh, I did that once, that's how I ended up with a headless server.......
[21:16] <valorie> should be able to do multiple VMs if necessary
[21:16] <yofel> well, there we go
[21:16] <valorie> weeeeee
[21:16] <valorie> Sysinfo for 'valorie-GT60-2PC': Running inside KDE Plasma 5.6.3 on Ubuntu 16.10 (Yakkety Yak) powered by Linux 4.4.0-23-generic, CPU: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz at 3148-3506/3800 MHz, RAM: 23694/24030 MB, Storage: 300/967 GB, 329 procs, 242.4h up
[21:16] <jimarvan> :(
[21:16] <yofel> I think I'll stop trying to open any settings today..
[21:17] <jimarvan> something bad happened?
[21:17] <clivejo> yofel: Im only messing, do what ever you were doing
[21:17] <clivejo> I was only showing acheronuk how things work
[21:18] <yofel> not while it has active running builds
[21:18] <acheronuk> clivejo: nope. what happened?
[21:18] <yofel> I'll just end up having to clean up the mess
[21:18] <clivejo> aborted
[21:18] <clivejo> queue should be empty
[21:18] <clivejo> acheronuk: Project merger_kinit build #627: FIXED in 16 sec: http://kci.pangea.pub/job/merger_kinit/627/
[21:18] <yofel> now it's running the daily promotion ^^
[21:19] <yofel> just leave it running
[21:19] <clivejo> okay
[21:19] <clivejo> does it still ignore the NOCI message?
[21:20] <acheronuk> aha!
[21:20] <clivejo> did you capture the log?
[21:21] <acheronuk> me? the staging? yes
[21:21] <clivejo> can you copy and pastebin the section when it was processing krunner
[21:21] <clivejo> Ive checked on depot and its there
[21:21] <acheronuk> 2 secs
[21:23] <clivejo> /stable/frameworks/5.24/krunner-5.24.0.tar.xz
[21:24] <acheronuk> http://paste.ubuntu.com/18582959/
[21:24] <clivejo> ah
[21:24] <clivejo> looking in portingAids
[21:25] <clivejo> in KA
[21:25] <clivejo> open packaging-exceptions.json
[21:26] <clivejo> and take krunner out of    "packages-in-porting-aids": ["kdelibs4support", "khtml", "kjs", "kjsembed", "kmediaplayer", "kross", "krunner"]
[21:26] <acheronuk> done
[21:27] <clivejo> commit and push back to LP
[21:27] <jimarvan> hmm >_>
[21:27] <yofel> ok, I think I managed giving kubuntu-ninjas CI "user" permissions
[21:30] <acheronuk> clivejo: permission denied
[21:30] <clivejo> humm
[21:31] <acheronuk> http://paste.ubuntu.com/18583346/
[21:31] <jimarvan> omg give the guy permission!
[21:31] <jimarvan> :D
[21:32] <yofel> acheronuk: what does 'git remote -v' say?
[21:32] <clivejo> ah
[21:32] <acheronuk> origin  git://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation (fetch)
[21:32] <acheronuk> origin  git://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation (push)
[21:33] <yofel> ah yeah, that's anonymous. You need the proper user url. 'git remote remove origin; git remote add origin lp:~kubuntu-packagers/+git/kubuntu-automation'
[21:33] <yofel> assuming 'lp' is set up
[21:34] <acheronuk> ah. yes. I cloned that anon originally
[21:34] <acheronuk> forgot that
[21:38] <clivejo> yofel: why was krunner in porting aids?
[21:39] <yofel> no idea
[21:39] <clivejo> strange
[21:39] <acheronuk> what is the point of that? briefly?
[21:40] <yofel> acheronuk: list of packages inside http://download.kde.org/stable/frameworks/5.23/portingAids/
[21:40] <clivejo> acheronuk: https://www.kde.org/announcements/announce-frameworks5-beta1.php
[21:41] <clivejo> they intend to be phased out 
[21:41] <acheronuk> I see
[21:41] <clivejo> which I cant understand why krunner was there
[21:42] <acheronuk> maybe they didn't either :P
[21:42] <clivejo> once everything is ported to KF5 they shouldnt be needed any more
[21:42] <clivejo> but krunner is a major part of Plasma 5
[21:43] <acheronuk> it does seem odd
[21:43] <clivejo> no way they be phasing that out
[21:44] <clivejo> very strange!
[21:45] <clivejo> is there anything else in manual?
[21:45] <yofel> well, it's now just in the regular tarball set
[21:46] <acheronuk> nope. it was just that as far as I can see
[21:49] <clivejo> yofel: so if we add Qt dev packages to dev-package-name-lists/frameworks-yakkety.json that would auto bump the Qt build dependencies?
[21:49] <acheronuk> so can I log in to KCI?
[21:49] <yofel> try it, should work as long as you make sure your kubuntu-ninjas membership is checked in the login
[21:49] <clivejo> acheronuk: should be able to, but dont push any buttons unless yofel finishes what hes doing
[21:50] <yofel> I'm done
[21:50] <yofel> clivejo: *should* work
[21:50] <yofel> I don't think it validates the list against something else
[21:50] <clivejo> is there a list of Qt build deps?
[21:51] <acheronuk> I'm in, but I'm not pushing anything yet!
[21:51] <yofel> not that I know of
[21:52] <clivejo> yofel: do you know what this file does?  https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/conf/versions.json
[21:53] <yofel> seems to be used for tarball download. No idea why qt is in there
[21:53] <clivejo> hummm
[21:54] <yofel> although santa might've had a use for that
[21:54] <clivejo> where did he disappear to?
[21:58] <yofel> no idea, haven't seen him in ages
[22:02] <acheronuk> Ok. Calling it a night here I think. Thanks for the promotion! 
[22:02] <jimarvan> :D
[22:02] <jimarvan> have a good good rest mate
[22:02] <jimarvan> you earned it
[22:03] <acheronuk> New things to learn is good. :)
[22:03] <ahoneybun> night acheronuk
[22:03] <clivejo> night night Rik
[22:03] <clivejo> thanks for all the help :)
[22:03] <ahoneybun> I'm guessing yofel did the upgrade for Rik
[22:04] <yofel> yes
[22:05] <clivejo> yofel: why does git-clone-all and staging upload use a different directory structure?
[22:08] <clivejo> staging upload creates a folder called git and clones into that, while git-clone-all just clones into the root for that package
[22:08] <clivejo> ie attica/debian and attica/git/debian
[22:09] <yofel> because people wrote them differently?
[22:11] <clivejo> so which structure is ubuntu-archive-upload written to use?
[22:12] <yofel> former
[22:12] <yofel> er no
[22:12] <yofel> latter
[22:13] <yofel> staging-upload and ubuntu-archive-upload are from the original script set. git-clone-all is from santa
[22:13] <clivejo> ok, well I rm my original staging_upload workspace
[22:14] <clivejo> and grabbed it again via git-clone-all and it keeps crashing
[22:15] <yofel> will have to wait till tomorrow. I'm off to bed - nini
[22:15] <clivejo> ok, night
[22:17] <jimarvan> gonna hit the bed too
[22:17] <jimarvan> good night peeps! :D
 yofel just got the invoice for linode
 Account should have 12 mouths of credit
[23:32] <ahoneybun> yofel: ^
[23:32] <ahoneybun> going to add a sponsor spot for Linode on the site
[23:37] <ahoneybun> mm I can't save a draft
[23:43] <ahoneybun> also need the Linode account setup completed for the credit to work I think