[10:45] <santa_> gcc 5 uploaded to unstable https://packages.qa.debian.org/g/gcc-5/news/20150731T094053Z.html
[10:45] <santa_> ~ final judgement starts, we must delay it
[11:03] <doko> santa_, Riddell: new packages are now in silo 39, with a lot of renamed library packages
[11:08] <santa_> doko: thank you, gcc 5 is going to be available in ubuntu unstable today as scheduled, right?
[11:09] <doko> trying ...
[11:49] <santa_> off for a while, brb
[11:59] <soee_> Riddell: https://plus.google.com/u/0/103317747728601767381/posts/8Ne3cbXF6qg?cfem=1
[13:06] <santa_> ScottK: list of possible debian's qt ftbfs'es: https://paste.kde.org/pjai4grix
[13:21] <soee_> from g+: http://cdn.overclock.net/d/d9/d9fcbaaa_QP5DBAz.jpeg
[13:53] <ScottK> santa_: Did anyone work out fixes for those?
[13:58] <santa_> if I'm not mistaken debian and ubuntu aren't sharing symbols files for Qt
[13:59] <santa_> ScottK: so, replying to your question: for debian -> nope afaik; for ubuntu -> I don't know, better check with those canonical fellows
[14:00] <ScottK> OK.  Thanks.
[14:00] <ScottK> mitya57: Have you looked into Qt5/gcc5?
[14:01] <santa_> ScottK: oh, and just a small thing: qtenginio has last upload to unstable not available in git master, maybe you want to poke the debian's person in charge
[14:01] <ScottK> K.
[14:10] <ScottK> santa_: pushed.
[14:21] <santa_> ScottK: thank you, I will rebuild that one
[14:44] <santa_> ScottK: ok, qtenginio master does build so you can remove it from the list
[14:55] <ScottK> Thanks.
[15:33]  * Riddell blogs http://jriddell.org/2015/07/31/kubuntu-paddleboard-club/
[15:36] <lordievader> Hehe, the movie at the end :D
[15:42] <genii> Riddell: Is this where my donation money goes? ;)
[15:42] <sgclark> lol
[15:42] <lordievader> Looks liek you guys had a good time ;)
[15:42] <Riddell> genii: no no, that's all self funded :)
[15:42] <lordievader> like*
[15:42] <genii> Ah, carry on then!
[15:43] <soee_> oh if you do surfing etc. maybe someon is diving also ?
[17:00] <Riddell> ovidiu-florin: app-install-data
[17:02] <doko> Riddell, santa_ : GCC 5 in proposed, have fun
[17:02] <Riddell> doko: awooga!
[17:02] <Riddell> doko: will you copy over stuff from your PPA like qt?
[17:03] <doko> Riddell, it already is
[17:03] <doko> if you have new transitions, please document them in https://wiki.ubuntu.com/GCC5
[17:07] <mitya57> ScottK, it builds, but some symbols need to be removed (they are already marked as optional)
[17:08] <mitya57> no transition needed because Qt does not use STL in public API/ABI
[17:09] <mitya57> I'll probably do the symbols removal for qtbase right now (in experimental branch)
[17:17] <ScottK> K.  Thanks.
[17:19] <doko> mitya57, ScottK : you should do the double-conversion library transition first, and I think libproxy, and maybe wait until the new icu is uploaded
[17:19] <ScottK> K.
[17:22] <mitya57> doko, ok. I'm not planning of uploading anything to Ubuntu, but I'll wait before doing it in Debian.
[17:24] <lisandro> ScottK: here
[17:24] <ScottK> Welcome lisandro.
[17:24] <lisandro> _o/
[17:25] <lisandro> I don't know what was already discussed wrt qt5 and gcc5, but so far I could only find symbols changes in qtbase (haven't checked tthe rest yet)
[17:26] <lisandro> mitya57, doko: I'm already working on the symbols stuff on Debian, at least to have things moving
[17:26] <doko> you should do the double-conversion library transition first, and I think libproxy, and maybe wait until the new icu is uploaded
[17:27] <doko> or prepare these first. 
[17:27] <lisandro> apart that they need to be rebuilt with gcc5, is there anything else missing?
[17:28] <lisandro> because they should not bring symbols changes for us except they are breaking API
[17:28] <mitya57> Should *we* do the double-conversion library transition in Debian? We are not maintaining it…
[17:28] <doko> yes followup library transitions
[17:28] <doko> let me file a bug, I didn't yet
[17:29] <lisandro> well, if it's just waiting for the libs to be rebuilt then it's just a mteer of following the transition
[17:29] <lisandro> *matter
[17:29] <lisandro> and keeping symbols up to date
[17:30] <lisandro> mitya57: I've got some vtables dissapearing from qtxmlsomething
[17:30] <lisandro> but I *think* those are safe
[17:30] <doko> for every library where  new cxx11 appear, you should do a library transition
[17:30] <mitya57> qtxmlpatterns?
[17:30] <doko> I see, I need to better explain that ...
[17:31] <lisandro> from that part of qtbase, just a minute
[17:32] <santa_> lisandro: http://irclogs.ubuntu.com/2015/07/31/#kubuntu-devel.html
[17:32] <lisandro> doko: it's just a matter of waiting to get all rdeps rebuilt until we push qt, that's all
[17:32] <lisandro> except again if somthing is breaking api
[17:32] <doko> abi, not api
[17:32] <doko> the api stays the same
[17:33] <doko> read one of the bugs at https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=libstdc%2B%2B-cxx11;users=debian-gcc@lists.debian.org
[17:34]  * lisandro reads
[17:35] <lisandro> doko: ahhh, then normal transition stuff. We just need to wait until all the pieces are put together
[17:35] <lisandro> Qt exported symbols will not change if rdeps change abi
[17:35] <doko> if everybody waits, then this will take a year ...
[17:36] <lisandro> there is no other way around I'm afraid
[17:36] <lisandro> that's why the transition is handled in levels
[17:37] <lisandro> well, it's either that or binNMUing packages a lot of times
[17:37] <lisandro> at the end it's faster to simply wait 
[17:37] <doko> if you think, fine
[17:38] <lisandro> sure thing, but don't worry, the RT will prompltly mark us if an upload is needed
[17:39] <doko> the release team is having a vacation right now
[17:40] <lisandro> then I'll do my best to keep an eye on the transition as a whole too
[18:28] <shadeslayer> mhall119: so coming to ubucon berlin?
[18:40] <ahoneybun> shadeslayer: happy with the patch ?
[18:42] <shadeslayer> idk, maybe
[18:42] <ahoneybun> lol
[18:42] <shadeslayer> perhaps check why it was ma: same
[18:42] <shadeslayer> anyway, have to go
[18:43] <Riddell> ovidiu-florin: #ubuntu-bugs
[18:43] <ovidiu-florin> Riddell: https://launchpad.net/ubuntu-bugs
[18:43] <Riddell> ovidiu-florin: see bottom of https://wiki.ubuntu.com/BugSquad
[18:56] <soee> someone seen sitter lately ?
[18:58] <ahoneybun> he left I think wedsday
[19:00] <soee> is there someone else who can add slack integratin to kubuntu-ci (jenkins) >
[19:01] <ovidiu-florin> soee: we still haven't decided if we will use slack, since it's NOT free software
[19:01] <ovidiu-florin> even if it can be integrated with all our tools
[19:01] <ovidiu-florin> it's NOT free software
[19:02] <soee> ovidiu-florin: sure thing, i just wanted to test allthe possible and easy to do options :)
[19:03] <ahoneybun> not that many people use slack tbh (at least in here
[19:03] <ahoneybun> I do like the mobile app over any irc app that I know of
[19:05] <soee> well i didn't knot slack either till the Neos devs started to use is so as TYPO3 CMS community
[19:05] <soee> and i just love it :)
[19:05] <soee> i see elementary os devs use it
[19:06] <valorie> I would like to see IRC <> Slack integration before we dismiss it
[19:06] <soee> i would like to know what is teh potential risk using such "non free" software
[19:06] <soee> is is tgainst our policy ?
[19:06] <valorie> I don't like using non-free software, but all of us use lots of it on our smartphones
[19:06] <sgclark> it makes folks grumpy!
[19:06] <valorie> all the time
[19:08] <soee> well than i think now its more not if it is good/better than irc etc. but rather that it is not open sourced right ? :)
[19:14] <soee> valorie: when it comes to bots we can try this: https://github.com/ekmartin/slack-irc
[19:21] <soee> i'd liek to know also Riddell opinion
[19:28] <Riddell> what what?
[19:31] <ovidiu-florin> Riddell: waht do you think of us adopting slack?
[19:31] <soee> Riddell: what do you think about testing slack as a communication tool for Kubuntu team
[19:31] <Riddell> soee: it's a proprietary tool so sounds like a bad idea
[19:40] <clivejo> Riddell: calligra built OK !!
[19:40] <Riddell> clivejo: awooga :)
[19:40] <Riddell> clivejo: calligra-l10n needs doing if you fancy another task :)
[19:40] <clivejo> have you used it?
[19:41] <Riddell> calligra? I've no updated yet
[19:41] <clivejo> why does calligra need l10n?
[19:42] <clivejo> everyone speaks english!
[19:44] <ovidiu-florin> that's a joke, right?
[19:46] <clivejo> just a bit of craic Ovidiu
[19:47] <yofel> FWIW, compared to calligra, -l10n is childs play :P
[19:48] <clivejo> not if you havent a clue!
[19:48] <yofel> there was some script inside it that did most of the job
[19:48] <yofel> IIRC
[19:51]  * clivejo waits on ahoneybunto publish the "Kubuntu Packaging Bible"
[19:51] <yofel> if he ever does, that will indeed be one huge book...
[19:51] <Riddell> there's a script in kubuntu-automation that I tend to use for calligra-l10n
[19:52] <clivejo> got a link?
[19:54] <yofel> clivejo: bzr co lp:~kubuntu-packagers/+junk/kubuntu-automation
[19:55] <ahoneybun> clivejo: yofel it would be a best selller
[19:56] <clivejo> oh dear, this code is copyright
[19:56] <clivejo> #Copyright Jonathan Riddell 2013
[19:57] <valorie> soee: without the bot it is rather impossible to test it
[19:59] <clivejo> ahoneybun: make an audio version I can learn in my sleep
[20:10] <Riddell> clivejo: I licence it though don't I?
[20:11] <Riddell> calligra-l10n-package is the one, let me know if you have problems
[20:11] <Riddell> calligra-l10n is a weird package with multiple .orig tars for the source which is rare
[20:14] <clivejo> I need to understand what is going on
[20:15] <clivejo> "depot.kde.org:/home/ftpubuntu/%s/calligra-%s/calligra-l10n/*tar*" % (stability, version)
[20:16] <clivejo> cant I just use the local tarbal on my machine?
[20:16] <yofel> the local 20 tarballs?
[20:17] <yofel> I don't think that's supported
[20:17] <clivejo> Im confused
[20:17] <yofel> oh, you need access to depot for that script :/
[20:18] <clivejo> and what is depot?
[20:19] <yofel> a kde server where the tarballs are published before release
[20:20] <yofel> you can try the "upstream2orig" script inside calligra-l10n, that uses local files.
[20:20] <yofel> You can fetch the tarballs from download.kde.org for that
[20:22] <soee> test
[20:22] <soee> valorie: ping
 hi slack-irc
