[06:32] <acheron_uk> clivejo: is that attica MISSING from here? https://quickgit.kde.org/?p=attica.git&a=commitdiff&h=d262b645ee0d7fdd32dcab57553a60bfcb32dd36
[06:32] <acheron_uk> remeoved - ProviderManager::parseProviderFile(const QString &xmlString, const QString &url)
[06:33] <acheron_uk> added instead - ProviderManager::parseProviderFile(const QString &xmlString, const QUrl &url)
[06:35] <acheron_uk> which looks like one of the other symbols additions? maybe?
[07:46] <acheron_uk> amd64 builds of kconfigwidgets & kjsembed red due to unpackaged locale files in the arch-indep data packages that get done in the amd64 builds?
[07:48] <acheron_uk> they look like fairly mainstream locales to me so I guess they should go in?
[08:06] <yofel> acheron_uk: parseProviderFile(const QString &xmlString, const QUrl &url); is private in attica ProviderManager, so that's fine
[08:09] <acheron_uk> thanks. that failure is blocking a lot, if I read the dependency-waits correctly
[08:12] <acheron_uk> yofel: + _ZN6Attica15ProviderManager17parseProviderFileERK7QStringRK4QUrl@Base 5.23.0-0ubuntu1~ubuntu16.10~ppa1
[08:12] <yofel> The version should be 5.23.0
[08:13] <yofel> without all the packaging suffix
[08:13] <acheron_uk> is the 5.23.0-0ubuntu1~ubuntu16.10~ppa1 some other problem there? Or is that to be expected?
[08:13] <acheron_uk> too slow...
[08:14] <acheron_uk> instinct said it wasn't right... but I'm on the edge of my knowledge with symbols files.
[08:15] <yofel> that's the default, you can tell batchpattch to use a different version, so I usually always pass -v explicitely
[08:15] <yofel> but IIRC it also asks you what to use?
[08:16] <acheron_uk> yeah. I was just going to try patch to see what outputs I got
[08:16] <acheron_uk> only done it once and I did use -v for that.
[08:24] <acheron_uk> yofel: version jump also puzzles me, as was 4.96 in all previously. https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/attica/tree/debian/libkf5attica5.symbols?h=kubuntu_yakkety_archive
[08:24] <acheron_uk> 4.96.0
[08:25] <yofel> acheron_uk: the symbol says in which version of the software the symbol was added. So it's always the oldest possible version for a symbol
[08:26] <yofel> the idea is that dpkg-shlibdeps can use that information to make properly versioned dependencies for libraries
[08:27] <acheron_uk> so jump from 4.96.0 to 5.23 for those few would imply no new ones until the latest frameworks. then those came in
[08:27] <yofel> right
[08:28] <acheron_uk> good. that's clear. thanks
[09:36] <clivejo> yofel: RE: https://code.launchpad.net/~acheron/kubuntu-packaging/+git/attica/+merge/296760 Should the version in symbols file be 5.23.0 or is 5.23 ok?
[09:43] <acheron_uk> yes I had just that minute noticed and started chaging it
[09:43] <yofel> clivejo: whatever is set as version in the changelog. That should match
[09:44] <clivejo> Id prefer 5.23.0
[09:44] <yofel> (although it technically doesn't matter)
[09:44] <clivejo> but not sure if it makes any difference
[09:44] <acheron_uk> I'm resubmitting with 5.23.0
[09:44] <clivejo> I know the scripts act badly if I dont include the .0
[09:44] <yofel> it doesn't. You would have "Depends: foo (>= 5.23)" vs "Depends: foo (>= 5.23.0)"
[09:45] <yofel> yes, but the scripts don't care about the symbols file
[09:46] <acheron_uk> the top of original symbols file said '-# SymbolsHelper-Confirmed: 5.21.0 amd64 i386'
[09:47] <acheron_uk> so for consistency if nothing else, I'm matching that
[09:47]  * clivejo is learning stuff too
[09:56] <acheron_uk> clivejo: done. see what you think
[10:00] <clivejo> so I have reviewed and approved it
[10:00] <clivejo> does the merge happen automatically?
[10:00]  * acheron_uk basks in the glow of 'approval'
[10:00] <acheron_uk> not a clue
[10:11] <clivejo> must have to do something else ?
[10:12] <acheron_uk> definitely not right
[10:12] <clivejo> I thought after review and acept that would happen automatically
[10:13] <acheron_uk> it's just added my repo/branch to kubuntu-packagers as a separate item, rather than merged with the branch requested
[10:14] <clivejo> I dont see it
[10:14] <acheron_uk> is that what it automatically did? or was that you trying?
[10:14] <clivejo> you see it here?
[10:14] <clivejo> https://code.launchpad.net/~kubuntu-packagers/+git
[10:14] <acheron_uk> https://code.launchpad.net/kubuntu-packaging/+git
[10:15] <clivejo> oh I can see it there
[10:15]  * clivejo is confused
[10:18] <acheron_uk> bug in LP?
[10:18] <clivejo> no idea
[10:18] <clivejo> its new to me
[10:19] <acheron_uk> my merge requested ~kubuntu-packagers/kubuntu-packaging/+git/attica:kubuntu_yakkety_archive with the ~
[10:20] <acheron_uk> though not sure why it should matter if everything else seems the same on both urls
[10:20] <clivejo> LP URL's confuse me
[10:22] <acheron_uk> wait packagERS on one, packagING on the other
[10:23] <clivejo> oh yofel 
[10:24] <clivejo> yo yo Phil, we need your help :)
[10:24] <acheron_uk> I did let LP search find your branch as I thought that was safest
[10:26] <acheron_uk> the merge request I did is directer at kubuntu-packagING
[10:26] <acheron_uk> *directed
[10:27] <clivejo> ~kubuntu-packagers is owner/team
[10:27] <acheron_uk> the notes say for git     [url "git+ssh://USER@git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/"]      insteadof = kubuntu:
[10:29] <acheron_uk> so I cloned from that
[10:35] <acheron_uk> when I searched for the repo to merge to, LP gave me this: http://i.imgur.com/HGQA2FY.png
[10:40]  * acheron_uk knew it was too simple
[10:44] <acheron_uk> back in an hour or so
[10:59] <yofel> clivejo, acheron_uk: the kubuntu-packagers one is the correct merge target
[10:59] <yofel> or what was the question again?
[11:01] <acheron_uk> LP finds http://i.imgur.com/HGQA2FY.png
[11:02] <acheron_uk> and I accepted the top one obviously
 Plasma 5.7 beta next week ...
