[00:00] <ali1234> reporting it
[00:04] <ali1234> https://launchpadlibrarian.net/148989210/gedit-no-icon.png
[00:05] <penguin42> yeh here (on kubuntu) I'm getting the X default one
[00:05] <penguin42> talking of gnome apps; I really don't like what they've done to evince and made the menu-on-the-button thing
[00:09] <ali1234> menu on the button?
[00:09] <penguin42> ali1234: If you start evince what do you see?
[00:09] <ali1234> i don't think i have it installed
[00:09] <ali1234> oh yeah i do. the cog? rhythmbox is like that now too
[00:10] <ali1234> i don't really like it much, but it's miles better than global menus
[00:10] <penguin42> hmm
[00:11] <ali1234> https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1219120 if you could confirm :)
[00:13] <ali1234> i bet this bug isn't even visible in unity/gnome shell
[00:14] <penguin42> done
[00:14] <ali1234> thanks
[00:36] <ali1234> i just installed kazam to record a screencast showing a bug, and found a bug in kazam
[00:38] <penguin42> yeh that's the way it goes
[08:47] <brobostigon> good morning everyone,
[08:49] <MartijnVdS> \o
[08:51] <brobostigon> morning MartijnVdS
[08:56] <AlanBell> morning all
[08:56] <MartijnVdS> \o
[08:56] <AlanBell> happy saturday to you
[08:56] <AlanBell> I just had chiken korma for breakfast and it is nice and sunny
[08:57] <MartijnVdS> it's a bit foggy here
[08:57] <MartijnVdS> still
[08:57] <brobostigon> morning AlanBell
[08:58]  * brobostigon contemplates a new blog post about various things.
[09:06] <Myrtti> I have my lovely microwave poached eggs and tomato on toast and a whole teapot of Yorkshire just for me
[09:07] <Myrtti> nevermind it's noon, I like eggs on toast.
[09:09] <AlanBell> eggs are great :)
[09:10] <AlanBell> http://hencam.libertus.co.uk/video loadsa chickens
[09:18] <Myrtti> THERES A CHICKEN LAYING AN EGG
[09:19] <Myrtti> DOOEEET
[09:19] <Myrtti> she's twerking :-D
[09:19] <MartijnVdS> ಠ_ಠ
[09:25] <AlanBell> heh
[09:26] <AlanBell> I need to go clean out the coop, but I will wait for that egg
[09:28] <bigcalm> Good morning peeps :)
[09:38] <AlanBell> EGGG!!!!
[09:39] <bigcalm> AlanBell: have you just laid one?
[09:39] <AlanBell> yeah http://hencam.libertus.co.uk/
[09:41] <bigcalm> \\\\\\
[09:41] <bigcalm> ||||||
[09:41] <bigcalm> I have my \| key back!!!
[09:42] <bigcalm> Was using a _very_ cheap USB->PS/2 converter which didn't know about the \| key (as well as not registering I was hitting any key at times)
[09:43] <bigcalm> Spent proper money with proper p&p to get a better built converter and it works nicely :D
[09:43] <bigcalm> TE UIC RWN  JUS VER TE LAY DG
[09:43] <bigcalm> No change on the double shift test though
[09:47] <popey> morning
[09:47]  * popey returns from the post office having shipped out all his ebay items
[09:47] <MartijnVdS> \o/
[09:48] <bigcalm> Morning
[12:43]  * popey hugs neuro
[13:58] <MartijnVdS> Prison Architect is fun :)
[14:22] <SuperEngineer> MartijnVdS: can you recommend a version [enn thinking of geting this for a while].. will the bog standard £11.99 Steam version be ok? [only occasional use]
[14:23] <SuperEngineer> enn? what's an enn? sub I've been ;)
[14:26] <dutchie> SuperEngineer: why it not be ok?
[14:28] <SuperEngineer> dutchie: dunno - that's why i was asking ;)
[14:28] <dutchie> it should be fine
[14:29] <dutchie> unless you want the soundtrack or your name in the game
[14:29] <SuperEngineer> [there'sseveral versions on Steam.. from bog standard to super duper - they seem to be, well, unnecessary
[14:30] <dutchie> nice to have the soundtrack sometimes
[14:30] <dutchie> and it's more money to the indie dev
[14:30] <SuperEngineer> nope - don't need name [don't want name in game] &... is the soundtrack any good then?
[14:32] <SuperEngineer> [would prefer a "preview soundrack" option ;)
[15:07] <dutchie>  i dunno about soundtrack
[15:17] <MartijnVdS> SuperEngineer: yeah, the standard standard cheap version is fine
[15:17] <MartijnVdS> SuperEngineer: it's still alpha, so sometimes it bugs a bit
[15:24] <SuperEngineer> MartijnVdS: cool - I'll put up with that - purchasing now...
[15:41] <popey> Afternoon all
[15:43] <brobostigon> afternoonings popey
[17:07] <penguin42> popey: Are you on chromium 28 ?
[17:09] <popey> penguin42: Version 28.0.1500.71 Ubuntu 13.10 (28.0.1500.71-0ubuntu3)
[17:10] <penguin42> popey: Same here - so what are you finding isn't working on ebay; just trying it here and it looks fine
[17:22] <bigcalm> Good afternoon peeps :)
[17:23] <popey> try and create an auction, it complains when you try and list that it should have paypal as a valid payment option
[17:23] <popey> there's some js on the page which breaks
[17:23] <penguin42> oh, not tried to create one
[17:38]  * popey tries to resist buying a pc-engine off ebay
[17:38] <popey> and a dreamcast
[17:39] <Azelphur> I have a dream(cast) :P
[17:39]  * bigcalm is lost in a maze of c++ corridors, all alike
[17:39] <Azelphur> it died though :(
[17:39] <penguin42> bigcalm: nail a baseclass to the floor and follow the string
[17:39] <bigcalm> Heh
[17:40] <bigcalm> I know nothing about C++ yet I'm trying to write some as a plug-in for QML. Really out of my comfort zone
[17:40] <penguin42> well, I know no QML but want to learn, but I know C++ - so feel free to ask
[17:40] <DJones> Martin Luthor King had a dream (is that anywhere near close?)
[17:41] <bigcalm> penguin42: very kind]
[17:48] <popey> for czajkowski & AlanBell https://www.youtube.com/watch?v=DMydVdwmuws
[17:49] <bigcalm> wow
[17:50] <bigcalm> The comments are special
[17:50] <popey> ya
[17:50] <MartijnVdS> welkcome to youtube
[17:55] <bigcalm> Welp, I'm not getting errors, but I'm also not getting a compiled object
[18:01] <SuperEngineer> weeeeeeeee Dr. Who!!
[18:03] <penguin42> bigcalm: ?
[18:03] <bigcalm> Where?
[18:03] <bigcalm> penguin42: ?
[18:03] <bigcalm> Oh
[18:03] <bigcalm> qmake
[18:04] <penguin42> hmm don't know qmake
[18:04] <penguin42> it's got to be similar to gmake right - just the tail on the bottom ?
[18:04] <bigcalm> I _think_ that things might be moving over to gcc. Would be nice
[18:05] <SuperEngineer> bigcalm: if that was re DW... BBC3
[18:05] <SuperEngineer> [if not - please ignore
[18:05] <bigcalm> SuperEngineer: it was and oh
[18:06] <SuperEngineer> :)
[18:18] <bigcalm> Silly me
[18:18] <bigcalm> Not reading enough
[18:19] <bigcalm> Have to run qmake and then make
[18:19] <bigcalm> Getting errors now :)
[18:25] <bigcalm> I'm trying to build this as a plugin http://askubuntu.com/questions/308968/how-can-i-run-a-command-from-a-qml-script
[18:25] <bigcalm> By following bits of this http://qt-project.org/doc/qt-4.8/gettingstartedqml.html#extending-qml-using-qt-c
[18:26] <bigcalm> Really confused :)
[18:33] <DJones> Has anybody looked at this 10TB of free cloud storage? http://thenextweb.com/asia/2013/08/30/forget-1tb-chinas-tencent-is-giving-away-10tb-worth-of-free-cloud-storage/
[18:33] <directhex> let's give all our data to the chinese!
[18:37] <penguin42> DJones: So that's where the NSA store it....
[18:37] <DJones> NSA/China/Google Probably not much difference anyway
[19:02]  * penguin42 wonders what drivers Ouya use to drive their off chip graphics card
[19:08] <directhex> off chip?
[19:09] <penguin42> http://en.wikipedia.org/wiki/Ouya says it has a GeForce
[19:09] <ali1234> isn't it tegra?
[19:09] <directhex> it's just tegra3
[19:09] <penguin42> ah ok
[19:10] <directhex> although nvidia does ship arm geforce drivers
[19:10] <popey> its very easy to run out of space on ouya
[19:10] <penguin42> directhex: Interesting
[19:11] <penguin42> popey: Oh I was just thinking the ebay prices weren't bad for a quad core A9
[19:11] <directhex> of course, only 2 motherboards exist right now with an ARM chip and a PCIe slot
[19:11] <directhex> but you can get the driver for those, damnit!
[19:11] <penguin42> directhex: Which 2 are you thinking of?
[19:12] <directhex> http://shop.seco.com/gpudevkit/gpudevkit-detail.html
[19:12] <penguin42> directhex: I think there's at least; the ARM dev boards (cost a fortune), the boards from Kontron (do they really exist? has anyone seen one?) and the globalscale mirabox
[19:14] <penguin42> hmm hadn't seen that one
[19:14] <directhex> er, where's the pcie slot on a mirabox?
[19:14] <penguin42> directhex: http://www.globalscaletechnologies.com/p-58-mirabox-development-kit.aspx  is kind of nice but only has mini-pcie
[19:24]  * bigcalm flops in on his laptop
[19:24] <MartijnVdS> howdy
[19:25] <bigcalm> Hullo
[19:38] <penguin42> popey: How many kickstarter projects have you funded now?
[19:38] <bigcalm> penguin42: all of them
[19:38] <penguin42> bigcalm: That's the conclusion I was coming to
[19:39] <penguin42> bigcalm: Do you think we should start a 'Get Popey to give us some money' project
[19:40] <bigcalm> Heh, do we count as throw away toys?
[19:40] <penguin42> bigcalm: Maybe he won't even notice by the time he's said yes
[19:41]  * MartijnVdS is still waiting for a shipping notification of Story War :(
[20:03] <mungbean_> penguin42 only 20.. http://www.kickstarter.com/profile/popey
[20:05] <penguin42> ah I didn't realise you could spy on people like that
[20:05] <popey> bit of a theme there
[20:06] <popey> only one that failed (got cancelled)
[20:06] <popey> i love those socks
[20:06] <penguin42> haha
[20:09] <popey> ooh http://www.kickstarter.com/projects/124039987/the-ridge-wallet-20 has doubled in very short period
[20:21] <mungbean_> when everybody was using that alternative android site before play got good, i spied on everybody to see what apps they had installed
[20:21] <mungbean_> can't remember the name of the site now
[20:22] <mungbean_> UK shipping fees make kickstarters suck for my budget
[20:23] <mungbean_> appbrain
[20:23] <mungbean_> sorry popey...http://es.appbrain.com/user/popey/apps-on-the-phone?o=40
[20:27] <mungbean_> man, zinio sucks for decent magazines
[20:44] <shauno> it also sucks for customer service :/
[20:45] <shauno> they're on my "not with a bargepole" list
[21:42] <popey> mungbean_: eh?
[21:42] <popey> that site is completely wrong
[21:43] <popey> so old
[22:26]  * penguin42 grumbles as I get outbid
[22:27] <daftykins> D:


[02:22] <jiffe> so if I want to still use my router's dhcp server for the desktops on my network I will have to segment my network and put maas machines on a different network from the desktops?
[09:17] <mup> Bug #1633822 opened: Device discovery ignores reverse DNS <MAAS:New> <https://launchpad.net/bugs/1633822>
[09:35] <mup> Bug #1633822 changed: Device discovery ignores reverse DNS <MAAS:New> <https://launchpad.net/bugs/1633822>
[09:41] <mup> Bug #1633822 opened: Device discovery ignores reverse DNS <MAAS:New> <https://launchpad.net/bugs/1633822>
[21:31] <smgoller> hey all, any ideas on troubleshooting remote virsh management? I've followed the instructions on the maas website for setting up ssh keys for a user and such, and virsh -c <my host> list --all works fine. however maas still says there's a problem logging in. any ideas?
[21:57] <pmatulis> smgoller, in what way does maas report a problem logging in?
[21:57] <smgoller> pmatulis: Failed to login to virsh console.
[21:57] <smgoller> that is via the gui
[21:58] <smgoller> no other interesting information seems to be in the logs that I can find
[22:20] <pmatulis> smgoller, so you became the 'maas' user and this works: virsh -c qemu+ssh://<user>@<kvm host>/system list --all ?
[22:20] <pmatulis> smgoller, but the web UI has a problem?
[22:21] <smgoller> yup
[22:22] <smgoller> pmatulis, that is exactly correct
[22:22] <smgoller> let me try something else.
[22:22] <pmatulis> smgoller, so the power check for a node must also not be working. i would 'tail -f' /var/log/auth.log on the kvm host and try a power check from the UI. see that pops up there
[22:22] <smgoller> ok
[22:22] <pmatulis> s/that/what
[22:24] <mup> Bug #1633247 changed: Used fallback datasource. PXE boot fail <MAAS:Invalid by charlienz> <https://launchpad.net/bugs/1633247>
[22:24] <smgoller> hm. it doesn't actually try to connect. I'm going to delete the node and re-add it.
[22:25] <pmatulis> smgoller, maybe you didn't configure the BMC correctly
[22:28] <smgoller> weird. So I copied the URL from the one not working, deleted the machine, then used the 'add chassis' with the virsh power driver and information, found it just fine

[22:28] <smgoller> chicken and egg problem maybe? Originally I had booted the VM to let maas discover it, then set the power type afterwards
[22:33] <mup> Bug #1633247 opened: Used fallback datasource. PXE boot fail <MAAS:Invalid by charlienz> <https://launchpad.net/bugs/1633247>
[22:36] <mup> Bug #1633247 changed: Used fallback datasource. PXE boot fail <MAAS:Invalid by charlienz> <https://launchpad.net/bugs/1633247>


[11:14] <s300> Quassel is rock
 @S300 yes, it is.
 It works out of the box since the last time i used to use pidgin for the irc (re @lubuntu_bot: (irc) <s300> Quassel is rock)


[12:00] <grvrulz> Hi everyone!! I'm here for the UTC 12:00 Membership Board meeting.
[12:12] <grvrulz> Looks like nobody is coming.
[12:17] <grvrulz> Looks like this is a bad time of day for most of the people. I'll come back for the next meeting.
[12:20] <Kilos> ai! missed him


[01:20] <olly> kieppie: I'd guess canonical probably hold any trademarks which might be relevant
[03:36] <ajmitch> morning
[04:47] <olly> "morning"
[04:47] <olly> (I'm in California)
[04:49] <ajmitch> you just couldn't stand any more talk of rugby?
[04:49] <olly> indeed
[04:50] <olly> though the cabin crew kept us updated on the france/australia match during the flight
[19:34] <ajmitch> morning
[19:35] <Atamira> morning
[19:36] <Atamira> tho its a public holiday
[19:36] <Atamira> so..good luck with anyone else piping up
[19:39] <ajmitch> I suppose a few people may have been up late last night too
[19:40] <stuartyeates> the ABs winning is going to make it harder to change the government...
[19:40] <Atamira> tell me about it
[19:40] <Atamira> police comms were run off their feet around 2am this morning
[19:41] <stuartyeates> Atamira: the expected drop in domestic violence didn't happen?
[19:41] <Atamira> not sure about the domestic violence thing. but certainly alot of parties
[19:41] <Atamira> or maybe it was just packed in auckland cbd last night
[19:41] <Atamira> everyone watching the finals on the big screen
[19:42] <ajmitch> it was noisy enough in dunedin last night, made it a little hard to sleep
[19:43] <ajmitch> imagine how it would have looked, john key handing over the world cup to the french
[19:43] <Atamira> lol
[19:43] <ajmitch> his approval ratings would have dropped to single figures :)
[19:43] <Atamira> did you see the fumbled hand shake between keys and whats his name...
[19:43] <Atamira> richie maccaw
[19:48] <ajmitch> yes, a bit embarassing :)
[20:56] <chilts> morning
[20:57]  * chilts missed the fumbled handshake