[20:26] <soee> ok sorry for the spam - testing tis bot :)
[20:29] <soee> this bot will not send all messages to #development hannel on slack
[20:29] <soee> *now
 does it work both ways?
[20:35] <soee> clivejo: yes, bot sends your message from slack to this irc channel
[20:36] <clivejo> I see
 soee++, now we can actually try this in a useful way :)
 i can also configure other channels like #kubuntu to log to #help slack channel for example, but this is not needed atm. i think
[20:39] <sgclark> !testers
[20:40] <sgclark> Plasma 5.3.2 vivid needs testing
[20:40] <soee> yay! :)
[20:40] <sgclark> neat
 Funny enough, here on the train slack's websocket connection is more stable than quassel's..
[20:46] <yofel> that slack-bot pings me every time I say something on slack is annoying though :/
[20:48] <yofel> otoh, you can answer pings on slack on irc..
 Hmm that could get bothersome 
[20:51] <clivejo> soee: you mentioned there was an app for slack?
[20:51]  * yofel is just installing that
[20:51] <yofel> there's also https://github.com/raelgc/scudcloud if you want something for the desktop
[20:52] <yofel> but that's not much different from just using the webapp
[20:52] <clivejo> I dont like leaving my computer on at night, will this allow me to stay logged in?
 clivejo: https://slack.com/apps
