[02:03] <xnox> please remove qtsvg-opensource-src 5.5.1-2 from xenial-proposed, as all of 5.5 landing is being prepared by Mirv in a silo, and this 5.5 qtsvg component that got auto-synced is in the way for bootstrap =)
[02:03] <xnox> "got auto-synced _and_ is in the"
[05:22] <Mirv> xnox: no need really
[05:23] <Mirv> xnox: I've all of them built as 'build1' already
[05:23] <Mirv> and there are 10+ autosynced modules
[05:58] <darkxst> can someone unleash bug 1237904 from wily-proposed?
[05:58] <darkxst> it was verification-done about 3 weeks ago
[06:00] <darkxst> infinity, RAOF ^
[06:04] <RAOF> darkxst: You are in luck! I now have a laptop with actual access to ubuntu-archive-tools!
[06:08] <darkxst> RAOF, great! :)
[06:10] <RAOF> C'mon, deja-dup. You can do it! Find the backup!
[09:14] <Laney> yofel: I fixed it, in future please debug starting from lp:~developer-membership-board/+junk/packageset
[09:33] <xnox> Mirv, ok, when will it land? or could you please share the silo ppa URL? /me is having test suite failures in qtbase
[09:33] <Mirv> xnox: today at current pace. https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012/+packages
[09:33] <Mirv> I'm just fixing some KDE arm64 rebuilds
[09:34] <xnox> cool
[09:36] <Mirv> xnox: note that qtbase unit tests are some of the most difficult ones to run on our builders (compared to Qt upstream's own test machinery), and we currently run the much modified set of unit tests only on amd64+armhf+i386. I can add s390x to the skipped architectures or you can try to get them working, but please don't upload a new qtbase today.
[09:36] <Mirv> and obviously upstream doesn't run them at all on many of our archs
[09:46] <cjwatson> Mirv: have you considered making it a positive list of architectures where they're run rather than a list of skipped architectures?
[09:47] <cjwatson> the latter approach is usually only suitable when it's particular known properties of the skipped architectures at issue
[09:48] <Mirv> cjwatson: yes, I thought I had already done that but I just noticed I didn't
[09:48] <Mirv> it was probably some other package
[09:50] <Mirv> I'll do that to the next upload
[12:06] <yofel> Laney: thanks a lot! (for both the fix an the repo :) )
[12:39] <Mirv> sorry I've invaded the arm64 builders by kicking builds of a lot of KDE packages to get them through to release pocket
[14:48] <Mirv> Qt 5.5.1 has been published to xenial-proposed. After a few hours there might be something migration related popping up, feel free to fix or I'll look at them tomorrow.
[16:37] <rtg> Can I get the Xenial 4.3 kernel released from the NEW queue ?
[16:48] <rbasak> Can an AA please review monitoring-plugins languishing in Xenial NEW? It's a merge of a Debian source package rename.
[19:47] <xnox> Mirv, interesting, for me it was mostly passing and i was trying to narrow it down to #if !defined(Q_T_S390X) here and there.
[19:47] <xnox> Mirv, or like chaning things to XFAIL etc.
[19:48] <xnox> Mirv, most things do pass. I wonder which things are skipped, i assumed we had a 100% pass rate on amd64, I shall compare with other arches now.
[20:28] <Mirv> xnox: the enable-tests.patch is what maintains the exception. it'd be doable for all archs, but quite a lot of test cases change between Qt versions. that's why it's easier to handle those for the archs I have direct access to.
[20:28] <xnox> Mirv, cool. i'll check if that's the same things on s390x or not =)
[20:29]  * Mirv -> sleep