[01:51] <ahoneybun> !info snapcraft
[01:51] <ahoneybun> !info snapcraft xenial
[03:27] <ahoneybun> so far yakkety has been good
[03:29] <ahoneybun> http://weegie.edinburghlinux.co.uk/~jr/tmp/PIM.png
[04:05] <tsimonq2> another long day
[04:05] <tsimonq2> off to bed
[04:05] <tsimonq2> o/
[06:29] <Mirv> tsimonq2 / others: it looks like lxqt-config is blocking the Qt & KDE migration now since it depends on libkf5screen6 instead of libkf5screen7. I guess that could be resolved with a rebuild.
[06:37] <Mirv> please remind me to not promise to do combined Qt & KDE transitions at the same time in the future :D
[06:44] <Mirv> I'm worried about the KDE language packs and other stuff listed at the end of http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt but I can't figure out anything
[07:39] <Mirv> anyone up who could comment on muon / plasma-discover?
[07:40] <Mirv> muon-notifier and muon-updater transitional packages seem to depend on missing plasma-discover-updater package no longer available in the 5.7.3?
[07:40] <Mirv> they all come from src:plasma-discover but something seems broken
[07:51] <Mirv> right so Kubuntu seeds need to remove dependency on plasma-discover-updater which no longer exists
[08:02] <Mirv> I've uploaded new plasma-discover and trying to upload new kubuntu-meta
[08:08] <soee> o/
[08:39] <lordievader> Good morning.
[08:46] <acheronuk> Mirv: is new plasma wanting to remove installed kde language packs? if so, then that's a known issue and needs the packs updating with an applications update I think? same issue with our staging ppa if not used with the updated language packs in the staging-kdeapplications ppa
[08:57] <Mirv> acheronuk: I have no idea, but I can install language packs too on my yakkety-proposed
[08:58] <Mirv> acheronuk: so that's why I'm wondering why update_output.txt does list language packs there
[08:58] <Mirv> and I have kubuntu-full installed
[08:59] <Mirv> acheronuk: do you know which plasma package would be resposible of requiring / hinting at something like that?
[08:59] <acheronuk> Mirv: odd. not the issue I thinking off then
[08:59] <acheronuk> *of
[09:01] <sheytan> acheronuk: you asked yesterday about my kubuntu version when i asked about the plasma update. Yes, it is Xenial :)
[09:08] <acheronuk> Mirv: plasma-desktop data breaks << 4:15.12.3-0ubuntu3~ perhaps while the archive is 4:15.12.3-0ubuntu2 ?
[09:10] <acheronuk> oh, requires it? not sure
[09:15] <acheronuk> sheytan: backports are being worked on, but plasma 5.7 requiring Qt 5.6 while Xenial has non kubuntu stuff in it's archives which was built against Qt 5.5 and may break with Qt 5.6, means it needs care and testing
[09:16] <acheronuk> can't just put new Qt and plasma in a backports ppa and say "here you go, new stuff, but it may break things not KDE"
[09:20] <sheytan> acheronuk: I get it :)
[09:22] <Mirv> acheronuk: oh, ok.. so should I copy kde-l10n-* everything from somewhere?
[09:23] <Mirv> acheronuk: so right, actually I couldn't install those langpacks on kde, I just tried selecting them but it gives an error :(
[09:23] <Mirv> so now those are blockers too
[09:24] <Mirv> acheronuk: is there a PPA I can copy all required new packages from, and does it include every last one of them needed?
[09:25] <Mirv> I wish this would have been noticed earlier
[09:28] <Mirv> clivejo: acheronuk: can those 4:16.04.3-0ubuntu1~ubuntu16.10~ppa1 versioned packages be used for 16.10 archives or what can be done to unblock the situation?
[09:28] <Mirv> (I see those at staging-kdeapplications)
[09:29] <Mirv> or could I, as a workaround to get things going, lessen the plasma-desktop-data conflicts actually?
[09:31] <Mirv> I mean, is it a "nice to have" ie force up-to-date translation, or does it break something if yakkety stays with old kde-l10n packages for a few days until they are ready somewhere?
[09:33] <Mirv> if I'd eg remove only Breaks: but not Replaces:
[09:34] <acheronuk> Mirv: my guess would be it could survive with a lessened depends for a short while, but yofel clivejo etc are the ones to say for sure
[09:35] <Mirv> like this: http://paste.ubuntu.com/22676059/ <- yofel clivejo 
[09:35] <Mirv> acheronuk: ok
[09:36] <Mirv> acheronuk: any idea why kde-spectacle would show up on potential problem list? that I've installed on my yakkety-proposed and I can't see any problem again
[09:43] <Mirv> I'm prebuilding the updated plasma-desktop in a PPA and copying it later. Leaving the Replaces: in sshould take care of any potential corner cases of -data conflicting with any kde-l10n packages
[09:44] <acheronuk> Mirv: spectacle, maybe the replacing of libkf5screen6 with libkf5screen7 on an upgrade? that I think give a this/that package will be removed and something depends on it warning when upgrading, bit it works cleanly when it proceeds?
[09:45] <acheronuk> if not that, then I have no idea
[09:45] <Mirv> acheronuk: lxqt-config was like that, but kde-spectacle already depends on libkf5screen7
[09:45] <Mirv> and there is no problem in having it installed together with kubuntu-full
[09:45] <Mirv> so what I'm staring at is http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[09:46] <Mirv> if you search for (currently): easy: 275+0: a-92:a-28:a-28
[09:46] <Mirv> it will show per arch packages it thinks there is some problem... but I'm no absolute expert on deciphering update_output.txt
[09:51] <acheronuk> Mirv: I'm staring at that, and I'm honestly none the wiser for it!
[09:51] <acheronuk> if you are not an absolute expert at that, then i'm 2 or 3 levels lower down!
[10:02] <Mirv> acheronuk: I know the feeling! however it correctly identified the maeta package, language packs and lxqt-config.. I really wonder what's up with the rest
[10:06] <acheronuk> Mirv: slightly frustrating is when I did a Xenial to Yakkety upgrade a couple of weeks ago (old fashioned debian dist-upgrade way) straight to our staging ppa packages, I recall some issue with spectacle. Like I think it wanted it removed or somesuch, but it was installable again afterwards. but I didn't pay attention or investigate the issue as I perhaps should have :(
[10:28] <Mirv> acheronuk: I'll try some no-change rebuilds in a PPA, if they build I'll copy them over...
[10:28] <Mirv> desperate times
[10:29] <Mirv> of camitk itksnap jacktrip kde-spectacle nifti2dicom nomacs
[10:30] <Mirv> I can't see anything wrong with any of them and all of them installed on my yakkety-proposed together with kubuntu-full, lxqt, everything ..
[10:30] <Mirv> but in case there's anything that a rebuild would update wrt to dependencies, it's worth a shot
[10:30] <Mirv> especially until some kind person on #ubuntu-release would help me out in this deciphering work
[10:36] <soee> and more from Rio: www.youtube.com/watch?v=zoKSJpy3yNw
[10:47] <acheronuk> soee: ouch!
[10:54]  * soee thinks kmail should be renamed to hog
[10:55]  * acheronuk thinks kmail should just be a meta-package that installs thunderbird
[10:58] <acheronuk> if I wasn't fairly fond akregator for feeds, I would uninstall all trace of KDE PIM that I could
[10:58] <soee> if kmail would have thunderbird speed and better interface it could be good mail client
[10:58] <soee> acheronuk: i switched to feedly in my browser and phone
[11:00] <acheronuk> tried that, but didn't find it as friendly as I hoped. akregator I can just add a feed to it straight from Firefox, or right click and add a feed from the clipboard
[11:01] <acheronuk> plus I want a feed reader that sits in the systray telling me how many new stories it has
[11:03] <soee> ay :)
[11:03] <soee> kde apps should have LTS release like Plasma 5.8 will be
[11:04] <soee> and instead of doing some new that might break apps, just fix what is not working
[11:04] <soee> and finally have solid Plasma and Apps
[11:04]  * soee dreams ...
[11:17] <yofel> Mirv: hm, sorry about lxqt-config, I was aware of that 2 months ago, but as qt5.6 took so long I forgot about it. (I even had a ben file back then but by now I totally thought libkscreen7 was done..)
[11:17] <yofel> I'll upload l10n in a bit, that *shouldn't* break anything else, as all the breaks are in the app packages, not the translations
[11:18] <yofel> not that I have upload permissions for lxqt-config anyway
[11:32] <Mirv> yofel: no problem, that was at the end one of the easiest problems today.. hey great if you can upload l10n, maybe I won't need that plasma-desktop change then and also l10n packages are quick to build
[11:54] <Mirv> yofel: can you upload them directly or should I copy them from a PPA?
[11:55] <yofel> Mirv: l10n I can upload directly
[11:55] <Mirv> btw meanwhile there _are_ built packages that I copied from the applications PPA, just funny version numbers and maybe otherwise wrong too: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-073/+packages
[11:55] <Mirv> yofel: ok, great
[11:55] <Mirv> I'm using that silo for all kinds of rebuilds now
[12:05] <soee> what is good in  kmail is that inside notification i can enable button to directly open an email and have id displayed: http://i.imgur.com/6iX27jo.png
[12:15] <yofel> Mirv: l10n up, but I got a reject for kde-l10n-ast, so please copy that from the silo when you have time (version is ok)
[12:15]  * yofel thought the seed wildcard was supposed to catch that, but seems not..
[12:17] <Mirv> yofel: great! ast copied now.
[12:17] <yofel> thanks
[12:18] <Mirv> it just might be however that the whole Qt and KDE transition will stop at a GCC6 powerpc issue needed to be fixed to rebuild a package for a s390x issue :S
[12:18] <Mirv> I don't have currently an idea how to go forward after these other things are done
[12:31] <Mirv> yofel: oh, there is no -ast package currently in ubuntu, so my copy went to NEW queue
[12:31] <Mirv> also it doesn't matter therefore
[12:31] <Mirv> https://launchpad.net/ubuntu/yakkety/+queue?queue_state=0&queue_text=
[15:00] <acheronuk> clivejo: Mirv's qtchooser build Breaks: libqt5core5a (<< 5.5.1+dfsg-17~), libqtcore4 (<< 4:4.8.7+dfsg-7~)
[15:00] <acheronuk> xenial I think is libqtcore4 Candidate: 4:4.8.7+dfsg-5ubuntu2
[15:01] <Mirv> acheronuk: there's updated qt4-x11 too in 011
[15:01] <Mirv> due to that, and due to qtchooser required for other things (I forget now what)
[15:01] <acheronuk> so I think that is 1 reason why plasma* doesn't build
[15:02] <acheronuk> Mirv: ooh! thank you :)
[15:13] <BluesKaj> update-apt-xapi runs after every boot on yakkety, why does it need to update/upgrade so often ?
[15:13] <BluesKaj> never saw that on previous kubuntu releases
[15:20] <yofel> it shouldn't need to do that...
[16:12] <tsimonq2> Mirv: is that resolved ot 
[16:12] <tsimonq2> *or do you need me to do something?
[17:54] <Mirv> qqq
[17:54] <Mirv> :)
[17:55] <Mirv> tsimonq2: if you refer to the lxqt-config yes I recompiled that to upgrade dep to libkfscreen7
[17:55] <Mirv> seema ages ago since it was 12h ago in the morning
[17:55]  * Mirv -> need rest
[18:42] <acheronuk> clivejo: tested building breeze with Mirν's qt4-x11 and that seems to work ok.  
[18:43] <acheronuk> should that be ok to put in the staging ppa, then not sure if it would be best to copy it over or rebuild. with all the architectures that are enabled in that landing ppa, a copy over would eat up 2.8GB of ppa space!
[18:45] <mamarley> Isn't the PPA like 20GB though?
[18:49] <acheronuk> mamarley: think so, so can't see an issue, but thought I better mention it anyway.
[19:27] <clivejo> acheronuk:  is that the issue with the backported breeze not building? 
[19:27] <acheronuk> yes
[19:28] <clivejo> mind copying over the correct version?
[19:28] <clivejo> hi slhk
 update-apt-xapi runs after every boot on yakkety, why does it need to update/upgrade so often ?
 never saw that on previous kubuntu releases
 it shouldn't need to do that...
