[00:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #57: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/57/
[00:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #64: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/64/
[00:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #54: STILL FAILING in 21 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/54/
[00:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #64: STILL FAILING in 7 min 49 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/64/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #134: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/134/
[00:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #53: STILL FAILING in 16 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/53/
[00:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #65: STILL FAILING in 5 min 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/65/
[00:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #58: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/58/
[00:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #55: STILL FAILING in 21 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/55/
[00:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #135: STILL FAILING in 5 min 37 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/135/
[00:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #65: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/65/
[00:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #54: ABORTED in 7 min 18 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/54/
[01:10] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #55: FIXED in 29 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/55/
[01:28] <yofel> well, this was fun
[01:29] <IrcsomeBot> <tsimonq2> Oh?
[01:29] <yofel> thanks to everyone for actually making a really smooth backports upgrade. I have lots of stuff installed on my notebook and not a single error during the upgrade
[01:29] <IrcsomeBot> <tsimonq2> :D :D :D
[01:30] <yofel> but after that, as usual, I ofc. couldn't reboot because plasma essentially stops working the moment some of its libs get switched out (has been like that for years now)
[01:30] <yofel> and after I rebooted, my plasma session had no panel
[01:32] <yofel> at least, that's the only thing I ran into, still annoying. Wonder how that happened
[01:32] <yofel> hm...
[01:33] <yofel> is the stuff in backports-landing actually synced with git?
[01:33] <IrcsomeBot> <tsimonq2> Uhhhh I THINK?
[01:33] <yofel> Rejected:
[01:33] <yofel> akonadi_16.04.3-0ubuntu1~ubuntu16.04~ppa62.dsc: Version older than that in the archive. 4:16.04.3-0ubuntu1~ubuntu16.04~ppa62 <= 4:16.04.3-0ubuntu2~ubuntu16.04~ppa61
[01:33] <yofel> and I was wondering where my akonadi upload from git went
[01:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #136: FIXED in 53 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/136/
[01:34]  * yofel goes comparing package contents
[01:36] <yofel> nope, that doesn't quite match...
[01:37] <IrcsomeBot> <tsimonq2> pls thx sync
[01:37] <IrcsomeBot> <tsimonq2> ? ;)
[01:37] <yofel> I'm more worried about what else is all out-of-sync
[01:37] <yofel> and syncing is kind of annoying as I have to 3-way merge my changes from today now -.-
[01:40] <yofel> clivejo, acheronuk, we have a workflow bug somewhere ^
[01:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #66: FIXED in 59 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/66/
[01:45] <yofel> no conflicts at least
[02:00] <yofel> [02:16:03] <betzen529> I enter login credentials at login screen.  plasmashell tries to load.  desktop comes up. bottom panel tries to load.  crash.
[02:00] <yofel> I might not be the only one with that...
[02:01] <dmj_s76> It seems the Kdenlive has a missing critical dependency on 16.10.
[02:01] <dmj_s76> Kdenlive crashes on startup unless the user manually installs the qml-module-qtquick-controls package.
[02:01] <IrcsomeBot> <tsimonq2> Ok so do we have a fixable bug?
[02:01] <IrcsomeBot> <tsimonq2> Is it a config issue?
[02:01] <IrcsomeBot> <tsimonq2> What's the deal?
[02:01] <dmj_s76> Could we get an updated package in the yakkety repo that includes the dependency?
[02:01] <yofel> I think we don't know what the deal is yet
[02:02] <yofel> dmj_s76: you are not running plasma, right?
[02:02] <yofel> dmj_s76: and can you please file a bug?
[02:02] <dmj_s76> yofel: No, not running plasma.  Standard Ubuntu 16.10.
[02:02] <yofel> ok, thanks
[02:02] <dmj_s76> https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1634478
[02:02] <ubottu> Launchpad bug 1634478 in kdenlive (Ubuntu) "module "QtQuick.Controls" is not installed" [Undecided,Confirmed]
[02:02] <yofel> and thanks again
[02:03] <dmj_s76> I'm not the original filer, but this affects me and others in the office have run into it too.
[02:03] <yofel> ack. The bug is valid in any case, thanks for bringing it up
[02:03] <dmj_s76> yofel: Does plasma affect this issue?
[02:04] <yofel> dmj_s76: no, just that we have a work around in kubuntu by installing that qml module in the default installation. But it seems like it's a more general requirement..
[02:05] <dmj_s76> Yes, many of our customers use Kdenlive on vanilla Ubuntu.
[02:05] <dmj_s76> And it's always best if things just work out of the box.
[02:06] <dmj_s76> yofel: The right thing seems to be to include it as a dependency.
[02:16] <dmj_s76> yofel: thanks.  If there's an updated package I'll test on Monday.
[02:25] <IrcsomeBot> <tsimonq2> Go to bed yet yofel?
[09:48] <yofel> moin
[09:49] <acheronuk> yofel: morning
[09:50] <acheronuk> backports *should* be synced with git, unless anyone managed to do something odd with the tooling AFAIK
[09:52] <yofel> or did something by hand. Hard to say with the amount of time the packages have been waiting now
[09:52] <acheronuk> saying that, apps at least was done with earlier versions with maybe less checks, so perhaps there is any old issue there....
[09:52] <yofel> hm, why did akonadi ftbfs on armhf o.O
[09:55] <yofel> fixed akonadi pushed to backports for now, except armhf
[09:56] <acheronuk> controlinterface.h
[09:56] <acheronuk> ummm.....
[09:59] <yofel> not all architectures were enabled for -landing though, so maybe a dep is missing for that arch
[10:03] <acheronuk> maybe. at least it it done for amd64 and i386, so that covers all but anyone trying something very weird
[10:03] <acheronuk> TY :)
[10:03] <yofel> I just synchronized the architectures over all PPAs. If you turn it on, at least be consistent, otherwise stuff like this happens
[10:04] <yofel> and I disabled armel, barely anyone uses that
[10:06] <yofel> or nvm
[10:06] <acheronuk> armel, is that new on the ppas?
[10:07] <yofel> well, all non-x86 archs are fairly new on the PPAs, but armel is actually fairly old
[10:10] <acheronuk> seems so. I coulda just have sworn by default there were 5 archs you could enable, plus 2 that only LP adins could set, and armel seemed unfamiliar
[10:10] <acheronuk> but seems it is actually 6+2
[10:12] <acheronuk> ah... not built for the archive which defaults to 7 archs
[10:49] <Raspberry> hello
[10:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-nm build #43: FIXED in 17 min: http://kci.pangea.pub/job/zesty_unstable_plasma-nm/43/
[10:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #262: FIXED in 18 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/262/
[11:00] <acheronuk> Raspberry: hi. can we help?
[11:01] <blaze> o.O
[11:02]  * acheronuk shrugs
[11:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #86: STILL FAILING in 4 min 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/86/
[11:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #79: STILL FAILING in 4 min 59 sec: http://kci.pangea.pub/job/xenial_unstable_kirigami/79/
[11:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #28: STILL FAILING in 6 min 10 sec: http://kci.pangea.pub/job/zesty_unstable_kirigami/28/
[11:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #87: STILL FAILING in 3 min 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/87/
[11:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #80: STILL FAILING in 4 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_kirigami/80/
[11:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #29: STILL FAILING in 5 min 7 sec: http://kci.pangea.pub/job/zesty_unstable_kirigami/29/
[12:48] <BluesKaj> Hiyas all
[13:33] <soee_> why there is no any news about backports on kubuntu.org ?
[13:37] <acheronuk> soee_: Only speaking for myself, I've not prodded anyone to post news of the backport yet, to give us a chance to tackle the obvious bugs found by early upgraders
[13:38] <soee_> any reported so far ?
[13:40] <acheronuk> a few missing panels for some people, the akonadi fail to start, some missing non KDE things which still depended on Qt ABI 5-5-5
[13:41] <acheronuk> most accounts seem favourable, but with any big plasma update you get a minority where things go south
[13:47] <IrcsomeBot> <ovidiuflorin> I just got Plasma 5.8.3 in my updated
[13:48] <IrcsomeBot> <ovidiuflorin> you guys Rock!!!
[13:48] <IrcsomeBot> <ovidiuflorin> updates*
[13:48] <acheronuk> \o/
[13:48] <acheronuk> but I prefer it if you had 5.8.4 ?
[13:48] <acheronuk> :p
[13:50] <IrcsomeBot> <ovidiuflorin> I'd preffer 5.12, but this will do :-P
[13:50] <IrcsomeBot> <ovidiuflorin> 😜
[13:52] <IrcsomeBot> <acheronuk> (Document) https://irc-attachments.kde.org/qX3R5tl0/file_1405.png
[13:53] <IrcsomeBot> <acheronuk> as I am bored....  ^^^
[13:54] <acheronuk> that new wallpaper is slowly growing on me. hated it at first
[14:07] <BluesKaj> acheronuk, which new wallpaper?
[14:11] <acheronuk> The new plasma one for 5.9 when it's released
[14:16] <BluesKaj> acheronuk, is the 5.9 in an available ppa ?
[14:30] <soee_> acheronuk: though for me it is a bit blurry
[14:30] <soee_> maybe due to how Plasma scales and crops images - output isn't perfect :/
[14:31] <soee_> http://i.imgur.com/70Lm0ni.jpg
[14:32] <soee_> BluesKaj: it is not, it hasn't been released yet in any official form
[14:33] <BluesKaj> soee_, ok, thanks
[14:49] <IrcsomeBot> <ahoneybun> So we moved -landing to backports?
[14:53] <IrcsomeBot> <ovidiuflorin> Apparently
[15:07] <acheronuk> yep
[15:15] <soee_> https://plus.google.com/110954078302330754910/posts/H4GR6ySAK3a?sfc=true
[15:15] <soee_> one user had freeze after upgrade
[15:23]  * blaze removed "-landing" from the sources and ran "dist-upgrade", nothing's changed after that :D
[15:24] <soee_> that strange :D
[15:28] <DarinMiller> Morning/Afternoon/Evening o/
[15:30] <acheronuk> hi Darin :)
[15:30] <DarinMiller> Hi Rik :)
[15:33] <DarinMiller> a couple packaging questions:  why is kdevelop not part std apps, i.e. why is it in Staging Misc PPA and not stage kde apps?
[15:36] <DarinMiller> I noticed clive uploaded kdevelop 5.0.3 to Staging Misc for Zesty whereas staging apps ppa does not have any zesty apps yet.
[15:37] <acheronuk> 'KDE applications' is a standard set, released together and versioned the same (externally), an that have to keep to a release schedule for that set
[15:37] <acheronuk> other applications do their own thing in their own time, or don't really fit, so are release separately on their own schedule
[15:38] <acheronuk> as usual there is a bit of too and fro. this and that getting dropped or included in the main big 'KDE applications' set as things evolve
[15:39] <IrcsomeBot> <ahoneybun> I'd like to think that the KDE Apps are programs that users use daily
[15:40] <IrcsomeBot> <ahoneybun> And Misc are those that only some use
[15:40] <acheronuk> kdevelop sits on it's own at the moment due to release schedule and what it's used for
[16:00] <DarinMiller> OK harder question: the python package is not included in the Misc PPA.   There is a kdev-python package listed here: https://code.launchpad.net/~kubuntu-packagers/+git
[16:02] <DarinMiller> But I am not sure if that is the missing package.   Does anyone have time to show me how to fix the  kdevelop PPA package to include the python pkg?
[16:04] <DarinMiller> The reason I question if kdev-python is correct is that the php packages are called kdevelop-php (full kdevelop name not kdev abreviated).
[16:06] <DarinMiller> nm: the kdevelop control files lists https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdev-python
[16:07] <DarinMiller> OK, so now I am still confused.  Why is the python package absent from the kdevelop install?
[16:10] <DarinMiller> i.e.:  on zesting with Misc PPA enabled, apt list kdev* does not show the python package and nor are the python options available when kdevelop is installed.
[16:10] <DarinMiller> s/zesting/zesty
[16:24] <acheronuk> kde renamed the git repo to a shorter version so AFAIK we did the same with our packaging repo as it help make KCI and other stuff simpler if those match
[16:24] <acheronuk> the package names produced remained the same though
[16:25] <acheronuk> as far as packaging goes, clivejo was doing those, so you should prob check with him
[16:27] <DarinMiller> OK, I will check with clive.. I think he said he was out for the weekend so I will contact him next week.
[16:28] <DarinMiller> another question: I was attempting to build the kdevelop locally using  dpkg-buildpackage -us -uc
[16:30] <DarinMiller> I have not built anything that way before.  It wants a zip file for the package.  /kdevelop-python_5.0.3.orig.tar.{bz2,gz,lzma,xz}
[16:31] <DarinMiller> where do I find the tar file?  do I just tar the package I downloaded and give it that name?
[16:32] <acheronuk> you need the source tar.xz
[16:32] <acheronuk> 2 secs
[16:32] <DarinMiller> http://download.kde.org/stable/kdevelop/5.0.3/src/
[16:32] <DarinMiller> ?
[16:33] <acheronuk> probably, though it's timing out for me at the moment
[16:34] <DarinMiller> but names do not quite match.... kdevelop-python_5.0.3.orig.tar vs kdev-python-5.0.3.tar.xz
[16:35] <acheronuk> debian packaging uses it's own naming format for source tarballs, so yes, quite often you have to rename them. or create a symlink of the correct name
[16:38] <DarinMiller> I tried downloading, renaming and rebuilding but then the rebuild crashes and burns for other other issues.  Now that I know renaming is necessary I can continue solving the other crash and burn issues...
[18:33] <IrcsomeBot> <CliffordTheBigRedDoggie> Darin I uploaded those to the KDevelop project PPA
[19:14] <clivejo> anyone tested the newly created ISO's?
[19:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #88: STILL FAILING in 4 min 42 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/88/
[19:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #81: STILL FAILING in 5 min 1 sec: http://kci.pangea.pub/job/xenial_unstable_kirigami/81/
[19:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #30: STILL FAILING in 5 min 11 sec: http://kci.pangea.pub/job/zesty_unstable_kirigami/30/
[19:21]  * acheronuk glares at kirigami
[19:21]  * ahoneybun glares at kdenlive
[19:24] <acheronuk> clivejo: not yet, sorry
[19:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #82: STILL FAILING in 3 min 57 sec: http://kci.pangea.pub/job/xenial_unstable_kirigami/82/
[19:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #89: STILL FAILING in 4 min 40 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/89/
[19:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #31: STILL FAILING in 5 min 8 sec: http://kci.pangea.pub/job/zesty_unstable_kirigami/31/
[19:26] <acheronuk> yes yes, I know you will fail kirigami. I just want to see the proper reason!
[19:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #90: STILL FAILING in 3 min 40 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/90/
[19:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #83: STILL FAILING in 3 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kirigami/83/
[19:30] <clivejo> whats wrong with Kdenlive?
[19:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #32: STILL FAILING in 5 min 9 sec: http://kci.pangea.pub/job/zesty_unstable_kirigami/32/
[19:32] <acheronuk> hmpth.....
[19:32] <acheronuk> FAIL!  : qmltestrunner::tst_pagerow::compile() module "QtQuick.Controls" version 2.1 is not installed
[19:32] <clivejo> well install it!
[19:32] <acheronuk> and as far as I can see, QtQuick.Controls 2.1 is in Qt 5.8
[19:34]  * acheronuk hands baton to clivejo
[19:34] <acheronuk> you 'install' it :P
[19:34] <clivejo> qt5-qtquickcontrols2-devel-5.7.0-1.fc25.i686 RPM
[19:34] <clivejo> it was looking for Qt5QuickControls2Config.cmake
[19:34] <acheronuk> not any more
[19:35] <clivejo> I went looking for it, but our unstable version seems to been copied from somewhere
[19:35] <clivejo> and couldnt find a buildlog
[19:36] <acheronuk> see: http://blog.qt.io/blog/2016/10/06/qt-quick-controls-2-1-and-beyond/
[19:36] <acheronuk> clivejo: did you read the email I CC'd to you?
[19:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #91: STILL FAILING in 4 min 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/91/
[19:38] <clivejo> https://launchpad.net/~kubuntu-ci/+archive/ubuntu/stage/+build/11246146
[19:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #84: STILL FAILING in 5 min 1 sec: http://kci.pangea.pub/job/xenial_unstable_kirigami/84/
[19:38] <acheronuk> how does that help?
[19:39] <clivejo> qtquickcontrols2-5-dev
[19:39] <clivejo> -rw-r--r-- root/root      6870 2016-11-23 13:01 ./usr/lib/x86_64-linux-gnu/cmake/Qt5QuickControls2/Qt5QuickControls2Config.cmake
[19:39] <acheronuk> yes, and that is installed as a build dep
[19:40] <acheronuk> I did that here: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kirigami/commit/?id=d103b50fbe4bcbdcb601681290c784dab0366865
[19:40] <acheronuk> that lets kirigami build, but the tests fail
[19:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #33: STILL FAILING in 5 min 8 sec: http://kci.pangea.pub/job/zesty_unstable_kirigami/33/
[19:41] <acheronuk> as they seem to want a version of qtquickcontrols2 that doesn't exist until Qt 5.8
[19:42] <acheronuk> but the rest of kirigami only requires 2.0, which I was able to give it
[19:42] <clivejo> I see
[19:43] <clivejo> can you add git to build deps
[19:43] <clivejo> only an optional
[19:44] <acheronuk> maybe. let me test. I tried to at git as a dep to somethign a while back and it failed. not sure if that was kirigami or not
[19:45] <clivejo> have you got it locally?
[19:45] <acheronuk> yes
[19:45] <clivejo> what happens if you downgrade the autotest qtquickcontrols to 2?
[19:46] <acheronuk> that is also something I was considering trying, but I emailed upstream 1st
[19:47] <acheronuk> I would guess it's a mistake, but you never know
[19:48] <acheronuk> seems nonsensical to me to have the build requires set to v2.0 but the tests need v2.1
[19:52] <IrcsomeBot> <tsimonq2> Hai guys
[19:52] <IrcsomeBot> <tsimonq2> How goes it?
[19:53] <IrcsomeBot> <tsimonq2> What did you break clivejo? :O
[19:57] <clivejo> broke my eye
[19:58] <IrcsomeBot> <tsimonq2> :O
[19:58] <IrcsomeBot> <tsimonq2> Why?
[19:59] <clivejo> got grit/dirt into it yesterday
[20:01] <IrcsomeBot> <tsimonq2> Max!
[20:13] <acheronuk> hmmm... maybe these tests are not meant to be run at build time?
[20:21] <acheronuk> dammit. yes they are. as now I get further I see they fail for the kirigami modules not being installed, but that won't happen until the thing is built :P
[20:22] <acheronuk> *yes they are not build time
[20:26] <clivejo> DarinMiller: https://launchpad.net/~kdevelop/+archive/ubuntu/release/
[20:27] <DarinMiller> Hi Clivejo!  
[20:28] <clivejo> hello
[20:29] <sintre> hi all devs
[20:29] <sintre> so is plsma 5.8 stable and released yet for 16.04 :)
[20:37] <acheronuk> sintre: yes in backports, and as stable as we can reasonably make it with the testing we have been able to do
[20:38] <sintre> so will that auto update running update command?
[20:38] <sintre> or can you pls give me command line to install newest
[20:38] <acheronuk> as with any release, there will undoubted be things that have bugs for some people. an some hardware that will just not like it
[20:39] <sintre> i ubnderstand , just anxious to see if new plsma fixed an okld bug :)
[20:39] <acheronuk> sintre: see the adding this ppa instructions here: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports
[20:39] <acheronuk> then you do 'sudo apt-get dist-upgrade"
[20:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #34: STILL FAILING in 3 min 44 sec: http://kci.pangea.pub/job/zesty_unstable_kirigami/34/
[20:41] <sintre> i got the back ports already , or i think i do
[20:42] <DarinMiller> clivejo: the +archive/ubuntu/release ppa works as expected.  So it that the source for Kubuntu?  If not how/where does the Kubuntu specific version land in the package set?
[20:43] <blaze> sintre: how can you be so uncertain? :D
[20:43] <sintre> well i did install them
[20:43] <sintre> but maybe secret new backports lol
[20:45] <clivejo> DarinMiller: no, just a team we setup at Akacademy
[20:47] <sintre> 531 packages can be upgraded. Run 'apt list --upgradable' to see them.
[20:47] <sintre> na@na:~$ 
[20:47] <sintre> 531 packages can be upgraded. Run 'apt list --upgradable'
[20:47] <sintre> this might take awghihle
[20:48] <sintre> i assume new plsma might be in here?
[20:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #35: STILL FAILING in 3 min 43 sec: http://kci.pangea.pub/job/zesty_unstable_kirigami/35/
[20:49] <blaze> plasma, apps and frameworks
[20:49] <acheronuk> clivejo: you know how to write rules for autotests?
[20:50] <clivejo> acheronuk: nope, still trying to learn that
[20:51] <acheronuk> clivejo: ok. we can both learn then, if we can pick someone's brain
[20:51] <clivejo> I'd probably disable them 
[20:51] <DarinMiller> clivejo: so how do we add kdvelep to KDE packages. Do we add the kdev soucres from lp soucre to kci  (i.e.  http://download.kde.org/stable/kdevelop/5.0.3/src/)
[20:52] <clivejo> They are in KCI
[20:53] <DarinMiller> How to they arrive in landing or misc ppa.  Is that a yaml or json file config somewhere?
[20:53] <clivejo> again, we added those after Akamedy
[20:53] <clivejo> I put them into misc staging
[20:53] <clivejo> well for zesty
[20:53] <acheronuk> clivejo: well, I want to know how to make them work in ubuntu's autopackagetest infra, so not completely disable them
[20:54] <clivejo> acheronuk: true, Id like that too, but cant't find anyone to explain it to me
[20:54] <DarinMiller> Yes, but the detail I do not understand.  Pull the src's to your local PC, compile and upload to the ppa?
[20:55] <clivejo> DarinMiller: you know about the KA tools?
[20:55] <acheronuk> clivejo: well, the kirigami ones are clearly not build time ones, so I disabled them for that. and for KCI at least, that will be fine
[20:55] <DarinMiller> clivejo: I know how to clone them.  Do they have documentation that explain the process?  
[20:56]  * DarinMiller Looking at KA tools git clone for docs....
[20:56] <clivejo> README has brief overview
[20:56] <acheronuk> so maybe a little excercise to work out how to write the rules for the autopackagetest ones to run them
[20:56] <clivejo> README.ng maybe
[20:57] <clivejo> These are the kdevelop jobs on KCI - http://kci.pangea.pub/search/?q=kdev
[21:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #92: NOW UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/92/
[21:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #85: NOW UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/85/
[21:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #36: NOW UNSTABLE in 11 min: http://kci.pangea.pub/job/zesty_unstable_kirigami/36/
[21:01] <acheronuk> well, at least it built ^^^
[21:05] <sintre> well survived that upgrade ,
[21:06] <sintre> had to do a forced shutdown afterwards, but seems plsama is stable so far :)
[21:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop-pg-qt build #84: FIXED in 7 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_kdevelop-pg-qt/84/
[21:07] <clivejo> what version of plasma have you go?
[21:07] <clivejo> got?
[21:07] <sintre> 5.8.4
[21:07] <sintre> after upgrade
[21:07] <clivejo> good good
[21:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #78: FIXED in 7 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/78/
[21:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #37: FIXED in 10 min: http://kci.pangea.pub/job/zesty_unstable_kirigami/37/
[21:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #86: FIXED in 11 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/86/
[21:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #93: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/93/
[21:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #348: STILL FAILING in 2 min 37 sec: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/348/
[21:40] <clivejo> acheronuk: yippeeee
[21:40] <sintre> well seem these real time updates here , did the upgrade and kirigami made itself a menu saing lost and found
[21:40] <sintre> what does this prog do lol
[21:41] <clivejo> sintre: ??
[21:41] <acheronuk> clivejo: it wants git to make a clone of breeze icons from kde git. it fails to do the clone, but doesn't seem to matter!
[21:41] <sintre> kirigami
[21:41] <clivejo> krigami is a framework
[21:41] <sintre> i have a new menu in app launcher menu , called "lost and found" and in there is that program
[21:42] <sintre> wonder why it ended up in lost and found hehe
[21:43] <clivejo> that is strange
[21:44] <sintre> something called kirigami gallery , seems to have option for stuff
[21:45] <sintre> says top right widegt gallery
[21:45] <sintre> i eman top left
[21:46] <clivejo> oh thats the example of what the framework does
[21:47] <sintre> ihh so its not meant to be moddified?
[21:47] <sintre> no wonder it aint changing anything lol
[21:47] <clivejo> just samples of what it can do
[21:48] <clivejo> look at the new discover
[21:48] <IrcsomeBot> <ahoneybun> I wonder if that has to do with kdevelop
[21:48] <sintre> lol k , was wondering why didn't have any options and a apply button there for a minute
[21:48] <IrcsomeBot> <ahoneybun> Or Qt Creator more likely
[21:49] <sintre> clivejo > look nice ,
[21:50] <sintre> but like last one when i hit installed doesn't show anything
[21:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #349: STILL FAILING in 5 min 40 sec: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/349/
[21:53] <sintre> user error  i think
[21:53] <sintre> not used to big descrptoions
[21:53] <sintre> descriptions
[21:53] <sintre> so yea its showing installed stuff
[21:54] <sintre> alos different icons than used to
[22:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #72: UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_discover/72/
[22:40] <rbetzen> yofel: glad it worked for you.  unfortunately it totally hosed my system.  reinstalling everyting.   I'm not upset, though.  Just a little feedback.  Not quite sure what happened.
[22:41] <yofel> rbetzen: sorry, what was the context again?
[22:41] <rbetzen> oh.  your backports upgrade.  glad it worked for you. ;)
[22:42] <yofel> uhm, now that really shouldn't happen. Do you still have some upgrade logs?
[22:43] <rbetzen> no.  had to get the system back up in a hurry.  reformatted and reinstalled.  although even after that I think i still have a couple of broken packages.  I"ll poke around.  
[22:44] <rbetzen> It happened late at night, so I wasn't particularly bright eyed when it happened either.  Two other systems worked flawlessly. 
[22:44] <valorie> rbetzen: apt has a fix option: sudo apt install -f
[22:46] <rbetzen> valorie:  I tried that, but for some reason I had quite a few broken packages by the time the upgrade completed.  I suspect it wasnt Kubuntu's fault.  I think it was some kind of configuration I may have done in the past. Possibly trying to get a newer version of kde coneect.
[22:48] <rbetzen> I have another system with identical hardware and it had no problems. 
[22:48] <valorie> !ppapurge
[22:48] <ubottu> To disable a PPA from your sources and revert your packages back to default Ubuntu packages, install ppa-purge and use the command: « sudo ppa-purge ppa:<repository-name>/<subdirectory> » – For more information, see http://www.webupd8.org/2009/12/remove-ppa-repositories-via-command.html
[22:48] <valorie> might be a good idea to purge any non-standard PPAs
[22:48] <valorie> but this is off-topic here -- let's move to #kubuntu
[22:49] <rbetzen> Probably.  Lesson learned.  I didn't even think of ppa purge. duh.  I was pretty sleepy last night. ;)
[22:52] <rbetzen> No problem.  No further help needed at the moment.  Just wanted to tell yofel and everyone else congrats on the upgrade and Kubuntu is looking really slick on my other systems.  Now back to rebuilding the other one... :p
[23:25] <IrcsomeBot> <marcinsagol> o/
[23:25] <clivejo> \o
[23:26] <IrcsomeBot> <marcinsagol> rbatzen but you had packages conflicts or upgrade was fine?