[00:01] <IrcsomeBot> <ahoneybun> March 1 is a Wednesday
[00:01] <IrcsomeBot> <ahoneybun> Sooo
[00:03]  * DarinMiller is trying to grasp the relavance :)
[00:04] <DarinMiller> relevance^
[00:07] <genii> I don't see anything on the fridge for that day
[00:30] <IrcsomeBot> <ahoneybun> We don't post on the Ubuntu Fridge
[00:31] <genii> ..and https://community.kde.org/Kubuntu/Meeting is somewhat unenlightening...
[00:32] <acheronuk> http://kubuntu.org/kubuntu-podcast/
[00:33] <wxl> should put it on the fridge
[00:33] <genii> Ah, good
[00:35] <genii> So always the first Wed :)
[04:14] <tsimonq2> wxl: I have access to the fridge fwiw
[05:27] <IrcsomeBot> <Valoriez> o/ from Anacortes
[05:48] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Zesty Beta 1] (20170218) has been added
[05:49] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop i386 [Zesty Beta 1] (20170218) has been added
[08:36] <lordievader> Good morning
[10:07] <acheronuk> morning :)
[11:52] <BluesKaj> Howdy folks
[13:12] <acheronuk> santa_: hi :)
[13:15] <santa_> acheronuk: hi
[13:15] <acheronuk> santa_: was one of those kstars failing QVERIFYs deliberately not switched to a qFuzzyCompare for some reason? or just missed unintentionally?
[13:15] <santa_> acheronuk: which one?
[13:16] <santa_> just give me an example
[13:17] <santa_> also note that I'm about to finish the right version of the patch
[13:18] <acheronuk> in TestDMS::stringCtor(), the QVERIFY(h.Hours() == d.Degrees());
[13:18] <acheronuk> santa_: still failing ^^^
[13:20] <santa_> acheronuk: still failing? no prob, I'm building now on staging the patch to be sent to kde's review
[13:22] <acheronuk> santa_: your patch replaces that in testcachingdms.cpp but not in testdms.cpp
[13:23] <santa_> acheronuk: anyway the old patch is wrong give me a sec
[13:24] -kubuntu-ci:#kubuntu-devel- Project merger_kstars build #765: FAILURE in 5.5 sec: http://kci.pangea.pub/job/merger_kstars/765/
[13:24] <santa_> acheronuk: ok, you have the more correct version of the patch in git
[13:24] <acheronuk> :)
[13:24] <santa_> build on the ppa: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+sourcepub/7495206/+listing-archive-extra
[13:25] <santa_> build on the ppa: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+sourcepub/7495206/+listing-archive-extrafuzzyCompare()
[13:26] <santa_> damn
[13:26] <santa_> konversation ate the last line I wanted to write, let me rewrite...
[13:27] <santa_> acheronuk: the old patch has 2 issues: 1) it doesn't cover all the unsafe comparisons because it was meant as a stop in gap solution 2) it doesn't use qFuzzyCompare() properly
[13:29] <acheronuk> ok. so that still has to sit inside qverify
[13:29] <santa_> yes because it's a function which returns true or false
[13:30] <santa_> if you put it alone it just calls the function ignoring the return value (which is legit in c++)
[13:30] <acheronuk> which QVERIFY can the return proper test result from
[13:30] <acheronuk> right
[13:31] <santa_> ok, so
[13:31] <santa_> if you hold a bit the 3 upload would be great, because I'm about to send this second patch to review
[13:32] <acheronuk> santa_: well that was my next question. so holding for now
[13:32]  * acheronuk starts circling @ 15,000 feet (holding pattern)
[13:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #379: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kstars/379/
=== santa is now known as Guest9564
[14:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #110: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/zesty_unstable_kstars/110/
[14:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #245: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/245/
=== Guest9564 is now known as santa_
[14:22] <clivejo> yofel: ping
[18:22] <santa_> acheronuk: thank you for the technical assesment of gpgme, you saved me a lot of time. In case yu haven't seen my message on the bug report: I hope to have a decent gpgme ubuntu3 upload soon solving the problem you pointed out
[18:27] <acheronuk> santa_: that is great, and you are welcome. :) 
[18:34] <santa_> acheronuk: regarding the kstars case, I have just seen that is blocking some frameworks migration from -proposed (I wasn't aware of that when I suggested to hold the upload) so maybe we could get it uploaded to unblock things?
[18:35] <santa_> (we can allways upload it again if they are still issues)
[18:37] <acheronuk> santa_: well, I held off uploading in case some changes were suggested in review today, but has more or less decided that if the review was not quickly done I would do as you say anyway, and upload the working fix
[18:37] <acheronuk> I will get that done shortly then
[18:38] <santa_> acheronuk: ack
[18:41] -kubuntu-ci:#kubuntu-devel- Project merger_kstars build #766: STILL FAILING in 6 sec: http://kci.pangea.pub/job/merger_kstars/766/
[18:43] <acheronuk> santa_: done
[18:43] <santa_> great :)
[18:44] <IrcsomeBot> <ahoneybun> And my machine does not boot
[18:44] <IrcsomeBot> <ahoneybun> Seems that grub issue caused it lol
[18:45] <santa_> ugh, not cool
[18:46] <acheronuk> :/
[18:47] <santa_> btw, we must investigate the problem with discover that aleix pointed out in the -devel mailing list
[18:48] <santa_> I hope to dig into it once I'm done with the gpgme thing, but if someone else wants to investigate it, be my guest
[18:55] <acheronuk> people should start reporting bugs when discover actually works. that would be the unusual thing.
[19:06] <santa_> it usually works here
[19:08] <santa_> it works usually here, however I'm not using it very much
[19:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #246: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/246/
[19:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #380: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kstars/380/
[19:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #111: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_kstars/111/
[20:02] <santa_> acheronuk: ok, I have been cleaning up things in my gpgme experiment. the last problem I had was this:
[20:03] <santa_> PASS: t-thread-keylist
[20:04] <santa_> t-thread-keylist-verify.c:61: GPGME: Inappropriate ioctl for device
[20:04] <santa_> /bin/bash: fork: Cannot allocate memory
[20:04] <santa_> /bin/bash: fork: Cannot allocate memory
[20:04] <santa_> acheronuk: I "solved" it commenting out the tests, how did you deal with that in your experiments?
[20:04] <santa_> * the test in question
[20:05] <santa_> if I comment out the t-thread-keylist-verify the thing would built succesfully I think
[20:05] <santa_> s/built/build/
[20:08] <acheronuk> I was building an upstream git snapshot, as the suggested commits from the gpg dev on the bug comments did not all apply cleanly to the 1.8.0 release in isolation. that got me to just the Qt test fails
[20:08] <acheronuk> maybe there is some middle ground to be found there?
[20:09] <santa_> so you built the current package in zesty proposed just proving a new upstream version, is that correct?
[20:12] <acheronuk> santa_: yes, a git snapshot anyway. 
[20:14] <santa_> so there must be a commit from upstream fixing this issue
[20:20] <acheronuk> santa_: presumably. my snapshot was 1.8.0+git20170207
[20:21] <santa_> acheronuk: ok, found the thing digging into the bug report https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/comments/33
[20:21] <ubottu> Launchpad bug 1647204 in gpgme1.0 (Ubuntu) "1.8.0-2 FTBFS in zesty 17.04" [Undecided,Confirmed]
[20:22] <acheronuk> aha. :) 
[20:23] <santa_> gonna test the patch in question now
[21:12] <santa_> acheronuk: https://launchpad.net/~panfaust/+archive/ubuntu/gpgme/+packages
[21:12] <santa_> FINALLY
[21:13] <santa_> so I think I have now a reasonably good candidate for upload
[21:15] <acheronuk> \o/
[21:16] <acheronuk> I wonder if Barry Warsaw might sponsor again once you are happy with that to go.....?
[21:17] <acheronuk> santa_: thank you :)
[21:18]  * acheronuk pours a large JD in a toast
[21:19] <santa_> yw, I will send the debdiff to the bug, let's hope he uploads again
[21:21] <acheronuk> claws-mail he was concerned about migrating from proposed is still stuck there due to gpgme failure, so I'd say there is a good chance
[21:24] <clivejo> acheronuk: could you pop a copy into KCI?
[21:44] <santa_> https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/comments/44
[21:44] <ubottu> Launchpad bug 1647204 in gpgme1.0 (Ubuntu) "1.8.0-2 FTBFS in zesty 17.04" [Undecided,Confirmed]
[21:44] <santa_> let's hot that's the end of this long standing issue
[21:45] <santa_> most horrible one since I'm here so far!
[21:45] <santa_> s/so far//
[21:46] <acheronuk> clivejo: yeah, will update KCI one soonish
[21:46] <acheronuk> santa_: yep, that was V frustrating. I just hope anything that builds against it now, also passes their autotests!
[21:48] <DarinMiller> Nice job santa_ and acheronuk figuring out the gpgme issue!
[21:48] <acheronuk> good job all round though. Thanks santa_ and anyone else who helped and might possibly read this
[21:56] <santa_> :)
[21:56] <santa_> clivejo: I have various things which might be interesting for you
[21:57] <santa_> 1. a kstars proposed patch to make it build without indi: https://phabricator.kde.org/D4660
[21:59] <santa_> 2. I have added your proposal to mark the packages with running autopkgtests in the proposed-migration here: https://phabricator.kde.org/w/kubuntu/black-operations/iron-hand/
[21:59] <santa_> 3. This "black op" https://phabricator.kde.org/w/kubuntu/black-operations/kraken/
[22:49] <acheronuk> Apparently successful
[22:49] <acheronuk> final: kauth,kcompletion,kconfig,kcoreaddons,kcrash,kdesu,kguiaddons,ki18n,kjobwidgets,kjsembed,knotifications,kpackage,kpty,kunitconversion,kwallet-kf5,kwidgetsaddons,kwin,libksysguard,mozjs38
[22:50] <acheronuk> amazing how much 1 dodgy test on kstars can hold back!