[04:48] <ahoneybun> valorie: I talked to yofe and one of the options was using qml/qt quick
[04:48] <ahoneybun> as a quick fix for this release
[04:50] <ahoneybun> I even added Calligra as an option in my script
[04:50] <ahoneybun> even if I don't use it lol
[04:50] <valorie> so it's like a partial port, rather than a full one?
[04:51] <valorie> I'd like to start using it
[04:51] <ahoneybun> well we need to port the installer to Qt5 since it is on Qt4
[04:51] <valorie> I'm not so in love with libreoffice
[04:51] <ahoneybun> that works fine for me
[04:51] <ahoneybun> but it's an option
[04:51] <ahoneybun> https://github.com/ahoneybun/fresh-install-script
[04:51] <valorie> yes
[04:51] <ahoneybun> the port might be a big deal and timely
[04:52] <ahoneybun> for sure would not make it in to yakkety if it was started
[04:52] <ahoneybun> my friend said he would look at it when he has time
[04:52] <valorie> we need to split the package, right?
[04:52] <ahoneybun> (he is a developer for a local business that uses his software that is a custom Ubuntu)
[04:52] <ahoneybun> it is split
[04:53] <valorie> OK
[04:53] <ahoneybun> the installer and slideshow are different
[04:53] <valorie> ok
[04:53] <ahoneybun> tbh I don;t know the whole thing
[04:53] <ahoneybun> I know that qtwebkit was dropped in Qt5 or something
[04:53] <ahoneybun> so it's not in our repos
[04:53] <ahoneybun> our frontend is in Qt4 Python
[04:54] <ahoneybun> from my understanding anyway
[06:40] <acheronuk> ahoneybun: yes, it's qtwebkit being dropped in the Yakkety pyqt4 packages that is the problem.
[06:42] <acheronuk> means the pyqt4/kde frontend to the installer can't work with those qtwebkit based slides, unless the whole kde/qt installer is ported to pyqt5 which does still support qtwebkit
[08:51] <soee> !info libkf5newstuff5
[09:14] <vip> hi ho
[09:18] <soee> hiho vip
[09:36] <jimarvan> heyllo all
[09:36] <jimarvan> any news from the front?
[09:41] <acheronuk> hi :) front what?
[09:42] <acheronuk> Aaron is/was working on getting some slides fixed up for the installer I think...
[09:43] <acheronuk> Plasma is still stuck in YY. Apps need a rebuild?
[11:43] <soee> omfg ..
[11:44] <soee> i have returned screen with bad pixel few days ago, now i bpught new one and after 5 min it has also bad pixel ...!!!!!
[11:46] <mamarley> Ugh, bad pixels suck.
[11:48] <mamarley> I seem to have had pretty good luck recently though.  My newer laptop, my two 1920x1080 panels at work, and my two 3840x2160 panels at home all have no stuck or dead pixels.  My first laptop, though, was a disaster.  I had to send it in to get the display replaced twice because of stuck pixels.
[12:08] <soee> mamarley: well this one in 29"
[12:09] <soee> with curved screen, IPS matrix etc. i like the design a lot to
[12:10] <soee> LG couldn't fixed it so i'm taking moenyback but they proposed some 34" as a replace but ugly tbh
[12:28] <soee> accidently posted on support chan: RIO nr 3: https://www.youtube.com/watch?v=kA-vCAd-3mY
[12:30] <acheronuk> soee: eek!
[12:57] <Esokra> is 5.7.2 planned to land in 16.10?
[12:58] <Esokra> how to test? shall i use the staging ppa? how far away from landing in the repos is it actually? what needs to be done?
[12:59] <yofel> Esokra: it's in yakkety-proposed (stuck in packagekit)
[12:59] <Esokra> yofel: oh ... how come proposed is not mentioned in the ubuntu-package search?
[13:00] <yofel> no clue..
[13:00] <Esokra> what do you mean by stuck in packagekit?
[13:00] <yofel> well, it's not a source that people should be using - it's just a technical thing
[13:01] <Esokra> what does "it's" refer to?
[13:02] <Esokra> one thing of special interest, are all kde packages now also built with -fpie as default? because checksec showed me in stock kubuntu 16.10 that pie and relro were disabled for a lot of things ... maybe, because things currently are quite old and have not been rebuilt since the global change in gcc?
[13:04] <Esokra> i guess "it's" refers to the proposed repo, i got somehow confused by the word "stuck" ... 
[13:07] <yofel> yes, it is proposed. 'stuck' refers to the auto-QA that runs before packages move from proposed to release (the situation is somewhat complex)
[13:07] <yofel> as for -fpie, I don't know. Whatever the curren gcc6 default is
[13:07] <yofel> *current
[13:08] <BluesKaj> Howdy all
[13:08] <yofel> o/
[13:14] <tsimonq2> yay, at the dentist
[13:14] <tsimonq2> :/
[13:14] <tsimonq2> time between getting looked at and the cleaning
[13:15] <BluesKaj> hey yofel , I've set the fonts wit root permissions in systemsetings to be large on this tv/monitor , but the changes don't happen when I open muon for example and check 'configure software sources' the reulting window still uses the default small fonts, same goes for kata or dolphin...any app that needs to be root. This problem has been with us since plasma5 and I can't seem to finsd a fix for it
[13:22] <yofel> BluesKaj: I fear I have no idea. I would expect it to write the necessary settings to /root/.config/ - unless something (sudo?) overrides the storage location (which is supposed to be $XDG_CONFIG_HOME (default ~/.config/) I believe)
[13:28] <BluesKaj> yofel, well I'm disappoinred with the lack of attentionto this matter ...guess I should file a bug 
[13:30] <yofel> BluesKaj: how *exactly* do you run systemsettings?
[13:45] <acheronuk> I get this by default. Seems readable to me? http://i.imgur.com/nUGGHYI.png
[13:46] <yofel> he did say TV, and that might indeed be too small
[13:50] <acheronuk> oh, so he did. sorry
[14:11] <BluesKaj> yofel, in the run command/krunner 'kdesudo systemsettings5'
[14:20] <ahoneybun> mm 
[14:20] <ahoneybun> that's in good old Qt4 or something
[14:24] <yofel> that's a custom kde4 thing we wrote back in the days
[14:24] <ahoneybun> for kdesudo?
[14:24] <yofel> kdesudo
[14:25] <yofel> today you're supposed to use pkexec, but that intentionally requires explicit whitelisting gui applications
[14:26] <yofel> but regardless of the fonts, dolphin doesn't work at all for me as root
[14:27] <soee> fu kamail!
[14:27] <soee> *kmail
[14:28] <soee> it removed everything from my inbox oO local and remote content
[14:28] <soee> when i clicked to open one mail
[14:28]  * ahoneybun tries to use wget to download a deb file
[14:28] <soee> what a day what a day ..
[14:29] <ahoneybun> there we go
[14:31] <genii> when does do-release-upgrade -d work to go from xenial to yakkety, after Beta 1 freeze?
[14:31] <ahoneybun> it does work, just breaks things
[14:32] <genii> Right now it tells me no candidate
[14:32] <ahoneybun> you have to change it to normal releases
[14:32] <ahoneybun> its on only LTS releases 
[14:32] <genii> Ah, got it
[14:39] <santa_> good afternoon everyone
[14:41] <ahoneybun> heyo santa_
[14:45] <soee> hiho
[14:50] <santa_> acheronuk: do we have the ppa's working again or not yet?
[14:52] <acheronuk> santa_: the apps one was increased to 25GB, and that seems ok for now. apps built, but with errors to sort. but probably a rebuild for YY needed with gcc6
[15:18] <genii> Yeah lots of breakage with do-release-upgrade so far, groaning about i386 zlib, libc6, and some others
[15:30] <BluesKaj> hey genii , I managed to get a successful upgrade to 16.04 from 14,04 without breakage, ...got lucky I guess
 Genii is moving from 16.04 to 16.10
