[09:57] <tsdgeos> cimi: you said "Just waiting for CI" in https://code.launchpad.net/~aacid/unity8/fix-1599238/+merge/299312
[09:57] <tsdgeos> CI finished
[10:14] <tsdgeos> ltinkl: https://code.launchpad.net/~lukas-kde/unity8/wizardKeyboardPage/+merge/295060/comments/777399
[10:14] <ltinkl> tsdgeos, ouch thanks... looks like a bad merge
[10:15] <ltinkl> tsdgeos, fixed
[10:47] <tsdgeos> Saviq: any idea when yakkety is going to get the new uitk?
[10:47] <tsdgeos> not sure if i should either continue workarounding not building or just install the .deb from proposed
[10:47] <Saviq> tsdgeos, whenever Qt 5.6 and new KDE get untangled
[10:48] <Saviq> tsdgeos, I'd recommend https://wiki.ubuntu.com/Testing/EnableProposed#Selective_upgrading_from_-proposed
[10:57]  * tsdgeos takes leap of faith
[10:58] <tsdgeos> gets new qt on the way
[10:58] <tsdgeos> hope not everything explodes :D
[10:59] <tsdgeos> Saviq: do you know what KDE stuff causing the blockage so maybe i can try to help tonight?
[11:02] <Saviq> tsdgeos, in general anything that's red in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html (or "Not considered" for any other reason)
[11:02] <Saviq> Mirv, know anything specific ↑↑?
[11:05] <Mirv> tsdgeos: I've tried pinging them but no response. they were originally saying that "just force anything" but I would like them to say that to release managers
[11:05] <Mirv> tsdgeos: I made a list yesterday, but for example kwin segfaults seen in tests. just a moment.
[11:06] <Mirv> https://irclogs.ubuntu.com/2016/08/01/%23kubuntu-devel.html#t09:44
[11:06] <Mirv> tsdgeos:  kde-cli-tools libkscreen kdepim-runtime kxmlgui extra-cmake-modules kconfigwidgets okteta (amd64, retried) akonadi-search kidentitymanagement kdelibs4support kwayland libkscreen plasma-framework (s390x, retried)
[11:06] <Mirv> + the kwin
[11:06] <Mirv> and well marble too
[11:06] <Mirv> after updating symbols it fails to build too
[11:07] <Mirv> tsdgeos: so I've tried to get info if they feel they functionally work right now so that they can also fix them later. KDE autopkgtests have failed for ages in many cases, so they should in many cases be overridden.
[11:08] <Mirv> after 073 lands I'll try again
[11:08] <tsdgeos> you're not making me confident this update is not totally going to destroy my system :D
[11:08] <Saviq> 073? what's interesting to KDE in there?
[11:16] <Mirv> tsdgeos: it's been tested by me (Unity 8, Plasma, LXQt) and several Kubuntu people. there were more autopkgtests failing _before_ the Qt 5.6.1 landing, it's just that the normal case of things in yakkety-proposed is that KDE stuff is always blocked until someone says that "yes it works let's ignore the autopkgtests"
[11:17] <Mirv> Saviq: 073 has the fix to only non-KDE autopkgtest failure, so after that it's only the KDE autopkgtests blocking the migration to release pocket (at least per excuses page)
[11:17] <Saviq> Mirv, ack
[11:17] <Mirv> so more reason to get the migration forward
[11:17] <Saviq> Mirv, it's in QA queue already
[11:17] <Mirv> Saviq: I know :)
[11:20] <Mirv> tsdgeos: it's just that I don't want to be the guy telling release managers to ignore KDE's autopkgtests, even if I could quote something like that from #kubuntu-devel
[11:23] <tsdgeos> Mirv: i see, at least konsole, kate and quassel still work after the update, something is something :D
[11:23] <tsdgeos> let's see my plasma session tonight :D
[11:31] <Mirv> tsdgeos: are you btw running proposed, silo 24 or 24 + 41?
[11:31] <tsdgeos> Mirv: i enabled proposed and intsalled "some" packages
[11:32] <tsdgeos> food
[11:32] <Mirv> tsdgeos: ok, so yeah you have the new Frameworks and Plasma too, great. they would not have been required but it seemed like people wanted to get the new releases in to fix autopkgtests (among else)
[12:12] <Mirv> Saviq: not sure why 073 doesn't show up at trello even though ticket says Ready
[12:14] <Saviq> me eiher
[12:14] <Saviq> +t
[12:14] <Saviq> prolly too long again ;)