[00:09] <jimbaker> hazmat, +1 on that branch
[00:09] <jimbaker> have a good weekend!
[00:10] <hazmat> jimbaker, cool, it works well in practice.. i've been hibernating and rebooting with local envs.
[00:10] <hazmat> jimbaker, cheers you too
[00:11] <hazmat> although i'm realizing that the ephemeral sequence coordination patterns begs for a notification of expiration, and that the sequence ephs shouldn't be tracked.. maybe latter


[00:01] <clivejo> something strange going on
[00:01] <valorie> I can access that URL
[00:01] <wxl> now it's past 00:00 so have fun
[00:01] <valorie> most recent access 2 hours ago by clive
[00:01] <wxl> you can `mtr` the FQDN
[00:05] <wxl> 1604 < foli:#ubuntu-devel> The firewall maintenance is done now, all should be back.
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #755: FIXED in 7 min 10 sec: http://kci.pangea.pub/job/mgmt_merger/755/
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #739: FIXED in 7 min 13 sec: http://kci.pangea.pub/job/mgmt_progenitor/739/
[00:21] <mamarley> Hah, looks like the build farm is all jammed up again…
[00:24] <clivejo> mamarley: yup :(
[00:24] <clivejo> even uploads
[00:25] <mamarley> Yeah, that was what made me notice.  It took 20 minutes to acknowledge my automatic tvheadend nightly upload.
[00:25] <valorie> good thing they did maintainence!
[00:26] <valorie> wow, I can't spell
[00:41] <clivejo> why does my laptop screen always dim when it locks
[00:42] <valorie> power saving perhaps?
[00:43] <clivejo> Ive told it not to
[00:43] <valorie> gosh, anybody wanna help friti in #kubuntu ?
[00:45]  * mamarley kicks LP
[01:25] <DarinMiller> Hey all   o/
 Hey o/
 \o
[02:02]  * DarinMiller arrives on-line and everyone goes to sleep (or leaves).
[02:43] <[Relic]> I bet they just go out to the bar
[02:47] <DarinMiller> [Relic]: :)
[03:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #105: STILL FAILING in 3 hr 2 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/105/
[03:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #67: STILL FAILING in 3 hr 3 min: http://kci.pangea.pub/job/xenial_unstable_marble/67/
[03:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #7: STILL UNSTABLE in 3 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/7/
[03:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #9: STILL UNSTABLE in 3 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_kdb/9/
[03:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kproperty build #5: STILL FAILING in 3 hr 8 min: http://kci.pangea.pub/job/yakkety_unstable_kproperty/5/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kate build #241: STILL FAILING in 3 hr 9 min: http://kci.pangea.pub/job/xenial_unstable_kate/241/
[03:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #37: STILL UNSTABLE in 3 hr 29 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/37/
[03:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #36: STILL UNSTABLE in 3 hr 30 min: http://kci.pangea.pub/job/zesty_unstable_kopete/36/
[03:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #111: STILL UNSTABLE in 3 hr 30 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/111/
[03:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #21: STILL FAILING in 3 hr 30 min: http://kci.pangea.pub/job/xenial_unstable_trojita/21/
[03:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #9: STILL UNSTABLE in 3 hr 30 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/9/
[03:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #16: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/16/
[03:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #112: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/112/
[03:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #48: FAILURE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/48/
[03:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kfind build #18: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/yakkety_unstable_kfind/18/
[03:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kate build #155: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kate/155/
[04:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #13: FAILURE in 4 hr 3 min: http://kci.pangea.pub/job/yakkety_unstable_krita/13/
[04:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #15: FAILURE in 4 hr 3 min: http://kci.pangea.pub/job/xenial_unstable_krita/15/
[04:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #135: STILL UNSTABLE in 57 min: http://kci.pangea.pub/job/xenial_unstable_kopete/135/
[04:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #137: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/137/
[04:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #38: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/38/
[04:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #184: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/184/
[04:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #77: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/77/
[04:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #43: FAILURE in 19 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/43/
[04:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #26: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_kirigami/26/
[04:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #52: STILL FAILING in 25 min: http://kci.pangea.pub/job/zesty_unstable_marble/52/
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_print-manager build #217: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_print-manager/217/
[04:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen build #40: FAILURE in 24 min: http://kci.pangea.pub/job/zesty_unstable_oxygen/40/
[04:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #106: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/106/
[04:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kate build #38: FAILURE in 24 min: http://kci.pangea.pub/job/zesty_unstable_kate/38/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #68: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_marble/68/
[04:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #75: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_marble/75/
[04:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #84: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/84/
[04:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konqueror build #33: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_konqueror/33/
[04:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #20: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_trojita/20/
[04:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kate build #242: STILL FAILING in 26 min: http://kci.pangea.pub/job/xenial_unstable_kate/242/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #9: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kreport/9/
[04:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kproperty build #6: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_kproperty/6/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kfind build #6: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kfind/6/
[04:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #38: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_kalzium/38/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #157: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/157/
[04:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #17: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/17/
[05:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #41: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/zesty_unstable_cantor/41/
[05:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #49: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/49/
[05:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #75: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/75/
[05:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kfind build #24: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/zesty_unstable_kfind/24/
[05:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #113: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/113/
[05:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kate build #156: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kate/156/
[05:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #53: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_marble/53/
[05:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #44: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/44/
[05:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #78: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/78/
[05:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #85: STILL FAILING in 8 min 20 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/85/
[05:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen build #41: STILL FAILING in 14 min: http://kci.pangea.pub/job/zesty_unstable_oxygen/41/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #317: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/xenial_unstable_kstars/317/
[05:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #184: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/184/
[05:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konqueror build #23: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/yakkety_unstable_konqueror/23/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #243: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_cantor/243/
[05:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #27: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_kirigami/27/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #132: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kalzium/132/
[05:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #52: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/52/
[05:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kate build #39: STILL FAILING in 18 min: http://kci.pangea.pub/job/zesty_unstable_kate/39/
[05:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #71: FAILURE in 6 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_discover/71/
[05:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #76: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_marble/76/
[05:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #87: FAILURE in 6 min 59 sec: http://kci.pangea.pub/job/xenial_unstable_discover/87/
[05:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #232: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/232/
[05:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #33: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/33/
[05:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #69: FAILURE in 8 min 13 sec: http://kci.pangea.pub/job/zesty_unstable_discover/69/
[05:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #45: STILL UNSTABLE in 1 hr 4 min: http://kci.pangea.pub/job/zesty_unstable_kstars/45/
[05:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kexi build #17: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_kexi/17/
[05:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #22: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_trojita/22/
[05:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #53: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/53/
[05:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #88: STILL FAILING in 18 min: http://kci.pangea.pub/job/xenial_unstable_discover/88/
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #18: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/18/
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #72: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_discover/72/
[05:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #70: STILL FAILING in 19 min: http://kci.pangea.pub/job/zesty_unstable_discover/70/
[05:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #37: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/37/
[05:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #86: STILL FAILING in 53 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/86/
[06:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #245: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/245/
[06:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #62: STILL FAILING in 4 min 12 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/62/
[06:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #28: STILL FAILING in 5 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/28/
[06:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #14: NOW UNSTABLE in 1 hr 18 min: http://kci.pangea.pub/job/yakkety_unstable_krita/14/
[06:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #132: STILL FAILING in 2 min 41 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/132/
[06:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #63: STILL FAILING in 4 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/63/
[06:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #29: STILL FAILING in 4 min 41 sec: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/29/
[06:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #133: STILL FAILING in 3 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/133/
[06:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #51: STILL FAILING in 3 min 54 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/51/
[06:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #16: NOW UNSTABLE in 1 hr 41 min: http://kci.pangea.pub/job/xenial_unstable_krita/16/
[06:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #52: STILL FAILING in 2 min 42 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/52/
[06:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #55: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/55/
[06:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #37: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/37/
[06:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #87: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/87/
[06:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #56: STILL FAILING in 8 min 10 sec: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/56/
[06:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #62: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/62/
[06:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #35: STILL FAILING in 5 min 40 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/35/
[07:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #63: STILL FAILING in 7 min 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/63/
[07:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #36: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/36/
[07:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #91: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/91/
[07:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #33: STILL FAILING in 1 hr 34 min: http://kci.pangea.pub/job/zesty_unstable_calligra/33/
[07:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calligra build #35: STILL FAILING in 1 hr 20 min: http://kci.pangea.pub/job/yakkety_unstable_calligra/35/
[07:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #92: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/92/
[07:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #33: STILL FAILING in 1 hr 25 min: http://kci.pangea.pub/job/xenial_unstable_calligra/33/
[07:49] -kubuntu-ci:#kubuntu-devel- Starting build #6 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[07:50] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #6: STILL FAILING in 1 min 51 sec: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/6/
[07:52] -kubuntu-ci:#kubuntu-devel- Starting build #7 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[07:53] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #7: STILL FAILING in 1 min 46 sec: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/7/
[08:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #34: STILL FAILING in 1 hr 7 min: http://kci.pangea.pub/job/zesty_unstable_calligra/34/
[08:32] -kubuntu-ci:#kubuntu-devel- Starting build #8 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[08:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #52: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/52/
[08:44] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #8: STILL FAILING in 12 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/8/
[08:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calligra build #36: STILL FAILING in 1 hr 23 min: http://kci.pangea.pub/job/yakkety_unstable_calligra/36/
[08:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kate build #243: FIXED in 12 min: http://kci.pangea.pub/job/xenial_unstable_kate/243/
[08:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #89: FIXED in 11 min: http://kci.pangea.pub/job/xenial_unstable_discover/89/
[08:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #73: FIXED in 12 min: http://kci.pangea.pub/job/yakkety_unstable_discover/73/
[08:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #50: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/50/
[08:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kate build #157: FIXED in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kate/157/
[09:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #45: FIXED in 17 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/45/
[09:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #34: STILL FAILING in 1 hr 11 min: http://kci.pangea.pub/job/xenial_unstable_calligra/34/
[09:06] -kubuntu-ci:#kubuntu-devel- Starting build #9 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[09:19] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #9: STILL FAILING in 13 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/9/
[09:20] <yofel> ...
[09:28] -kubuntu-ci:#kubuntu-devel- Starting build #10 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[09:42] <yofel> oh, it got to the squashfs part, progress :D
[09:47] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #10: STILL FAILING in 18 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/10/
[09:47] <yofel> that's SUCCESS really. It only failed at trying to put the finished file in /var/www/
[09:48] <acheronuk> \o/
[09:53] <kfunk> I'm not sure why, but I got subscribed to kdevelop-related build notifications on launchpad. e.g. I just got: https://launchpadlibrarian.net/298407446/buildlog_ubuntu-yakkety-i386.kdevelop-python_5.0.3-0ubuntu1~ubuntu16.10~ppa1_BUILDING.txt.gz
[09:53] <kfunk> dh_install: Cannot find (any matches for) "usr/lib/*/qt5/plugins/kdevplatform/26/kdevpdb.so" (tried in "." and "debian/tmp")
[09:53] <kfunk> dh_install: kdevelop-python missing files: usr/lib/*/qt5/plugins/kdevplatform/26/kdevpdb.so
[09:53] <yofel> acheronuk: not that we really need that? http://kci.pangea.pub/job/iso_xenial_unstable_amd64/ws/result/
[09:53] <kfunk> while CMake installed the following:
[09:53] <kfunk> -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/lib/i386-linux-gnu/qt5/plugins/kdevplatform/25/kdevpdb.so
[09:53] <kfunk> -- Set runtime path of "/<<PKGBUILDDIR>>/debian/tmp/usr/lib/i386-linux-gnu/qt5/plugins/kdevplatform/25/kdevpdb.so" to ""
[09:53] <yofel> so I'll just remove that part for now
[09:53] <kfunk> I suggest replacing the 25|26 with a wildmask
[09:53] <kfunk> that number can change any time
[09:53] <yofel> hm, that would break the workspace cleanup though :/
[09:54] <yofel> and we can't really keep image workspaces around
[09:56] <kfunk> yofel: talking to me?
[09:56] <yofel> no, rik
[09:57] <kfunk> ok :)
[09:58] <yofel> what you're saying makes sense. clivejo ^
[09:58] <yofel> and you're getting the notifications because they're from the kdevelop team ppa
[09:59] <yofel> if anything, clivejo: please testbuild stuff before uploading it to a "release" ppa
[10:00] <acheronuk> yofel: suppose it depends who we are doing these images for? just us to grab the latest and test? or to me made available a bit more generally to testers who would expect things not to vanish?
[10:00] <yofel> hm. good question.
[10:01] <yofel> The default CI behavior is to keep the workspace for failed builds, but delete it for successful ones, which is a bit inconvenient here
[10:01] <acheronuk> oh.
[10:01] <yofel> We could change for for iso_* I guess as long as we only want to keep the latest
[10:02] <yofel> *change that
[10:03] <yofel> but having maybe the latest... 10 would be nice for debugging purposes
[10:03] <yofel> the current build job expects to be run on master, and the storage to be on master as well though
[10:04] <yofel> we have plenty of disk space on master for the storage, would just need a vHost directory (which might already be there actually)
[10:05] <yofel> but unless we setup the build infra on master as well, we'll need to change the imager job to scp/rsync the result folder to master
[10:05] <acheronuk> will the rysnc link let us update daily images locally, or does the file name change with the buildstamp foil that?
[10:07] <yofel> the job puts the timestamp into the file right now, but I would prefer a timestamp subfolder and a current symlink the way cdimage.u.c is set up
[10:07] <yofel> then we can also make that accessible to rsync
[10:07] <acheronuk> yep, sounds a better way
[10:11] <alleehol> with backports-landing:  purging the now transisional pkg kdeconnect-plasma wants to remove kamoso here too.    Removing them nevertheless, schedules kdeconnect for autoremoval.    kubuntu-{desktop,full} and libpurpose(?) should depend now on kdeconnect not the 'old' kdeconnect-plasma'  (apt-cache rdepends kdeconnect{,-plasma})
[10:20] -kubuntu-ci:#kubuntu-devel- Starting build #11 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[10:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:40] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #11: FIXED in 20 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/11/
[10:55] <yofel> hm, I tried to disable ws-cleanup, but that thing doesn't match the documentation :/
[10:56] <yofel> oh no, it worked
[10:56] <yofel> I was looking at the wrong place >.<
[10:56] <yofel> now we just need to figure out how to work around gpg2 for the newer releases
[11:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kate build #40: FIXED in 15 min: http://kci.pangea.pub/job/zesty_unstable_kate/40/
[11:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen build #42: FIXED in 20 min: http://kci.pangea.pub/job/zesty_unstable_oxygen/42/
[11:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #33: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/33/
[11:44] <yofel> shadeslayer: is the gpg2 failure in http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/3/console familiar to you by chance? Sounds like something that should be happening in stretch as well
[11:45] <yofel> and I'm not really convinced that *I* am supposed to install and run dirmngr here
[11:45] <shadeslayer> Nope haven't seen that
[11:46] <yofel> hm, thanks
[11:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #71: FIXED in 16 min: http://kci.pangea.pub/job/zesty_unstable_discover/71/
[11:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #34: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/34/
[12:03] <yofel> oh, that code path is only triggered when you set extra ppa's, so maybe we're just the first ones to hit this *-.-
[12:06] <yofel> root@packaging:/usr/lib/live/build# apt-cache depends gnupg
[12:06] <yofel> gnupg
[12:06] <yofel>   Recommends: dirmngr
[12:06] <yofel> who packaged this >.<
[12:13] <clivejo> kfunk: yes sorry, Launchpad was in a bit of a mess last night and I was trying to dput to my own testing PPA which wouldnt work, do I tried to upload to the release PPA as a test.  I thought it had failed too, but apparently not!
[12:15] -kubuntu-ci:#kubuntu-devel- Starting build #4 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[12:16] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #4: STILL FAILING in 1 min 16 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/4/
[12:16] <clivejo> yofel: are we still paying for the S3 bucket?
[12:16]  * clivejo notices a payment to Amazon on the accounts
[12:16] <yofel> dunno
[12:17] <yofel> hm, that didn't work
[12:25] -kubuntu-ci:#kubuntu-devel- Starting build #5 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[12:26] <clivejo> yofel: where is the vhost pointing?
[12:26] <yofel> which one?
[12:26] <clivejo> for the finished iso?
[12:26] <yofel> dunno, would have to read the config
[12:27] <yofel> uhuh... running dirmngr by hand fixed the problem. this is retarded
[12:28] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #5: STILL FAILING in 3 min 17 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/5/
[12:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdev-python build #41: FAILURE in 6 min 25 sec: http://kci.pangea.pub/job/yakkety_unstable_kdev-python/41/
[12:29] <clivejo> is binary.hybrid.iso the actual built iso?
[12:30] <yofel> yes, though you should really be looking in result/ not build/
[12:31] <yofel> latter is just the workdir from lb
[12:31] -kubuntu-ci:#kubuntu-devel- Starting build #6 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[12:32] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #6: STILL FAILING in 48 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/6/
[12:34] -kubuntu-ci:#kubuntu-devel- Starting build #7 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[12:37] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #7: STILL FAILING in 3 min 9 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/7/
[12:37] <yofel> ?!?
[12:38] <yofel> can we go back to gpg1 please? gpg2 is just plain broken
[12:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-icons build #49: STILL FAILING in 5 min 40 sec: http://kci.pangea.pub/job/zesty_unstable_breeze-icons/49/
[12:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdev-python build #42: STILL FAILING in 5 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kdev-python/42/
[12:42] <yofel> I give up, back to work
[12:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-icons build #50: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/zesty_unstable_breeze-icons/50/
[12:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-python build #31: FAILURE in 6 min 24 sec: http://kci.pangea.pub/job/zesty_unstable_kdev-python/31/
[13:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-python build #32: STILL FAILING in 5 min 59 sec: http://kci.pangea.pub/job/zesty_unstable_kdev-python/32/
[13:14] <clivejo> when will a decision on backports be made?
[13:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #36: FAILURE in 5 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_kdev-python/36/
[13:17] <clivejo> kfunk: are you using those packages in kdevelop team?
[13:21] <soee> clivejo: wasn't it more or less made ?
[13:22] <clivejo> I dunno
 Rik put out a vote I believe
 Val and I said yed
[13:26] <acheronuk> I put out a 'proposal'
 Yes
[13:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #37: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_kdev-python/37/
[13:26] <acheronuk> so far yofel ack'd it and gave a +1
[13:27] <acheronuk> same with ahoneybun and valorie
[13:28] <clivejo> is wxl not acting RM?
[13:29] <acheronuk> faff about too much and we will never get anything done, so it was put in the terms of "I would like to do this tomorrow. if you think it shouldn't please raise objections"
[13:30] <clivejo> ok
[13:30] <clivejo> make it so, Number One!
[13:30] <kfunk> clivejo: what do you mean? if the kdevelop team installs ubuntu packages?
[13:30] <clivejo> do you use them?
[13:30] <kfunk> we use our self-compiled versions of course :)
[13:31] <kfunk> so, no, not really
[13:31] <clivejo> I see
[13:32] <kfunk> why? any problems?
[13:32] <acheronuk> clivejo: well wxl probably isn't sufficiently bedded in on the technical side yet, so what would in theory be a RM decision is I think a bit more of "are we ready yet, any objections?" to current -devs etc
[13:32] <acheronuk> if anyone objects, tell me!
[13:33] <yofel> backports has typically not been a concern to the RM anyway, as that position mostly just covers the primary archive tasks. Whoever did most of the work on the backports decided what gets done with it
[13:33] <clivejo> kfunk: no no, I dont use them myself.  Ovi setup a team on LP to provide released versions, while we sorted out the backporting issues with Frameworks and Plasma
[13:33] <acheronuk> yofel: ah. ok. that I didn't know. ty
[13:34] <kfunk> okok
[13:34] <clivejo> kfunk: the xenial build it failing as the arhive doesnt have the required Frameworks for it
[13:36] <kfunk> /<<BUILDDIR>>/kdevelop-python-5.0.3+p16.04+git20161216.1310/docfilekcm/kcm_docfiles.cpp:42:12: error: ‘DocumentationConfigPage’ is not a member of ‘KDevelop::ConfigPage’
[13:36] <kfunk>      return KDevelop::ConfigPage::DocumentationConfigPage;
[13:36] <kfunk>             ^
[13:36] <kfunk> hmm
[13:36] <clivejo> acheronuk: so your decision :)
[13:38] <acheronuk> clivejo: as it might come to that, is why I sent the email asking for opinions
[13:38] <kfunk> ah, that's actually kdevelop-python master branch. /me just got confused about "kdevelop-python-5.0.3" in there
[13:38] <kfunk> ok, that just needs a newer kdevplatform master, yep
[14:35] <alleehol> acheronuk: FWIW  +1 from me.    No problems found after 1/2 day of usage
[14:48] <BluesKaj> Howdy all
[14:51] <yofel> o/
[15:14] -kubuntu-ci:#kubuntu-devel- Starting build #8 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[15:19] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #8: ABORTED in 4 min 39 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/8/
[15:20] -kubuntu-ci:#kubuntu-devel- Starting build #9 for job iso_yakkety_unstable_amd64 (previous build: ABORTED)
 acheronuk: You do it yet?
[15:31] <acheronuk> alleehol: great. thanks for the feedback
[15:32] <acheronuk> tsimonq2: nope. had said late afternoon. so taking a fairly arbitrary meaning for that, I was waiting until 4pm UTC
[15:37] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #9: STILL FAILING in 16 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/9/
[15:40] <alleehol> acheronuk: about the kdeconnect fixes for (reverse)dependencies.  If it helps: I've seen it's fixed in kde neon.
[15:48] <yofel> kubuntu-meta will need an update. I think -backports already has a patched one
[15:48] <yofel> for earlier changes
[15:49] -kubuntu-ci:#kubuntu-devel- Starting build #10 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[15:50] <wxl> clivejo: yeah, i don't think me being RM has been made official. also, i've yet to hear anything constructive from Riddell, so if i (or i guess any of us) proceed as RM, we're kind of on our own to figure it out
[15:51] <Riddell> kubuntu's never had an official release manager, feel free to make one but the important bit is being on the ubuntu release team
[15:52] <wxl> Riddell: and by that you mean having access to mark images as ready on the qa tracker?
[15:52] <Riddell> right
[15:52] <wxl> right right
[15:53] <Riddell> the ubuntu release team should be there to help anyone figure it out, feel free to ask me if there's specific questions too but for the most part it's making sure everything is in place
[15:53] <wxl> within lubuntu that access is granted in other forms other than being on the release team itself
[15:54] <wxl> afaik you're the only release team member that's not a core ubuntu person
[15:54] <yofel> I think I'm still set as the manager for the kubuntu images, so worst case ask me
[15:56] <acheronuk> I'm reasonably sure in a few cases, after having some testing logged, the release team have just gone ahead and marked our images as ready themselves
[15:56] <yofel> they did. The only criteria is that the test are done anyway
[15:57] <wxl> they rarely do that, though
[15:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #69: NOW UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_marble/69/
[15:57] <wxl> at least not without bugging SOMEONE on irc before
[15:57] <yofel> well yes, *with* bugging someone on irc
[15:57] <wxl> i know at least during some cycle i wandered in here to get an idea of what's going on to pass off to them
[15:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #77: STILL FAILING in 37 min: http://kci.pangea.pub/job/yakkety_unstable_marble/77/
[15:57] <acheronuk> wxl: if I recall, they 'bugged' us on IRC at the time :P
[15:57] <wxl> :)
[15:58] <yofel> 1.0.5-1build1~2 - what the hell is that version supposed to mean... yay for copying stuff from ppas I guess
[15:59] <acheronuk> ok. if no objections, I am about to hit 'kopy' on the backports
[16:00] <wxl> yofel: do you know what membership gives you that ability? (you could try a fresh SSO login to the QA tracker)
[16:00]  * clem_l holds his breath
[16:00] <yofel> wxl: I would have to check again, but I'm failry certain that when I checked last time my actual account ID was set there
[16:00] <wxl> yofel: that's… weird.
[16:01] <acheronuk> kopy running :P
[16:01] <yofel> wxl: so, it's asking me for "ubuntu-testcase, kubuntu-council'
[16:02] <wxl> ah it's probably set so that all kouncil (name change suggested) members can mark images
[16:02] <wxl> which i think is totally sensible
[16:02] <wxl> but obviously not for me XD
[16:02] <yofel> maybe. Now I wondere where I saw my ID....
[16:04] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #10: STILL FAILING in 14 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/10/
[16:04] <acheronuk> kopy for xenial requested :)
[16:05] <acheronuk> wonder if I should give the LP publisher time to recover from a mild nervous breakdown before I do yaketty?
[16:05] <yofel> check the PPA page for errors please if you didn't use --sync
[16:06] <wxl> Lubuntu has a "product-manager" team
[16:06] <wxl> i think k could use something similar
[16:08] <clem_l> acheronuk: the issue where kalarm can't start is the same as the one for kmail right?
[16:08] <clem_l> it's the /var/lib/mysql-files dir missing?
[16:09] <yofel> uh, that would be akonadi being broken
[16:09] <yofel> did someone backport the broken version from yakkety?
[16:09] <yofel> actually, did we ever fix that in >=yakkety?
[16:10] <blaze> mysql is not meant for desktop apps :\
[16:11] <yofel> I think most of us got that by now, we just can't get rid of it -.-
[16:12] <yofel> bug 1633855
[16:12] <yofel> we did not -.-
[16:12] <wxl> blaze: tell that to the kde developers :)
[16:12] <yofel> someone please keep pinging me over the weekend until I'm annoyed enough to fix that
[16:13] <acheronuk> I didn't think that was fixable with the mysql in Xenial?
[16:13] <acheronuk> but I may be wrong there
[16:13] <clem_l> yofel: ping
[16:13] <clem_l> yofel: ping
[16:13] <clem_l> yofel: ping
[16:13] <clem_l> oh wait.. is it the weekend yet?
[16:13] <acheronuk> lol
[16:13] <wxl> hah
[16:13]  * wxl hands yofel a trout
[16:14] <yofel> good start, but you'll have to do better :D
[16:14]  * yofel binds the trout to an auto-slapper that responds to pings
[16:14]  * wxl sets the auto-slapper to kill
[16:14] <yofel> acheronuk: that was never broken in xenail
[16:14] <yofel> *xenial
[16:16] <acheronuk> I meant in xenial when you are running the backports akonadi
[16:17] <yofel> if that has the patches disabled that will probably break
[16:17] <yofel> as we esp. wrote those a couple days before the xenial release to get it running with 5.7
[16:22] <acheronuk> umm. I was only paying attention part of the time back then
[16:22] <yofel> well, me too ^^
[16:22] <yofel> oh, not then, but now
[16:23] <yofel> #postgresql-data-checksums.patch
[16:23] <yofel> #postgresql9.5.patch
[16:23] <yofel> #kubuntu_disable_secure_file_priv_check.diff
[16:23] <yofel> #kubuntu_fix_mysql_db_creation_57.diff
[16:23] <yofel> yep, we have a problem
[16:24] <yofel> typical release days :D
[16:26] <acheronuk> yeah. I find out that something I thought was not fixable, or very difficult to fix, actually has disabled patches 2 mins after hitting the 'release' button!
[16:26] <acheronuk> such is life XD
[16:29] <clem_l> that's all I've got
[16:30] <clem_l> other than that, the theming on the session screen
[16:30] <clem_l> I'm going to fix that right now
[16:30] <clem_l> I can squeeze an mkdir -p /var/lib/mysql-files in a postinst too if it helps
[16:31] <yofel> FWIW, that's done in the postinst of 'mysql-server', what you want is enable kubuntu_disable_secure_file_priv_check.diff in akonadi
[16:32] <yofel> and kubuntu_fix_mysql_db_creation_57.diff for initial DB creation using 5.7
[16:32] <clem_l> are you enabling these in an update in the backports PPA?
[16:32] <yofel> yes
[16:32] <clem_l> ok
[16:32] <yofel> acheronuk: are you? otherwise I'll have time to do that later
[16:34] <acheronuk> yofel: I'm not really sure what I'm doing with akonadi, so if you would be kind enough to do the honours as you know what is needed, that would be appreciated
[16:34] <yofel> ack
[16:35] <clem_l> I was looking at the task switcher there in Plasma, it's impressive the amount of configuration...
[16:36] <clem_l> not only you can choose among a wide variety of what is essentially a core component, but you can fine tune the selected switcher in detail
[16:36] <clem_l> and then not only that but you can go ahead and pull 3rd party ones
[16:37] <clem_l> I'm not sure whether that's completely mad or absolutely awesome, but it's impressive
[16:37] <acheronuk> that is one thing we tend love about KDE. configurability and being able to extend it
[17:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #37: STILL FAILING in 7 min 2 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/37/
[17:07] <yofel> the publisher really went on vacation it seems
[17:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #38: STILL FAILING in 5 min 38 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/38/
[17:19] <acheronuk> hmmm. did I kill it?
[17:21] <acheronuk> if clem_l is still holding his breath, I think he'll have turned blue by now :P
[17:21] <yofel> more likely the archive rebuilds :D
[17:29] <clem_l> :)
[17:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #54: NOW UNSTABLE in 2 hr 34 min: http://kci.pangea.pub/job/zesty_unstable_marble/54/
[18:00] <acheronuk> looks like Xenial has published
[18:05] <clivejo> oh its Friday today!
[18:05]  * clivejo looks at yofel
[18:05] <clivejo> and December too
[18:06] <yofel> hm? :D
[18:06] <clivejo> just reminding you :P
[18:06] <yofel> what, what could possibly go wrong on a december friday ^^
[18:06] <yofel> evening
[18:09] <clivejo> backports mayhem!
[18:12] <acheronuk> clivejo: right. I'm off. I'll be back on Monday :P
[18:12] <yofel> hey! XD
[18:13] <clivejo> me too
[18:13] <clivejo> probably wont be around until noon on Monday
[18:13] <acheronuk> tsimonq2: you'll be here, right :P
[18:13] <clivejo> let the dust settle
[18:13]  * mamarley turns on the HEPA filter.
[18:15] <clivejo> course tsimonq2 will be here, he volunteers to rebuild the entire stack on new Qt didn't he?
[18:16] <wxl> did he do his homework?
[18:16] <clivejo> no!
[18:16] <wxl> well—
[18:17] <yofel> well then, I'm out for about an hour. Try to not blow everything up in the meantime
[18:17] <clivejo> awwww yofel
[18:18] <clivejo> you're no fun!
[18:18] <yofel> hey, I'm still sitting in the office ^^
[18:18] <clivejo> why?!?
[18:18] <yofel> overtime work
[18:18] <clivejo> :(
[18:18] <clivejo> but its.... christmas
[18:18] <yofel> ... in a week
[18:18] <yofel> anyway, bbl
[18:19] <clivejo> did you do something naughty at your Christmas party?!?
[18:22]  * acheronuk tries updating VMs
[18:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #35: ABORTED in 17 sec: http://kci.pangea.pub/job/zesty_unstable_kdevelop/35/
[18:42] -kubuntu-ci:#kubuntu-devel- Starting build #12 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING)
[18:58] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #12: STILL FAILING in 15 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/12/
[18:59] <clivejo> 18:58:17 The following packages have unmet dependencies:
[18:59] <clivejo> 18:58:17  fcitx-frontend-qt5 : Depends: qtbase-abi-5-6-1
[18:59] <clivejo> 18:58:17 E: Unable to correct problems, you have held broken packages.
[19:18] <acheronuk> clivejo: where is that from?
[19:18] <clivejo> the ISO build job
[19:18] <acheronuk> right. just double checking
[19:19] <clivejo> some KDE4 stuffs being pulled in too
[19:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kleopatra build #102: FIXED in 2 hr 36 min: http://kci.pangea.pub/job/xenial_unstable_kleopatra/102/
[19:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #78: STILL FAILING in 3 hr 31 min: http://kci.pangea.pub/job/yakkety_unstable_marble/78/
[19:41] <yofel> clivejo: I uploaded rebuilds for that, they were just stuck on the publisher
[19:41]  * clivejo kicks publisher
[19:42] <yofel> lets try this agian
[19:42] -kubuntu-ci:#kubuntu-devel- Starting build #11 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[19:42] -kubuntu-ci:#kubuntu-devel- Starting build #12 for job iso_xenial_unstable_amd64 (previous build: FIXED)
[19:42] -kubuntu-ci:#kubuntu-devel- Starting build #13 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING)
[19:42] <clivejo> has it published?
[19:43] <yofel> yes
[19:43] <yofel> after like 3h..
[19:44] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #11: STILL FAILING in 1 min 38 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/11/
[19:44] <clivejo> ah only a slight delay then
[19:44] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #13: STILL FAILING in 1 min 40 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/13/
[19:44] <yofel> wtf
[19:44] <yofel> 19:44:01 gpg: keyserver receive failed: No data
[19:44] <yofel> the server is broken >.<
[19:44] <clivejo> LP keyserver?
[19:44] <yofel> ubuntu keyserver
[19:44] -kubuntu-ci:#kubuntu-devel- Starting build #12 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[19:45] -kubuntu-ci:#kubuntu-devel- Starting build #14 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING)
[19:45] <yofel> OTOH, we need job group throttling. 3 iso jobs at the same time is doable, but not a particulary good idea
[19:46] <yofel> (this is stress testing now)
[19:46] <tsimonq2> MEOW
[19:46] <yofel> HISS
[19:48] <yofel> now to fix akonadi for backports
[19:50] <mamarley> WOOF
[20:00] <yofel> clivejo: if you refresh patches, please also update the "Updated" field in the patch notes
[20:01] <clivejo> can you give me an example?
[20:01] <yofel> your patch updates in akonadi
[20:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #36: FIXED in 1 hr 26 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/36/
[20:08] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #12: SUCCESS in 26 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/12/
[20:08]  * clivejo high fives yofel
[20:09] <yofel> that one worked in the morning already ^^
[20:09] <yofel> at least I didn't break it
[20:09] <yofel> but the other too are looking good as well
[20:09] <yofel> *two
[20:10] <yofel> urgh, good that I did that on linode. Scaleway would've run out of disk space by now
[20:11] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #14: STILL FAILING in 26 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/14/
[20:11] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #12: STILL FAILING in 26 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/12/
[20:12] <clivejo> awwwww
[20:12] <yofel> 20:11:47 E: /usr/share/syslinux/themes/ubuntu-yakkety - no such directory.
[20:12] <yofel> hmmmmmm
[20:17] <tsimonq2> yofel: OOOOOOOOOH where is the code to do that???
[20:18] <yofel> tsimonq2: hm?
[20:18] <clivejo> pangea-tooling does it?!
[20:19] <yofel> pangea-tooling/kci/imager.rb and imager/* if you want to look at it
[20:19] <tsimonq2> :D :D :D :D :D
[20:24] <yofel> hm, looks like we're still using the xenial theme, now where the hell do I tell live build that
[20:25] <yofel> found it
 Hey yofel, questions
[20:27] -kubuntu-ci:#kubuntu-devel- Starting build #13 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[20:27] <yofel> hm?
[20:27] -kubuntu-ci:#kubuntu-devel- Starting build #15 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING)
 Let's say we ship Kubuntu G with Plasma 1.1.1. Kubuntu G gets released. Can 1.1.2 be SRUed into G?
[20:28] <yofel> yes, 1.2 no
[20:28] <yofel> well
[20:28] <yofel> yes, under the condition that it contains no features
[20:29] <yofel> so the question is are we talking about semantic versioning here? ^^
 I mean if we ship Zesty with 5.9.4 for example, can we SRU in 5.9.5?
[20:29] <yofel> yes we can
 Ooh yay ok
[20:29] <yofel> I believe the MRE for plasma is still valid
[20:30] <wxl> http://i.imgur.com/aAbDQy9.gif
 'cause we might end up needing to do that
[20:30] <yofel> XD
 (Photo, 720x1280) https://irc-attachments.kde.org/oGslA00o/file_1399.jpg
 Hmm
[20:31] <wxl> aw
[20:32] <wxl> works for me
 Oh I see it
 Lol
[20:34] <yofel> hm, now I completely broke the workspace cleanup for the image builds it seems -.-
[20:37] <yofel> oh, ws-cleanup renamed the folders instead of wiping them o.O
[20:43] <yofel> which is *supposedly* fixed in 0.32 - which we have...
[20:47] <yofel> oh hm, rm: cannot remove 'imager-amd64_ws-cleanup_1481883609881/build/chroot/lib/modules/4.4.0-53-generic/kernel/drivers/usb/gadget/legacy/tcm_usb_gadget.ko': Permission denied
[20:48] <yofel> might be a problem
[20:51] <yofel> a hm, yeah. The user/group names aren't consistent in the CI
[20:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:54] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #13: FIXED in 27 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/13/
[20:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:54] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #15: FIXED in 26 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/15/
[20:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcompactdisc build #58: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_libkcompactdisc/58/
[20:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #41: NOW UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/41/
[20:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #78: NOW UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/78/
[20:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #229: STILL FAILING in 49 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/229/
[20:55] <yofel> please don't touch the image jobs for now, linode will run ENOSPC after a few
[20:59] <yofel> great, how the hell do I figure out what UID I need to chown this to...
[21:05] <yofel> great, how the hell do I figure out what UID I need to chown this to...
[21:05] <yofel> and why do I have connection issues again
[21:11] -kubuntu-ci:#kubuntu-devel- Starting build #16 for job iso_zesty_unstable_amd64 (previous build: FIXED)
[21:11] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #16: FAILURE in 1.9 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/16/
[21:14] <yofel> o.O
[21:17] -kubuntu-ci:#kubuntu-devel- Starting build #17 for job iso_zesty_unstable_amd64 (previous build: FAILURE -- last SUCCESS #15 50 min ago)
[21:17] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #17: STILL FAILING in 1.9 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/17/
[21:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcompactdisc build #59: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_libkcompactdisc/59/
[21:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #79: FIXED in 18 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/79/
[21:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #42: FIXED in 18 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/42/
[21:19] -kubuntu-ci:#kubuntu-devel- Starting build #18 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING -- last SUCCESS #15 52 min ago)
[21:19] <yofel> ruby is wieird
[21:30]  * clivejo nods
[21:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #230: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/230/
[21:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:41] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #18: FIXED in 21 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/18/
[21:46] -kubuntu-ci:#kubuntu-devel- Starting build #19 for job iso_zesty_unstable_amd64 (previous build: FIXED)
[21:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #114: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/114/
[21:47] <yofel> that didn't work :(
[21:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #107: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/107/
[21:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcddb build #40: STILL FAILING in 17 min: http://kci.pangea.pub/job/zesty_unstable_libkcddb/40/
[21:48] <yofel> because I'm running chown in the wrong folder -.-
[21:52] <valorie> everybody be sure to run updates or at least check your version of apport: https://bugs.launchpad.net/apport/+bug/1648806
[21:52] <valorie> undecided?
[21:53] <valorie> weird, but fixed
[21:56] <valorie> http://www.theregister.co.uk/2016/12/15/researcher_details_justpatched_pwnage_flaws_in_ubuntu/ -- wow: "while working on his Apport research, he was offered $10,000 for his exploits by an unnamed third party."
[21:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-python build #33: FIXED in 12 min: http://kci.pangea.pub/job/zesty_unstable_kdev-python/33/
[22:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #115: FIXED in 12 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/115/
[22:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #108: FIXED in 12 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/108/
[22:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcddb build #41: FIXED in 12 min: http://kci.pangea.pub/job/zesty_unstable_libkcddb/41/
[22:08] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #19: SUCCESS in 21 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/19/
[22:10] -kubuntu-ci:#kubuntu-devel- Starting build #20 for job iso_zesty_unstable_amd64 (previous build: SUCCESS)
[22:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #85: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/85/
[22:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #82: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/82/
[22:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #28: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/28/
[22:29] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #20: SUCCESS in 19 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/20/
[22:35] -kubuntu-ci:#kubuntu-devel- Starting build #21 for job iso_zesty_unstable_amd64 (previous build: SUCCESS)
[22:35] <yofel> ok, I think I got it now
[22:35] <clivejo> yipppeeee
[22:42] <valorie> nice to see the green
[22:45] <clivejo> were is the gree?
[22:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #83: FIXED in 16 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/83/
[22:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #86: FIXED in 17 min: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/86/
[22:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #29: FIXED in 17 min: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/29/
[22:53] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #21: SUCCESS in 18 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/21/
[22:59] -kubuntu-ci:#kubuntu-devel- Starting build #13 for job iso_xenial_unstable_amd64 (previous build: SUCCESS)
[22:59] -kubuntu-ci:#kubuntu-devel- Starting build #14 for job iso_yakkety_unstable_amd64 (previous build: FIXED)
[23:00] -kubuntu-ci:#kubuntu-devel- Starting build #22 for job iso_zesty_unstable_amd64 (previous build: SUCCESS)
[23:23] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #13: SUCCESS in 23 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/13/
[23:26] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #14: SUCCESS in 26 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/14/
[23:26] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #22: SUCCESS in 25 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/22/
[23:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkgeomap build #20: FIXED in 13 min: http://kci.pangea.pub/job/zesty_unstable_libkgeomap/20/


[18:14] <ibeardslee> morning
[18:17] <jdowner> morning
[19:03] <hads> morning
[19:25] <olly> morning
[21:00] <kcj[work]> Morning.


 suggestions for a mail client? I cant seem to find one in the store.
 Dekko2
 from the openstore?
 Yes but not with xenial
 oh. Figured I would just try it out. I can wipe it again and go back if there are more apps on stable
 Sure
 any idea when it will come to xenial? I'm not useing this as my daily driver just a nexus I had lying around so I could just wait.
 Often asked but no more answer than « in development »
 https://gitlab.com/dekkoproject/dekko/issues/98
 3 months ago :(
 wonder how long it takes to compile apps on phone? I hope there is an emulator or something they can use to compile faster
 most can be cross-compiled
 Has anyone ported Ubuntu touch for Mtk devices? … Is there any documentation for it?
 @Yugal_Patil, I'm thinking there was something weird with mtk devices that make porting a nightmare. I could be wrong though
 @Yugal_Patil, do you have kernel source code?
 @anpok, I meant before it's enabled through hdmitx, it's not considered attached, so I wondered if any code in Ubuntu Touch handled that
 oh, the browser-ng scroll bar is a part of qtwebengine...
 as for source... hwcomposer is closed-source blob at least before Oreo
 @NotKit, yes...
 which SoC?
 if's mt6737 or so, might be feasible
 yes I've mt6737 device...
 is there any written guide for that...?
 Halium + UBPorts porting docs
 but it won't contain all the possible quirks needed
[05:01] <ubptgbot> Photojoe4 was added by: Photojoe4
 Has anyone had any real success using UT on a Nexus 5x?
 By that I mean basic functionality- make/recieve phone calls and texts, web browser, maps...
 I'm wanting to try to try to make the transition to the Librem 5 as seamless as I can, so I want to start using a device now that can run either UT or Plasma Mobile...
 @Photojoe4, UT is not ported yet to that device
 I saw that the Nexus 5 has been, but it won't support a 32bit OS will it?
 @amolith, Yep, it's even one of the first warnings on the Halium guide: "Mediatek chipsets are not open-sourced and so there is rarely a usable Android source tree available for them".
 @Photojoe4, What do you mean?
 Sorry, meant to say it will ONLY support a 32bit OS...
 Ah okay, right
 And I'd imagine that 64bit systems will become the norm before too much longer...
 Yeah, probably
 It seems like the 5x would be the better buy if UT were going to be developed for newer devices, and there's not really much of a price difference (think the 5x is about $30 more), and it could be used wih other OS's (Plasma Mobile, Pure OS)...
 UT is being ported to other devices currently, but the problem wiht N5x is that porters found a very weird bug
 [Edit] UT is being ported to other devices currently, but the problem with N5x is that porters found a very weird bug
 Well that's a shame. Are they still trying to port it, or has it been abandoned?
 Trying afaik
 Thanks, I'll keep watching...
 you're welcome
 @NotKit Not that I am aware of. Can you point to the kernel sources and configuration for the device?
 of Ubuntu Tablet or the one I'm porting?
 the one you are portin
 https://github.com/gemian/gemini-linux-kernel-3.18
 Does Matrix allow persistent storage of message history?
 @TartanSpartan, I will tell you more, as it's federated, there's no way you can disable persistent storage
 Are those stored on a cloud server or locally on your device?
 On a server (on a lot of federated servers actually) + on device caching
 It's ot though, @ubports_ot
 Thanks, that's all I needed to know.
 @advocatux, I'm wondering where that leaves us with the M10 FHD 32GB 4G internet tablet. Are the other M10's open-sourced? But not this one?
 https://www.pdevice.com/product/bq-aquaris-m10-full-hd-32gb-4g-specs
 @Photojoe4, UT is developed for 5x
 It has 3.10 kernel which is a mess and hard to work with
 There is only one usable 64 bit rootfs, and it's a reference one. Don't worry too much
 5x is not going to be abandoned, don't worry
 I would help maintaining music-app
 Is there any todo list?
 @turanmahmudov, This is the current list of open issues https://github.com/ubports/music-app/issues
 Ah, and thank you for your work !!
 The uNav developer @costales told me that he has removed uNav from 16.04 because it did not work as it should be
 He thinks the problem is from the OS
 (Photo, 720x1280) https://irc.ubports.com/eXnLWd0P.png
 @TartanSpartan, No, no M10 is open-sourced
 @turanmahmudov, I had the same idea, but idk if I have enough time... Anyway, we could work together!
 Sound great!
 (Sticker, 512x512) https://irc.ubports.com/25izNIir.webp
 @mymike00, Do it!!!! :) Sounds great guys, join forces
 @turanmahmudov, Very cool! You can for the beginning just fork it and send us PRs ;)
 @vanyasem, it shouldn't be, as i m still holding on to my newly purchased n5x
 So the reason the other two M10s happened is because, of course, BQ had their closed device trees. Right?
 correct
 @GiovanniStaiano, Strange, I tried it in a Nexus 5 on the road and it worked OK, I did not spot any problem.
 @wagafo, same here, works fine on my FP2 16.04 devel. haven't seen anything wron, am even amazed at how quick and accurate the gps is
 @wagafo, [Edit] same here, works fine on my FP2 16.04 devel. haven't seen anything wrong, am even amazed at how quick and accurate the gps is
 @wagafo @YougoChats Can you check if voice navigation works?
 @GiovanniStaiano, It worked when I tried it
 I switched to RC a couple of weeks ago … and now I thought the screenshot with Libertine in the settings app was a mock-up LOL … but it was real. awesome! … but maybe we can name it a bit more user friendly? not everyone knows or cares about the term "Libertine"
 [Edit] Sounds great!
 @GiovanniStaiano, can i trigger it? i've set a navigation, but i'm sitting at my desk, lol
 @GiovanniStaiano uNav is working fine for me in Hammerhead 16.04 devel, the gps is a bit slower tan in Vivid but its ok.. uNav and google maps from the browser works fine as usual. Not amazing but works
 @GiovanniStaiano, ok, it just spoke. it's working, but it's a rather robotic English voice and the download function for custom voices doesn't seem to work
 The European Parlament has just blocked the "upload filter" 🤩
 good news! article 13 is not dead though
 Libertine to me means freedom to run desktop apps on the go/in a mobile context.
 (Sticker, 512x512) https://irc.ubports.com/n37DiZ7k.webp
 do we have disk encryption ?
 @dreamcreator108, yes and no
 https://github.com/ubports/ubuntu-touch/issues/178
 https://forums.ubports.com/topic/1012/one-method-to-encrypt-home-phablet/2
 @malditobastardo, Thanks!
 Hi
 Libertine works with OPO
 ?
 16.04/RC
 it should
 oh so libertine now works in xenial?
 I guess except Nexus 5? 😁
 @Javacookies, it works now in hammerhead too, excepto mpv and vlc
 *mpv and vlc are both working fine in other devices
 really? no more python erros?
 I didn't know there has been works with libertine recently
 check system settings
[12:32] <ubptgbot> <Thomas Eitzenberger> @Javacookies Yes Libterine kinda works (alas you need to start the apps via cmd line)
[12:32] <ubptgbot> <Thomas Eitzenberger> [Edit] @Javacookies Yes Libertine kinda works (alas you need to start the apps via cmd line)
[12:32] <ubptgbot> <Thomas Eitzenberger> [Edit] @Javacookies Yes Libertine kinda works (alas you need to start the apps via cmd line) … ubuntu-app-launch nameofapp
[12:32] <ubptgbot> <Thomas Eitzenberger> [Edit] @Javacookies Yes Libertine kinda works (alas you need to start the apps via cmd line) … ubuntu-app-launch nameofapp … libertine-container-manager list-apps
 oh I see, so the icon in the scope still doesn't work?
 everything is WIP
 but it's good to know 👍 … although I don't really use libertine LOL
 @wagafo @YougoChats In reality, the app worked initially on 16.04 but then I saw in the OpenStore that it is no longer installable. In fact I think that if you had to uninstall it, it would not be possible to install it again, for now.
 @GiovanniStaiano, I will try it again tomorrow, I think voices were working fine also, at least for my language
 @GiovanniStaiano, you can go to open-store.io in a browser and manually download a click file, and then install it with OpenStore app or UTTT. with a bit of luck a vivid app will run on xenial
 if not, just uninstall again
[12:45] <ubptgbot> ulrichard was added by: ulrichard
 @YougoChats, I will try this way
 @wagafo, Ok maybe only the voices already downloaded work
 Is there a Bitcoin wallet for UBports? I cannot even find the half working java wallet, that was in the store a couple of years ago.
 if there isn't one in the store then the short answer is no
 So, the place to start would be (https://docs.ubports.com/en/latest/appdev/index.html)?   … How feasible is it to port something like electrum which is python and Qt?
 yes. it's definitely feasible, especially if it's using pyotherside and qt5 already
 HI tried to flahs nexus 5 got messed up as error say thre is a bug anyone else had this problem
 I was trying to install16.04 rc
 Yeah, I got tha tyesterday. Think it's a known issue but @neothethird will know. I just retried a couple of times and things worked ok.
[14:23] <ubptgbot> ar7ch was added by: ar7ch
 How to install ut for nexus5 without using the app ? App for windows not see phone. Adb works
 Windows app is phucked and therefore you should use linux one
 @Kirill, Are you using the latest version of the installler? https://github.com/ubports/ubports-installer/releases/latest
 @VeryOriginalUsername, your intel is outdated ;) just fixed it the other day
 Latest and  0.1.9
 @neothethird, Uhh last time I tried 0.13 was newest 😜
 @VeryOriginalUsername, yeah, we didn't make a big announcement or something :D still in beta anyways
 @Kirill, Hmm, that shouldn't happen, but it does from time to time unfortunately. Could you try a different usb cable and usb port on the PC to rule connection problems out?
 (Photo, 960x1280) https://irc.ubports.com/Qlmdg9zC.png No problem
 Hmm
 @Kirill, are you perhaps missing fastboot?
 I will look into it, but it might take some time
 @dohbee, it's the same driver
 oh ok
 @Kirill, i don't know how technical you are, but if you're comfortable with that, you could try running the installer from source
 Just to be sure, could you try and see if your device is detected with these adb and fastboot binaries as well? https://dl.google.com/android/repository/platform-tools-latest-windows.zip
 that's the ones that are shipped with the installer
 (Photo, 720x1280) https://irc.ubports.com/w8QXosqE.png
 https://github.com/ubports/ubuntu-touch/issues/701
 Fastboot need reboot bootloader
 Could that bug be why I haven't been able to launch Libertine apps via CLI (or otherwise) on Xenial RC MX4?
 @Kirill, just for the heck of it, could you try running the installer as an administrator?
 (Photo, 720x1280) https://irc.ubports.com/kjntg84b.png no change, does not see device
 (Photo, 720x1280) https://irc.ubports.com/IALAYOWO.png Driver
 I usually manually go to fastboot at that point
 In the manual also did not see
 on ubuntu 18.04 too not sees device
 is it unlocked, and then debug mode turned back on
 @Kirill, and when you select it manually?
 because auto-detection does not (read: can not) work always
 (Photo, 720x1280) https://irc.ubports.com/bTheXp37.png
 then it flashes recovery right, then manually go back into again
 try both volume up and then volume down
[15:44] <ubptgbot> Vikas Poonia was added by: Vikas Poonia
 Nothing happens
 (Photo, 960x1280) https://irc.ubports.com/bG9mW6Ms.png
 Fastboot
 On another computer also does not see the device
[18:06] <ubptgbot> <Vikas Poonia> @Kirill, ??
[18:23] <ubptgbot> <Remus Barth> Feedback: Nexus 5, for me installing UBports works only from ubuntu installed on pc, no chance (device not seen ) on win10, high Sierra macOS or Ubuntu live, all with latest updates.
 @Kirill, are you running installer with admin privs btw?
 Yes admin privs
 Is there anybody succeeded with installing ubports onto latest FP2. Tried on debian 9.4, ubuntu 16.04, macOS... nothing.
 @Pascal, Logs please
 @Remus Barth, Did you check out `adb` and `fastboot` is on your user `$PATH` ? I've seen that issue with both Sierra and W10 … What installer did you use on Ubuntu live? Did you check out `adb` and `fastboot` tools were installed?
 Yes. adb and fastboot manually fond the phone, ubports-installer fails.
[18:38] <ubptgbot> <Remus Barth> Adb, fastboot ok, path don’t check, Ubuntu live 16.04
 Tried 0.1.13, 0.1.18, 0.1.9.
 Ubuntu is not live, but installés.
 @Remus Barth, which package did you use on Ubuntu live xenial? .snap, .deb., appimage?
 Did you see anything weird in the installer log?
 Adb and fastboot are in /usr/bin.
 I must manually select the FP2, not detected. I tried the install on nexus 7 2013 today with success.
[18:42] <ubptgbot> <Remus Barth> Snap
[18:42] <ubptgbot> <Remus Barth> Result: fail: .. Error ...loading libudev.so.1......
 FAILED (remote: bootimage : incomplete or not signed), then installer hangs.
 I downloaded the debs from ubports, or GitHub.
 @Remus Barth, Did you check out that Ubuntu live was fully updated? Is that library installed on your computer? BTW a full log is better to know what was happening ;)
 Pascal only the full installer log can give us a clue of what was happening
[18:52] <ubptgbot> <Remus Barth> Fully updated, no log sorry, it was live...
 It doesn't matter it's a live stick, the snap installer log is in `/snap/ubports-installer/current/.cache/ubports`
 You can paste the full log on https://paste.ubuntu.com/ for example and give us the link
 thx for help ! … https://paste.ubuntu.com/p/X7jkfc8rsr/
 Another thing while I take a look to the log. Have you tried with a different usb cable and/or different usb port? You wouldn't believe how many installation fail for that
 Sorry, i had to install Telegram on my debian distro.
 Tried with the Nexus 7's cable i used successfully today : nope. I notice adb's talking about port 5038 in the logs,  but debian's talking about port 5037 in any shell.
 @Pascal, Good, I'm a Debian as well :) … Okay, it seems you're suffering this bug https://github.com/ubports/ubports-installer/issues/184 Can you try with the latest installer once again? https://github.com/ubports/ubports-installer/releases/latest Thank you
 I tried with the 0.1.18 two minutes ago.
 Oh
 I'm out of ideas then, sorry
 How you tried to run the installer with sudo?
 @NotKit I would try building a kernel with debugging enabled: https://github.com/gemian/gemini-linux-kernel-3.18/blob/master/drivers/misc/mediatek/hdmi/sil9024/hdmi_drv.c there seem to be some printks..
 you could turn on..
 also the hdmi_drv_status always returns  no_device...
 [Edit] Have you tried to run the installer with sudo?
 I ran installer the installer with sudo too.
 I am not such an expert to build a kernel... and I probably have no such time to learn it today !
 @Pascal, That was my last idea 😅 Let's see what the installer developers have to say!
 Thanks a lot fr your help, again !
 @Pascal, That's a different thread, I mean, not related with your issue 👍
 @Pascal, You're welcome, and again I'm sorry I couldn't find a solution!
 Is there a dual sim phone that works with UT that is a bit higher spec than my old BQ4.5? I'm looking at affordable second hand options not new and expensive ones.
 Pro 5.
 By the way, what is the most recent device that runs ut
 Like I don't think there's one with snap 821/835/845
 https://m.ebay.co.uk/itm/95-new-Meizu-PRO-5-64GB-4gbRAM-LTE-Unlocked-DualSIM-21Mcam-NFC-FastCharge-/272196027342?nav=SEARCH
 @VeryOriginalUsername, FP2 probably
 @VeryOriginalUsername, perhaps htc 10, though it is incomplete port
 not sure if there's anything newer with an active port happening
 maybe galaxy s8?
 @dohbee, Stale port
 @dohbee, Marius ported Op6
 Which is currently the newest device
 It's incomplete just as htc 10 though
 Same state
 Yes, I'm waiting for a full port since this https://twitter.com/Mariogrip/status/987788101387997185
 wow
 Marius thought that it'd have USB 3
 It does not
 lol
 He did not actually port it to my knowledge
 That was a "I want to do this" tweet.
 Oh... any progress on the other OPOs (3&5)?
 @UniversalSuperBox, htc 10 does. wink wink nudge nudge
 Xperia XZ2 has 3.1 gen1
 The LG G5 has DP out/Slimport :v
 @Lyokanthrope, Htc 10 too
 It's even confirmed working my Marius
 [Edit] It's even confirmed working by Marius
 Ye
 and 1440p
 mmm pixels
 (Document) https://irc.ubports.com/5Nc03G1d.mp4
 Oh this is the super group, I got confused with "mmm pixels"
 Well I've run into some trouble. All my repairing of my Nexus 5 seems to have finally actually damaged something. How can I check (using cli) if the vibrate . . . thing? still works? It's not vibrating at all now and I'm not sure if it's software or hardware.
 test_vibrate?
 Well it's not even vibrating when I turn it off/on. It's probably hardware then 😕


For the worms that devour them will never die, and the fire that burns them will never go out.  For the worms that devour them will never die, and the fire that burns them will never go out.