[00:08] -kubuntu-ci:#kubuntu-devel- Project artful_stable_libkdcraw build #55: FAILURE in 18 sec: https://kci.pangea.pub/job/artful_stable_libkdcraw/55/
[00:08] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_libkleo build #52: FAILURE in 8.5 sec: https://kci.pangea.pub/job/zesty_stable_libkleo/52/
[00:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpeople build #104: FAILURE in 36 sec: https://kci.pangea.pub/job/zesty_unstable_kpeople/104/
[00:09] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_elisa build #53: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/artful_unstable_elisa/53/
[00:10] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkipi build #51: FAILURE in 7.5 sec: https://kci.pangea.pub/job/artful_unstable_libkipi/51/
[00:10] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkomparediff2 build #52: FAILURE in 27 sec: https://kci.pangea.pub/job/artful_unstable_libkomparediff2/52/
[00:18] -kubuntu-ci:#kubuntu-devel- Project artful_stable_dolphin build #52: FAILURE in 50 sec: https://kci.pangea.pub/job/artful_stable_dolphin/52/
[00:18] -kubuntu-ci:#kubuntu-devel- Project artful_stable_knotes build #45: FAILURE in 50 sec: https://kci.pangea.pub/job/artful_stable_knotes/45/
[00:18] -kubuntu-ci:#kubuntu-devel- Project artful_stable_akregator build #36: FAILURE in 50 sec: https://kci.pangea.pub/job/artful_stable_akregator/36/
[00:18] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kontact build #37: FAILURE in 50 sec: https://kci.pangea.pub/job/artful_stable_kontact/37/
[00:19] <gsilvapt> What can be done to fix an error returning something like Depends: libsnapd-qt-dev but it is not installable
[00:19] <gsilvapt> Is it wrong "versioning" of the dependency again?
[00:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #130: FIXED in 1 hr 11 min: https://kci.pangea.pub/job/zesty_unstable_calligra/130/
[00:21] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Artful Alpha 1] has been marked as ready
[00:25] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kalzium build #52: STILL UNSTABLE in 55 min: https://kci.pangea.pub/job/artful_stable_kalzium/52/
[00:25] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ark build #54: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/artful_stable_ark/54/
[00:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_phonon build #34: FAILURE in 29 sec: https://kci.pangea.pub/job/zesty_unstable_phonon/34/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #143: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_unstable_kitemmodels/143/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcrash build #126: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_unstable_kcrash/126/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcompletion build #134: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_unstable_kcompletion/134/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ki18n build #124: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_unstable_ki18n/124/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcodecs build #132: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_unstable_kcodecs/132/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #197: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_unstable_kdbusaddons/197/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #195: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_unstable_kjobwidgets/195/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #155: STILL UNSTABLE in 1 hr 23 min: https://kci.pangea.pub/job/xenial_unstable_calligra/155/
[00:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kjs build #446: FAILURE in 50 sec: https://kci.pangea.pub/job/xenial_unstable_kjs/446/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_phonon build #41: FAILURE in 50 sec: https://kci.pangea.pub/job/xenial_unstable_phonon/41/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_solid build #411: FAILURE in 50 sec: https://kci.pangea.pub/job/xenial_unstable_solid/411/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_attica build #473: FAILURE in 50 sec: https://kci.pangea.pub/job/xenial_unstable_attica/473/
[00:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kfilemetadata build #44: FIXED in 15 min: https://kci.pangea.pub/job/artful_unstable_kfilemetadata/44/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #461: FAILURE in 50 sec: https://kci.pangea.pub/job/xenial_unstable_kcrash/461/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #490: FAILURE in 50 sec: https://kci.pangea.pub/job/xenial_unstable_ki18n/490/
[03:44] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kalzium build #57: FAILURE in 4 hr 0 min: https://kci.pangea.pub/job/artful_unstable_kalzium/57/
[05:28] <IrcsomeBot4> <acheronuk> @ahoneybun from a comment I read in -release, I think cyphermox is on vacation
[05:33] <IrcsomeBot4> <ahoneybun> Ahh
[05:33] <IrcsomeBot4> <ahoneybun> If I had known that I would have pinged someone else
[05:34] <IrcsomeBot4> <ahoneybun> Muon seems to be working good here
[05:35] <IrcsomeBot4> <ahoneybun> installs stuff fine and does not crash on shutdown
[05:37] <acheronuk> [14:48]  <seb128> slangasek, hey, do you know who could be pinged about nplan autopkgtests blocking the  n-m update in artful while cyphermox_ is on vac?
[05:50] <acheronuk> gsilvapt: that dep simply does does not exist in Xenial. have reverted it, as upstream fixed it so it's not asked for until we actually start building the snap backened for discover, and it's not ready yet so is set to 'off' for now
[05:58] <acheronuk> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1447144
[05:58] <ubottu> Launchpad bug 1447144 in ubiquity (Ubuntu) "oem-config forgets to update /etc/sddm.conf" [High,Triaged]
[06:00] <acheronuk> https://irclogs.ubuntu.com/2017/04/13/%23kubuntu-devel.html#t02:04
[06:07] <valorie> dang, now I remember that conversation
[06:07] <valorie> I guess he forgot to fix, or push the fix
[07:31] <acheronuk> yofel: KCI = no space left on device o_O
[08:00] <lordievader> No monitoring?
[08:09] <acheronuk> run out of inodes? WTF
[08:21]  * acheronuk leaves that well alone
[08:30] <lordievader> Lots of small files?
[08:32] <acheronuk> presumably, but quite where I'm not sure. 
[08:37] <acheronuk> hmmm.... too many build logs etc stored in /var/lib/jenkins/jobs/ maybe?
[08:37] <lordievader> Usually with lots of small files you will earlier run into the inode boundary than the file sizes.
[08:41] <acheronuk> well / has used 100% of it's inodes, with /dev/mapper/kubuntu--vg-root 3276800 3276800 0 100% /
[08:42] <acheronuk> file/dir count in /var/lib/jenkins/jobs/ is 2820873
[08:43] <lordievader> In that case you might consider putting that folder on a seperate volume.
[08:43] <acheronuk> so that is using 2.8M out of the 3.2M available inodes
[08:44] <lordievader> Then you can also tune the fs to allocate more inodes.
[08:44] <acheronuk> the workspaces are, but not the jobs folder it seems :/
[09:12] <sitter> acheronuk: https://plugins.jenkins.io/discard-old-build
[09:13] <sitter> in neon we simply have a timed job running that archives old builds onto a different disk
[09:15] <sitter> there is very little point in keeping builds that are months old available through jenkins. to that end, if one simply moves the actual numbered build dir to a different disk one can simply move it back in should one find the need to look at the data through the webui
[09:21] <IrcsomeBot4> <gsilvapt> @acheronuk what do you mean with "revert"? Is it something I can do?
[09:23] <acheronuk> sitter: thanks. had just found that plugin. that or something like you also say sounds a good plan 
[09:24] <acheronuk> gsilvapt: I did https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/discover/commit/?id=83fb9fdb776502f8fd72d2b3dab922a40bdb5fcf
[09:26] <hajix> hi there
[09:26] <hajix> how r u guys
[09:26] <hajix> any body is here for helping 
[09:26] <hajix> im in elementary os with no liber office
[09:26] <hajix> and i download liber from the offical site 
[09:26] <hajix> and then i extracted
[09:26] <hajix> but in the folder there is a lot of deb files
[09:26] <hajix> i dont know how to install
[09:26] <hajix> witch one to install 
[09:26] <hajix> HELP!
[09:26] <acheronuk> gsilvapt: saying that, in unstable we can maybe build the plugin for now. I only set it not to build for stable/artful archive as the KDE developer advised it wasn't working properly yet
[09:27] <gsilvapt> So, basically you checked where that dependency was being used or you  checked when it was inserted and why, and since it isn't needed for the package itself, you decided it was a safe bet to remove it?
[09:28] <gsilvapt> hajix, this is not the right channel to ask for that kind of support. #libreoffice-channel should be it.
[09:28] <hajix> tnx for answer.
[09:29] <gsilvapt> Thanks for the explanation, acheronuk.
[09:29] <hajix> bot no body in this channle
[09:29] <acheronuk> gsilvapt: cmake was wanting it, so I added it, then thought "hey, this shouldn't be asked for if we are not building the snap backend", so I then asked the kde -dev if he should really only have cmake ask for that it the snap backend is set to build, yo which he agreed and made a change so it wasn't
[09:30] <gsilvapt> hajix, there's a bunch of ways to ask support for Libreoffice in https://www.libreoffice.org/get-help/community-support/
[09:31] <acheronuk> gsilvapt: so he did https://cgit.kde.org/discover.git/commit/?id=1ff711c54630b665988a728d6318f06004d598ed
[09:31] <hajix> gsilvapt, thanks for helping 
[09:31] <hajix> bye
[09:32] <gsilvapt> But if you downloaded the .deb file it is available in the website, you should be able to install it via software center (double-click) or via terminal (sudo dpkg -i /path/to/debFile
[09:32] <gsilvapt> Annddd, he is gone.
[09:32]  * acheronuk shrugs
[09:33] <gsilvapt> Ok, I see it. I'm trying to understand how I could have figure out this, so apologies for the questions :) 
[09:35] <acheronuk> np. some of the things require a bit of knowledge of what has been done previously, and the reasoning behind it.
[09:36] <gsilvapt> Yes, I'm realizing that now
[09:37] <acheronuk> I suppose we could exhaustively document all the changes and decisions we make, but seems a bit OTT
[09:37] <acheronuk> being a bit more verbose in git commits might help
[09:39] <acheronuk> right. back later.
[09:39] <acheronuk> I've not touched any of those files on jenkins. If anyone more competent at server management wants to do so, please do!
[10:19] <BluesKaj> Hiyas all
[14:22] <acheronuk> sitter: if we as a stopgap were to use the built in discard old builds property, would something like this make sense in the build template? http://paste.ubuntu.com/24989309/ 
[14:24] <acheronuk> or yofel if around? ^^^
[14:34] <sitter> can't say, I am not using it. the values certainly look reasonable
[14:40] <acheronuk> sitter: thank you. fair point. at least knowing it doesn't look completely mad is helpful
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1613: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1613/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1613: SUCCESS in 1 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1613/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1613: SUCCESS in 4 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1613/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1613: SUCCESS in 4 min 23 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1613/
[15:27] <clivejo> I think the only way to sort it is the increase the inodes on the Filesystem?
[15:27] <clivejo> the KCI interface is totally locked up
[15:28] <acheronuk> clivejo: interface is ok here now for me
[15:28] <clivejo> you can log in?
[15:28] <acheronuk> yes
[15:28] <clivejo> ah, won't let me
[15:29] <clivejo> what device is the problem?
[15:29] <acheronuk> I couldn't earlier, but I deleted a few logs to free it up that much for me
[15:30] <clivejo> ah, Im in now
[15:30] <clivejo> you installed that plugin?
[15:30] <acheronuk> root!
[15:30] <acheronuk> nope
[15:30] <clivejo> I don't understand how the disks are setup
[15:31] <clivejo> some kind of raid
[15:31] <clivejo> sda, sdb, sdc, sdd
[15:31] <acheronuk> there is a built in version. Just not as configurable as the plugin Harald linked to
[15:32] <acheronuk> clivejo: http://i.imgur.com/yo1P2P7.png
[15:32] <acheronuk> the built in job option ^^^
[15:32] <clivejo> sdb looks like a mirror of sdd
[15:33] <clivejo> and sda = sdc
[15:34] <clivejo> we have plently of disk space
[15:37] <clivejo> weird
[15:37] <clivejo> /dev/mapper/kubuntu--vg-root                           3276800 3276564       236  100% /
[15:38] <clivejo> wereas all the workspace ones are low
[15:38] <clivejo> /dev/mapper/kubuntu--storage--vg-jenkins--workspaces   7864320  431820   7432500    6% /var/lib/jenkins/workspaces
[15:39] <clivejo> don't understand how this is configured
[15:40] <acheronuk> which is why I was just looking at maybe automating some job log clean up, until Phil can look
[16:19] <acheronuk>  /var/lib/jenkins/jobs/mgmt_tooling/builds/
[16:20] <acheronuk> contains 26,919 files!
[17:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #293: ABORTED in 33 min: https://kci.pangea.pub/job/zesty_unstable_messagelib/293/
=== clivejo changed the topic of #kubuntu-devel to: Kubuntu - Friendly computing | Artful Aardvark 17.10 - Alpha 1 - please test! | Support in #kubuntu | Plasma 5.8.7 X Backports, 5.10.2 Z Backports A Staging | Apps 16.04.3 X/Y Backports, 16.12.3 (excluding PIM)  Z Archive 16.12.3 A | FW 5.35 X/Z Backports, A Archive| Phab: https://tinyurl.com/mwh2lkd | QA links: https://is.gd/p7kblH | Package Docs (WIP): https://phabricator.kde.org/w/kub
[18:58] <ahoneybun> acheronuk: http://www.ocsmag.com/wp-content/uploads/2017/06/nomad-settings.png
[18:58] <ahoneybun> is that the new settings or did they make their own?
[19:03] <IrcsomeBot4> <acheronuk> the new KDE one I think
[19:03] <IrcsomeBot4> <ahoneybun> ahh nice
[19:51] <ronnoc> Nice! There's not 154 acres of un-used real eastate :-)
[19:54] <ronnoc> Looks like Discover...using Kirigami I assume? Consistency is a Good Thing™
[19:56] <IrcsomeBot4> <acheronuk> correct. systemsettings in master has been porred to kirigami for that list view style
[19:56] <IrcsomeBot4> <acheronuk> *ported
[19:57] <ronnoc> very nice indeed
[21:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #294: FAILURE in 4 hr 0 min: https://kci.pangea.pub/job/zesty_unstable_messagelib/294/
[21:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #295: FIXED in 35 min: https://kci.pangea.pub/job/zesty_unstable_messagelib/295/