[19:28] <acheronuk> clivejo: if it's ok to include that in the staging ppa, then yes, I can do
[19:29] <clivejo> would you know why his system is running update-apt-xapi on every boot?
[19:29] <acheronuk> nope. I saw that and thought, WTF?
[19:30] <clivejo> sorry that was directed at slhk
[19:30] <acheronuk> oops
[19:32] <clivejo> acheronuk: sorry, Ive been out all day, just getting caught up
[19:32] <acheronuk> np
[19:33] <clivejo> the updated package is qt-chooser?
[19:34] <acheronuk> yes, with a depends on a higher version of qt4-x11 than is in the XX archive
[19:35] <clivejo> how did your version work?
[19:35] <acheronuk> which is why there is an updated version of qt4-x11 in that landing ppa
[19:35] <clivejo> will that break other components?
 plasma
[19:39] <slhk> clivejo: there is a cron job running update-axi weekly afaik
[19:41] <slhk> and maybe it is run by the updater, when is updates the apt lists of packages
[19:47] <acheronuk> clivejo: not sure why it worked with my version
[20:04] <acheronuk> clivejo: ah. my version was based on Neon's, as I recall 1st go didn't work for some reason. Neon's has those breaks removed.
[20:06] <clivejo> Im not sure if we should be updating qt4-x11 though
[20:07] <clivejo> yofel: ^^
[20:07] <clivejo> what would you do?
[20:11] <acheronuk> debian added those breaks here: https://anonscm.debian.org/cgit/pkg-kde/qt/qtchooser.git/commit/?id=b42dc5c88bf284e195dfe1017e65c5eccab73515
[20:12] <acheronuk> presumably they were just versioned on what debian had for qt4 at that point in time?
[20:22] <clivejo> what do you think?
[20:24] <clivejo> LOL
[20:24] <acheronuk> huh?
[20:24] <clivejo> Windows 10 Anniversary Update is borking boxes everywhere: Microsoft's response: Have you tried uninstalling it and installing it again?
[20:25] <acheronuk> LOL indeed
[20:25] <clivejo> regarding updating qt4-x11 what are your thoughts?
[20:25] <acheronuk> Neon went full on and did this: http://packaging.neon.kde.org/cgit/qt/qtchooser.git/commit/?h=Neon/release&id=b8d8e0eba28299b260f8ba887b017a447a5aecd0
[20:26] <acheronuk> but presumably we want qtchooser not to lose that option
[20:27] <clivejo> I dont have enought experience to know :/
[20:27] <clivejo> KDE Neon are only concerned about their stack, we have a ton of 3rd parrty software to be aware of and not break
[20:28] <acheronuk> so I guess it's either a qtchooser with those breaks removed or reduced, or updated qt4-x11 
[20:28] <acheronuk> clivejo: yep, I know
[20:28] <clivejo> whats your gut saying?
[20:29] <acheronuk> well, I already copied it over when you said "[20:28] <clivejo> mind copying over the correct version?"
[20:30] <clivejo> ok, we'll go ahead with it
[20:30] <acheronuk> but I guess you hadn't quite realised what it was at that point?
[20:30] <clivejo> LOL I still dont
[20:30] <clivejo> hard getting up to speed 
[20:30] <clivejo> my mind is still on the wasps nest Im trying to burn out!
[20:31] <acheronuk> that's why I waited until people popped up on here this evening, as I didn't know if it would be ok either
[20:31] <acheronuk> oooh. nasty wasps
[20:31] <clivejo> yeah
[20:31] <clivejo> I think one stung my pup on his paw
[20:32] <clivejo> and they are terrorising my bees
[20:32] <clivejo> so they got to go!
[20:33] <acheronuk> remember my father burning one out of compost heap they had somehow managed to get into
[20:33] <clivejo> they are in a rocky bank
[20:34] <acheronuk> him standing there wearing an old net curtain like a ghost, flame gun in hand, is an enduring image from my childhood
[20:35] <clivejo> LOL
[20:36] <clivejo> I just empied a litre of petrol into the nest entrance, let it soak for 10 mins and throw a lit pair of underwear into it!
[20:36] <acheronuk> he had one of these http://i.imgur.com/VBWvoVT.png
[20:37] <clivejo> ah cool
[20:37] <clivejo> I wasnt planning on standing around that long!
[20:38] <clivejo> swarm of angry wasps coming home after a hard days work!
[20:38] <acheronuk> don't blame you. they are gonna be a tad angry
[20:40] <acheronuk> hmmm. gtk update on YY has fubar'd my Firefox theme a bit
[20:41] <acheronuk> but Firefox developer is ok. guess they built that with a newer gtk
[20:45] <valorie> clivejo: wow, lolk
[20:45] <valorie> what a mental picture you paint
[20:46] <clivejo> :P
[20:51] <clivejo> it was old underwear!
[20:52] <clivejo> surprising how well they catch fire :/
[21:07] <valorie> such creativity, I love it
[21:30] <pursuivant> muon (master) v5.6.0-5-gc1b63af * Carlo Vanini: src (2 files in 2 dirs)
[21:30] <pursuivant> save and restore status of columns in changes preview widget
[21:30] <pursuivant> Save and restore status (e.g. shown/hidden, sorting) of columns in the
[21:30] <pursuivant> "preview changes" tab, like it is done for the list of packages.
[21:30] <pursuivant> http://commits.kde.org/muon/c1b63af4edbfdb6a4d4d55de16764f1d4801f24d
[21:34] <clivejo> reminds me, must run Muon and do a system update