[00:40] <tsimonq2> CVE fixed, waiting for a sponsor. Bug 1663950 when it gets published.
[01:26] <tsimonq2> acheronuk, clivejo: bug 1663950
[02:45] <tsimonq2> acheronuk, clivejo, santa_: https://bugs.launchpad.net/ubuntu/+source/vc/+bug/1629881/comments/4
[02:46] <tsimonq2> Actually no
[02:46] <tsimonq2> acheronuk, clivejo, santa_: https://bugs.launchpad.net/ubuntu/+source/vc/+bug/1629881/comments/5
[03:11] <genii-netbook> !info vc
[03:11] <genii-netbook> !info vc-dev
[03:11] <wxl> seems like we need some testing on 16.04.2
[03:11]  * genii-netbook sips and ponders
[03:12] <wxl> at least for i386
[03:22] <wxl> valorie: i'm fairly confident someone is confused in regards to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1663298
[03:23] <valorie> looking
[03:24] <wxl> it might be good to have someone we really trust as a thorough, meticulous tester confirm it and create a very explicit reproduction case
[03:25] <valorie> "the issue appears to occur when the virtual disk is increased, which does not seem to be consistent with the conditions of your assertion."
[03:26] <wxl> yeah
[03:26] <valorie> I saw the discussion of this issue in -release
[03:26] <wxl> that's just ragging on infinity for being so dismissive :)
[03:26] <wxl> oh i missed that
[03:27] <wxl> what's the tl;dr?
[03:27] <valorie> I'm thinking this same issue is why my i386 test failed
[03:28] <valorie> my tl;dr is that it takes a hell of a lot of space allocated to a VM to install 2 or 3 
[03:28] <wxl> yeah and that's reasonable
[03:28] <wxl> should be 16gb+
[03:28] <valorie> so I don't see this as a bug in the installer
[03:29] <wxl> that's kind of what adam suggested
[03:29] <valorie> yup
[03:29] <valorie> how are you, btw?
[03:29] <wxl> not terrible
[03:29] <valorie> perhaps that's the best you can expect
[03:29] <valorie> :(
[03:30] <wxl> yeah well i'd say i'm just depressed. not like crying my eyes out but just not my usual self. a bit apathetic.
[03:45] <valorie> sorrow and grief are hard
[03:47] <wxl> yep for sure
[08:36] <lordievader> Good morning.
[12:34] <BluesKaj> Hiya folks
[15:00] <ahoneybun> mm x86_64-efi platform is stuck installing
[19:26] <clivejo> hi santa_ how are autotest fixes going?
[19:34] <santa_> clivejo: I'm going to do them soon
[20:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #119: STILL FAILING in 6 min 47 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/119/
[20:05] <santa_> clivejo, acheronuk: ok, I have finished what I was doing and I'm going to take a break. if you are around in ~40 minutes I will show you the "state of the art" things in KA and we will discuss th uploading of frameworks and plasma to the archive
[20:06] <clivejo> I should be about, just ping me
[20:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #120: STILL FAILING in 7 min 51 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/120/
[20:24] <acheronuk> santa_ clivejo - I'm about, but with other stuff to do and family here, so may or may not respond promptly
[20:26] <clivejo> poking kmail
[20:27] <acheronuk> just poked messagelib as last kmail build had that linking against old functions
[20:29] <acheronuk> mailcommon I mean. gah. too many similar named sources
[21:10] <santa_> clivejo, acheronuk: I'm back, are you around?
[21:10] <clivejo> Im here
[21:11]  * acheronuk raises hand
[21:11] <santa_> ok
[21:12] <santa_> first of all, I would like you to update your ka clone in a machine with desktop env
[21:13] <acheronuk> just did. anticipating that request ;)
[21:13] <clivejo> me too
[21:14] <santa_> + dist-upgrade and make sure you have the ka-deps version ppa12 installed
[21:16] <acheronuk> done
[21:16] <santa_> once done, please execute
[21:16] <santa_> $ kagraphdemo
[21:18] <acheronuk> kagraphdemo: command not found
[21:18] <santa_> do you have the debug/ dir from ka in your path?
[21:19] <clivejo> in runs on mine and creates a pdf in /tmp
[21:19] <acheronuk> maybe not on this machine... checking...
[21:19] <clivejo> Dot file: /tmp/testkagraph.dot
[21:19] <clivejo> PostScript 2 file: /tmp/testkagraph.ps
[21:19] <clivejo> PDF file: /tmp/testkagraph.pdf
[21:19] <santa_> which should be like this one: http://gpul.grupos.udc.es/things/testkagraph.pdf is that correct?
[21:20] <clivejo> yup
[21:20] <santa_> acheronuk: what about you?
[21:21]  * DarinMiller kagraphdemo working for me too...
[21:22] <acheronuk> santa_: yup
[21:22] <santa_> ok
[21:22] <acheronuk> yes
[21:22] <santa_> acheronuk: I know why the links weren't working the other time and why your conf removal fixed it
[21:23]  * acheronuk wonder what he broke
[21:23] <santa_> acheronuk: in okular you have to be in the navigation mode, not on the zoom mode; that setting is stored in one rc file so when you removed it you went back to the navigation mode
[21:24] <acheronuk> santa_: ah, right.
[21:25] <santa_> acheronuk: so nothing wrong. just for the record it tricked me too, so that's why I found out the reason
[21:26] <santa_> so now that we know that we have to put okular in navigation mode ... can you confirm that the links for pkg_warning and pkg_warning_highlight work?
[21:26] <santa_> it should open a google query wih the package names
[21:27] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #121: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_kmail/121/
[21:27] <sintre> sinse there is some traffic here just a few comment that are meant to be helpful
[21:27] <sintre> imagemagick (display Q16)
[21:28] <acheronuk> santa_: nope. just opens google home page here with no search
[21:28] <sintre> in lts won't even load
[21:28] <sintre> i know its somebody eleses software but if they won't fix it
[21:28] <sintre> then maybe a replacement?
[21:29] <DarinMiller> acheronuk:  try clicking on pkg_warning_highlight, not all of my links produce google searches.
[21:29] <santa_> acheronuk: can you hover the mouse over the package in question and see if the url is like this one: https://www.google.com/#safe=off&q=pkg_warning_highlight ?
[21:29] <acheronuk> santa_: it is
[21:29] <santa_> ok, so lets supose it works
[21:30] <santa_> now that we have confirmed that the engine seems to work, go a head with
[21:30] <santa_> $ kubuntu-retry-builds -r plasma -d zesty -f --dry-run -gv
[21:31] <santa_> it's going to take time
[21:31] <acheronuk> done
[21:32] <santa_> the -gv option is new and optional and it's meant to show a graph after it's done
[21:32] <acheronuk> it does. all green
[21:33] <clivejo> same here
[21:33] <santa_> shit
[21:33] <santa_> I meant
[21:33] <santa_> $ kubuntu-retry-builds -r applications -d zesty -f --dry-run -gv
[21:33] <santa_> that will take much more time
[21:34] <acheronuk> santa_: last one popped up a kwallet dialogue. I don't use that so told it to get lost
[21:35] <acheronuk> *first command
[21:35] <sintre> second comment related , can we get rid of kwallet auto install , this is almost my 100% go to chore when doing a new install
[21:36] <sintre> i don't need a peogram to remember my passwords and most don't either
[21:36] <santa_> acheronuk: but does it work anyway?
[21:37] <clivejo> taking a while ....
[21:37] <acheronuk> santa_: it does. just a minor irritation
[21:38] <santa_> ok
[21:38] <acheronuk> yay! a graph telling be how ****ed up PIM is
[21:39] <acheronuk> as if I didn't know
[21:40] <santa_> actually it tells you which packages have been rebuilt by kubuntu-retry-builds
[21:43] <acheronuk> so the ones with the additional border highlighting
[21:43] <santa_> yes
[21:44] <santa_> if you enter ~/kubuntu-retry-builds_logs you will see a couple of logs
[21:44] <santa_> one is a txt file with the program output, and the other one with a pdf you have just seen
[21:45] <acheronuk> got it
[21:45] <santa_> this feature can be disabled in your ~/kubuntu-automation.conf
[21:46] <santa_> however I recommend you to keep it activated in case you want to tell me about bugs in kubuntu-retry-builds
[21:47] <acheronuk> ok
[21:47] <DarinMiller> one comment on the  kubuntu-retry-builds script, it did not run for me unless I was logged into an lp browser session...
[21:47] <santa_> if kubuntu-retry-builds gets enough mature and tested maybe we could convert it to a server daemon
[21:47]  * acheronuk kills and disables kwallet
[21:47] <acheronuk> don't come back
[21:47] <santa_> DarinMiller: yes, that's how it worked allways
[21:48] <DarinMiller> ah ok.  Never ran before today....
[21:48] <santa_> that's because you would need permissions to retry the builds
[21:48]  * sintre aplauds acheronuk's actions!
[21:49] <santa_> ... so you  need to log in authenticaed
[21:49] <DarinMiller> do non-ninja's have build retry permissions?
[21:49] <clivejo> DarinMiller: nope
[21:49] <acheronuk> DarinMiller: no
[21:49] <santa_> no, but you just did a dry-run so probalbly it worked for you anyway
[21:50] <clivejo> but it will ask you who you are, to determined if you can re-try or not
[21:56] <santa_> acheronuk, clivejo: so that's all about kubuntu-retry-builds, as I said maybe it would be a good idea to have a server running kubuntu-retry-builds automatically (without -f) and displaying in a public place the logs, so we won't have to run it manually so many times
[21:57] <santa_> this way we would only need to run it when it needs -f and we would see that just looking at the graph
[21:57] <clivejo> handy
[21:57] <santa_> now about frameworks and plasma, have you tested the dist-upgrades?
[21:57] <acheronuk> some revamped QA pages somewhere sounds a good plan.
[21:58] <acheronuk> santa_: upgraded here fine on this zesty machine. bit no more than that
[21:58] <santa_> ok
[21:59] <santa_> also, beyong my incoming autopkgtest's fixes anything else that would need to be done before uploading to the archive?
[21:59] <santa_> s/beyong/beyond/
[21:59] <clivejo> acheronuk: was there something might need patched?
[22:00] <acheronuk> clivejo: not essential. solid. just looking for a link
[22:00] <clivejo> is it critical, or a bug fix?
[22:01] <acheronuk> clivejo: bug fix https://phabricator.kde.org/D4570
[22:01] <acheronuk> If you still use floppy disks!!!!!
[22:02] <clivejo> not very critical, in my eyes!
[22:02] <acheronuk> no
[22:02] <clivejo> looks like thats been broken for a while too
[22:02] <clivejo> and not a deal breaker for most people
[22:02] <santa_> jesus christ
[22:03] <clivejo> where?
[22:03] <clivejo> second coming?
[22:03]  * acheronuk looks for his iomega zip drive
[22:03] <acheronuk> if we are going retro
[22:05] <clivejo> still got a 5 1/4 inch floppy drive for commodore 64!
 G'day m8s
[22:12] <clivejo> is FW5.31 ready to go then?
[22:12] <santa_> acheronuk, clivejo: so I have just checked the overall status of fw and plasma, so I think I'm going to fix the autopkgtests and test the dist-upgrades; wrt that my "fixes" are going to be stop-in-gap solutions
 @clivejo, >__> ... <__< Who, me?
[22:13] <clivejo> was directed at santa_ and acheronuk
[22:13] <santa_> acheronuk, clivejo: so that being said are you ok if I add working notes on phab here: https://phabricator.kde.org/w/kubuntu/
 :P ok
[22:14] <clivejo> acheronuk fixed the symbols issues and santa_ has been working on the autotests
[22:14]  * DarinMiller notes that plasma 5.91 and fw 5.31 is working fine here (with known gpgme excecption)
[22:14] <santa_> I think I will add the "working notes" section there
[22:14] <clivejo> can you add them under the KA section - https://phabricator.kde.org/w/kubuntu/kubuntu-automation/  ?
[22:15] <santa_> but autpkgtests are not related to KA
[22:16] <clivejo> oh, we should start a new section for autotests I think
[22:16] <clivejo> has anyone spoken to Rick T?
[22:16] <clivejo> been pinging him all week on Telegram and no reply
[22:18] <clivejo> apparently we have a VM on Elastic Hosts as well
[22:19] <santa_> clivejo: so thumbs up for starting an autopkgtests section ?
[22:19] <clivejo> and as autotests are a bit of black magic to me, was hoping we could setup an environment to run them against our PPA's
[22:19] <clivejo> santa_: ack
[22:19] <santa_> allrigh
[22:20] <clivejo> santa_: would you help out on setting up a autotests machine?
[22:20] <clivejo> if I can get the details from Rick, ie log in, machine specs etc
[22:23] <acheronuk> santa_: on a slight tangent, can you see sometime if you can replicate the testsuite failures on 'purpose' package? I have tried a few permutations on locally run test in sbuild, and qemu with the ubuntu cloud image, but can't get it to fail the way it is on ubuntu's infra
[22:27] <santa_> clivejo: you mean like the one I have? we would need a lot of time to do that, the thing I have is very complex to set up
[22:27] <clivejo> santa_: yes, something that the whole team can see and understand how it works
[22:28] <santa_> keep in mind that I growed up "iron balls" packaging kde in distros where they are no ppas
[22:28] <clivejo> so that failures can be fixed before upload
[22:28] <santa_> clivejo: yeah, that's the idea but I need time to prepare for that
[22:28] <santa_> we will get there
[22:28] <santa_> also I need to check if there's a better option
[22:29] <clivejo> might be a good machine to have as a QA 
[22:29] <santa_> because well, setting up what I have might be like killing a fly with a gun
[22:29] <clivejo> also run your graphs for there too
[22:29] <clivejo> from
[22:29] <santa_> do we have anything where we could get root and set up containers?
[22:30] <santa_> I'm almost clueless of our resources because I work with my own server, you know
[22:30] <clivejo> well this donated server should have that
[22:31] <clivejo> but I need to get in touch with Rick T to get the details
[22:31] <santa_> ok, so if we have that I could start to write documentation to replicate my setup
[22:32] <clivejo> yeah, Id like to know how you do it
[22:32] <santa_> but keep in mind that is very hackish and I'm running some self-made software
[22:33] <acheronuk> we could maybe start with just a setup where people can easily run tests on x against y & z without too much hassle
[22:36] <tsimonq2> Easy
[22:36] <tsimonq2> Very easy
[22:36] <tsimonq2> Want a script? I can write a script.
[22:38] <santa_> https://phabricator.kde.org/w/kubuntu/autopkgtests/
[22:40] <acheronuk> santa_: anyway, the fixes/test you want to do. what ETA does that now give us for an upload?
[22:40] <clivejo> santa_: Ive changed the links to keep them in the same sub category
[22:41] <clivejo> ie https://phabricator.kde.org/w/kubuntu/autopkgtests/autopkgtests_in_kubuntu/
[22:41] <clivejo> just allows the wiki to add a navigation 
[22:44] <clivejo> so is FW5.31 ready for upload?
[22:44] <santa_> will be soon
[22:46] <clivejo> hummm
[22:46] <clivejo> kmail is crashing when I try and send a new email!
[22:48] <clivejo> kmail: symbol lookup error: /usr/lib/x86_64-linux-gnu/libkmailprivate.so.5: undefined symbol: _ZN14TemplateParser14TemplateParserC1ERK14QSharedPointerIN5KMime7MessageEENS0_4ModeE
[22:48] <acheronuk> joys of running KCI builds!
[22:48]  * clivejo stares at acheronuk
[22:50] <santa_> clivejo: https://phabricator.kde.org/w/kubuntu/tritemio/
[22:51] <clivejo> cool, so you'll add to the setup guide as we setup this new server
[22:51] <santa_> it's going to take time and it's not easy so then don't say I didn't warn you
[22:52] <santa_> my idea would be doing here some containers and try to reproduce the steps I followed *years* ago
[22:52] <santa_> so someone else would set up something similar for kubuntu
[22:53] <santa_> I mean, in the official server
[23:00] <acheronuk> we can have a go. at the moment we are blind or tinkering around the edges (your setup excluded)