[11:06] <acheron_uk> and https://code.launchpad.net/~kubuntu-packagers/+git itself lists the attica repo as lp:~kubuntu-packagers/kubuntu-packaging/+git/attica
[11:07] <acheron_uk> but it ended up here as a separate repo https://code.launchpad.net/kubuntu-packaging/+git
[11:09] <acheron_uk> marcinsagol: requires QT 5.6? which we don't have?
[11:13] <yofel> acheron_uk: it *is* a seperate repository - owned by you
[11:14] <yofel> the ~kubuntu-packagers page shows all repositories owned by the team
[11:14] <yofel> the kubuntu-packaging page shows all repositories belonging to the project - *regardless* of owner
[11:15] <acheron_uk> ah. I get you
[11:16] <acheron_uk> didn't realise it would appear there
[11:16] <acheron_uk> so I presume from that someone still has to do the actual merge?
[11:18] <yofel> yes, doesn't look like auto-merging is implemented yet
[11:18] <acheron_uk> seems not. sorry, I saw that there and jumped to conclusions
[11:20] <acheron_uk> short sharp lesson in LP structure though ;)
[11:21] <yofel> Ok, LP detects pushing the merge at least
[11:23] <acheron_uk> yep, just got that email
[11:24] <yofel> Hm, now we need to figure out how to manage review notifications
[11:24] <yofel> so far that mail goes to all direct members of packagers. Which is a fairly short list
[11:25] <yofel> maybe we should direct the mail to -devel...
[11:25] <acheron_uk> did you merge that from LP website? if so, clivejo probably wants to know how, as I don't think he could see an option earlier
[11:26] <yofel> no, I did: git clone kubuntu:attica; cd attica; git checkout kubuntu_yakkety_archive; git remote add acheron lp:~acheron/kubuntu-packaging/+git/attica; git fetch acheron; git merge acheron/kubuntu_yakkety_archive
[11:26] <yofel> git push auto-closes the review at least
[11:28] <acheron_uk> was looking at the LP docs eralier, and even on the bzr side I couldn't find instructions for completing the merge on the web. that just pointed you to bzr command line
[11:29] <acheron_uk> so not surprised at all with git
[11:30] <acheron_uk> OK. so at least I can carry on doing some others later if I have the time. I'll know I'm not send patches into a 'black hole'
[11:32] <acheron_uk> thank you
[11:35] <acheron_uk> oh, is it safe to delete my repo now merged?
[11:49] <yofel> yes it is
[11:54] <acheron_uk> great. couldn't see why it shouldn't be, but it's too late to ask once already done
[11:54] <acheron_uk> thanks again for your patience
[11:59] <ahoneybun> thank you for your work acheron_uk :)
[12:07] <acheron_uk> ahoneybun: I've used and benefited from kubuntu for many years, so it is a pleasure to give even a little back :)
[12:08] <ahoneybun> that's great to hear acheron_uk 
[12:32] <BluesKaj> Hey folks
[13:17] <clivejo> acheron_uk: can you fix kconfigwidgets - 5.23.0-0ubuntu1~ubuntu16.10~ppa1 ?
[13:18] <clivejo> sorry, Im in and out today, but I am reading the backlog and Ive uploaded your fix as attica-kf5 - 5.23.0-0ubuntu1~ubuntu16.10~ppa2
[13:25] <acheron_uk> attica seems to have built
[13:28] <acheron_uk> if it's ok for the new man page language file to go into kconfigwidgets, then yes that seems fixable 
[14:38] <acheron_uk> clivejo: not sure about kconfigwidgets
[14:39] <acheron_uk> https://quickgit.kde.org/?p=kconfigwidgets.git&a=commit&h=2b55dc1cfbed5dbf08dfa534517db9c0dc26e54b and https://todo.kde.org/?controller=task&action=show&task_id=520
[14:40] <acheron_uk> suggests to me that they are moving over some translated man pages to the main package tarballs
[14:41] <acheron_uk> and perhaps renaming them i.e. preparetips.1 to preparetips5.1
[14:43] <acheron_uk> but I'm wary of the situation I half recall before, where they were still in the main translations as well (at least until the other packages caught up)
[14:48] <yofel> manpages shouldn't be an issue (esp. not with a rename), and I don't see any translations there
[14:48] <yofel> when you find actual translations then those might need to be removed from kde-l10n at the same time
[14:49] <acheron_uk> are these not translations? http://paste.ubuntu.com/17119034/
[14:50] <yofel> ah yeah, they are. But with the rename that's fine
[14:52] <acheron_uk> there is a libkf5configwidgets-data.manpages files, so naive logic would say they are specified in there?
[14:58] <clivejo> looks like they need to go in not-installed too - https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kconfigwidgets/tree/debian/not-installed?h=kubuntu_yakkety_archive
[14:59] <clivejo> and here https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kconfigwidgets/tree/debian/libkf5configwidgets-data.manpages?h=kubuntu_yakkety_archive
[14:59] <acheron_uk> looks like it
[15:01] <acheron_uk> and presumably they use the same format in the .manpage file as the existing 'debian/tmp/usr/share/man/man1/preparetips5.1'
[15:02] <clivejo> I dunno how that works though
[15:03] <acheron_uk> no. this wasn't presicely helpful https://www.debian.org/doc/manuals/maint-guide/dother.en.html#manpages
[15:12] <acheron_uk> so lacking any other rationale, just a change like http://paste.ubuntu.com/17119699/
[15:46] <clivejo> acheron_uk: worth a try!
[15:48] <acheron_uk> just trying in pbuilder for the hell of it
[16:01] <acheron_uk> clivejo: no missing files warning this time - but looking at the produced .deb with an archiver, can't see those man pages in there either  
[16:16] <clivejo> acheron_uk: I pushed those changes to LP to see what would happen and it gone orange
[16:16] <clivejo> just a Lintian warning - libkf5configwidgets-data: manpage-has-bad-whatis-entry usr/share/man/man1/preparetips5.1.gz
[16:17] <acheron_uk> yes. that's precisely what I got in my pbuilder
[16:18] <acheron_uk> Question is.... Did those man pages end up in the .debs?
[16:18] <clivejo> they look to be zipped
[16:20] <clivejo> ./usr/share/man/man1/preparetips5.1.gz
[16:21] <acheron_uk> that's just one. where are the translated ones?
[16:23] <clivejo> what does ./usr/bin/preparetips5 do?
[16:23] <acheron_uk> not a clue
[16:23] <clivejo> LOL
[16:23] <clivejo> blind leading the blind here !
[16:24] <acheron_uk> umm. in my pbuilder deb ./usr/share/man/man1/preparetips5.1.gz is in Ukranian
[16:24] <clivejo> did you ever join the #debian-qt-kde channel on Freenode?
[16:25] <clivejo> I have to go get some tea, but Ill try and ask there later
[16:26] <clivejo> Ive just poked LP to rebuild
[16:26] <acheron_uk> the rest of the stuff seems to be filtering through
[16:27] <clivejo> kjsembed - 5.23.0-0ubuntu1~ubuntu16.10~ppa1 seems to be the same man page issues as kconfigwidgets
[16:27] <clivejo> kwayland is a missing file, you want to do up a git diff or pull request for that?
[16:28] <clivejo> if you dont have time or dont want to, just let me know.  Im just trying to give you practice :)
[16:30] <acheron_uk> Your deb from LP has that man page in Ukrainian as well - so I guess it just substituted the last one in the list -./usr/share/man/uk/man1/preparetips5.1
[16:31] <acheron_uk> I looked a kwayland, and wasn't sure why that was only in amd64
[16:33] <acheron_uk> I have time to spare today :)
[16:53] <acheron_uk> "Plasma now depends on Qt 5.6.1" https://mail.kde.org/pipermail/release-team/2016-June/009489.html
[17:00] <acheron_uk> clivejo: think I understand now
[17:00] <mamarley> I guess when Plasma 5.7 is released it will be necessary to use the Qt from the landing PPA in order to get it to compile.
[17:01] <acheron_uk> going to have to do something as there is only one more possible 5.6.x
[17:02] <acheron_uk> after that its 5.7 or nothing
[17:38] <clivejo> theres LP down again
[17:45] <acheron_uk> clivejo: http://manpages.ubuntu.com/manpages/xenial/man1/dh_installman.1.html
[17:46] <acheron_uk> seems that is see all those files as not translations, so it's put them one after the other in the default location, overwriting each time so you still end up with just one. That last one, hence Ukranian
[17:48] <acheron_uk> on kwayland I presume you need this? https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kwayland/commit/?h=kubuntu_unstable&id=d17acdbca5e8c53472faae11e02bae1a71c8c029
[17:48] <acheron_uk> maybe adding as well http://packaging.neon.kde.org/cgit/frameworks/kwayland.git/commit/?h=Neon/unstable&id=6c2f280bc0eabb133d553c94a414e8e5975c5e53
[17:49] <clivejo> sure, can you do me up a debdif or pull reuest?
[17:51] <acheron_uk> OK
[18:11] <acheron_uk> clivejo: sent as merge to give you practice as well ;)
[18:12] <clivejo> thanks so much :P
 mhall119 ping