[20:53] <soee> clivejo: but all slack channels history you can see next day
[20:53] <soee> it will show you howmany unread messages you heve there
[20:53] <soee> no need for app etc. 
 That could be useful
[20:56] <valorie> soee: sorry was either offline or in other stuff
[20:56] <valorie> here now
[20:56] <valorie> until this whisky in my glass is gone
[20:57] <ScottK> Considering slack isn't free software, I don't see the point.
[20:57] <clivejo> mmmm whiskey
[20:58] <valorie> ScottK: just a test, no worries
 Cant you add #kubuntu-ci to slack like you did #kubuntu-devel?
[20:58] <valorie> and only for those who need to access IRC on their phones sometimes, and can't use quasseldroid etc.
[20:58] <ScottK> There are other IRC clients.
[20:59] <clivejo> the history feature is nice
[20:59] <valorie> yes
[20:59] <valorie> no argument
[20:59] <ScottK> Connectbot is pretty good.
[20:59] <valorie> since soee made a group, I thought it worthwhile to *test*
[20:59] <valorie> if people refuse to use it, we won't use it
[21:00] <clivejo> it can share media too?
[21:00] <valorie> unsure
[21:00] <valorie> you are in charge of it soee
[21:00] <valorie> !
[21:03] <soee> clivejo: media ?
[21:03] <clivejo> pdf, pics, audio etc
[21:04] <soee> slack - yes
[21:05]  * valorie logs off, turns off computer, goes to bed!
[21:05] <valorie> thank you, soee
[21:06] <valorie> niters all
[21:07] <clivejo> good night valorie
[21:09] <ScottK> soee: Are you in charge of this slack bot?
[21:09] <ScottK> I've read the terms of service for slack and I'm not at all comfortable with this IRC channel being copied to slack.
[21:10] <ScottK> Someone can ping me when it's turned off and I'll rejoin.  I have no intention of being bound by their TOS and it's not at all clear to me that relaying my IRC onto slack doesn't trigger that.
[21:10] <soee> ScottK: yes i just started it for a tets
[21:15] <sgclark> heh irc bit is the only feature I find useful. 
[21:16] <yofel> soee: can you turn the bot off please? we need Scott more than slack
[21:16] <soee> sure :)
[21:20] <soee> ok