[00:00] oic [00:08] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #759: SUCCESS in 8 min 12 sec: http://kci.pangea.pub/job/mgmt_merger/759/ [00:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-icons build #53: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_breeze-icons/53/ [00:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_frameworkintegration build #202: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_frameworkintegration/202/ [00:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #115: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/115/ [00:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #11: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/11/ [00:31] Intial bootstrap started: https://launchpad.net/~kubuntu-ci/+archive/ubuntu/stage/+packages [00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #7: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_kdb/7/ [00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #13: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kdb/13/ [00:37] !info libssl1.0-dev yakkety [00:37] Package libssl1.0-dev does not exist in yakkety [00:37] !info libssl1.0-dev xenial [00:37] Package libssl1.0-dev does not exist in xenial [00:37] !info libssl1.0-dev zesty [00:37] libssl1.0-dev (source: openssl): Secure Sockets Layer toolkit - metapackage. In component main, is optional. Version 1.0.2g-1ubuntu10 (zesty), package size 3 kB, installed size 206 kB [00:39] So it looks like we need to backport libssl... [00:39] No, I mean openssl [00:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #238: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/238/ [00:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #40: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_kopete/40/ [00:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kfind build #22: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kfind/22/ [00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #41: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/41/ [00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #27: STILL FAILING in 34 min: http://kci.pangea.pub/job/xenial_unstable_trojita/27/ === tsimonq2alt is now known as tsimonq2 [00:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #22: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/22/ [00:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #13: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/13/ [00:45] But yeah, we need a newer openssl for Qt 5.7.1... [00:47] Before we take this new openssl out of KCI's repos, I want to consult with the Security Team to see how risky this is... [00:49] backport to what? [00:49] Our PPAs. [00:49] Qt 5.7.1 won't build without it. [00:49] ppas for what release? [00:49] Right now KCI but in the future, Backports. [00:50] I doubt we will be wanting to put Qt 5.7.1 in backports [00:50] ...don't we need it for apps? [00:51] Unless we're sticking with Apps 16.04.3 for a while. :) [00:51] (or using the 5.6.1 one...) [00:52] I would say we would be sticking with apps 16.04.3 and plasma 5.8 LTS for a while in Xenial backports [00:53] Ok [00:53] And yakkety has too short a life to maybe worry overly about backports of much more tahn we have [00:54] When do you think we stop supporting Backports? [00:54] just my opinion, but I think we have other issue to concentrate on [00:54] I mean, for Xenial. [00:54] I mean after 5.8 LTS cycle, we need to watch for any fixes and backport them. [00:54] But how long do we keep that up? [00:55] for the 3 years I would say, at least for critical stuff [00:56] shadeslayer: How long did you guys keep up with Backports on Trusty after it was released? [00:57] last trusty packages in updates ppa are Nov 2015 [00:57] I would say backports lands only for latest short and latest lts [00:58] so when new lts is released stop backporting to previous one [00:59] tsimonq2: so that was about 18 months for trusty, if you count the updates ppa [00:59] Ok, fair enough. [00:59] tsimonq2: nothing much in backports for trusty [00:59] MAYBE 18 months. [00:59] Is 24 months a bit much? [01:00] I dunno, like acheronuk said, not a discussion for now... [01:00] we can do what we like, so maybe not try to set an artificial time limit. [01:01] Oh, awesome, so the only difference between Zesty's and Yakkety's openssl is just adding the virtual package that Qt needs! [01:01] if something in the future seems a good and not too disruptive backport, we can decided [01:01] *decide [01:01] It builds off of Yakkety's which is a Whole Lot Of Security Patches. [01:01] acheronuk: Ok, fair enough. [01:02] It depends on how long Plasma 5.8 LTS is supported I guess? [01:02] 18 months? [01:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #317: STILL FAILING in 6 min 40 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/317/ [01:03] I mean, ok, let's look at the release schedule... [01:03] Because I'd rather stick with LTS on backports if at all possible [01:04] Perfect! [01:04] well that is the sensible option, no matter the length [01:05] 5.8.9 LTS is scheduled for April 10, 2018! [01:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #139: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kopete/139/ [01:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #188: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/188/ [01:06] there you go then. release date of 18.04 (hopefully LTS) then [01:06] and we can more or less switch focus then if that is what we want [01:06] acheronuk: We might need to do something like this -- have Xenial always be Plasma LTS and the regular Kubuntu (9 month) always have the latest Plasma. [01:06] ¯\_(ツ)_/¯ [01:07] Let's discuss in January when Plasma 5.9.0 gets released. [01:07] IMHO it would be the best to do that if at all possible... [01:07] but who knows? depends of schedules and resources, and they can change. we don't know what the kubuntu team will be like then [01:08] Exactly. We could have 20 more minions or we could barely be alive. Who knows? :) [01:08] (HOPEFULLY the former) [01:10] acheronuk: In fact, right now I see no reason why we can't backport apps 16.12 to Yakkety backports (but NOT Xenial!), as like I said, the openssl isn't that different, it's new software, and it's less of a Qt mess. [01:10] acheronuk: I'll send something to the ML in a bit, maybe? [01:10] Oh wait nvm... [01:11] We have the policy of "land in devel before putting it in backports" ^__^ [01:11] * clivejo thinks that policy may need looked at [01:12] Yes! :P [01:14] indeed. have to be careful for LTS releases, as once it's there you can't pull it back, but for short 9 month support versions it may be an easier choice [01:15] IF it's worth the work [01:15] I think it is [01:15] Absolutely! [01:16] imo fixing openssl is a security issue and we should do if possible [01:17] tsimonq2: well, it depends. little point backporting to a 9 month version when say it only has 3 months left [01:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #141: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/141/ [01:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_print-manager build #221: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_print-manager/221/ [01:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #175: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/175/ [01:21] acheronuk: sure, but we're supporting xenial for another year, almost? [01:21] I mean Yakkety [01:22] acheronuk: Well when it hits the 3 month mark, we just tell everyone to upgrade if they want newer software! [01:22] valorie: yakkety EOL = July 2017 [01:22] ^ [01:22] ok, 7 months [01:23] + I was talking theoretically, and not specifically about yakkety [01:23] * sintre is gonna stay stubborn with 1604 till the end until new iso has new packages! [01:23] imo worth it because it is a security issue [01:23] and Konvi because it is a crashing issue [01:23] acheronuk: But I think we should backport to whatever the latest release. Doesn't matter how close it is to release, worth the effort imho. [01:23] I might have to learn how to package! [01:23] obviously security issues we deal with right until the EOL date [01:24] acheronuk: Because we may not always have the ability to upload to the devel release, not saying people would run that! [01:24] I think so, acheronuk. [01:24] valorie: Hop on the train with wxl. He's good at teaching. Like really good. :) [01:25] perhaps after the holidays [01:25] we are talking a bit at cross purposes here. I was mainly talking about major Plasma and apps releases [01:25] having xmas eve here at the house [01:25] etc. [01:26] acheronuk: there I agree with you 100% [01:26] have fun if your cooking guilt guests into doing dishes my mom is master at that [01:26] security and major bugfixes are a whole other matter [01:26] amen [01:26] ya want the new, get the new [01:26] don't expect the new, on the old [01:27] he yi like new stuff on my old [01:27] love the backports :) [01:27] But whatever happens, I'm all-time merge failure vanguard. :P [01:27] sintre: backports is pretty much bugfixes [01:27] tsimonq2: you mind if I look at the Qt builds while you are sleeping, during my morning? [01:27] valorie > gave me new plsma [01:28] sure, because of release scheds [01:28] wxl: getting anywhere with the script? [01:28] acheronuk: Absolutely (not, I don't mind, whatever ahhhh), go ahead. I'll post here before I go to bed what I've been up to and we can tag team. :) [01:28] clivejo: if by that you mean am i about ready to pull my hair out, yes [01:28] wxl: Have you been working on this the whole time? :D [01:29] was looking more for an ETA [01:29] tsimonq2: I may not get to them at all, but just didn't want to step on your toes should I have time and can see something I can clearly progress with [01:29] well yes but i had to fix some other things along the way [01:29] acheronuk: Ok, let's keep communicated. :) [01:29] i need to identify the point at which the actual probelm begins [01:29] valorie > i'd love newwest of new but yakkity still is suer crashy in live envirmoment , so maybe super new way to go iso updated every two week :) [01:29] it's a little unclear [01:29] so i'm trying to unravel types and crap [01:29] when i learn to do more than type sudo apt update i might help :) [01:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #83: STILL FAILING in 58 min: http://kci.pangea.pub/job/yakkety_unstable_marble/83/ [01:32] !info default-libmysqlclient-dev [01:32] Package default-libmysqlclient-dev does not exist in yakkety [01:32] !info default-libmysqlclient-dev zesty [01:32] default-libmysqlclient-dev (source: mysql-defaults): MySQL database development files (metapackage). In component main, is optional. Version 1.0.0ubuntu1 (zesty), package size 3 kB, installed size 9 kB [01:33] ffs [01:33] language! [01:33] !language [01:33] Please avoid any language that may be considered offensive, including acronyms and obfuscation of such - also see https://wiki.ubuntu.com/IRC/Guidelines || The main channels are English only, for other languages, see https://wiki.ubuntu.com/IRC/ChannelList [01:34] lol [01:34] For Freak's Sake [01:34] For Frank's Sake [01:34] For Feather's Sake [01:34] I heard what you said! [01:34] uh [01:34] uhhhhhhhh [01:34] :) [01:34] * tsimonq2 runs [01:35] ok. goodnight all I think. If I don't sleep. I won't be doing much tomorrow! [01:35] um [01:35] hahah [01:35] weird [01:35] i just ran a test and it didn't even print out akonadi-import-wizard [01:36] ah but there's a whole bunch of kdepim stuff [01:36] so it looks like git-clone-all didn't behave right but no matter [01:36] o/ acheronuk [01:36] cuz it has the problem [01:36] wxl: Ok, cool, now Fix It. :) [01:36] * acheronuk goes ZZZZzzzz.... [01:42] dinner..... [01:42] shower .... [01:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_print-manager build #75: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_print-manager/75/ [01:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #42: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/42/ [01:42] good idea clivejo [01:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #73: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/xenial_unstable_marble/73/ [01:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #41: STILL UNSTABLE in 1 hr 33 min: http://kci.pangea.pub/job/zesty_unstable_krita/41/ [01:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #18: STILL UNSTABLE in 1 hr 34 min: http://kci.pangea.pub/job/yakkety_unstable_krita/18/ [01:43] * clivejo smells of wet dog [01:43] (not in the same one though :P) [01:43] I smell of sweat and long day... [01:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_frameworkintegration build #203: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_frameworkintegration/203/ [01:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_print-manager build #32: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/zesty_unstable_print-manager/32/ [01:46] clivejo, acheronuk: I almost wonder if we should ask the Launchpad team to lower our build priorities on our nightlies (once holidays are over) to make sure we aren't stopping other people from building things... [01:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #50: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/50/ [01:47] LP are adding resources, so unless they complain, I would say not [01:47] ok i finally think i unraveled it [01:47] now to figure out a solution [01:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-icons build #54: STILL FAILING in 16 min: http://kci.pangea.pub/job/zesty_unstable_breeze-icons/54/ [01:47] Fair enough @acheronuk [01:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_peruse build #14: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_peruse/14/ [01:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #236: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/236/ [01:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #145: FAILURE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/145/ [01:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #13: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kreport/13/ [01:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #49: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_kstars/49/ [01:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #20: STILL UNSTABLE in 1 hr 43 min: http://kci.pangea.pub/job/xenial_unstable_krita/20/ [01:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #45: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_cantor/45/ [01:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #139: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/139/ [01:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #56: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/56/ [01:53] got something but i'll be back with the implementation [01:53] you'll have something tonight [01:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #23: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_trojita/23/ [02:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #247: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_cantor/247/ [02:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #235: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/235/ [02:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-nm build #46: FAILURE in 30 min: http://kci.pangea.pub/job/zesty_unstable_plasma-nm/46/ [02:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #239: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/239/ [02:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #23: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/23/ [02:04] wxl: :D [02:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #349: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_frameworkintegration/349/ [02:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #318: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/318/ [02:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #162: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/162/ [02:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kreport build #11: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_kreport/11/ [02:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kimap build #175: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_kimap/175/ [02:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #57: STILL UNSTABLE in 54 min: http://kci.pangea.pub/job/zesty_unstable_marble/57/ [02:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #37: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/37/ [02:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #321: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/xenial_unstable_kstars/321/ [02:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #33: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_peruse/33/ [02:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #188: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/188/ [02:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konqueror build #37: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/zesty_unstable_konqueror/37/ [02:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #266: FAILURE in 31 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/266/ [02:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #101: FAILURE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kdevplatform/101/ [02:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #350: STILL FAILING in 6 min 40 sec: http://kci.pangea.pub/job/xenial_unstable_frameworkintegration/350/ [02:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #29: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_peruse/29/ [02:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #41: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/41/ [02:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kfind build #28: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_kfind/28/ [02:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khtml build #148: STILL FAILING in 42 min: http://kci.pangea.pub/job/yakkety_unstable_khtml/148/ [02:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #28: STILL FAILING in 42 min: http://kci.pangea.pub/job/xenial_unstable_trojita/28/ [02:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #146: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/146/ [02:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #84: STILL FAILING in 43 min: http://kci.pangea.pub/job/yakkety_unstable_marble/84/ [02:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kimap build #176: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kimap/176/ [02:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #267: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/267/ [02:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #236: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/236/ [02:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-nm build #47: STILL FAILING in 24 min: http://kci.pangea.pub/job/zesty_unstable_plasma-nm/47/ [02:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #102: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_kdevplatform/102/ [02:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevplatform build #95: FAILURE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kdevplatform/95/ [02:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #249: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/249/ [02:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khtml build #149: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_khtml/149/ [03:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #282: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/282/ [03:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #92: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/92/ [03:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop build #66: FAILURE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop/66/ [03:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevplatform build #96: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kdevplatform/96/ [03:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [03:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_grantlee-editor build #34: FIXED in 18 min: http://kci.pangea.pub/job/yakkety_unstable_grantlee-editor/34/ [03:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #39: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/39/ [03:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konqueror build #25: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_konqueror/25/ [03:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop build #57: FAILURE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop/57/ [03:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop build #67: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop/67/ [03:34] does upstream Krita even want to be in the archives? They already provide up to date AppImage and Snaps [03:37] o/ mhall119 [03:37] mhall119: Well if we want to include it on an image by defualt, well, yeah... [03:37] *default [03:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevplatform build #57: FAILURE in 15 min: http://kci.pangea.pub/job/zesty_unstable_kdevplatform/57/ [03:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #39: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_korganizer/39/ [03:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #93: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/93/ [03:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop build #58: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop/58/ [03:52] mhall119: not just us, but Ubuntu-Studio [03:53] this was an issue for them before Yakkety release [03:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #40: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/40/ [04:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #41: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/41/ [04:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevplatform build #58: STILL FAILING in 16 min: http://kci.pangea.pub/job/zesty_unstable_kdevplatform/58/ [04:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #30: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_korganizer/30/ [04:12] acheronuk: Going to bed, I only have qtbase done, but Debian doesn't have it done either, so good luck... :) [04:13] thanks for doing that, tsimonq2! [04:14] valorie: np :) [04:14] o/ [04:16] sleep well [04:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #40: FAILURE in 15 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/40/ [04:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #41: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/41/ [04:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #97: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/97/ [04:53] Hello. Does anybody know if digikam is unmaintained now in Kubuntu? [04:54] I was wondering if anybody knew why digikam 5.x packages haven't yet made it into the distro. Thanks! [04:57] !info digikam [04:57] digikam (source: digikam): digital photo management application for KDE. In component universe, is optional. Version 4:4.14.0-4ubuntu6 (yakkety), package size 2407 kB, installed size 10235 kB [04:57] hmmm [04:57] jfd5xte: please file a bug [04:57] it's possible someone started to package it and ran into problems [04:59] interesting. I haven't yet done this using launchpad before. Looking into it... [05:01] easiest way is `ubuntu-bug packagename` [05:01] much of the work is done for you [05:01] if you tell me the bug number once you file it, I'll confirm it [05:02] wow this is all new. kewl [05:03] it's lovely that you care enough to help out [05:07] jfd5xte: digikam 5.1 parked in the staging ppa in August, but somehow it never made it out. The people who know a heck of lot more as to why are sleeping (or busy with homework). [05:08] Oh ok. [05:08] Should I still file a bug? I just created an account [05:08] yes, file the bug [05:08] please [05:08] DarinMiller: ! [05:09] "somehow never made it out" [05:09] ... [05:10] we need better checking [05:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #98: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/98/ [05:13] Ok, I just created Bug #1651942 [05:13] bug 1651942 in digikam (Ubuntu) "Digikam 5.x packages not available in Kubuntu 16.10" [Undecided,New] https://launchpad.net/bugs/1651942 [05:13] Yes, if I can ever learn enough to be useful, I will assist with the process. But for now, work takes up to much of my time. [05:14] Thanks jfd5xte! [05:14] o^ [05:14] \o/ [05:15] Thank you valorie, DarinMiller [05:15] anybody know a link toa simple explaination of grub loaders and boot loaders [05:15] * valorie goes off to pile on! [05:15] !grub [05:15] GRUB2 is the default Ubuntu boot manager. Lost GRUB after installing Windows? See https://help.ubuntu.com/community/RestoreGrub - For more information and troubleshooting for GRUB2 please refer to https://help.ubuntu.com/community/Grub2 [05:15] have a very interested asian guy who saw me help somebody in ubuntu know he really won't stop pmin me lol [05:15] and thank you for your contribution, jfd5xte [05:16] sintre: /mode sintre +i [05:16] will stop the PMs [05:17] sintre: here are some older links but still mostly valid: http://www.howtogeek.com/114884/how-to-repair-grub2-when-ubuntu-wont-boot/ [05:17] http://www.av8n.com/computer/htm/grub-reinstall.htm [05:19] * DarinMiller is heading to bed... [05:19] Night all o/ [05:21] of course i ge tto line 8 of typing hwow i would explain linux to a child and my lil china man decides to quit irc [05:21] well atleast it got rid of him lol [05:24] please ask support questions in #kubuntu and not here [05:31] ? [05:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #98: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/98/ [05:31] this is not a support channel [05:32] that's #kubuntu [05:34] well seem some lee way for a line or to of casual conversation but i guess , not [05:34] and i apologise for sending you a msg [05:35] sintre: we have separate channels for a reason [05:49] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #56: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/56/ [06:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #99: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/99/ [06:21] argh [06:21] well [06:21] clivejo: acheronuk: i would make a merge proposal but lp doesn't want to let me, so here's the code https://git.launchpad.net/~wxl/+git/kubuntu-automation/commit/?id=265051d5723d7e31fa9b709220a59b59805cd395 [06:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #149: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/149/ [07:49] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kexi build #25: STILL FAILING in 8 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_kexi/25/ [07:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [07:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevplatform build #97: FIXED in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kdevplatform/97/ [07:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [07:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [07:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #103: FIXED in 27 min: http://kci.pangea.pub/job/xenial_unstable_kdevplatform/103/ [07:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevplatform build #59: FIXED in 27 min: http://kci.pangea.pub/job/zesty_unstable_kdevplatform/59/ [07:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [07:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #268: FIXED in 20 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/268/ [08:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [08:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #147: FIXED in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/147/ [08:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [08:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-nm build #48: FIXED in 22 min: http://kci.pangea.pub/job/zesty_unstable_plasma-nm/48/ [08:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kexi build #26: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_kexi/26/ [08:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [08:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop build #59: FIXED in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop/59/ [08:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [08:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #42: FIXED in 18 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/42/ [08:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [08:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop build #68: FIXED in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop/68/ [09:04] tsimonq2, acheronuk: FWIW, we had the plasma on xenial discussion a while ago already and back then the plan was to stick to 5.8. As you noticed people care less and less about the LTS backports as time goes on, so using anything other than the LTS is not in the interest of our backports users [09:05] now that's about plasma, apps and qt5.7 is a different story depending on the amount of work it is [10:22] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1178: FAILURE in 2 min 49 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1178/ [10:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [10:38] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1179: FIXED in 3 min 46 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1179/ [12:29] tsimonq2: there were scripts [12:29] I don't remember [12:42] (Photo, 1280x720) https://irc-attachments.kde.org/0gAJ652w/file_1484.jpg Moon [12:43] shadeslayer: I mean when did you release what? [12:43] tsimonq2: in some PPA, again, don't recall [12:43] backports were a lot easier in the past as there were less components [12:44] qt4 was essentially one bundle, then there was the SC as one bundle, then the extra stuff [12:44] so backports were usually done in a day or two with little adjustments. [12:44] Support timeline was typically until the next LTS is out. [12:44] yofel: whats your thoughts on krita being snap only? [12:45] EDONTCARE [12:45] We can't have it like that, we need it on an image... [12:45] it sitting in NEW for so long isn't nice, but that happenes every now and then [12:45] We need a package in the archive! [12:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_digikam build #1: FAILURE in 3 min 12 sec: http://kci.pangea.pub/job/zesty_unstable_digikam/1/ [12:46] keep poking archive/release people close to FF [12:46] and digikam isn't CI-able in it's current packaging format [12:46] Oh? [12:46] How's that? [12:47] digikam git is *just* digikam. What we package is the SC which is digikam + showfoto + kipi-plugins + bundled libs [12:47] there is a bundle git repo that can create the bundle, but you would have to make like another CI job that does the bundling, push that to a hidden repo on LP, then use that in the CI [12:48] Ah ok [12:48] or you create packaging repos for the CI, but that kind of defeats the point [12:48] How does one add different types of jobs to KCI anyways? [12:49] either by hand (not recommended) or by adding it to the job list in the tooling and then running the update script [12:49] Hi all [12:49] One of these days yofel, could you give me a walkthrough of how KCI is set up so I can submit patches? :) [12:50] yofel: I forgot about that! Thought it was a victim of Haruld's rampage [12:50] With Ruby...? [12:50] I should have time over the next 2 weeks for that. And we might want to shedule an evening to talk about CI anyway [12:50] Eew Ruby... [12:51] *schedule [12:51] yofel: OK, on a bus right now, any chance you could send a Doodle to the ML or at least here? :) [12:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_digikam build #2: STILL FAILING in 1 min 4 sec: http://kci.pangea.pub/job/zesty_unstable_digikam/2/ [12:53] Hi all, today kwin_x11 started crashing. When add sound and displayed on the screen icon's kwin crashing, someone else this happening? [12:53] What version of Kubuntu are you running? [12:53] Do you have Backports enabled? [12:53] When did this start? [12:53] When is the last time you updated your system? [12:54] :) [12:54] and this is not a support channel, #kubuntu please [12:55] Well yeah, but answer those questions there please. :) [12:55] I have a feeling KurousagiMK2 has the KCI repo enabled, from what they said in #kde the other day [12:55] Eek! [12:55] Whyyyyyyyyy? [12:56] Kubuntu 17.04 +KCI [12:56] kwin_x11-20161222-143029.kcrash.txt -> https://paste.kde.org/pbslt49ub [12:56] We do not support the KCI ppa, it's extremely unstable... [12:57] * clivejo looks at tsimonq2 [12:57] I would suggest using ppa-purge or even reinstalling. :) [12:57] clivejo: Hey now. :P [12:57] this is -devel [12:57] KCI is devel [12:58] But do any Kubuntu developers ACTUALLY use that PPA? [12:58] libc [12:58] yes, I do [12:58] Just saying... [12:58] Oh? [12:58] tsdgeos: in a VM here. to test [12:58] acheronuk: has it on VM too [12:58] libc is the raise, line 30 is the crash [12:59] Simin I mean [12:59] *Simon... [12:59] clivejo: Max must have turned you mad! :O [13:00] tsimonq2: Ive always run +1 stuff [13:00] Me too but not the KCI ppa! [13:00] https://cgit.kde.org/kwin.git/commit/?id=6383f8304711719fe22371474138efc144adc750 [13:01] KurousagiMK2: I think that needs to go upstream [13:02] I can't see mgraesslin online at the moment [13:03] KurousagiMK2: is there anything that triggers that crashing? [13:03] adding/removing monitors? [13:04] well, Neon dev git-unstable is pretty much the same and people run that, but you still have to expect frequent breakages while code is WIP [13:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_digikam build #1: FAILURE in 9 min 8 sec: http://kci.pangea.pub/job/xenial_unstable_digikam/1/ [13:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_digikam build #3: STILL FAILING in 10 min: http://kci.pangea.pub/job/zesty_unstable_digikam/3/ [13:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_digikam build #1: FAILURE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_digikam/1/ [13:06] ‎‎clivejo:‎ only adds sound, appears OSD -> crash [13:08] well, Martin Gräßlin is clearly making some changes to the OSD system in git, so until complete and tested bugs/crashes in that quite possible [13:08] https://cgit.kde.org/kwin.git/log/ [13:09] understood [13:10] He might be away for the holidays [13:16] mhall119: from my understanding they want to be in the archive, but they want the latest bug fix versions. I don't think they are very happy about the version in the achives being so old [13:17] !info krita zesty [13:17] krita (source: calligra): pixel-based image manipulation program for the Calligra Suite. In component universe, is optional. Version 1:2.9.11-0ubuntu3 (zesty), package size 8254 kB, installed size 32415 kB [13:18] 2.9.11 compared to latest which is 3.1 [13:19] 2.9.11 was released on 3rd Feb 2016 [13:19] 3.1 on the 14th December [13:21] uploading a calligra without the krita binary might help too (and any files removed from other packages) [13:22] also, britney might need an easy hint for the binary package takeover for the migration [13:22] acheronuk: you scared me with that typo D: [13:26] tsdgeos: whoops. sorry. tab completing the wrong nick there! [13:49] clivejo: well that's the blessing and curse of the archives isn't it? You get frozen in time [13:50] clivejo: what's the bug # for getting the new package uploaded? [13:50] is it in debian? [13:52] Hi everybody. I'm Kubuntu 16.04 user and today I have updated plasma to 5.8 version: http://kubuntu.org/news/kubuntu-and-linux-mint-doing-plasma-5-8-testing/ After upgrade I have tried to run vlc player, but it failed with segfault. I captured valgrind log, but I don't know how to report this issue correctly. There is no link in the news to bugtracker or [13:52] something like that. Can somebody help me with issue reporting? [14:07] mhall119: Its not new per se, its a split from calligra. [14:07] !info krita unstable [14:07] Package krita does not exist in unstable [14:10] !info calligra unstable [14:10] calligra (source: calligra): extensive productivity and creative suite. In component main, is optional. Version 1:2.9.11+dfsg-4 (unstable), package size 41 kB, installed size 155 kB [14:10] it's been sitting in debian NEW for some 3 months too now [14:22] hi mariogrip [14:22] long time no see! [14:25] clivejo: Hey! yeah been a long time. We should do the party again soon! haven't seen any notification about it so i assumes it got shut down or on halt? [14:26] Hai :D [14:26] I heard something about Google changing the events thingie [14:30] lmnet: did you use backport or backport-landing? [14:30] acheronuk: I'm using backport-landing. [14:34] lmnet: that has a test build of qt in it to fix a timezone bug at the moment. the updates are all actually now in ppa:kubuntu-ppa/backports [14:34] lmnet: hmm.. the new Qt does seem to segfault VLC! [14:35] typical. fix one bug and another pops up! [14:35] is 17.04 no longer using .bashrc or .bash_aliases. none of my aliases are working , receivibg errors about wrong syntax [14:36] acheronuk: your vlc crashes too? [14:37] lmnet: yep. just tried it. it's fine with the qtbase in ppa:kubuntu-ppa/backports though [14:38] acheronuk: so, what should I do with this? Report a bug somewhere? [14:39] lmnet: I shall try a rebuilt VLC in a bit, but if you want VLC to work right now you'll need to downgrade qtbase to the verion in just 'backports' [14:41] lmnet: you can, report a bug here if you like https://bugs.launchpad.net/kubuntu-ppa but I am looking at this. [14:41] ok, thx. I can wait [14:43] lmnet: going to upload a rebuild of VLC in another ppa soon. may fix it. may not. but if you are about I will post a link to test [14:44] ok [14:52] hi marco-parillo [14:53] Good day, clivejo [15:08] kubuntu will use custom menu icon now after it changed ? [15:08] *it changed in Plasma [15:08] it changed? [15:09] yofel: http://embra.edinburghlinux.co.uk/~jr/tmp/plasma.png [15:09] todays commit [15:09] there was a talk on ml also [15:09] Sweet! Awesome wallpaper! [15:11] well, putting the plasma logo there is at least consistent with the branding [15:11] but that might be a nice point to put something else there [15:11] and we need a login wallpaper, this blue is driving me crazy [15:11] Yep, let's do it! [15:12] maybe we could talk to someone from vdg to create kubuntu login, menu artwork ? [15:12] I'm pestering my go-to guy now. [15:14] VikingRedwolf was added by: tsimonq2 [15:27] the new logo: http://i.imgur.com/EvfRgz0.jpg [15:28] Hm, yellow [15:32] I thought it looked sickly at the start [15:32] but its growing on me [15:34] lmnet: vlc rebuild didn't seem to make a difference, so doing one of QT instead [15:55] clivejo wxl: result of running the metadata update script after wxl's fix https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/commit/?id=bd4c6d96bc8d7f788ff3c920e568602f357084fb [15:56] started with files removed, do that is basically the diff between the faulty result, and a fresh one from scratch [16:02] acheronuk: looks like vlc or qt bug [16:04] lmnet: well, to fix the qt timezone bug, I imported a pre-done Qt build from a ubuntu test ppa that had the fix I wanted. BUT it came with some other changes/patches that may be causing that issue with VLC [16:05] or exposing a VLC bug [16:05] also, non-qt vlc interface works fine [16:06] lmnet: so, I'm doing a rebuild of the Qt build in normal backports that worked fine for me with VLC, but just adding the timezone patch. nothing else. [16:07] lmnet: so I'm hoping that will fix the timezone bug, but not break VLC [17:00] acheronuk: tl;dr yay it works :) [17:07] wxl: seems so. :) what's more, I understand what you did! [17:07] acheronuk: miraculous XD [17:07] i'm kind of wondering if i shouldn't add a comment in there [17:08] it's a bit "clever" [17:11] i'm going to do that [17:11] and just push to ka, skipping the mp which apparently lp doesn't want me to do anyways [17:14] there [17:14] now i feel better [17:24] ah, you can't do MPs personal repositories, only for ones that belong to a project [17:24] kind of annoying [17:26] but ka is not a personal repo is it? [17:26] it is [17:27] personal to the team [17:29] then how have i done this before??? [17:30] I would like to know that as well if you did it o.O! [17:32] heh [17:32] maybe i haven't [17:32] * wxl shrugs [17:38] wxl: I think you just sent an email to the -devel list with a link to the branch you were requesting to be merged? [17:39] acheronuk: ah that's right. i forgot about that! [17:39] stupid. [17:40] lmnet: can you try the Qt build here? https://launchpad.net/~rikmills/+archive/ubuntu/staging3 [17:41] I'm afraid if you have Qt from the landing ppa, you'll need to downgrade packages. sorry [18:33] soee: that logo is hardly new? [18:33] ne w? [18:33] but now official I suppose? [18:34] seems so [18:39] /ud [18:40] oops [22:30] tsimonq2: I didn't get around to touching Qt 5.7.1 in the end :/ [22:31] having enough hassle with Qt 5.6 failing builds on me! [22:36] * clivejo puts on his VLC hat and dances in front of acheronuk [22:37] Lol [22:38] Grrr.... [22:38] that is one craaaaaazy hat! [22:39] acheronuk: did it build? [22:39] VLC? yes, but didn't fix the issue. [22:40] so cherry picked the timezone patch for QT. [22:40] oh [22:40] *Qt [22:40] Q Tea [22:40] * clivejo runs [22:40] which built fine in my ppa, but weirdly failed on i386 in the staging ppa [22:42] oh i guess i misplaced my "down boy" [22:58] no, thats reserved for Simon being a "dirty" dog [22:59] Heh === rjj_ is now known as rjj