[16:40] <soee> :)
[16:40] <soee> https://phabricator.kde.org/M58/178/
[16:43] <yofel> wow
 That's nice
[16:48] <acheronuk> ahoneybun: yofel currently in neon-dev http://i.imgur.com/CFIgqAv.png
[16:49] <yofel> hm, that feels a bit too simple.. or maybe the input and button don't feel right with that fuzzy transparent background
[16:49] <yofel> I like the idea though
[16:49] <soee> we could grab and change a bit neon plymouth
[16:50] <genii> Interesting, must be in runlevel 2-5 for postinstall of apt 1.3~pre3 to complete
[16:50] <soee> replace their logo with Kubuntu and ame with text
[16:51] <soee> this is how Media Player widget will look more or less in Plasma 5.8 - my design :) 
[16:51] <soee> http://wstaw.org/m/2016/07/22/media-player-t2.png
[16:52] <soee> where will be also shuffle and repeat controls
[16:52] <yofel> well, that's certainly better than the current oen
[16:52] <soee> wasn't hard to create better layout than current 
[16:53] <yofel> might be, but it also feels right, so good job
[16:56] <acheronuk> I also like the new splash http://i.imgur.com/IVggNLb.png
[16:56] <acheronuk> even if it is a bit windows startup like
 I'd rather have the gear turn
 Looks cool soee
