[04:28] <fone626>
[04:36] <DarinMiller_> santa_: git_checks.py has been fixed: https://code.launchpad.net/~darinmiller/ka/+git/ka/+merge/323422
[04:37]  * DarinMiller_ thinks the mp is always the hardest part of the crazy packaging stuff.
[04:38] <DarinMiller_> wxl: do you want the other script fix? if not I will fix later this weekend.
[05:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_elisa build #7: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/artful_unstable_elisa/7/
[07:15] <lordievader> Good morning
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1487: SUCCESS in 1 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1487/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1487: SUCCESS in 1 min 11 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1487/
[08:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1487: SUCCESS in 3 min 39 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1487/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1487: SUCCESS in 4 min 21 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1487/
[08:51] -kubuntu-ci:#kubuntu-devel- Project merger_calligra build #179: FAILURE in 6.9 sec: https://kci.pangea.pub/job/merger_calligra/179/
[08:55] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:55] -kubuntu-ci:#kubuntu-devel- Project merger_calligra build #180: FIXED in 12 sec: https://kci.pangea.pub/job/merger_calligra/180/
[09:28] <acheronuk> santa_: https://phabricator.kde.org/D5570
[09:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #111: STILL UNSTABLE in 59 min: https://kci.pangea.pub/job/zesty_unstable_calligra/111/
[09:55] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_calligra build #5: NOW UNSTABLE in 1 hr 4 min: https://kci.pangea.pub/job/zesty_stable_calligra/5/
[09:56] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_calligra build #9: STILL UNSTABLE in 1 hr 4 min: https://kci.pangea.pub/job/artful_unstable_calligra/9/
[10:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #134: STILL UNSTABLE in 1 hr 9 min: https://kci.pangea.pub/job/xenial_unstable_calligra/134/
[10:06] -kubuntu-ci:#kubuntu-devel- Project artful_stable_calligra build #7: NOW UNSTABLE in 1 hr 14 min: https://kci.pangea.pub/job/artful_stable_calligra/7/
[10:06] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_calligra build #15: NOW UNSTABLE in 1 hr 14 min: https://kci.pangea.pub/job/xenial_stable_calligra/15/
[10:17] -kubuntu-ci:#kubuntu-devel- Project merger_calligra build #181: FAILURE in 13 sec: https://kci.pangea.pub/job/merger_calligra/181/
[10:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:19] -kubuntu-ci:#kubuntu-devel- Project merger_calligra build #182: FIXED in 11 sec: https://kci.pangea.pub/job/merger_calligra/182/
[10:49] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:49] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #112: FIXED in 57 min: https://kci.pangea.pub/job/zesty_unstable_calligra/112/
[11:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:06] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_calligra build #10: FIXED in 1 hr 9 min: https://kci.pangea.pub/job/artful_unstable_calligra/10/
[11:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #135: STILL UNSTABLE in 1 hr 9 min: https://kci.pangea.pub/job/xenial_unstable_calligra/135/
[11:16] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:16] -kubuntu-ci:#kubuntu-devel- Project artful_stable_calligra build #8: FIXED in 59 min: https://kci.pangea.pub/job/artful_stable_calligra/8/
[11:32] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_calligra build #16: STILL UNSTABLE in 1 hr 14 min: https://kci.pangea.pub/job/xenial_stable_calligra/16/
[11:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:37] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_calligra build #6: FIXED in 1 hr 20 min: https://kci.pangea.pub/job/zesty_stable_calligra/6/
[12:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #384: FIXED in 11 min: https://kci.pangea.pub/job/xenial_unstable_breeze-icons/384/
[12:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:05] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_breeze-icons build #12: FIXED in 11 min: https://kci.pangea.pub/job/artful_unstable_breeze-icons/12/
[12:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-icons build #130: FIXED in 11 min: https://kci.pangea.pub/job/zesty_unstable_breeze-icons/130/
[12:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #136: STILL UNSTABLE in 1 hr 8 min: https://kci.pangea.pub/job/xenial_unstable_calligra/136/
[12:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #111: STILL FAILING in 4 min 46 sec: https://kci.pangea.pub/job/zesty_unstable_kigo/111/
[12:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kigo build #148: STILL FAILING in 5 min 11 sec: https://kci.pangea.pub/job/xenial_unstable_kigo/148/
[12:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kigo build #11: STILL FAILING in 6 min 14 sec: https://kci.pangea.pub/job/artful_unstable_kigo/11/
[13:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kigo build #149: STILL FAILING in 4 min 4 sec: https://kci.pangea.pub/job/xenial_unstable_kigo/149/
[13:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #112: STILL FAILING in 4 min 7 sec: https://kci.pangea.pub/job/zesty_unstable_kigo/112/
[13:00] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kigo build #12: STILL FAILING in 4 min 35 sec: https://kci.pangea.pub/job/artful_unstable_kigo/12/
[14:04] <clivejo> I hate timezones
[14:04] <clivejo> so confusing
[14:04] <DarinMiller_> Ditto
[14:04] <DarinMiller_> timezone + DST per country = extra confusion
[14:05] <acheronuk> it is 14:05 UTC :P
[14:05] <clivejo> I know
[14:05] <clivejo> but my phone is teeling me Im late for the meeting
[14:05] <acheronuk> get a smarter smartphone then
[14:06] <clivejo> I think its the way Ovi scheduled it
[14:06] <acheronuk> he scheduled it?
[14:06] <clivejo> he setup the thingie
[14:07] <acheronuk> wut thingie...>
[14:07] <acheronuk> ?
[14:07] <clivejo> the thingie to remind me about the meeting
[14:07]  * acheronuk shrugs
[14:08] <acheronuk> no 'thingie' here
 (Photo, 1080x436) https://irc-attachments.kde.org/z00u5Nyo/file_2479.jpg
[14:10] <acheronuk> not got that, which seems probably just as well!
[14:15] <acheronuk> santa_: FYI. I uploaded the just released kirigami 2.1 to staging-plasma, and am rebuilding discover against it
[14:15] <acheronuk> for artful
[14:23] <ahoneybun> lovely
[14:23] <ahoneybun> maybe discover won't crash as much
[14:24] <acheronuk> maybe more...
[14:25] <ahoneybun> well since it crashes everytime I try to close it that might be impossible
[14:27] <acheronuk> ahoneybun: Segmentation fault (core dumped)
[14:28] <acheronuk> oh well
[14:28] <clivejo> same here
[14:28] <clivejo> stupid thing
[14:28] <ahoneybun> acheronuk: do you find it funny that the discover screenshot has nautiuls icon as Dolphins icon?
[14:28] <acheronuk> ahoneybun: does it????
[14:28] <acheronuk> where?
[14:29] <ahoneybun> well now they closed that page
[14:29] <ahoneybun> https://lh3.googleusercontent.com/proxy/1A3Dt8VIonWKd0_nG1mzUQUeXyLWpQDoUXgljJ04Cv-XBPOTbmUbaIYmv4VLgCA644jeMtUPZ1hPqh4mY-e5ZUsrwBwp-NLK57zc61rmrII=w530-h322-p-rw
[14:29] <ahoneybun> xD
[14:29] <acheronuk> sigh.....
[14:34] <acheronuk> well. crash is a qtquick thing? so maybe stuck with that until qt 5.9?
[14:34] <clivejo> yofel: are you aware of that message in KCI?
[14:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #113: STILL FAILING in 4 min 37 sec: https://kci.pangea.pub/job/zesty_unstable_kigo/113/
[14:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kigo build #150: STILL FAILING in 5 min 6 sec: https://kci.pangea.pub/job/xenial_unstable_kigo/150/
[14:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kigo build #13: STILL FAILING in 6 min 17 sec: https://kci.pangea.pub/job/artful_unstable_kigo/13/
[14:49] <BluesKaj> Hiyas all
[14:49] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kigo build #14: STILL FAILING in 4 min 39 sec: https://kci.pangea.pub/job/artful_unstable_kigo/14/
[14:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kigo build #151: STILL FAILING in 6 min 4 sec: https://kci.pangea.pub/job/xenial_unstable_kigo/151/
[14:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #114: STILL FAILING in 7 min 8 sec: https://kci.pangea.pub/job/zesty_unstable_kigo/114/
[14:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kigo build #152: STILL FAILING in 4 min 42 sec: https://kci.pangea.pub/job/xenial_unstable_kigo/152/
[14:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #115: STILL FAILING in 5 min 36 sec: https://kci.pangea.pub/job/zesty_unstable_kigo/115/
[15:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kigo build #153: STILL FAILING in 5 min 41 sec: https://kci.pangea.pub/job/xenial_unstable_kigo/153/
[15:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #116: STILL FAILING in 5 min 35 sec: https://kci.pangea.pub/job/zesty_unstable_kigo/116/
[15:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1488: SUCCESS in 58 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1488/
[15:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1488: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1488/
[15:10] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1488: SUCCESS in 3 min 36 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1488/
[15:11] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1488: SUCCESS in 4 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1488/
[15:23] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:23] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kigo build #154: FIXED in 12 min: https://kci.pangea.pub/job/xenial_unstable_kigo/154/
[15:23] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kigo build #15: FIXED in 12 min: https://kci.pangea.pub/job/artful_unstable_kigo/15/
[15:23] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kigo build #117: FIXED in 12 min: https://kci.pangea.pub/job/zesty_unstable_kigo/117/
[15:52] <santa_> good aftnernoon eveyone
[15:52] <DarinMiller> hi santa_
[15:52] <santa_> I've just woke up from an unintended map
[15:52] <santa_> give me a few minutes to become human and check all above pings XD
[15:53] <DarinMiller> :)
[15:53]  * BluesKaj slides santa_  a large strong cooffee
[15:53] <BluesKaj> coffee even :-)
 (Photo, 960x1280) https://irc-attachments.kde.org/ayDBxsX5/file_2484.jpg
 why?
 (Photo, 1280x720) https://irc-attachments.kde.org/0I4f0HKp/file_2485.jpg
 wrong pic
[16:16] <santa_> thanks BluesKaj :)
[16:16] <santa_> I neeed to reboot brb
 (Photo, 1280x960) https://irc-attachments.kde.org/ub0yStn8/file_2486.jpg Oh Windows, you silly thing you
[16:25] <santa_> hi again, let me check the history of the channel...
[16:26] <acheronuk> ok
[16:29] <santa_> ok, so we got a patch from darin for Ka which looks good and also this https://phabricator.kde.org/D5570
[16:30] <santa_> acheronuk: ↑ does this affect 5.9.5?
[16:30] <acheronuk> santa_: that klipper test fails on Neon, with <IP_ADDRESS>
[16:31] <acheronuk> and I think in your build?
[16:32] <acheronuk> santa_: your http://gpul.grupos.udc.es/buildstatus_ubuntu-exp2/ubuntu-exp2_status_plasma.html
[16:32] <santa_> in my build it fails because ot the b-d bumping I guess
[16:32] <santa_> let me check
[16:32] <acheronuk> shows the autotest failure that is meant to fix
[16:32] <acheronuk> plasma-workspace
[16:33] <acheronuk> http://i.imgur.com/5YI2e96.png
[16:34] <santa_> indeed
[16:34] <santa_> acheronuk: about the bd bumping, wasn't plasma-workspace suposed to fail if breeze bd or something wasn't bumped?
[16:35] <acheronuk> santa_: I saw (1) plasma-integration = fail without the b-d bump
[16:37] <acheronuk> (2) plasma-desktop built, but without b-d on breeze bumped it could build without doing so agains latest breeze which it did not like in cmake
[16:39] <santa_> ahhhh, ok
[16:39] <acheronuk> window decoration plugin issue if not bumped I think
[16:39] <santa_> right, so I think my test is valid
[16:39] <santa_> clivejo: ping?
[16:40] <acheronuk> he's gone for a bit. will be back later
[16:40] <santa_> ok, np
[16:41] <santa_> just wanted to explain you how I did that build test and a couple of interesting things from debian
[16:43] <acheronuk> FW ok to upload?
[16:43] <santa_> acheronuk: probably
[16:44] <santa_> I haven't tested the upgrades but other people did
[16:44] <acheronuk> upgraded ok here
[16:44] <santa_> DarinMiller: replied in the MP
[16:45] <santa_> acheronuk: so go ahead and upload fw 5.33 if you want
[16:45] <acheronuk> santa_: do you want to build on your container for any reason, or happy for me to do it here?
[16:46] <acheronuk> here is better for me, as I can gpg sign the tags that way
[16:47] <santa_> acheronuk: do it as it's more convenient for you. I expect KA to work correclty, but if you have any issue let me know
[16:48] <BluesKaj> Artful seems to hang on bootup for about 30 secs looking for a nonexistent hdd, which I removed from the system and deleted from /etc/fstab
[16:48] <santa_> :S
[16:48] <BluesKaj> no biggie , but mildly annoying
[16:49] <acheronuk> santa_: ok. will get on it while waiting for clive
[16:50] <santa_> acheronuk: so, while you work on that I will prepare the remaining stuff for plasma
[17:04]  * acheronuk grins a progress bar
[17:04] <acheronuk> *at
[17:11] <santa_> :)
[17:11] <santa_> still has its small flaws
[17:17] <acheronuk> santa_: ok. all ready to upload
[17:26] <acheronuk> santa_: all uploads accepted. think you should be getting 74 emails :P
[17:28] <santa_> I have them filtered XD
[17:40] <acheronuk> back in a little while
 Back :)
 *pokes* @ovidiuflorin
 I see you!
[17:52] <santa_> http://gpul.grupos.udc.es/ka-iron-hand_reports/frameworks_archive/5.33_artful_proposed_migration.pdf
 @CliffordTheBigRedDoggie, What.
 ?
[17:53] <clivejo> I see you :P
[17:53]  * clivejo waves
[17:53] <santa_> hi ovi
 Aaaa.... Hello?
[17:54] <clivejo> how are you today?
[17:54] <clivejo> relaxing?
[17:54] <santa_> ovi, would you be able/ have time to add a filter by architecture for the status pages?
 You could say that...
[17:54] <santa_> btw according to linkedin you have a new job, congrats
 I have this job since November
[17:55] <santa_> lol
 I just didn't update LinkedIn
 But thanks
[17:55] <clivejo> https://apachelog.wordpress.com/2017/04/26/kde-neon-cmake-package-validation/ interesting
 When do you need that filter by?
[17:56] <clivejo> I would love a package search for our PPA's
 Does lp have a rest api?
[17:57] <clivejo> https://help.launchpad.net/API ?
[17:58] <santa_> yes
[17:58] <santa_> it's being used in the informational part of KA
[17:58] <clivejo> there is a python lib for it
[17:58] <clivejo> santa_: do you have experience/interest in packaging python modules?
[17:58] <santa_> indeed, python[3]-launchpadlib
[17:59] <santa_> clivejo: I don't have much expecience with python packaging except fo KA. what do you have in mind?
[18:00] <clivejo> I'd like to see mycroft packaged, but it would need a number of python modules packaged as well
[18:00] <santa_> btw talking about python, some frameworks have some python bindings. so far we have been skipping it as they are experimental, but I think at some point we should start with them
[18:01] <santa_> clivejo: this https://mycroft.ai/ ?
[18:02] <clivejo> yes
[18:02] <clivejo> not urgent, just something I'm interested in on a side note
[18:03] <santa_> I guess I could try if I have time, packaging python modules shouldn't be hard
[18:03] <santa_> which ones do you need?
[18:03] <clivejo> well I hacked at some to test
[18:04] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/plasma-mycroft
[18:05] <clivejo> but having issues with the mycroft-core package
 santa_: filter architecture: A combobox containing: All, [enumeration of each arhitecture]
[18:05] <santa_> wow, you have been busy!
 hows that?
[18:05] <clivejo> it is designed to install it and setup a system user called mycroft
[18:05] <clivejo> then start the services
[18:05] <santa_> that could be a possible way
 I installed that package before and mycroft would randomly tell me my active code
 santa_ do you have a better idea?
[18:06] <clivejo> but the plasmiod need mycroft running as the local user in order to use KDE skills
[18:06] <santa_> another way would be putting a checkbox for each arch, but the challenge with that approach would be not bloating the top of the page too much
[18:07] <santa_> so maybe the combobox is a better idea
 the combobox, gives just the option of a single architecture, or all of them
 separate filters, bloates the filter area
 what do you actually need?
[18:08] <clivejo> would it be possible to have a floating div with filter and search on it?
[18:08] <santa_> I think the options offered by the combobox would be more than enough
 clivejo, if I add this filter as well, I'd also like to play with the style of the page as well
 make it pretty
[18:09] <clivejo> :)
[18:09] <santa_> ovi, for my build box I'm using a ppa-build-status fork (I need to merge there your filters btw), see: http://gpul.grupos.udc.es/buildstatus_ubuntu-exp2/ubuntu-exp2_status_plasma.html
[18:10] <santa_> sometimes I'm not building the i386 packages, so I would like to see the amd64 only
[18:10] <santa_> wrt to our official status pages, sometimes I would just like to see amd64 only too
[18:11] <santa_> so I have shorter lists to look at
 so I see you have a summary on top
[18:11] <santa_> this isn't urgent, of course, but I think it would be a nice addition
 separated by architecture
 nice
[18:11] <santa_> yeah, I made that, because I need to know when the thing gets stalled
[18:12] <santa_> note that I don't have graphs for tritemio (the stuff I have in my build box) yet
[18:13] <santa_> regarding the status pages, I would like to merge both scripts code (tritemio page status code + the 'official' code) into the iron hand
[18:13] <santa_> (but that's going to take time)
[18:13] <santa_> (just fyi)
 no idea what tritemio is
[18:14] <clivejo> https://phabricator.kde.org/w/kubuntu/tritemio/
[18:15] <santa_> ↑ this. it's like a home-made ppa. sometimes you can do more than what you can do in the official ppa's
[18:15] <clivejo> the system behind that page
[18:17] <clivejo> basically an effort to find and fix autotests before they get uploaded and get "stuck"
[18:18] <clivejo> santa_: http://gpul.grupos.udc.es/ka-iron-hand_reports/frameworks_archive/5.33_artful_proposed_migration.pdf kapidox ?
[18:19] <santa_> lolwut
[18:19] <clivejo> kapidox is red
[18:21] <clivejo> just a glitch? https://launchpad.net/ubuntu/+source/kapidox/5.33.0-0ubuntu1
[18:21] <santa_> ah, "incorrect version". maybe it gets fixed on the next cron run
[18:21]  * clivejo loves these charts!
[18:21] <santa_> I guess the 5.33 package wasn't available when the thing accessed lp, I don't know
[18:22] <santa_> now it's green
[18:22] <clivejo> no prob, just curious as to know it thought it was incorrect version
[18:22] <clivejo> https://launchpad.net/ubuntu/+source/kunitconversion/5.33.0-0ubuntu1
[18:22] <clivejo> FTBFS
[18:23] <santa_> temporary issue probably, I guess it was just migrating from -proposed to the release pocket
[18:25] <santa_> clivejo: that ftbfs is an annoying lp feature: when the build depends aren't ready the package is built anyway. so it's usually marked as dep-wait. however sometimes it's marked as ftbfs and that's why the -f option of kubuntu-retry-builds exists
[18:26] <clivejo> ah, I just poked them manually via LP GUI
[18:27] <santa_> this is something which I would really *love* to see fixed in lp. that works properly on debian's wannabuild, which puts the packages not ready to built on hold properly
[18:27] <santa_> and tends to work like a swiss clock, I have wannabuild for tritemio
[18:27] <clivejo> ever mention it in LP channel?
[18:28] <santa_> nope, I think it's a long stading issue
 I forgot, how do I generate the status page locally?
[18:28] <santa_> just execute ppa-build-status with the proper params, the html code will be printed in the stdout
[18:29] <santa_> don't forget to make sure you have the css in the same directory than the html
 I forgot everything related to that...
 what do I have to have and where?
 can you give me a command snippet?
[18:31] <clivejo> you need the ka tooling
[18:31] <clivejo> https://launchpad.net/ka
 I have that git cloned and git pulled
[18:32] <clivejo> use this script to gen the page - https://git.launchpad.net/ka/tree/ppa-build-status
[18:32] <clivejo> you could use frameworks 5.33 in staging
[18:33] <santa_> ovi check that you have the env vars + ka-metadata, as explained here: https://git.launchpad.net/ka/tree/INSTALL?id=0980566f05678a0b34aac01fc5c9220aa0a05ba1
[18:44] <acheronuk> wow. interesting apt sources for that Nitrux OS beta! http://i.imgur.com/mVEDnDY.png
[18:45] <clivejo> indeed
[19:07] <acheronuk> santa_: http://paste.ubuntu.com/24481034/
[19:08] <acheronuk> likely ECM migrating....?
[19:09] <santa_> I hope so, it vanished from launchpad, no idea why
[19:10] <santa_> anyway kubuntu-retry-builds could handle that better
[19:11] <acheronuk> santa_: also kdoctools also has new binaries, so may be held in the new queue for a bit
 I can't refigure out how to test this...
 I have this command in  my history:
 `KUBUNTU_PPA_BUILD_STATUS_CONFIG=./build-status-conf/applications-local-test.conf ./ppa-build-status-cron >> ./Output/CRONOUT ; beep -f 3000 -n 3`
 but... the applications-local-test.conf is old, and has settings bout applications
 and that generation takes a loooooooooooong time
[19:13] <acheronuk> new conf file for frameworks then
[19:13] <acheronuk> and the generation for apps will take a loooooooooooooooong time
[19:14] <acheronuk> that would be parsing build logs for 230 packages for 5-7 architectures each!
 can you give me a sample?
[19:14] <acheronuk> frameworks is only 74
[19:14] <santa_> sure, give me a few mins ovi
[19:23] <santa_> I'm trying this
[19:23] <santa_> ppa-build-status -p ppa:kubuntu-ppa/staging-plasma -r plasma -d artful -v 5.9.5 > result.html
 it's doing something
[19:27] <santa_> it worked for me
 it's still doing something....
[19:28] <santa_> just make sure you have kubuntu-ppa-build-status.css in the same directory than result.html, and you should be able to open that with the browser
 err...
 ok
[19:30] <santa_> fyi I have just pushed a few fixes to master
 it workes
[19:30] <santa_> one affects the ppa-build-status script but it shouldn't interfere with your work
[19:41] <santa_> I need to be afk for a while, I'll be back https://www.founditemclothing.com/itgoesto11/wp-content/uploads/2014/07/terminator-680x382.jpg
[19:42] <acheronuk> frameworks is depwaiting on those new binaries anyway
 how do I set-up the merge request again?
[20:43]  * clivejo watches FW5.33 slowly go green
[20:51] <acheronuk> https://kver.wordpress.com/2017/04/29/aether-icon-theme/
[21:11] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_labplot build #9: UNSTABLE in 21 min: https://kci.pangea.pub/job/artful_unstable_labplot/9/
[21:54] <clivejo> Regression on kguiaddons s390x - https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kguiaddons
[22:05] <acheronuk> clivejo: may have run that test before some of the deps were finished building. I clicked to retry
[22:07] <clivejo> with proposed enabled?
[22:07] <santa_> back
[22:07] <acheronuk> clivejo: without for now. all-proposed is not a cure all
[22:08] <acheronuk> although it helps quite often
[22:24] <clivejo> you poke ki18n too?
[22:25] <acheronuk> no. I'm messing with PIM at the moment
[22:25] <santa_> acheronuk: so, regarding plasma build depends, do you have a few minutes for an explanation?
[22:25] <clivejo> Ill poke it
[22:27] <acheronuk> santa_: go on
[22:27] <santa_> k, a few things from debian
[22:28] <santa_> as you probably already know it has 3 complete suites: stable, testing and sid
[22:29] <santa_> you usually upload packages to sid, and then they get into testing when they are migrated by britney
[22:29] <santa_> in addition to that, there's a suite which is an overlay of debian sid, which is debian experimental
[22:30] <santa_> it's a bit like a single gigantic ppa where you usually upload packages which can't be uploaded to sid
[22:30] <acheronuk> yes
[22:31] <santa_> e.g. because of a release freeze or because you have a large set of packages such as frameworks an some of them have to go trough the NEW queue
[22:31] <santa_> well, that's just FYI
[22:31] <santa_> now the important bit about experimental
[22:32] <santa_> unlike sid, it's a suite configured as...
[22:32] <santa_> NotAutomatic: yes
[22:32] <santa_> ButAutomaticUpgrades: yes
[22:33] <santa_> which means if you add experimental to your sources.list and you want to install something from experimenal you must type "apt-get -t experimental install whatever"
[22:34] <santa_> or just configure apt or do apt pinning so you can omit the '-t experimental'
[22:35] <acheronuk> makes sense. forces you to 'opt in'
[22:35] <santa_> now, regarding how packages are being built, they are built by sbuild working for a wannabuild setup
[22:35] <santa_> wannabuild/buildd/sbuild is what I have in tritemio
[22:35]  * acheronuk can see where this is going
[22:36] <santa_> so regarding sbuild, in case you haven't noticed it has 2 resolvers to install the build dependencies
[22:36] <santa_> in ubuntu in general and also debian sid the apt resolver is the one doing the job
[22:36] <santa_> in debian experimental is the aptitude one
[22:37] <santa_> so the behaviour of each one is the following:
[22:38] <santa_> ubuntu's ppas have the apt one which grabs for each build dependency the last version
[22:38] <santa_> either in the ppa or the archive
[22:39] <santa_> this is good in way: it reduces the probability of ftbfses
[22:39] <acheronuk> so not good for build dep testing if you are doing a bulk build
[22:39] <santa_> and this is bad in a way: this ↑
[22:40] <santa_> so what I did in tritemio with plasma is, basically, simulate the behaviour of debian experimental for package building
[22:41] <santa_> and that's how I tested the current build depend bumping system we have in KA
[22:41] <acheronuk> got it
[22:41] <santa_> which is case you don't know, it's one of the oldest and most stable in KA
[22:41] <santa_> it would be difficult to find bugs there
[22:42] <santa_> so all of that being said, I have documented a couple of days ago a possible black op - accuracy
[22:42] <santa_> which would be testing our packaging with this build resolver and trying to make it compatible with it
[22:43]  * acheronuk thinks santa_ has played too much CoD
[22:43] <santa_> because last time I checked I had some issues with it, and I think it's something which would be convenient to support
[22:44] <santa_> acheronuk: actually calling that "black ops" comes from the latest jason bourne movie
[22:44] <acheronuk> damn. close
[22:44] <acheronuk> lol
[22:44] <santa_> they even say at some point something line "iron hand! that's not implemented yet..."
[22:45] <santa_> s/line/like/
[22:45] <acheronuk> think I watched the 1st, and maybe the 2nd......
[22:45] <santa_> they are 4 or 5 I think
[22:46]  * acheronuk lost count... and interest really
[22:47] <acheronuk> ok. so you want to make this a tool we can take out and use when required, easily?
[22:48] <santa_> what? the tritemio stuff? yes, I think knowing how to use it would enable you to do anything
[22:49] <santa_> also think about the future
[22:49] <santa_> let's say we get frameworks6 and plasma6 or something to replace the 5 counterparts
[22:49] <santa_> probably the first packages are going to be available on kde neon
[22:50] <santa_> so we could grab and rebuild them and send them patches to improve it's compatibility with kubuntu or debian while they are not available on debian
[22:51] <santa_> this way it would reduce our "merge pain" and it would be also good for debian because they will need to make less modifications to the packaging
[22:51] <acheronuk> very doable
[22:51] <santa_> that's what I did when plasma 5 arrived
[22:52] <santa_> but anyway all of this are just conjectures, time will tell what actually happens
[22:52] <acheronuk> I aim to spend more time on Neon/KDE stuff
[22:52] <acheronuk> Just last cycle it never quite happened.
[22:53] <santa_> yeah, right now we are in a stage where the frameworks/plasma/apps packaging is mostly done and we are just doing maintenance
[22:53] <acheronuk> now I have access permissions, and you might go -dev, I can maybe bridge things a bit
[22:54] <santa_> yeah, lets hope I get -dev in this cycle
[22:54] <acheronuk> yup, fewer radical changes now. just small incremental ones
[22:54] <acheronuk> hope so
[22:54] <santa_> at some point would be nice to apply for motu too
[22:55] <acheronuk> santa_: I was eyeing MOTU as well
[22:55] <santa_> that would help us a lot
[22:55] <acheronuk> logical step, and would help
[22:55] <santa_> so if you have time and you think you can pass the process, please proceed
[22:56] <acheronuk> once we have got our uploads going then I'll take a look at starting that road
[22:56] <acheronuk> though too many hats could be tricky
[22:56] <santa_> acheronuk: so thanks for pointing the autotests patch, I'm going to tweak the plasma bds, so we upload plasma to artful today too?
[22:57] <acheronuk> if it's ready. FW may take a while
[23:27] <acheronuk> or I can do it in the morning?
[23:43] <santa_> as you whish, I am building those packages with the build dependency bump
[23:45] <acheronuk> santa_: infinity just turned on auto-sync from debian, so a few 1,000 packages are about to build!
[23:46] <santa_> ugh
[23:48] <acheronuk> santa_: going to go sleep. if you have pushed your changes and want me to upload at first opportunity, then just leave a note here
[23:49] <acheronuk> or on telegram
[23:50] <santa_> ok
[23:51] <acheronuk> thanks for explaining earlier :)