[00:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #219: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_marble/219/
[00:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #176: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/176/
[00:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #181: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/181/
[00:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #178: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/178/
[00:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #183: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_marble/183/
[00:29] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #601: FAILURE in 40 sec: http://kci.pangea.pub/job/merger_kdiamond/601/
[00:35] -kubuntu-ci:#kubuntu-devel- Project merger_kio build #799: STILL FAILING in 58 sec: http://kci.pangea.pub/job/merger_kio/799/
[00:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #91: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/91/
[00:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #100: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/100/
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #251: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/xenial_unstable_kstars/251/
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #184: STILL FAILING in 41 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/184/
[00:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #190: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/190/
[00:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #261: STILL FAILING in 47 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/261/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #245: STILL UNSTABLE in 48 min: http://kci.pangea.pub/job/xenial_unstable_kwin/245/
[00:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #118: STILL UNSTABLE in 47 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/118/
[00:52] -kubuntu-ci:#kubuntu-devel- Project merger_marble build #469: STILL FAILING in 40 sec: http://kci.pangea.pub/job/merger_marble/469/
[00:56] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #685: STILL UNSTABLE in 56 min: http://kci.pangea.pub/job/mgmt_merger/685/
[00:57] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #665: STILL UNSTABLE in 57 min: http://kci.pangea.pub/job/mgmt_progenitor/665/
[01:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #58: STILL FAILING in 6 min 47 sec: http://kci.pangea.pub/job/xenial_unstable_discover/58/
[01:04] <santa_> clivejo: if you are up for uploading there is a fixed marble here: http://gpul.grupos.udc.es/sponsor/
[01:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #188: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/188/
[01:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #132: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/132/
[01:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #184: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_marble/184/
[01:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #54: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_libkleo/54/
[01:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #33: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/33/
[01:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #61: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/61/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop-pg-qt build #39: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop-pg-qt/39/
[01:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #12: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/12/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #29: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/29/
[01:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #54: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_discover/54/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #46: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/46/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #40: STILL FAILING in 25 min: http://kci.pangea.pub/job/xenial_unstable_libkleo/40/
[01:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #87: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/87/
[01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #220: STILL FAILING in 29 min: http://kci.pangea.pub/job/xenial_unstable_marble/220/
[01:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #185: STILL FAILING in 29 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/185/
[01:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #75: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/75/
[01:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #191: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/191/
[01:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #78: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/78/
[01:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #55: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/55/
[01:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #89: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_okular/89/
[01:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #78: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_kopete/78/
[01:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #145: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/145/
[01:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #147: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/147/
[01:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #186: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/186/
[01:59] <tsimonq2> early bed for me o/
[02:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #192: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/192/
[02:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kidletime build #270: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_kidletime/270/
[03:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpty build #273: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kpty/273/
[03:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #269: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/269/
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #252: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_kstars/252/
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #87: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/87/
[04:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #203: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/203/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #193: STILL FAILING in 1 min 15 sec: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/193/
[04:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #133: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/133/
[04:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #194: STILL FAILING in 1 min 14 sec: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/194/
[05:03] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #105: FAILURE in 14 sec: http://kci.pangea.pub/job/merger_audiocd-kio/105/
[05:03] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #106: STILL FAILING in 15 sec: http://kci.pangea.pub/job/merger_audiocd-kio/106/
[05:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #177: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/177/
[05:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #41: STILL FAILING in 27 min: http://kci.pangea.pub/job/xenial_unstable_libkleo/41/
[05:28] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #107: STILL FAILING in 17 sec: http://kci.pangea.pub/job/merger_audiocd-kio/107/
[05:29] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #108: STILL FAILING in 14 sec: http://kci.pangea.pub/job/merger_audiocd-kio/108/
[05:29] <Mirv> clivejo: sitter: there's a Qt PPU too one can apply for http://people.canonical.com/~ubuntu-archive/packagesets/yakkety/qt5
[05:33] <Mirv> oh that was just part of developer application talks. congrats clivejo! :)
[05:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #189: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/189/
[05:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #129: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/129/
[05:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #47: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/47/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #62: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/62/
[05:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #130: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/130/
[06:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libgravatar build #22: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_libgravatar/22/
[06:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #25: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/25/
[06:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #246: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_kwin/246/
[06:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #145: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/145/
[06:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libgravatar build #23: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_libgravatar/23/
[06:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #26: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/26/
[06:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #251: STILL FAILING in 29 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/251/
[06:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #105: STILL FAILING in 27 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/105/
[06:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #109: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/109/
[07:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #146: STILL FAILING in 34 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/146/
[07:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #252: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/252/
[07:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #106: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/106/
[07:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #110: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/110/
[07:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #64: STILL FAILING in 41 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/64/
[07:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #81: STILL FAILING in 1 min 15 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/81/
[07:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #65: STILL FAILING in 40 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/65/
[07:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #82: STILL FAILING in 44 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/82/
[09:14] <ahoneybun> tsimonq2: did you install Kirigami into your 5.8 test ppa?
[09:15] <ahoneybun> seems it is a dep for 5.8 since Discover uses it as it's UI
[10:11] <soee_> clivejo: o/
[11:01] <tibi> hi! I'd like to test the Plasma 5.7 on my Kubuntu machine (I get a crash from my plasma shell at least once every 5 minutes)
[11:01] <tibi> Is there a PPA or repository with debs that I can use>
[11:01] <tibi> ?
[11:02] <clivejo> what version of Kubuntu are you running?
[11:02] <tibi> (unfortunately) 16.06
[11:02] <tibi> 14.04 was rock solid :)
[11:02] <clivejo> you sure?
[11:02] <clivejo> no such thing as 16.06
[11:03] <clivejo> 16.04 maybe?
[11:03] <clivejo> Xenial?
[11:03] <tibi> yeah, sorry
[11:03] <tibi> Description:    Ubuntu 16.04.1 LTS
[11:03] <clivejo> ok
[11:03] <tibi> plasmashell -v
[11:03] <tibi> plasmashell 5.6.5
[11:03] <clivejo> oh
[11:03] <clivejo> where did you get that#
[11:03] <tibi> (from backports)
[11:03] <clivejo> which backports PPA did you add?
[11:03] <tibi> the stock plasma was just as bad
[11:03] <tibi> let me check
[11:04] <tibi> http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu
[11:05] <clivejo> are you getting any crash info?
[11:05] <tibi> clivejo: I can look inside .xsession-errors. I didn't see anything relevant there last time I checked
[11:06] <clivejo> usually when it crashes you get a report pop up asking you what you want to do
[11:06] <tsimonq2> clivejo: we really do need to update the staging PPA with 5.7.5 :/
[11:06] <tsimonq2> s/staging/backports/
[11:06] <tibi> (at least not to my eyes)
[11:06] <clivejo> tibi: is it a production machine?
[11:06] <tibi> clivejo: oh, that. Yeah, I even submited several times the report
[11:07] <tibi> clivejo: yes, it's my main machine. I use it for web development
[11:07] <clivejo> any chance of copying that report and putting it on paste.ubuntu.com ?
[11:07] <tibi> is there a way to get it once it dissapeared from th systray?
[11:08] <clivejo> was the backports PPA the only one you added?
[11:08] <clivejo> could you have added another whilst trying?
[11:08] <tibi> no, no other
[11:08] <tibi> well, plasma just crashed, but no report coming
[11:08]  * clivejo knows that some online articles are telling people to add other PPA's
[11:09] <acheronuk> 5.6.5 from backports was pretty stable during the period I was using it
[11:09] <acheronuk> clivejo: ummm.... which ones?
[11:09] <clivejo> staging *face palms*
[11:09] <acheronuk> holy ***!
[11:09] <clivejo> yeah!
[11:10] <tibi> the only other "odd" thing I have is the Intel Graphics repository
[11:10] <tibi> I've installed the intel drivers, per #kubuntu suggestion
[11:10] <clivejo> oh
[11:10] <clivejo> that could be your problem
[11:11] <tibi> I've added the intel repo to try to fix the crashing problem, it was there before
[11:11] <tibi> even with stock KDE
[11:11] <acheronuk> is that the 01.org ones?
[11:11] <tibi> "stock Kubuntu 16.04"
[11:11] <tibi> acheronuk: yes, the https://download.01.org/gfx/ubuntu/16.04/main
[11:13] <acheronuk> without a log or error give a clue to a reason, it's hard to diagnose
[11:14] <tibi> acheronuk: I'll provide a section from from my .xsession-errors
[11:14] <acheronuk> I've had intel be rock stable sometimes, and a bit error prone at others
[11:15] <acheronuk> one reason why debian etc are wanting to fall back to modesetting and drop the driver
[11:15]  * acheronuk goes in hunt of articles saying to add the staging ppas !!!!
[11:16] <tsimonq2> acheronuk: what's blocking us from getting 5.7.5 in backports?
[11:16] <acheronuk> tsimonq2: I explained only a day or 2 ago
[11:16] <tsimonq2> oh? /me greps logs
[11:16] <tibi> http://paste.ubuntu.com/23274614/
[11:18] <acheronuk> tsimonq2: --> http://paste.ubuntu.com/23274620/
[11:19] <tsimonq2> acheronuk: in your honest opinion, what should migrate to backports-landing first?
[11:21] <tsimonq2> acheronuk: imho we should land Frameworks, then Plasma, then Apps
[11:21] <tsimonq2> acheronuk: I could have our little mini dep tree messed up though ;)
[11:21] <tibi> http://paste.ubuntu.com/23274626/ this is better, it has the crash inside
[11:21] <acheronuk> the staged plasma for xenial was built with FW 5.24 I think, so needs a rebuild on staged 5,26 I think
[11:22] <tsimonq2> acheronuk: which is why I say that we should get that good to go first
[11:23] <acheronuk> tsimonq2: we should get YY good to go FIRST
[11:23] <tsimonq2> ah yes
[11:23] <tsimonq2> that
[11:24] <tsimonq2> acheronuk, santa_, clivejo: what's left for all the mess in yakkety-proposed?
[11:24] <acheronuk> tsimonq2: even plasma and FW on YY is still help up a bit on autopackagetests
 Specifically?
[11:25] <acheronuk> tsimonq2: and to quote the release team.......
 santa_: right; my point is, if these packages don't clear proposed-migration on their own merits, chances are they will not make it for release
 Which is why I'm asking the *specifics* of what we're dealing with.
 I don't want that to happen
[11:26] <acheronuk> any with failing tests on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
 God forbid we release a half migrated anything
[11:28] <acheronuk> I'm going to go through that later to try to work out what can be done, but many of the tests fail without really giving a good reason in the logs
[11:29] <acheronuk> or at least not one that makes sense to me
 You know how to reproduce locally?
[11:29] <acheronuk> never tried
 Launchpad likes to mangle some things sometimes
 It's on the ProposedMigration page
[11:33] <acheronuk> tsimonq2: that page. which no matter how many times you read parts of it, makes little sense
 YOU
 To ME it makes perfect sense
[11:34] <acheronuk> tsimonq2: each to their own. I could give you a page of QM that makes sense to me, but would look like gibberish to you
[11:35] <tsimonq2> yeah
[11:35] <clivejo> but you are Super Simon
[11:35] <tsimonq2> lol
[11:35] <tsimonq2> cosas buenas
[11:36] <tsimonq2> autopkgtests
[11:36] <tsimonq2> autopkgtest tests are run in ephemeral cloud instances as described on /AutopkgtestInfrastructure. The update excuses link to relevant test results, and all results can be browsed on http://autopkgtest.ubuntu.com. 
[11:36] <tsimonq2> In most cases test results should be reproducible in a local QEMU VM. 
[11:36] <tsimonq2> Reproducing tests in the cloud
[11:36] <tsimonq2> Reproducing tests as they are run in production requires access to an OpenStack-based cloud (e.g. Canonistack). Source the relevant nova.rc file with the cloud credentials. Ensure that you have autopkgtest 3.16 or newer installed (the deb installs on all supported Ubuntu releases without further dependencies). 
[11:36] <tsimonq2> First make sure that your cloud knows your public SSH key, in nova keypair-list. If you don't have one yet, add it with nova keypair-add. Let's call this testkey here. 
[11:36] <tsimonq2> You can now run your tests with the ssh runner and the nova setup script, e. g. for the libpng package: 
[11:36] <tsimonq2>     autopkgtest libpng --apt-pocket proposed --apt-upgrade --setup-commands cloud-vm-setup \
[11:36] <tsimonq2>       -- ssh -s nova -- --flavor m1.small --image ubuntu-trusty-i386-server.img --keyname testkey
[11:36] <tsimonq2> The complete command as used in production (including all proxy settings) can also be seen at the top of test logs. 
[11:36] <acheronuk> ^^^^ gibberish
[11:36] <tsimonq2> acheronuk: is that confusing to you?
[11:36] <acheronuk> lol
[11:36] <tsimonq2> you must have a hard life... :P
[11:36]  * tsimonq2 runs
[11:37] <tsimonq2> do you know what QEMU is?
[11:37] <acheronuk> tsimonq2: it's perspective. each person has a different background
[11:41] <acheronuk> soee_: :P https://www.kde.org/announcements/plasma-5.8.0.php
[11:43] <santa_> tsimonq2: various uploads and autopkgtests
[11:43] <soee_> :D
 Y'all get Harald's email?
 I say get rid of Apport :P
[11:57] <acheronuk> I normally disable the damn thing anyway, unless I really need it for a report
 Me too
[12:12] <mamarley> Same here.
[12:13] <mamarley> clivejo: Congratulations on making Developer!!
[12:14] <clivejo> thanks, not as happy an occasion as I thought it would be
 What's wrong, Clive?
[12:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #109: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_okteta/109/
[12:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okteta build #103: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_okteta/103/
[12:48] <acheronuk> Mirv: do you know why tests like this would timer out? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/k/kwin/20161004_005822@/log.gz
[13:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okteta build #104: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_okteta/104/
[13:26] <soee_> clivejo: you have now power to upload to archive ? :)
[13:32] <acheronuk> soee_: in 'theory'. I think clive wants to gain more experience before doing so though?
[13:39] <BluesKaj> Hey folks
[13:40] <soee_> hiho BluesKaj
[13:47] -kubuntu-ci:#kubuntu-devel- Project merger_okteta build #641: FAILURE in 16 sec: http://kci.pangea.pub/job/merger_okteta/641/
[13:52] <BluesKaj> hey soee_
[14:12] <marco-parillo> Hi all; I welcome our new Kubuntu Developer Overlord.
[14:13] <BluesKaj> oh? and who can that be mparillo ? :-)
[14:13] <BluesKaj> marco-parillo,^
[14:17] <marco-parillo> mparillo is my KDE identity (used on my bouncer). marco-parillo is my Launchpad ID, used at work via IRC webchat (IRC ports are blocked here).
[14:18] <marco-parillo> Oh, the question was clivejo is now a Kubuntu Developer.
[14:18] <marco-parillo> The joke came from a Simpsons meme.
[14:50] <Mirv> acheronuk: possibly some stale test process that isn't ended correctly
[14:52] <acheronuk> Mirv: and it would do that on all architectures? as it has done?
[14:53] <acheronuk> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kwin
 Eek!
[15:23] <acheronuk> tsimonq2: eek what?
[15:25] <acheronuk> if you mean that test failure, there is plenty more where that came from :/
[15:26] <acheronuk> tempting to just sign off and come back once ZZ 17.04 has got under way
[15:28] <BluesKaj> I've had 2 yakkety iso images fail after the download, think the source files are corrupt ...yakkety is becoming even messier by the day
[15:32] <acheronuk> BluesKaj: you are a jinxed tester. everything you touch seems to break
[15:32]  * clivejo does even know what that means
[15:32] <clivejo> fail after download?
[15:34] <BluesKaj> md5sums
[15:37] <BluesKaj> nope acheronuk, it's just yakkety ...xenial is running perfectly here even after upgrading with staging ppas last week.
[15:50] <santa_> acheronuk: do you still have the frameworks clones you used for the 5.26 uploading?
[15:51] <acheronuk> santa_: maybe on my other machine
[15:52] <santa_> acheronuk: ok, it's not urgent, but whenever you get there check the e-c-m tag
[15:52] <santa_> it seems it wasn't pushed
[15:53] <acheronuk> odd. will do in a little bit
 Hey clivejo, you should upload calligra :P
[16:03] <clivejo> no I shouldnt
 Lol
 Why not? :P
[16:04] <clivejo> does it have a FFE?
 Afair Kubuntu doesn't follow Feature Freeze
 Plus it's ftbfs
[16:34] <Mirv> acheronuk: sorry on my (Ubuntu) phone and on the run, but yes we have seen cases where a thread by the software was loose at the end of the test run so the autopkgtests waited for it and only killed after 300 minutes or so when the infra kills the test. I can't check the logs right now easily.
[16:36] <acheronuk> Mirv: no problem 
[17:38] -kubuntu-ci:#kubuntu-devel- Project merger_okteta build #642: STILL FAILING in 18 sec: http://kci.pangea.pub/job/merger_okteta/642/
[17:53] -kubuntu-ci:#kubuntu-devel- Project merger_extra-cmake-modules build #782: FAILURE in 17 sec: http://kci.pangea.pub/job/merger_extra-cmake-modules/782/
[18:03] -kubuntu-ci:#kubuntu-devel- Project merger_marble build #470: STILL FAILING in 23 sec: http://kci.pangea.pub/job/merger_marble/470/
[18:34] <acheronuk> santa_: did you say something was being done with drumstick?
[18:34] <santa_> acheronuk: we have to upload it
[18:34] <santa_> we have it in the ppa but not in the archive
[18:35] <acheronuk> yep. who? how?
[18:35] <santa_> acheronuk: let me check later, I feel ark is going to be ready soon
[19:00] <ahoneybun> is it just me or does the guy in the 5.8 video sound like Chris from the Linux Action Show?
[19:15] <soee> "Linux Action Show's Chris Fisher takes us through the existing and new features﻿"
[19:43] <santa_> clivejo: remember to push the ark commit + tag
[19:46] <clivejo> santa_: I did push after the upload
[19:46] <clivejo> but I dont see it in the web UI
[19:48] <clivejo> http://paste.ubuntu.com/23276515/
[19:48] <santa_> hmm I don't get it here with git pull
[19:49] <santa_> push again?
[19:49] <santa_> also what does 'tig' say about kubuntu_yakkety_archive and origin/kubuntu_yakkety_archive ?
[19:49] <clivejo> $ git push --tags origin 
[19:49] <clivejo> Everything up-to-date
[19:49] <santa_> do they point to the same commit?
[19:50] <santa_> hmm
[19:50] <santa_> try git push origin kubuntu_yakkety_archive
[19:50] <santa_> and then git push --tags
[19:52] <clivejo> ok that worked
[19:52] <clivejo> that was weird
 (Photo, 720x1280) https://irc-attachments.kde.org/43DZENaH/file_665.jpg Screenshot (Oct 4, 2016 3:54:58 PM)
 :( :(
[19:57] <santa_> clivejo: I think it tries to push master if you don't say the branch
[19:58] <acheronuk> I'm fairly sure I didn't have to do that pushing tags the other day
[20:54] <santa_> clivejo: are you still around?
[21:16] <clivejo> santa_: I am now
[21:18] <santa_> clivejo: libkeduvocdocument is ready to upload in git
[21:18] -kubuntu-ci:#kubuntu-devel- Project merger_libkeduvocdocument build #709: FAILURE in 14 sec: http://kci.pangea.pub/job/merger_libkeduvocdocument/709/
[21:19] <santa_> while there is so much diff, it's just an soname bump requested by the release team to accept the package for yakkety
[21:20] <tsimonq2> they're talking about Plasma 5.8 now on Linux Unplugged
[21:20] <tsimonq2> I'm in the queue to say hai
[21:21] <valorie> oh nice
[21:21] <tsimonq2> and he moved on from it /o\
[21:22]  * valorie is preparing to leave for the cabin
[21:22] <valorie> it is really dark and dreary here!
[21:22] <tsimonq2> valorie: have a fun time :)
[21:22] <clivejo> santa_: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/libkeduvocdocument/commit/?id=2e670f6bbf0796f49511dabb1a666c15298045b5
[21:22] <clivejo> seems to be missing a changelog entry?
[21:22] <valorie> no internet, beyond enough phone bandwidth for an occasion Telegram update
[21:23] <clivejo> is that on purpose?
[21:23] <valorie> no indeed
[21:23] <valorie> when we can get something up there, we will
[21:23] <santa_> clivejo: ugh, nope, adding it now...
[21:24]  * clivejo is amazed at how socially as ease Simon is
[21:25] <clivejo> at his age I wouldnt have said boo to a ghost
[21:25] <wxl> well we've had to work on him a bit since he entered the community XD
[21:25] <wxl> still, he is certainly well ahead in many areas
[21:25] <santa_> clivejo: added now
[21:26] -kubuntu-ci:#kubuntu-devel- Project merger_libkeduvocdocument build #710: STILL FAILING in 14 sec: http://kci.pangea.pub/job/merger_libkeduvocdocument/710/
[21:27] <valorie> https://goo.gl/maps/2jL8NkMGGqw -- small clearing across the river from the end of the runway is where our cabin is
[21:27] <tsimonq2> clivejo: oh?
[21:27] <valorie> not a lot of reasons for a company to provide service up there
[21:28] -kubuntu-ci:#kubuntu-devel- Project merger_libkeduvocdocument build #711: STILL FAILING in 15 sec: http://kci.pangea.pub/job/merger_libkeduvocdocument/711/
[21:29] <clivejo> tsimonq2: yeah, I was a shy wee thing
[21:29] <clivejo> still am
[21:31] <clivejo> santa_: done
[21:36] <santa_> clivejo: ok, I will have dinner and talk to steve later, thanks!
[21:37] <clivejo> any idea why none of our uploads have been processed yet other packages in the queue before and after us have?
[21:40] <clivejo> and why every question I ask gets ignored! :/
[21:50] <tsimonq2> clivejo: ping someone
[21:50] <tsimonq2> clivejo: slangasek infinity etc.
[21:50] <tsimonq2> clivejo: if it's urgent make it urgent
[21:50] <clivejo> I have
[21:50] <tsimonq2> ok
[21:50] <tsimonq2> well
[21:50] <tsimonq2> what have you said?
[21:51] <tsimonq2> 14:28 < clivejo> slangasek: would you have time to help with something?
[21:51] <tsimonq2> NEVER EVER EVER ask them something like that :P
[21:52] <tsimonq2> clivejo: what did you need? I'll throw a ping his way
[21:52] <clivejo> I have a few questions
[21:52] <tsimonq2> !ask
[21:52] <tsimonq2> clivejo: follow that advice by heart ^^^^^^
[21:52] <acheronuk> ha!
[21:53] <clivejo> I wanted to know how we deal with the kdeconnect renaming 
[21:53] <acheronuk> ubottu knows best
[21:53] <acheronuk> except on that ^^^
[21:53] <tsimonq2> clivejo: the release team won't bat an eye if you don't ask then questions they can answer
[21:53] <clivejo> and how we add new packages
[21:53] <tsimonq2> clivejo: you upload and it goes into a NEW queue
[21:54] <tsimonq2> clivejo: for package renames, it's just a metter of renaming the appropriate files, it might go in the NEW queue
[21:54] <clivejo> can you stuff be added at this time?
[21:54] <tsimonq2> *matter
[21:54] <clivejo> can new
[21:54] <tsimonq2> clivejo: well ask them, tell them why :)
[21:54] <clivejo> I have asked lots of question and never got an answer
[21:55] <clivejo> the only answer I ever got was to make a donation
[21:55] <tsimonq2> clivejo: give me a specific one line question, and I'll show you how to ask it :P
[21:55] <tsimonq2> OH SH*T XD
[21:55] <tsimonq2> "make a donation" lol
[21:55] <acheronuk> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[21:56] <acheronuk> for kirigami ??
[21:56] <tsimonq2> clivejo: plus the release team knows me because I act as Lubuntu release manager from time to time :)
[21:56] <tsimonq2> clivejo: come on, ask me!
[21:56] <tsimonq2> don't be shy! :P
[21:56] <clivejo> oh I see, favouritism
[21:57] <tsimonq2> well they'll (most likely) pay more attention to pings from people they know
[21:57] <acheronuk> more likely they know that if they don't answer, he won't go away ;)
[21:58] <acheronuk> tsimonq2: or what you said
[21:58] <tsimonq2> !ignore
[21:58] <tsimonq2> acheronuk: ubottu knows best ;)
[22:01] <acheronuk> I know
[22:10] <clivejo> tsimonq2: how do I get this package sync'ed with debian and into yakkety - https://bugs.launchpad.net/ubuntu/+source/libdrumstick/+bug/1584310
[22:12] <tsimonq2> ok I'll ask them that
[22:16] <tsimonq2> !info drumstick-alsa unstable
[22:16] <tsimonq2> :/
[22:16] <clivejo> libdrumstick
[22:17] <tsimonq2> !info libdrumstick unstable
[22:17] <tsimonq2> :/
[22:17] <tsimonq2> aha nvm
[22:18] <tsimonq2> 0.5.0-4 is in unstable
[22:18] <tsimonq2> !info libdrumstick testing
[22:18] <clivejo> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824771
[22:18] <tsimonq2> whatever
[22:18] <tsimonq2> clivejo: oh so you want it updated to the latest version?
[22:19] <tsimonq2> I wish the bug report could have mentioned that...
[22:19] <clivejo> libdrumstick (1.0.2-1) unstable; urgency=medium
[22:19] <clivejo> it does
[22:19] <clivejo> Changed in libdrumstick (Debian):
[22:19] <clivejo> status:	New → Fix Committed
[22:19] <tsimonq2> oh nvm
[22:19] <clivejo> Committed → Fix Released
[22:20] <acheronuk> they did it?
[22:20] <clivejo> debian did it
[22:20] <clivejo> Ubuntu havent
[22:20] <tsimonq2> clivejo: not in unstable, can't sync
[22:21] <tsimonq2> clivejo: harumph, https://launchpad.net/debian/+source/libdrumstick
[22:21] <acheronuk> experimental
[22:22] <clivejo> https://launchpad.net/debian/+source/libdrumstick/1.0.2-1
[22:22] <tsimonq2> libdrumstick (1.0.2-1) experimental; urgency=medium
[22:22] <tsimonq2> but you don't understand
[22:22] <tsimonq2> no SANE Ubuntu Release team member would even TRY to sync from Experiemental
[22:23] <tsimonq2> clivejo: you have to poke someone to migrate it
[22:23] <clivejo> Im fed up poking
[22:23] <clivejo> my finger is sore
[22:23] <tsimonq2> clivejo: even then, it has to migrate from Sid to Stretch, which takes a minimum of five days
[22:24] <clivejo> well minuet isnt going anywhere then
[22:24] <tsimonq2> clivejo: slangasek will poke it later so it gets out of the NEW queue
[22:24] <tsimonq2> OH that's something
[22:25] <tsimonq2> the uploader is Ross Gammon!
[22:25] <clivejo> its needs libdrumstick to build
[22:25] <clivejo> thats why I opened that bug back in May
[22:26] <tsimonq2> clivejo: then why do you wait a week and a half before release to bump it!
[22:26] <clivejo> because minuet is stuck in the queue
[22:27] <clivejo> and it needs libdrumstick!
[22:27] <clivejo> as I said in the report requires 'drumstick-alsa>=1.0.1'
[22:29] <tsimonq2> clivejo: check your facts, dude. I asked the release team to do that, and you kept facts.
[22:30] <clivejo> Im too tired and fed up to argue
[22:59] <ScottK> tsimonq2: re syncing from experimental, it depends on why it's there.
[23:10] <tsimonq2> ScottK: oh?
[23:10] <tsimonq2> ScottK: please explain
 Marble just been accepted
[23:15] <acheronuk> :)
[23:16] <tsimonq2> :D
[23:19] <acheronuk> accepted okteta
[23:26] <acheronuk> our uploads are now buried under a pile of 'mate'
 I don't like the idea of any of our packages mating
 We have enough as it is
[23:27] <wxl> you mean mah-tay-ing
[23:28] <ScottK> tsimonq2: as an example, sometimes a package is in experimental only because the Debian release team hasn't given the OK to start a transition due to other transitions in progress.
[23:38]  * acheronuk yawns
[23:38] <acheronuk> zzzzzzzzzzzz
 ScottK is there a way to remove a package that has been uploaded?
 But is stuck in the queue
 I believe its stuck in NEW
 Good night all :)
[23:44] <acheronuk> oooh. Unapproved: accepted extra-cmake-modules [source] (yakkety-proposed) [5.26.0-0ubuntu2]
 Good night Rik, thanks for all your help today bringing me up to speed
[23:50] <ScottK> If it's in source New, removal is easy.  If it's binary New it's more complicated since the source has already been accepted 
 It is minuet which needs an updated libdrumstick to build
 Might be better to drop it and start afresh in zz
[23:56] <tsimonq2> .or
[23:56] <tsimonq2> whoops
 Backport it to our PPA