[17:03] <soee> acheronuk: i like GRUB style in Neon :D
[17:14] <santa_> yofel: inb4 the gcc 6 symbols fixes I'm doing may not turn off the red light of the KCI, if they doen't maybe the solution would be fixing the builder.rb from the ci-tooling
[17:14] <santa_> s/doen't/don't/
[20:24] <acheronuk> I assume a rebuild of apps for YY and then bugfix of them has to be done before the feature freeze so Yofl can upload to archive?
[20:25] <acheronuk> and FF is 1 week today!
[20:28] <yofel> should be done, right. Do you want to do the upload? Otherwise I'll prepare the packages today
[20:30] <clivejo> where is santa getting these changes from?
[20:30] <acheronuk> yofel: I'm only popping in for 5/10 mins, so I guess perhaps you should. I may be back in a couple of hrs for a bit, but can't guarantee that.
 yofel what about the slideshow?
[20:32] <clivejo> Im available if you need something?
 If we are a week away
[20:34] <clivejo> yofel: you need a NC rebuild of apps on Yakkety?
[20:34] <yofel> clivejo: yes
[20:35] <clivejo> what are your thoughts on those merge requests from santa?
[20:35] <yofel> ahoneybun: what you had yesterday looked acceptable as an emergency measure (I agree with the spacing after the title though)
[20:35] <yofel> ahoneybun: we might want to get that up over the weekend
[20:35] <yofel> just so we have *something* for yakkety at least
[20:37] <yofel> clivejo: I am wondering whether those are gcc5 or qt5.5 symbols - meaning whether the comment is correct. But I do agree that marking them optional if they suddenly go missing is the right thing to do
[20:37] <yofel> I don't think anything should get broken by such symbols going missing
[20:37] <clivejo> I just cant seem to generate the same
 I did some changes and I'll post a image in a hour or so
 yofel
 I'll finish the rest today or tomorrow
[20:38] <yofel> clivejo: he was buliding his own builds - which might not have matched what we have?
[20:38] <yofel> clivejo: what did you build against?
[20:38] <clivejo> yakkety archive
[20:38] <yofel> ahoneybun: excellent, thanks!
 Not sure how to make them 'slide'