[18:52] <jimarvan> helloz :D
[18:53] <clivejo> hi jimarvan
[18:53] <acheron_uk> podcast in a few mins?
[18:53] <clivejo> yup :)
[18:53] <jimarvan> yeap
[18:53] <jimarvan> i have some nice chill trance music this time :P
[18:53] <acheron_uk> I'm reading lots about man pages. Not much helps, so the podcast will be nice
[18:54] <jimarvan> :D
[19:05] <acheron_uk> I can hear you ;)
[19:06] <clivejo> acheron_uk: join #kubuntu-podcast
[19:07] <acheron_uk> whoops forgot about that
[19:51] <mhall119> IrcsomeBot: pong
[19:51] <mhall119> or ovidiuflorin pong
 We've had some technical problems, but now we're back. We're live on this link: http://www.youtube.com/channel/UC-ChyPPcJSMUw2au2UyIKwQ/live
[19:52] <ahoneybun> mhall119: we're busy with the podcast now 
[19:52] <mhall119> IrcsomeBot: ovidiuflorin: I'm building kdevelop right now and my computer hates me :/
[19:52] <ahoneybun> not sure what he wanted tbh
[19:52] <ahoneybun> snap wise?
[19:52] <mhall119> ahoneybun: yeah
[19:52] <mhall119> also, that video requires flash :-P
[19:52] <ahoneybun> cool
[19:53] <mhall119> ahoneybun: yeah, I need to show you how to build with snaps this weekend
[19:53] <ahoneybun> mm not sure about snaps tbh but I'll listen
[19:53] <ahoneybun> lol
[19:53] <ahoneybun> mhall119: would you like the Nexus7 to have OTA11/Stable?
[19:54] <clivejo> mhall119: do you know the team working on Qt in Ubuntu?
[19:55] <mhall119> ahoneybun: yeah, that's new enough
[19:55] <mhall119> clivejo: yes
[19:56] <clivejo> any idea on the status of Qt 5.6.1?
[19:56] <ahoneybun> alright cool I grabbed the image this morning and will have it installed before tomorrow
[19:56] <mhall119> clivejo: it's kind of split between the SDK developers and d_ed I think
[19:56] <mhall119> clivejo: we're not even on 5.6 yet are we? Xenial is still 5.4 I think
[19:56] <clivejo> yeah
[19:57] <clivejo> but it looks like Plasma 5.7 will need Qt5.6.1
[19:57] <mhall119> clivejo: if you join #ubuntu-app-devel, the SDK devs are usually in there
[19:57] <mhall119> you can ask bzoltan or Mirv and they might be able to tell you timeframes (or blockers if that's the holdup)
[19:58] <mhall119> maybe t1mp
[19:58] <clivejo> what other projects use Qt?
[19:58] <mhall119> I honestly don't know who's building our QML and who's maintaining Qt these days
[19:58] <mhall119> clivejo: you mean other than the Ubuntu SDK and KDE?
[19:58] <clivejo> yes, do any other flavors use it?
[19:59] <ahoneybun> Lubuntu is working onit
[19:59] <ahoneybun> * on it
[19:59] <acheron_uk> lxqt?
[20:00] <mhall119> oh, right, I think they are going ot try and switch to LXQT for 16.10
[20:01]  * ahoneybun is very looking forward to SELF
[20:01] <mhall119> me too
[20:02] <mhall119> ahoneybun: I won't be there until mid-day Friday though, so can you help Jose setup and run the booth?
[20:02] <ahoneybun> yea sure with my 4 or so hours of sleep XD
[20:02] <mhall119> clivejo: I think some 3rd party commercial apps use qt, but they probably bundle their own version
[20:02] <ahoneybun> of course though
[20:02] <mhall119> ahoneybun: you driving up late tomorrow?
[20:03] <mhall119> I have to be at the airport by 6:30 on Friday, which means I'll be out the door by 5:30 :/
[20:03] <mhall119> am
[20:13] <ahoneybun> mhall119: sorry was writing something
[20:13] <mhall119> no worries
[20:13] <ahoneybun> mhall119:  leaving for the road around 4pm
[20:14] <mhall119> oh lord, that's like a 12 hour drive isn't it?
[20:14] <ahoneybun> Keith is driving till he needs a break
[20:14] <ahoneybun> yea we did that last year
[20:14] <mhall119> ok, at least you're taking shifts
[20:14] <ahoneybun> yea we have 4 people this time over 2
[20:14] <mhall119> well drive carefully, I-95 is always under construction
[20:15] <ahoneybun> yea Keith is very good at that
[20:15] <ahoneybun> driving lol
[20:16] <mhall119> ahoneybun: do you have a slimport adapter for your N7?
[20:17] <ahoneybun> I have one in general from the N4 days
[20:17] <mhall119> does it work with the tablet?
[20:17] <ahoneybun> it works but I've had some stable issues
[20:17] <ahoneybun> yea
[20:18] <mhall119> man, building kdevelop takes *forever*
[20:18] <acheron_uk> I only tried it once
[20:18] <clivejo> mhall119: did you create a snap for krita?
[20:19] <ahoneybun> someone did
[20:19] <mhall119> clivejo: yup, and I thought that one took a long time, but kdevelop is even bigger
[20:19] <clivejo> do you use debian packaging ?
[20:19] <mhall119> krita was a multi-person effort, sgclark hade started it, I ran with it from there and got help from upstream
[20:19] <mhall119> clivejo: for all of it's dependencies, yeah
[20:20] <mhall119> which isn't great, because it's using qt 5.4 instead of 5.6.1
[20:20] <clivejo> where did you get it?
[20:20] <mhall119> get which?
[20:20] <clivejo> the packaging?
[20:21] <mhall119> sgclark had started on a snapcraft.yaml, she gave me what she had and I continued it
[20:21] <ahoneybun> I think he means the source
[20:21] <clivejo> oh right
[20:21] <mhall119> oh, the source is from upstream's git
[20:21] <mhall119> the 3.0 branch
[20:21] <clivejo> I was working on Krita3 packaging - https://launchpad.net/~clivejo/+archive/ubuntu/krita/
[20:22] <mhall119> clivejo: someone from usptream had 3.0 pre-release builds in a PPA
[20:22] <clivejo> just wondered where the packaging came from
[20:22] <mhall119> I used build and runtime dependencies
[20:22] <mhall119> I used those to find the build and runtime dependencies
[20:23] <clivejo> are you calling it krita3 ?
[20:24] <mhall119> my snap? no
[20:24] <mhall119> just krita
[20:25] <clivejo> know anyone would sponsor me to get it into yakkety?
[20:25] <clivejo> the packaged version 
[20:26] <mhall119> I'm sure we can find someone
[20:26] <clivejo> and also updated calligra
[20:26] <mhall119> clivejo: do you not have upload rights?
[20:26] <clivejo> no
[20:26] <clivejo> Im newbie
[20:26] <mhall119> oh, ok
[20:27] <mhall119> right, it's yofel who has upload rights I think
[20:27] <clivejo> yup
[20:27] <mhall119> clivejo: if you ask in #ubuntu-devel during US/Europe workday times tomorrow you can probably get some help
[20:27] <acheron_uk> clivejo: this seems to work in pbuilder for kconfigwidgets http://paste.ubuntu.com/17128475/
[20:28] <acheron_uk> oops thought you had finished
[20:30] <clivejo> still listening to the podcast
[20:30] <acheron_uk> same here
[20:32] <clivejo> mhall119: is there anyone could act as a mentor/sponsor?
[20:32] <mhall119> clivejo: it will depend on who has time
[20:33] <mhall119> clivejo: I would recommend asking dholbach for help, he's on the community team but he works closely with the ubuntu developers and tracks upload sponsorship requests
[20:33] <mhall119> he can't sponsor it himself, but he would know who can 
[20:34] <mhall119> if he's not in #ubuntu-devel tomorrow, he will be in #ubuntu-community-team
[20:35] <clivejo> so many channels!
[20:35] <mhall119> heh, you have no idea :)
[20:35]  * mhall119 has 169 channels or PMs open 
[20:35]  * clivejo gulps
[20:36] <mhall119> most of them get ignored though, but they take up so little room in irssi I just never bother to /quit
[20:54] <sgclark> mhall119: is there not some sort of mentors list like debian has for clivejo getting sponsored? This is really a bigger problem as I too had that issue when looking into going for ubuntu developer.
[20:55] <sgclark> and Krita would be NEW so I don't think even yofel can sponsor it.
[20:55] <clivejo> is it new?
[20:56] <clivejo> I know the source is new, but the binary packages are same
[20:56] <sgclark> kf5 port of Krita? yes that would be new.
[20:56] <acheron_uk> only the kf5 version?
[20:56] <sgclark> How on earth can the binaries of new source not be new?
[20:57] <sgclark> maybe I am confused
[20:57] <clivejo> when I chatted to Debian guys they said to just use the old package names etc
[20:57] <mhall119> sgclark: if there is such a list, I don't know about it
[20:57] <clivejo> !info krita
[20:57] <mhall119> like I said, dholbach is a better contact for that than me
[20:58] <clivejo> so the new kf5 version is 1:3.0.0
[20:58] <sgclark> clivejo: krita is no longer bundled with calligra. Everything about it will be new.
[20:58] <sgclark> names of binaries is irrelevant in this case.
[20:58] <clivejo> I know, but they said to just use the old packaging
[20:59] <clivejo> like kdeconnect
[20:59] <mhall119> OMG! kdevelop finally finished building
[21:00] <sgclark> mhall119: wow, didn't you start that like a couple hours ago?
[21:00] <mhall119> sgclark: not quite that bad, I had to re-start it a couple times to fix build dependencies
[21:00] <mhall119> but...it did take a while
[21:00] <sgclark> ah
[21:00] <goddard> who is in charge of KDevelop package?
[21:01] <sgclark> mhall119: can you do a pull request on my packaging with the changes? I would appreciate it.
[21:01] <sgclark> goddard: anyone that wants to package it.
[21:01] <mhall119> sgclark: yup, will do
[21:01] <sgclark> thanks!
[21:01] <mhall119> sgclark: only very minor changes so far
[21:03] <sgclark> mhall119: the only thing I could get get sorted was templates.
[21:03] <sgclark> could not*
[21:04] <mhall119> sgclark: darn, got an error about plugins when trying to run it
[21:04] <mhall119> Could not find any plugins, aborting
[21:05] <sgclark> hmm
[21:05] <sgclark> oh I think I had to devmode it too
[21:06] <mhall119> I did too
[21:06] <mhall119> are any of the plugin included in the snap?
[21:06] <mhall119> I wonder if you have them on your system already, and that's why it's not complaining to you
[21:07] <sgclark> that is entirely possible
[21:07] <sgclark> I think I need to make a clean empty system to snap stuff it seems
[21:18] <sgclark> mhall119: output of ls -l /snap/kdevelop/current/usr/lib/x86_64-linux-gnu/qt5/plugins/ ?
[21:19] <sgclark> and you had the qt5-launch script?
[21:26] <clivejo> acheron_uk: merged
[21:26] <acheron_uk> TY :)
[21:26] <clivejo> sorry I took so long, was listening along in the Podcast incase they needed something
[21:27] <clivejo> uploaded to PPA
[21:27] <acheron_uk> no probs
[21:27] <clivejo> do you think that your fix for man pages is working?
[21:30] <acheron_uk> built I think
[21:30] <clivejo> is it installing all the man files?
[21:30] <acheron_uk> seemed ok in pbuilder. the man pages went in the right place. 
[21:31] <acheron_uk> If I looked in the deb and extracted the italian one, it was in italian
[21:31] <clivejo> could you do a merge request for that?
[21:31] <acheron_uk> only thing is it did away with the .manpages file
[21:32] <acheron_uk> but it would work while that was being used for me
[21:32] <acheron_uk> *wouldn't
[21:33] <acheron_uk> found a couple of other source packages with similar scheme to one I used though
[21:34] <acheron_uk> I'll submit a merge later or in the morning, and people can have a look. If they throw it out, no harm done
[22:31] <mhall119> sgclark: http://paste.ubuntu.com/17130197/ is /snap/kdevelop/100001/usr/lib/i386-linux-gnu/qt5/plugins
[22:32] <mhall119> which I also verified is $QT_PLUGIN_PATH
[22:33] <mhall119> and yes, it was launching via the qt5-launch script
[22:35] <sgclark> mhall119: ok, I have tons more than that, but I was buillding a ton more frameworks at one point. I am building cleanbuild now and will fix it up.
[22:35] <sgclark> thanks for testing lol
 o/
 @acheron_uk yes Plasma 5.7 will depend on Qt 5.6.1 from what I read on ml
 So it seems we can't start building it without this Qt version :(
[22:41] <mamarley> You can probably copy it from one of the landing-YYY PPAs, just for the purposes of staging/testing, since it isn't going to officially be in Yakkety for months, or in Xenial at all.
[22:42] <sgclark> that is what we always did, kubuntu has not packaged qt for a long time
 So it won't land in Yakkety?
[22:42] <mamarley> I meant that as opposed to just waiting until it was available in the official repository.
[22:43] <sgclark> it will land there eventually I reckon.
 But if this won't happen before Yakkety release, than we can't have new Plasma 16.10?
 *in 16.10
[22:59] <mhall119> sgclark: did you notice this when building kdevelop as well? https://bugs.launchpad.net/snapcraft/+bug/1590599
[23:03] <sgclark> mhall119: using cleanbuild it cannot even find C compiler lol
[23:25] <mhall119> sgclark: ah yes, I did the same mistake with krita, add build-essential to build-packages
[23:26] <sgclark> mhall119: ok ty