[20:38] <clivejo> with proposed
[20:38] <yofel> clivejo: including proposed?
[20:38] <yofel> hm
 Now we know what we need to do next release lol
[20:39] <yofel> or those really are qt5.6 symbols and he built with 5.5
[20:39] <clivejo> I really cant get my head around it
[20:39] <yofel> ahoneybun: port ubiquity? ^^
 That's a huge thing to port
 This is the easy fix
 Temp if anything
[20:41] <yofel> right
 You said you would not work on it as the license is insane
 And I agree and respect the decision
[20:42] <yofel> I could work on it, but that would have no chance to get merged back in. Maybe we could make a forked kde-ui package with just the UI, but I haven't looked at how feasable that is
[20:43] <valorie> we have time before our next LTS for a long-term fix
 Yea but that's for next release planning
[20:43] <yofel> ack
 UOS planning
 (Photo, 960x1280) https://irc-attachments.kde.org/gRIrlm4Y/file_151.jpg
 Fueling up for work
[20:48]  * clivejo grabs an apple
[20:54] <valorie> time to face the heat and do the watering
[20:54] <clivejo> send me some heat
[20:55] <clivejo> been a miserable day here
[20:55] <yofel> been slightly warmer than yesterday here. The morning was 13° and a buddy told me he had 7° - we have summer, right?
[20:56] <ahoneybun> and I'm home
[20:57] <ahoneybun> yofel: do I just send you the qml files?
[20:57] <yofel> what did you use as the source?
[20:57] <ahoneybun> I'm just making them atm
[20:57] <ahoneybun> I have the slideshow downloaded
[20:58] <yofel> so you fetched the package?
[20:58] <ahoneybun> since I grabbed the images and text from the html files
[20:58] <ahoneybun> bzred it
[20:58] <yofel> can't you make a bzr branch?
[20:58] <ahoneybun> as make mine and merge?
[20:58] <yofel> right
[20:59] <ahoneybun> well I need to look into the python and see how it calls the slideshow
[20:59] <yofel> ack
[21:00] <ahoneybun> so it loads a conf file
[21:00] <ahoneybun> slideshow_config.read(os.path.join(slideshow_path,'kubuntu/slideshow.conf'))
[21:00] <ahoneybun> oh
[21:00] <ahoneybun> thats just the side of the window
[21:00] <ahoneybun> looks at the index.html
[21:01] <ahoneybun> mm this kinda breaks our translations
[21:01] <ahoneybun> but since I use the same words it might be a easy fix
[21:05] <ahoneybun> not sure if I should follow that conf file in size
[21:09] <ahoneybun> any idea yofel?
[21:10] <yofel> no, maybe ask whoever worked on it last?
[21:11] <ahoneybun> mm
[21:17] <ahoneybun> yofel: I'll bug around #ubuntu-devel
[21:20] <genii> After much cursing and rending of hair and gnashing of teeth, I finally managed to get this machine next to me from Xenial to Yakkety
[21:29] <clivejo> genii: any issues?
[21:30] <genii> clivejo: Well, previously I used to go into recovery mode, enable networking and mount rw, then do-release-upgrade from there without issue. but this time some packages require normal runlevels to finish installing instead of single user
[21:30] <ahoneybun> yofel: if all the slideshows use html then should they all not be broken?
[21:31] <ahoneybun> or is it just us for some reaosn
[21:31] <ahoneybun> *reason
[21:31] <yofel> just us as we use *Qt*Webkit
[21:31] <ahoneybun> GTK has it's own?
[21:31] <yofel> yes
[21:31] <ahoneybun> this whole thing is based on html files
[21:31] <ahoneybun> this is going to be a big hack
[21:32] <genii> clivejo: Also apt is graoning some about no Release files on kubuntu-ppas
[21:32] <yofel> hence porting it to qt5 webkit or later qtwebengine would be the appropriate path
[21:32] <yofel> but probably not trivial
[21:32] <ahoneybun> changing this from html to qml might be on the same level
[21:32] <yofel> unless *just* the slideshow can use qt5
[21:34] <ahoneybun> do you know the name of the qt5 one?
[21:35] <ahoneybun> from PyQt5.QtWebKit import *
[21:35] <ahoneybun> this does not work
[21:35] <ahoneybun> from PyQt4.QtWebKit import * was the old one
[21:38] <yofel> I do not, there should be some qt5 porting guide on the net?
[21:38] <ahoneybun> I just changed that one line to test it
[21:38] <ahoneybun> I did installed the new version
[21:40] <ahoneybun> there is : python3-pyqt5.qtwebkit
[21:40] <ahoneybun> I installed that as well
[21:47] <ahoneybun> I got it to start at least
[21:48] <ahoneybun> so progress
[21:50] <santa_> yofel, clivejo: regarding my merge requests I have been building them against qt packages from either: a) yakkety-proposed b)  the landing 024 ppa
[21:50] <santa_> some of them are from b) because not all of them are available in a)
[21:51] <santa_> so it's the closest thing to what we'll have in yakkety
[21:51] <yofel> weird that we haven't seen them then
[21:51] <santa_> well, note that the ppa builds were against gcc 5
[21:51] <santa_> (I think)
[21:51] <clivejo> currently rebuilding - http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.3_yakkety.html
[21:52] <ahoneybun> yofel: changing a few of the libraries got it to open at least
[21:52] <clivejo> ppa50 are the NC rebuilds
[21:52] <ahoneybun> the kubuntu-slideshow.py
[21:53] <santa_> yofel: also note that, at least, the bluez-qt symbol is also gone in the KCI build
[21:54] <santa_> it's not failing because of the dpkg-gensymbols -c0
[21:55] <santa_> I have also other stuff to fix in apps btw
[22:00] <yofel> ok, then I guess I misunderstood clive and he meant the ppa builds
[22:01] <yofel> it would be best if you 2 talk that out, as I know little about the state of apps
[22:01] <yofel> I'll only comment that marking those symbols optional looks correct to me
[22:01] <yofel> *if* that's really gcc6 stuff
[22:02] <ahoneybun> mm not sure why this is not working
[22:05] <santa_> clivejo: about apps I'm right now building a (hopefully) fixed krfb, will make a merge request soon
[22:05] <santa_> there are also other packages failing to build
[22:05] <santa_> right now these ones: http://gpul.grupos.udc.es/buildstatus_ubuntu-exp/ubuntu-exp_status_not-built.html
[22:06] <santa_> I have also a solution in mind for kalzium
[22:06] <santa_> regarding print-manager I bet the recent cups upload to yakkety is the cause of the ftbfs
[22:07] <santa_> and regarding kde4libs I bet there's already a patch out there to make it build against gcc 6
[22:07] <yofel> kalzium is a follow-up error from kde4libs I think
[22:08] <yofel> yes, all packages need to be synced with the archive before upload
[22:08] <yofel> the release team has fixed most of the gcc6 issues based on 15.12 already
[22:09] <santa_> kalzium is failing because of avogadro
[22:09] <santa_> I will check my theory about that soon
[22:11] <clivejo> yofel have we a script for syncing with the archive?
[22:11] <yofel> somewhat, staging-upload does that, but that has not been ported to the new tooling yet - which would've been really handy right now....
[22:12] <santa_> but you aren't using the new tooling yet except for the bumping script right?
[22:12] <santa_> btw, the build logs of frameworks with my fixes: http://gpul.grupos.udc.es/buildstatus_ubuntu-exp/ubuntu-exp_status_frameworks.html
[22:13] <santa_> just checked that the qtbase version is >= 5.6 for bluez-qt
[22:13] <yofel> yes, but staging-upload cannot really be run now, so that's not really useful
[22:13] <yofel> and ubuntu-archive-upload has no changelog verification
[22:14] <yofel> santa_: frameworks for unstable / 5.25?
[22:15] <santa_> yofel: I haven't build them, but I could if you want
[22:15] <santa_> did you?
[22:15] <yofel> 5.24 is already in proposed
[22:15] <yofel> so if there were any gcc6 issues someone else fixed those
[22:15] <yofel> same for plasma
[22:15] <santa_> there wasn't any issue with plasma
[22:16] <santa_> let me check the frameworks status in proposed...
[22:16] <yofel> well, the ci builds frameworks, so that's covered if we want to update it
[22:17] <santa_> because of the -c0
[22:17] <yofel> yes, I mean that should be green if we want to update it
[22:17] <santa_> outside the kci they would fail
[22:17] <yofel> but we don't need another test build
[22:18] <santa_> ok
[22:18] <yofel> fixing apps 16.04.3 up for upload is the highest priority right now
[22:18] <santa_> about proposed: https://launchpad.net/ubuntu/+source/bluez-qt
[22:19] <santa_> ↑ the frameworks ftbfs'ing with gcc 6 probably weren't fixed by someone else
[22:19] <yofel> that's all built?
[22:19] <santa_> it's just that they were built by gcc5 so they are built
[22:19] <yofel> ah ok
[22:20] <santa_> but as soon as you rebuild them with gcc 6 they will fail
[22:20] <yofel> right, I remember someone talking about rebuild failures, but until the whole qt5.6 blob migrates, that's in a do-not-touch state
[22:20] <clivejo> but surely your merges should be going into kubuntu_unstable ?
[22:21] <yofel> frameworks should go to _unstable, apps should go to _archive
[22:21] <clivejo> sorry, Im just confused here
[22:22] <clivejo> The merge requests santa_ has submitted are for yakkety_archive branch
[22:22] <valorie> clivejo: 26 here; you can have 10 of that for sure
[22:23] <yofel> clivejo: well, check how the ppa rebuild goes, that *should* show the same issues
[22:23] <santa_> the merge resuets I did, are indeed targeted to kubuntu_yakkety_archive
[22:23] <santa_> BUT
[22:23] <santa_> they must be merged in kubuntu_unstable as well
[22:23] <yofel> *that* is automatic
[22:23] <ahoneybun> yofel: I put what I have in here :https://code.launchpad.net/~aaronhoneycutt/ubiquity-slideshow-ubuntu/yakkety
[22:23] <yofel> ahoneybun: thanks, I'll look tomorrow
[22:24] <santa_> indeed it was automatic, at least back in the days
[22:24] <yofel> it still is
[22:24] <ahoneybun> I'll work on it some more then chill out
[22:24] <clivejo> santa_: would you mind helping me with apps?
[22:24] <ahoneybun> I changed a few versions and adding some modules in kubuntu-slideshow.py
[22:24]  * yofel is slightly confused by now as well
[22:24] <ahoneybun> so it at least launches with no errors
[22:24] <ahoneybun> ./test-slideshow.sh needs glib and gtk crap
[22:24] <santa_> clivejo: yes, I will send you a merge request for krfb soon
[22:25] <clivejo> santa_: Id like to go through them with you using Kubuntu workflow if thats OK?
[22:25] <clivejo> I dont understand your build box 
[22:25] <clivejo> so on http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.3_yakkety.html
[22:26] <clivejo> analitza is saying New symbols#
[22:26] <santa_> clivejo: no prob, you can ignore my build box
[22:27] <clivejo> when I batchpatch the symbols Im getting one marked as missing
[22:27] <clivejo> #MISSING: 4:16.04.3# (optional=templinst)_ZN8Analitza8Analyzer15alphaConversionINS_9MatrixRowEN5QListIPNS_6ObjectEE8iteratorES4_EEvPT_i@Base 4:15.04.0
[22:27]  * acheronuk is slightly confused, just reading that backlog
[22:29] <santa_> clivejo: with that one you can either remove the line, or remove the "#MISSING: 4:16.04.3#" keeping the entry in the symbols file
[22:29]  * yofel -> bed
[22:30] <clivejo> can you explain what that symbol is?
[22:30] <clivejo> ie whats a (optional=templinst) symbol?
[22:30] <valorie> sweet dreams yofel
[22:30] <clivejo> good night yofel
[22:30] <acheronuk> night :)
[22:30] <santa_> clivejo: thats something produced by C++ templates if I'm not mistaken
[22:31] <santa_> and being option the fact is missing won't produce a build failure
[22:31] <santa_> s/option/optional/
[22:32] <santa_> clivejo: tldr: just remove it and make sure the new symbol is in the symbols file, this way you will get it green in the status page
[22:32] <santa_> doubts?
[22:34] <clivejo> ok
[22:36] <clivejo> these symbols are just due to building with gcc6?
[22:37] <santa_> maybe, I didn't checked things being orange in the status page, I just checked build failures which are the bigger problem now
[22:38] <santa_> * biggest
[22:48] <acheronuk> kdepim: CMake Warning at CMakeLists.txt:205 (find_package): Could not find a package configuration file provided by "KF5Prison"
[22:49] <acheronuk> Do we have that, and want that added if we do?
[22:49] <valorie> I think prison is new
[22:49] <valorie> !info kf5prison
[22:49] <valorie> hmmm
[22:50] <valorie> !info prison
[22:50] <acheronuk> I've seen though, so that must be only in KCI
[22:52] <santa_> !info libkf5prison-dev
[22:52] <santa_> acheronuk: ↑
[22:54] <acheronuk> oh, yes, frameworks, but not frameworks! 
[22:55] <acheronuk> not sure this is the stage to start adding in more optional build deps though?
[22:56] <clivejo> probably need a new version of that
[22:57]  * clivejo pokes KCI
[22:59] <clivejo> good start!
[23:01] <acheronuk> okular *could* have LibKScreen dev added for "DPI detection support"
[23:02] <clivejo> does it build with it enabled?
[23:03] <acheronuk> that's what I mean, will have to test all that if we start enabling those optionals.
[23:05] <acheronuk> clivejo: fixes would go to yakkety_archive? and ppa uploads increment your ppa50?
[23:06] <clivejo> !info libkscreen-dev
[23:06] <acheronuk> if so, I shall spend a bit of time on it in the morning
[23:06] <acheronuk> !info libkf5screen-dev
[23:08] <clivejo> yes
[23:08] <clivejo> Ive done okular and added that as build dep
[23:09] <acheronuk> that or whatever else needs doing/has not been done, I mean
[23:09]  * clivejo fingers crossed it builds
[23:09] <clivejo> Ive fixed a lot of those symbols errors
[23:09] <clivejo> just LP is taking forever to update the status page
[23:09] <acheronuk> good, I went through the orange and there seems a fair few
[23:10] <clivejo> not sure how many are fixed
[23:10] <tsimonq2> what's up? :D
[23:11] <acheronuk> I'll see what is left in the morning..
[23:11] <clivejo> Id like to know why those are FTBFS
[23:11] <clivejo> santa_: do you know?
[23:12] <santa_> clivejo: yes, except for kde4libs
[23:13] <santa_> clivejo: https://code.launchpad.net/~panfaust/kubuntu-packaging/+git/krfb/+merge/302734
[23:13] <santa_> kde4libs btw isn't failing but I think it will if you rebuild it
[23:16]  * acheronuk wonders what gcc kde's CI builds with now
[23:20] <santa_> acheronuk: pick any recent build log, go to the cmake part, that reports the gcc detected with version
[23:25] <acheronuk> yes, just finding how to get the build log on their jenkins is a pain
[23:26] <acheronuk> 5.2.1
[23:31] <santa_> yeah, I find it difficult too