[07:06] <soee> good morning
[09:58] <shadeslayer> yofel: pingly
[09:59] <shadeslayer> yofel: http://paste.kde.org/776720/
[09:59] <shadeslayer> what I ran : bzr-buildpackage-ppa -d saucy -y 13.10
[09:59] <shadeslayer> oh right
[09:59] <shadeslayer> nvm
[10:18] <smartboyhw> Good evening.
[10:19] <smartboyhw> How's kde-workspace?
[10:21] <smartboyhw> Erm, nobody fixed it for me?
[10:21] <smartboyhw> :O
[10:21] <smartboyhw> I thought I left it with someone able to takeover...
[10:22] <shadeslayer> debian/tmp/usr/share/kde4/services/searchproviders/freshmeat.desktop
[10:22] <shadeslayer> why that looks like a fun search provider
[10:22] <smartboyhw> Nice:)
[10:22] <smartboyhw> Some of my exam results came out today. Most crapped is Chinese:(
[10:23] <smartboyhw> Best subjects are chemistry , biology and computer
[10:24] <shadeslayer> congrats :)
[10:24] <shadeslayer> atleast you passed :P
[10:24] <smartboyhw> shadeslayer, eh hum it's still Form 3, I pass everything (I do have a good result at school)
[10:25] <shadeslayer> smartboyhw: IMHO passing is all that matters :P
[10:25] <shadeslayer> because even that was super hard at my uni
[10:25] <smartboyhw> shadeslayer, in Hong Kong, passing is just s***t
[10:25] <shadeslayer> maybe you should move to Austria
[10:25] <shadeslayer> where they complete their Bachelors in 12 years
[10:25] <smartboyhw> shadeslayer, :O
[10:25] <smartboyhw> 12 years for a single bachelor degree!?
[10:26] <shadeslayer> ask apachelogger
[10:26] <Riddell> smartboyhw: I had no access to the machine and it's an expensive machine that so I had to turn it off
[10:26] <smartboyhw> Riddell, oh dear....
[10:26] <smartboyhw> Can someone who has a fast machine build that?
[10:26] <Riddell> smartboyhw: ok I'll take a look
[10:26] <smartboyhw> It takes SO long for me to build kde-workspace..
[10:26] <smartboyhw> Riddell, thx:)
[10:26] <Riddell> it is a beast with its double compilation
[10:32] <Riddell> dpkg-source: warning: unknown information field 'Kde-Window-Manager-Creplaces' in input data in package's section of control info file
[10:32] <Riddell> smartboyhw: I don't suppose you worked out what that random warning is?
[10:32] <Riddell> I couldn't work it out at all last time i looked
[10:32] <smartboyhw> Riddell, I dunno what the hell is that... probably the extra C makes the issue...
[10:32] <smartboyhw> I never heard of that thing before though.
[10:34] <Riddell> having 4 builds of kwin is a bit nuts, I'm really not convinced that makes sense
[10:34] <smartboyhw> Hmm, we got a problem in kmajohgg
[10:34] <Riddell> and I remember martin saying we could get rid of one at least
[10:34] <Riddell> smartboyhw: what's up?
[10:34] <mgraesslin> Riddell: why do you have 4 builds?
[10:34] <Riddell> oh hello :)
[10:34] <smartboyhw> Riddell, python-twisted depends on 7 packages but they can't be installed...
[10:34] <smartboyhw> https://i142731151.restricted.launchpadlibrarian.net/142731151/buildlog_ubuntu-saucy-i386.kajongg_4%3A4.10.80-0ubuntu1~ubuntu13.10~ppa2_FAILEDTOBUILD.txt.gz?token=c89fa49fefe5edabc1bf8d42de71e186
[10:34] <Riddell> mgraesslin: debian/control:Package: kde-window-manager
[10:34] <Riddell> debian/control:Package: kde-window-manager-gles
[10:34] <Riddell> debian/control:Package: kde-window-manager-active
[10:34] <Riddell> debian/control:Package: kde-window-manager-active-gles
[10:35] <shadeslayer> we have 4 packages, but it only builds twice
[10:35] <mgraesslin> good
[10:35] <shadeslayer> once for desktop, once for active
[10:35] <mgraesslin> just wanted to point out that it only needs two build
[10:35] <Riddell> right, once with -DKWIN_PLASMA_ACTIVE=true and once without
[10:36] <mgraesslin> for active the gles package does not make sense
[10:36] <mgraesslin> active should always be gles
[10:36] <Riddell> because it's always gles?
[10:36] <Riddell> right
[10:36] <shadeslayer> makes sense, lets drop that then
[10:36] <mgraesslin> for desktop you could merge kde-window-manager and kde-window-manager-gles
[10:37] <mgraesslin> I think that's from the time when the build system was not able to build both binaries at the same time
[10:37] <Riddell> mgraesslin: merge as in put in the same binary package?
[10:37] <mgraesslin> yes
[10:37] <mgraesslin> it would then have kwin and kwin_gles in one package
[10:37] <mgraesslin> that reminds me: I need to send a mail to packagers about the Wayland dependencies
[10:38] <Riddell> we've added libwayland-dev to the kde-workspace build-depends
[10:38] <Riddell> anything else needed?
[10:38] <mgraesslin> runtime dependencies
[10:39] <mgraesslin> without Weston it doesn't make much sense
[10:39] <Riddell> mm
[10:39] <mgraesslin> so I would make that a recommends
[10:39] <Riddell> but do we want weston installed for our default X only setup
[10:40] <Riddell> mgraesslin: if kwin and kwin_gles are in the same binary how does it choose between them (in startkde presumably)?
[10:40] <mgraesslin> like before: you have to set the env variable in case you want kwin_gles
[10:40] <Riddell> right
[10:40] <mgraesslin> http://userbase.kde.org/Desktop_Effects_Performance#kwin_gles
[10:41] <Riddell> smartboyhw: instead of building the whole of kde-workspace twice I think it'll be no problem to just build kwin twice
[10:42] <smartboyhw> Riddell, OK.
[10:42] <mgraesslin> yes that works
[10:42] <mgraesslin> KWin can be built without kde-workspace
[10:42] <smartboyhw> For now, let me fix some analitza red lights.
[10:42]  * mgraesslin uses that in Jenkins
[10:42] <smartboyhw> Missing symbols (again)
[10:42] <shadeslayer> smartboyhw: analitza needs SO version bumping
[10:42] <smartboyhw> shadeslayer, alright.
[10:42] <shadeslayer> apol hasn't done that :/
[10:43] <smartboyhw> meh:P
[10:43] <smartboyhw> So?
[10:43] <shadeslayer> hm?
[10:43] <shadeslayer> 2 public symbols were changed
[10:43] <shadeslayer> breaking ABI
[10:43] <shadeslayer> so they need to bump the SO version
[10:43] <smartboyhw> Alright, kdegraphics-mobipocket then.
[10:44] <smartboyhw> Coding error it seems....
[10:44] <Riddell> smartboyhw: there was something in https://notes.kde.org/p/kubuntu-ninjas about analitza
[10:44] <smartboyhw> Riddell, just read it:)
[10:44] <Riddell> yeah the so version
[10:44] <smartboyhw> Looks the kdegraphics-mobipocket got a completely broke generator_mobi.cpp
[10:45] <shadeslayer> huh
[10:45] <shadeslayer> GENERIC_LIB_SOVERSION
[10:45] <shadeslayer> set_target_properties(analitzagui PROPERTIES VERSION ${GENERIC_LIB_VERSION} SOVERSION ${GENERIC_LIB_SOVERSION} )
[10:47] <Riddell> set by kdelibs I think
[10:47] <shadeslayer> oh
[10:47] <Riddell> means he needs to start setting it manually
[10:47] <shadeslayer> this is the first time I've encountered GENERIC_LIB_SOVERSION
[10:47] <shadeslayer> I guess I'll email Aleix so that he remembers to do this
[10:49] <mgraesslin> Riddell: if you want to pass something on about this Mir/KWin thread: 11 files changed, 1588 insertions(+), 1020 deletions(-)
[10:50] <mgraesslin> that's the difference I created since yesterday in the Wayland backend - the file Thomas looked at
[10:51] <mgraesslin> plus uncommitted changes: 5 files changed, 108 insertions(+), 5 deletions(-)
[10:51] <mgraesslin> it's kind of insane to try to do any adoption of KWin right now
[10:52] <mgraesslin> but we would love to see the Wayland help we got promised years ago ;-)
[10:53] <smartboyhw> Riddell, shadeslayer confirmed: kdegraphics-mobipocket failed due to coding error.
[10:53] <shadeslayer> oh
[10:53] <shadeslayer> pastebin error?
[10:53] <shadeslayer> tsdgeos: ^^
[10:53] <Riddell> you just move so fast mgraesslin all anyone else can see is a blur!
[10:53] <smartboyhw> http://paste.kde.org/776810/
[10:53] <shadeslayer> smartboyhw: could be a gcc 4.8 issue
[10:54] <smartboyhw> shadeslayer, look at the paste and determine:)
[10:54] <Riddell> smartboyhw: places to check for a fix would be upstream git and if other distros have managed to compile it
[10:55] <Riddell> also check if 4.10.4 compiles or not in saucy
[10:56] <smartboyhw> Riddell, second sentence confirmed it does.
[10:56] <mgraesslin> Riddell: that's the reason why the Wayland backend is marked as experimental in 4.11 - it's just a random development snapshot which works
[10:56] <smartboyhw> in saucy
[10:56] <mgraesslin> (works with limitations, e.g. gles doesn't work)
[10:57] <smartboyhw> Riddell, last commit is @ 6/6/2013, aligning to okular patch.
[10:57] <smartboyhw> I'm starting to think that since okular didn't build then it can't build also.
[10:58] <smartboyhw> 4.10.80 I mean.
[10:58] <mgraesslin> Riddell: did I get correct that the discussion is mainly about how the stack will look like in 14.04?
[10:58] <smartboyhw> okular can't build due to plasma-active-dev:O
[10:58] <smartboyhw> kde-runtime is the prob I think...
[11:01] <Riddell> mgraesslin: only timescale I've seen (I've not looked hard) is robert ancell saying "We're aiming to be able to preview XMir in 13.10. We're doing the work right now to integrate Unity 7 with XMir.
[11:01] <Riddell> smartboyhw: oh wouldn't okular be a dep of that?
[11:02] <smartboyhw> Riddell, yep. Okular (>=4.10.80) should be the dep. But it failed to build also...
[11:02] <Riddell> mgraesslin: so should we build against libwayland or just ignore it?
[11:03] <smartboyhw> Riddell, speaking of it, you have a nice launchpad karma: 88888
[11:04] <Riddell> 8 is good luck in china isn't it? :)
[11:04] <Riddell> smartboyhw: did you get this error?..-- DebianABIManager: unable to find CMake target 'solidcontrol' for package 'libsolidcontrol4abi2'. Please set X-CMake-Target
[11:04] <Riddell> -- DebianABIManager: unable to find CMake target 'solidcontrolifaces' for package 'libsolidcontrolifaces4abi2'. Please set X-CMake-Target
[11:04] <smartboyhw> Riddell, well, you have to remove these two packages.
[11:04] <smartboyhw> It's KOed.
[11:04] <smartboyhw> Riddell, yeah, 8 is gd luck in China
[11:04]  * smartboyhw has painfully discovered that:P
[11:05] <smartboyhw> I mean the build thing.
[11:05] <yofel> what's there to remove?
[11:06] <smartboyhw> yofel, the solid::control.
[11:06] <yofel> ah right
[11:06] <smartboyhw> Check yesterday's backlog.
[11:06] <mgraesslin> Riddell: I highly recommend to build against libwayland
[11:07] <mgraesslin> that's why I need to send a mail to packagers
[11:07] <yofel> Riddell: yeah, that got remove in 4.11, it was used by networkmanagment it seem and was killed with it
[11:07] <yofel> *removed
[11:07] <mgraesslin> Riddell: ok, let's consider 14.04 - you will be shipping KWin 4.11
[11:07] <mgraesslin> Riddell: anything else won't make sense
[11:07] <mgraesslin> Riddell: we had already the dependency freeze for 4.11 and that does not include Mir - neither with an XMir nor directly
[11:08] <mgraesslin> we will not support any setup which is not X11 based in the long term support version of KWin 4.11
[11:08] <mgraesslin> so if 14.04 would have a setup with XMir replacing the normal X Server we would not be able to support it
[11:08] <shadeslayer> yofel: btw where have you traditionally put the qmldir ? in a install file or a .dirs file
[11:09] <mgraesslin> this means we would just have to close all bug reports of Kubuntu users
[11:09] <shadeslayer> have -./usr/lib/kde4/imports/org/kde/dirmodel/qmldir
[11:09] <Riddell> mgraesslin: mm in kubuntu 13.10 we will be shipping kwin/kde sc 4.11
[11:09] <yofel> shadeslayer: uh, install file
[11:09] <Riddell> mgraesslin: 14.04 would be kde 4.12 no?
[11:09] <shadeslayer> any reason not to put it in a .dirs file?
[11:09] <yofel> shadeslayer: does debian do it differently?
[11:09] <mgraesslin> Riddell: there is no 4.12 of KWin
[11:09] <shadeslayer> no idea, I haven't checked
[11:09] <mgraesslin> there will be a KDE SC 4.12
[11:09] <mgraesslin> but not with kde-workspaces
[11:10] <shadeslayer> yofel: any recommendations on where would be a good place to look?
[11:10] <Riddell> mgraesslin: ah right
[11:11] <mgraesslin> getting back to my point: with an XMir in between we have no chance to figure out whether a problem is a general problem or a Ubuntu specific problem
[11:11] <mgraesslin> and we would not have the manpower to carry such an overhead
[11:11] <mgraesslin> all bugs would be RESOLVED DOWNSTREAM
[11:11] <Riddell> mgraesslin: right, I hate the very idea of running kwin on x on mir, I'd be very reluctant to do that for the reasons you say
[11:11] <yofel> shadeslayer: hm, any of the merged packages that could have a qmldir
[11:11] <mgraesslin> I don't think that this would look good for the distribution
[11:12] <shadeslayer> right, like?
[11:12] <Riddell> when I asked if they would run unity on mir on wayland I got a "nope" which is pretty telling
[11:12] <shadeslayer> we have like a bazillion packages
[11:12] <shadeslayer> lets see, a game that was ported to QML maybe
[11:13] <yofel> debian/plasma-widgets-workspace.install:usr/share/kde4/apps/plasma/plasmoids/org.kde.notifications/contents/ui/NotificationDelegate/qmldir
[11:13] <yofel> debian/plasma-widgets-workspace.install:usr/share/kde4/apps/plasma/plasmoids/org.kde.notifications/platformcontents/touch/ui/NotificationDelegate/qmldir
[11:13] <shadeslayer> install file it is
[11:15] <Riddell> mgraesslin: so my current thinking is we expect kubuntu 14.04LTS to have KWin on X and for 14.10 we can see if switching to wayland is ready using packages synced from debian
[11:15] <mgraesslin> yes
[11:15] <Riddell> which will kill any ability to run ubuntu desktop and kubuntu switching at login but oh well
[11:15] <mgraesslin> but you should be prepared that also in the Wayland world you might need to provide X
[11:15] <mgraesslin> if NVIDIA and Catalyst do not support Wayland at that time you are forced to provide X
[11:16] <Riddell> one worry is for the live CD stuff, that ubiquity-dm is faffy
[11:16] <mgraesslin> so from looking at Robert's mail - none of the possibilities a to g suit us
[11:17] <mgraesslin> that is upstream will support: KWin on X
[11:17] <mgraesslin> and KWin on Wayland
[11:17] <mgraesslin> anything else can be done downstream
[11:17] <mgraesslin> but at least without any support from me
[11:17] <mgraesslin> maybe someone else will help
[11:17] <mgraesslin> but to my knowledge no KWin developer is using Ubuntu
[11:18] <smartboyhw> The question is: Who will help?
[11:18] <Riddell> smartboyhw: we have offers from e.g. thomas voss but I really don't want to take them up
[11:18] <Riddell> there's no way he can support kwin on mir part time
[11:18] <Riddell> and do a good enough job
[11:18] <mgraesslin> unlikely - quite true
[11:18] <Riddell> I just don't believe it's possible
[11:18] <shadeslayer> ^^
[11:18] <mgraesslin> especially without any help from upstream
[11:19] <mgraesslin> and we don't make it easy to fork kwin - we have a huge churn
[11:19] <shadeslayer> plus with the amount of code churn that mgraesslin says happens in KWin, it'll be impossible to do it part time
[11:19] <Riddell> and that would be the mother of all distro only patches which we have a policy against
[11:19] <shadeslayer> will require full time work
[11:19] <mgraesslin> (for adding the Wayland backend I changed our internal interfaces)
[11:19] <mgraesslin> also some assumptions in the thread are wrong
[11:20] <mgraesslin> I do not plan to have KWin with a pluggable windowing system interface
[11:20] <mgraesslin> KWin is a Wayland compositor
[11:20] <mgraesslin> just currently only supporting X11
[11:20] <mgraesslin> that has been my planning for a few years now
[11:20] <mgraesslin> I don't change that just for the fun of it :-)
[11:22] <Riddell> a wayland compositor only supporting x11?  I'm not sure I understand that
[11:22] <mgraesslin> I consider Wayland as our primary windowing system
[11:22] <mgraesslin> we just don't support it yet
[11:24] <shadeslayer> I can't wait to try out wayland stuff in 4.11 :P
[11:25] <Riddell> smartboyhw: you can install weston now and run it on X, works fine
[11:25] <Riddell> shadeslayer: rather
[11:25] <mgraesslin> I was able to use it two days in full production, then my Intel card froze
[11:26] <mgraesslin> http://wstaw.org/m/2013/06/18/plasma-desktopt14572.png - Weston with KWin as client and XRender compositing backend
[11:27] <shadeslayer> mgraesslin: btw any ideas why this would happen on a multi monitor setup? http://i.imgur.com/yALluEB.png
[11:27] <shadeslayer> when using cover switch
[11:27] <mgraesslin> yes
[11:28] <shadeslayer> oh?\
[11:28]  * mgraesslin cannot do math
[11:28] <shadeslayer> I see :D
[11:28] <shadeslayer> it works fine on the bigger monitor
[11:29] <shadeslayer> mgraesslin: bug already reported?
[11:29] <shadeslayer> or should I report one for 4.11 if I can reproduce it there
[11:29] <mgraesslin> of course it is reported
[11:29] <mgraesslin> years ago
[11:29] <shadeslayer> hah
[11:29] <mgraesslin> https://bugs.kde.org/show_bug.cgi?id=184874
[11:30] <mgraesslin> 2009 - nice
[11:30] <shadeslayer> KDE 4.2.0 @_@
[11:31] <mgraesslin> my Math skills got worse since then
[11:31] <shadeslayer> my bug is slightly different btw, windows are fine, but the black gradient is misplaced
[11:31] <mgraesslin> no the windows are wrong
[11:31] <shadeslayer> oh
[11:32] <mgraesslin> they should be at the edge of the screen
[11:32] <shadeslayer> ah, and I thought the windows were fine but the gradient was misplaced
[11:32] <shadeslayer> ( which looks more likely, since the windows IMHO appear to be placed correctly )
[11:34] <shadeslayer> you know better obviously :)
[11:34] <mgraesslin> yeah I know that I lost all my math skills :-(
[11:35] <shadeslayer> hehe
[11:36] <mgraesslin> one of the reasons why I don't want to write effects anymore
[11:53] <apachelogger> so hot again -.-
[11:55] <Riddell> apachelogger baby you're always hot
[11:56] <smartboyhw> Riddell, :O.....
[11:57] <yofel> lol
[11:57] <yofel> here it's not as hot as yesterday, + the fridge isn't empty ^^
[11:57] <smartboyhw> It's very hot here.
[11:57] <smartboyhw> 29C
[11:57] <smartboyhw> Tomorrow 33C
[11:58] <apachelogger> well, I am totally going to spend the day at the pool, see you in the evening :P
[11:59] <yofel> yesterday it was 36°C here, today it's 32
[12:08] <shadeslayer> well .. good thing I didn't go for my vacation
[12:08] <shadeslayer> would have been swept away by all the water due to cloud bursts and rainfall
[12:09] <smartboyhw> shadeslayer, :)
[12:09] <shadeslayer> Riddell: Netflix doesn't have Dr Who S5
[12:09] <shadeslayer> OTOH it's 31 degrees here, but 80% humidity
[12:10] <yofel> do you at least have a fan? I don't -.-
[12:11] <Riddell> oh you wimps, heat is a feature of living in india and continental europe, if you want cloud and cold come to scotland
[12:12] <Riddell> shadeslayer: depending on your numbering system that might be 40 years old
[12:13] <shadeslayer> Riddell: the one that features Matt Smith playing the doctor for the first time
[12:14] <Riddell> fishfingers and custard!
[12:16] <shadeslayer> heh
[12:19] <Quintasan> JontheEchidna: I get Muon crashing when trying to use Firefox installed
[12:19] <Quintasan> Installer*
[12:19] <Quintasan> logs coming soon
[12:21] <Quintasan> JontheEchidna: http://paste.ubuntu.com/5776939
[12:22] <JontheEchidna> Quintasan: looks like bug https://bugs.kde.org/show_bug.cgi?id=320230
[12:23] <Quintasan> JontheEchidna: Quite possible, want me to add the backtrace there?
[12:23] <JontheEchidna> Quintasan: nah, that's fine
[12:27] <shadeslayer> yofel: kcm_pimactivity seems like it could go in kontact?
[12:41] <yofel> shadeslayer: possibly. I pondered libkdepim4 as that has plugin files too and should always be there. (you can use kmail without kontact)
[12:47] <shadeslayer> possibly
[12:49] <shadeslayer> yofel: similar thing with usr/bin/asapcat
[12:49] <shadeslayer> which is a developer tool
[12:50] <shadeslayer> but I just put it in akonadi-server for now
[12:50] <BluesKaj> Hiyas all
[12:52] <shadeslayer> bbl
[12:59] <tsdgeos> shadeslayer: may be that you're building against an old okular, but hey let's blame people coding!
[13:18] <shadeslayer> tsdgeos: well, technincally it is a upstream issue because someone didn't bump the minimum requirement on Okular in CMakeLists.txt
[13:19] <tsdgeos> shadeslayer: you know where the repo is
[13:19] <shadeslayer> *nod*
[13:30] <shadeslayer> tsdgeos: review plz http://paste.kde.org/777050
[13:32] <Riddell> shadeslayer: don't we have a versioned build-depends on okular in that package?
[13:33] <yofel> it wasn't part of kdesc-dev-latest-saucy.txt though, I just added it
[13:34] <shadeslayer> yup  okular-dev (>= 4:4.10.80),
[13:34] <shadeslayer> ah okay
[13:36] <tsdgeos> then why the compile error?
[13:36] <shadeslayer> tsdgeos: that version was recently changed
[13:36] <tsdgeos> ah
[13:36] <shadeslayer> Riddell: but kdegraphics-mobipocket should complain if it finds a old okular imho
[13:37] <tsdgeos> shadeslayer: if the aptch works, go on
[13:37] <smartboyhw> shadeslayer, that's the prob I'm having here:P
[13:38] <shadeslayer> tsdgeos: it works in the sense that cmake can't find okular 4.10.80 on a 4.10.4 system :)
[13:38] <smartboyhw> The first thing though: Someone repair okular:P
[13:38] <tsdgeos> good then
[13:38]  * shadeslayer nominates smartboyhw for that
[13:38] <smartboyhw> shadeslayer, it involves kde-runtime.
[13:38] <shadeslayer> I uploaded that
[13:39] <smartboyhw> shadeslayer, hmm but it also involes plasma-active...
[13:39] <yofel> huh?
[13:39] <yofel> -- DebianABIManager: CMake target 'okularcore' SOVERSION does not match package name 'libokularcore2abi1'
[13:39] <shadeslayer> ^^
[13:39] <yofel> that looks pretty straight forward
[13:39] <shadeslayer> how does that involve plasma active
[13:40] <smartboyhw> yofel, shadeslayer https://i142414905.restricted.launchpadlibrarian.net/142414905/buildlog_ubuntu-saucy-amd64.okular_4%3A4.10.80-0ubuntu1~ubuntu13.10~ppa2_FAILEDTOBUILD.txt.gz?token=822c3ac9ce5ef35e6ee788890e39fda1
[13:40] <shadeslayer> your token is showing
[13:40] <smartboyhw> Somebody added it as a strict build-dep.
[13:40] <yofel> oh ok, archive skew
[13:41] <Riddell> all this OptiPNG does add to the build time a lot
[13:41] <shadeslayer> yofel: btw thanks for mentioning hp systray the other day
[13:41] <shadeslayer> yofel: fixed the issue where printing PDF's would cut off the top on my printer because page scaling wasn't happening
[13:41] <yofel> shadeslayer: that turned out to be actually useful? ^^
[13:41] <yofel> aah
[13:41] <yofel> need to check if I can do the same here
[13:42] <smartboyhw> Riddell, you didn't fix calligra for me:(
[13:42] <Riddell> smartboyhw: it's on he todo!
[13:42] <shadeslayer> yeah, I couldn't for the life of me figure out how to make it print PDF's properly
[13:42] <smartboyhw> Riddell, he!?
[13:42] <yofel> okular cuts off parts when I have the duplexer in the printer but I set it to single-sided
[13:42] <smartboyhw> *the you mean?
[13:42] <Riddell> smartboyhw: it's on the todo!
[13:42] <shadeslayer> chrome / okular  both cut them off
[13:42] <smartboyhw> Riddell, :)
[13:42] <smartboyhw> great:)
[13:42] <shadeslayer> yofel: dunno, cuts it off on single sided as well
[13:43] <yofel> yeah, that's why I used evince lately when I needed properly printed PDF's :(
[13:43] <shadeslayer> so I had to copy the PDF's over to a Windows machine and printed using Adobe thingamajing
[13:43] <shadeslayer> *thingamajig
[13:43] <yofel> lol, evince didn't work?
[13:43] <yofel> wait, we have the adobe thing for linux too
[13:44] <shadeslayer> we do?
[13:44] <shadeslayer> also, evnice, I prefer not to install gtk apps, and the desktop was already on the network, was a simple copy and print
[13:44] <yofel> acroread is in partner
[13:45] <shadeslayer> but yeah, the systray thing has a option to scale documents
[13:45] <yofel> 9.5.5 at least
[13:45] <shadeslayer> worked for the 5 pages I printed today
[13:45]  * smartboyhw is expecting ninjas PPA build failure messages:P
[13:47] <smartboyhw> Now it makes sense
[13:47] <smartboyhw> Unpacking plasma-active (from .../plasma-active_3.0-0ubuntu1_amd64.deb) ...
[13:47] <smartboyhw> dpkg: error processing /var/cache/apt/archives/plasma-active_3.0-0ubuntu1_amd64.deb (--unpack):
[13:47] <smartboyhw>  trying to overwrite '/usr/lib/kde4/imports/org/kde/dirmodel/qmldir', which is also in package kde-runtime 4:4.10.80-0ubuntu1~ubuntu13.10~ppa1
[13:47] <smartboyhw> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
[13:48] <smartboyhw> shadeslayer, fix fix please:)
[13:48] <shadeslayer> :<
[13:48] <shadeslayer> I think that's the qml move that was done
[13:48] <smartboyhw> Yes it is:)
[13:48] <smartboyhw> :P
[14:00] <smartboyhw> shadeslayer, how to determine okular's abi version?
[14:00] <smartboyhw> yofel, ^
[14:00]  * smartboyhw can't determine...
[14:00] <yofel> you'll find it in some CMakeList.txt
[14:01]  * yofel checks
[14:01] <shadeslayer> hmmm
[14:01] <shadeslayer> how do we handle this
[14:01] <yofel> set_target_properties(okularcore PROPERTIES VERSION 3.0.0 SOVERSION 3 )
[14:01] <yofel> smartboyhw: ^
[14:01] <shadeslayer> because dirmodel is shipped in 3.0
[14:01] <shadeslayer> and will be removed in 4.0
[14:02] <shadeslayer> so do I just break it against 4.0?
[14:02] <smartboyhw> Argh so it is abi3 now is it?
[14:02] <yofel> it's libokularcore3
[14:02] <yofel> X-Debian-Abi: 0
[14:02] <shadeslayer> i.e Breaks: plasma-active (<< 4.0-0ubuntu1)
[14:03] <yofel> how about removing the files from active and depending on kde-runtime >= 4.10.80 ?
[14:05] <shadeslayer> but then is that compatible with what PA is using?
[14:05] <yofel> good question
[14:05] <yofel> this has to be backportable too...
[14:05] <yofel> well, breaking active is probably ok ^^
[14:06] <shadeslayer> hah
[14:06] <shadeslayer> I'll ask in #active
[14:07] <Riddell> what is the installgen file for in debian/ ?
[14:07] <shadeslayer> !find usr/lib/kde4/imports/org/kde/dirmodel/libdirmodelplugin.so
[14:07] <shadeslayer> !find usr/lib/kde4/imports/org/kde/dirmodel/libdirmodelplugin.so saucy
[14:08] <yofel> last I heard about installgen was that it was something from before my time
[14:08] <smartboyhw> YAY IT BUILDS!!!!!!!!!!
[14:08] <shadeslayer> ^^
[14:08]  * smartboyhw then waits for a lot of symbols issues;P
[14:09] <shadeslayer> yofel: it's compatible with PA3, exact same code
[14:10] <shadeslayer> so lets drop it from PA3
[14:10] <yofel> heh, typical
[14:10] <smartboyhw> second try.
[14:12] <Riddell> hmm, installgen..
[14:12] <Riddell> "It is a system used to automatically update the .install files. The
[14:12] <Riddell> installgen files in kde-sc packaging however have not been updated for
[14:12] <Riddell> a long time and we do not actively use them anymore. You can ignore
[14:12] <Riddell> them."
[14:12] <shadeslayer> yofel: Breaks/Replaces : plasma-active ( << 3.0-0ubuntu1)
[14:12]  * Riddell ignores them
[14:12] <shadeslayer> sound fine?
[14:12] <yofel> not 4?
[14:12] <shadeslayer> why 4?
[14:13] <shadeslayer> I'll drop them from 3.0-0ubuntu2
[14:13] <yofel>  << 3.0-0ubuntu2 then
[14:13] <shadeslayer> ah right
[14:13] <shadeslayer> beause 1 has the files as well
[14:16] <BluesKaj> wonder why the Windows 7 L2TP/IPsec vpn connection is so much faster than the Linux equivalent ...must be missing an important setting , but haven't been able to track it down
[14:17] <smartboyhw> shadeslayer, yofel: What's the final decision for the control file of okular?
[14:17]  * smartboyhw will upload it soon....
[14:18] <smartboyhw> Probably in an hour
[14:18]  * smartboyhw still has to fix the HUGE number of symbols.
[14:18] <yofel> uh, as I said
[14:18] <yofel> it's libokularcore3
[14:18] <yofel> X-Debian-Abi: 0
[14:18] <smartboyhw> yofel, I mean the build-deps
[14:18] <smartboyhw> active, etc. etc....
[14:18] <yofel> wait for shadeslayer
[14:19] <smartboyhw> yofel, OK:)
[14:19] <shadeslayer> well
[14:19] <shadeslayer> I'll have to upload plasma-active to ninjas
[14:19] <shadeslayer> and the archive
[14:19] <shadeslayer> so that you can build without issues
[14:19] <smartboyhw> shadeslayer, OK.
[14:19] <shadeslayer> or maybe not
[14:19] <smartboyhw> !?
[14:19] <shadeslayer> if you have -proposed enabled, then it'll work
[14:20] <yofel> ninjas depends on proposed so you shouldn't need to
[14:20] <shadeslayer> yeah, fine
[14:20] <shadeslayer> britney won't auto migrate because p-a will depend on kde-runtime > 4.10.80
[14:20] <shadeslayer> and there is no 4.10.80 in the archive :)
[14:20] <shadeslayer> so you'll have to run -proposed
[14:20] <smartboyhw> shadeslayer, I don't since it messes up calligra:(
[14:21] <shadeslayer> fun, the PA install file has a bunch of free space at the top
[14:21] <shadeslayer> for no reason
[14:21] <Riddell> hmm, should I package kdenetwork-strigi-analyzers?
[14:21] <Riddell> it's in the 4.10.80 release but it didn't build in old kdenetworks
[14:22] <yofel> in neon it builds:
[14:22] <yofel> /opt/project-neon/lib/strigi/strigiea_tiff.so
[14:22] <yofel> /opt/project-neon/lib/strigi/strigiea_dvi.so
[14:22] <yofel> no idea if something uses that
[14:23] <smartboyhw> For symbols files, should I change it to 4:4.10.80 only?
[14:24] <yofel> smartboyhw: where, what, why?
[14:24] <smartboyhw> yofel, symbols
[14:24] <yofel> yeah, but what exactly is the context?
[14:24] <smartboyhw> What: All the symbols like _ZNK60kular10Annotation5flagsEv@ABI_3_0
[14:24] <smartboyhw> After that it is originally 4.9.80
[14:24] <yofel> oh okular, yeah, you could simply re-create the file from scratch
[14:25] <smartboyhw> LOL
[14:25] <yofel> smartboyhw: see http://pkg-kde.alioth.debian.org/symbolfiles.html
[14:25] <yofel> or you change the lib name and version in the header, build and use batchpatch
[14:25] <shadeslayer> smartboyhw: quick review : http://paste.kde.org/777146/
[14:25] <yofel> that's what I usually do
[14:26] <shadeslayer> erm
[14:26] <shadeslayer> yofel: ^^
[14:26] <smartboyhw> LOL
[14:26] <smartboyhw> It looks fine 'ere though:P
[14:27] <Riddell> yofel: that's kdegraphics-strigi-analyzer
[14:27] <Riddell> yofel: kdenetwork is /usr/lib/strigi/strigita_torrent_analyzer.so
[14:27] <yofel> uh... right
[14:27] <Riddell> anyway, packaged :)
[14:27]  * yofel should read what he types...
[14:28] <smartboyhw> Continue:)
[14:28] <smartboyhw> :P
[14:28] <smartboyhw> Third build, 73%
[14:28] <smartboyhw> Oops
[14:28] <yofel> shadeslayer: ship it
[14:30] <Riddell> ssh! that's the secret debian upload password!
[14:30] <smartboyhw> fourth build with fixed .install files:P
[14:30] <smartboyhw> Riddell, really?
[14:30] <smartboyhw> :P
[14:36] <smartboyhw> - _ZN6Okular10Annotation6Window7setTextERK7QString@ABI_3_0 4:4.10.80
[14:36] <smartboyhw> +#MISSING: 4:4.10.80-0ubuntu1~ubuntu13.10~ppa3# _ZN6Okular10Annotation6Window7setTextERK7QString@ABI_3_0 4:4.10.80
[14:36] <smartboyhw> Can somebody explain!?
[14:37] <shadeslayer> that function was removed?
[14:37] <yofel> symbol went missing, which is fine as the SOVERSION changed
[14:37] <shadeslayer> ^^
[14:37] <yofel> smartboyhw: just remove all MISSING lines from the file
[14:38] <shadeslayer> kde-runtime fixed and uploaded as well
[14:38] <yofel> but as shadeslayer said, it happened because that function was removed:
[14:38] <yofel> $ c++filt _ZN6Okular10Annotation6Window7setTextERK7QString
[14:38] <yofel> Okular::Annotation::Window::setText(QString const&)
[14:39] <shadeslayer> alternatively, the signature changed
[14:40] <shadeslayer> so maybe its called setMagicText now, who knows :P
[14:42]  * shadeslayer takes up kstars
[14:42] <shadeslayer> Riddell: any progress on the split packages?
[14:43] <Riddell> shadeslayer: I'm doing kdenetwork now
[14:43] <Riddell> any ideas if I should worry about this?
[14:43] <Riddell> E: kde-zeroconf: library-not-linked-against-libc usr/lib/kde4/kio_zeroconf.so
[14:43] <shadeslayer> \o/
[14:43] <shadeslayer> uhm
[14:43] <shadeslayer> that looks odd
[14:44] <yofel> no sure, check whether it acutally uses libc stuff
[14:44] <shadeslayer> ^^
[14:44] <Riddell> surely everything uses libc?
[14:44] <yofel> I checked one lib from nepomuk, and that had no libc method call from what I could see
[14:44] <Riddell> kdeworkspace has the same thing on various bits so it might be some facet of saucy gcc
[14:44] <shadeslayer> what Riddell said
[14:45] <yofel> would everything really use libc?
[14:45] <yofel> I mean: if I write a lib with only one class with one function, that callls one function from Qt, would it link against libc?
[14:45]  * smartboyhw really can't understand how humans invented symbols, so difficult...
[14:45] <Riddell> dunno I assumed it included some fundamentals
[14:46] <Riddell> like I think libstdc++.so.6 includes the definition of "new" which is pretty important to c++
[14:46] <yofel> considering our linking is really conservative lately, I can imagine it not linking against libc if it uses none of its symbols
[14:46] <yofel> hm
[14:47] <shadeslayer> well, doesn't it work like this : Qt app uses some symbols of Qt and Qt itself uses some symbols of libc, hence app is linked to libc
[14:47] <shadeslayer> because the same thing happend with amarok and GStreamer 1.0
[14:48] <shadeslayer> Amarok was compiled against QtWebkit which used GStreamer 0.10
[14:48] <shadeslayer> and the pgst port I was trying to test used GStreamer 1.0
[14:48] <yofel> yeah, it depends where it takes the symbol from. If Qt has all of the symbols it needs, then there's no need to link against libc
[14:50] <Riddell> sound reasonable, I'll stop worrying then
[14:51] <yofel> I'm not 100% convinced myself yet.. apachelogger ^
[14:51] <shadeslayer> yofel: but wouldn't something as basic as say new require libstdc++ ?
[14:52] <Riddell> shadeslayer: it does link against libstdc++
[14:52] <shadeslayer> so that class would definitely need to link against libstdc++
[14:52] <Riddell> just not libc
[14:52] <shadeslayer> oh
[14:52] <shadeslayer> hmm
[14:52] <shadeslayer> the I /suppose/ it's possible
[14:53] <apachelogger> eh
[14:53] <yofel> well, looking at the source that kioslave is rather small and from what i see pure c++, so this sounds possible
[14:53] <apachelogger> yofel: what's the question?
[14:54] <yofel> apachelogger: whether something can work without linking aginst libc6
[14:54] <yofel> E: kde-zeroconf: library-not-linked-against-libc usr/lib/kde4/kio_zeroconf.so
[14:54] <apachelogger> no
[14:54] <apachelogger> that's not a library though
[14:54] <apachelogger> that's a plugin
[14:54] <apachelogger> :P
[14:54] <yofel> how does that make a difference?
[14:56] <apachelogger> plugins are loaded after runtime linker resolution such that in theory it needs no libs at all iff all the libs it would need are loaded prior to the plugin loading :P
[14:57] <apachelogger> anyway
[14:57] <apachelogger> cmake allows you to link non-recursively
[14:57] <yofel> different example then:
[14:57] <yofel> E: libnepomukcleaner4: library-not-linked-against-libc usr/lib/libnepomukcleaner.so.4.11.0
[14:57] <apachelogger> so unless libfoo actually uses libc crap it won't be linked against libc
[14:58] <apachelogger> so in a qt context you can get around libc, you'll probably not get around libc++ as Riddell already mentioned that operator new is defined in there
[14:59] <yofel> ok, so lets conclude that we can ignore it
[14:59] <apachelogger> well
[14:59] <apachelogger> it works, doesn't it? :P
[14:59] <apachelogger> It is theoretically possible to have a library which doesn't use any symbols from libc, but it is far more likely that this is a violation of the requirement that "shared libraries must be linked against all libraries that they use symbols from in the same way that binaries are".
[15:00] <apachelogger> from lintian
[15:01] <smartboyhw> I HATE SYMBOLS.
[15:01]  * smartboyhw faints.
[15:02] <yofel> good, you're starting to understand them :P
[15:02] <shadeslayer>  ^^
[15:03] <shadeslayer> interesting :   * Add kubuntu_link_pthread.diff to link to pthread, fixes compile on    i386
[15:03] <shadeslayer> from yofel
[15:03] <yofel> uh.... that's DSO stuff IIRC
[15:04] <yofel> please drop if possible
[15:04] <shadeslayer> lets see if it we still need it?
[15:04] <Riddell> shadeslayer: that kstars?
[15:04] <shadeslayer> yes
[15:04] <shadeslayer> though then we might need it for raring still?
[15:04] <Riddell> shadeslayer: I've not worked out why we need that, and neither does upstream
[15:04] <shadeslayer> okay
[15:05] <yofel> well, drop it and we'll see. Worst case we can add that back for raring-only or so
[15:05] <shadeslayer> yeah
[15:07] <Riddell> shadeslayer: I'm pretty sure we still needed it when I merged kstars this cycle
[15:10] <shadeslayer> hurray
[15:10] <shadeslayer> we can drop the patch
[15:10] <Riddell> oh?
[15:10] <shadeslayer> yeah, compiled fine
[15:11] <yofel> on i386
[15:11] <yofel> ?
[15:11] <shadeslayer> oh ... good point :/
[15:12]  * shadeslayer forgot that it had to compiled against i386
[15:17] <smartboyhw> ready to upload now:)
[15:17] <smartboyhw> shadeslayer, fixed already?
[15:17] <shadeslayer> fixed?
[15:17] <shadeslayer> whats fixed?
[15:18] <shadeslayer> bag
[15:18] <shadeslayer> bah
[15:18] <shadeslayer> /usr/bin/ld: note: 'pthread_create@@GLIBC_2.1' is defined in DSO /lib/i386-linux-gnu/libpthread.so.0 so try adding it to the linker command line
[15:18] <shadeslayer> k will fix post dinner
[15:23] <smartboyhw> shadeslayer, plasma-active?
[15:28] <smartboyhw> Now if okular doesn't build, it will be super-weirdo.
[15:34] <Riddell> phew, kde-workspace uploaded
[15:38] <lordievader> Good afternoon.
[16:01] <Riddell> anyone else unable to suspend from a session in saucy?
[16:01] <Riddell> I wonder if that's a consolekit thing
[16:01] <Riddell> being replaces by logind
[16:03] <yofel> Riddell: me
[16:04] <yofel> pm-suspend itself works, just not from UI
[16:05] <shadeslayer> well
[16:05] <shadeslayer> Riddell: I couldn't until I installed pm-utils
[16:05] <shadeslayer> doesn't pm-suspend come from pm-utils?
[16:05] <shadeslayer> http://paste.kde.org/777194/
[16:06] <yofel> yeah
[16:06] <shadeslayer> I can suspend from UI and pm-suspend
[16:06] <shadeslayer> but I didn't have pm-utils installed
[16:09] <shadeslayer> wait what
[16:09] <shadeslayer>  libpython2.7 : Depends: libpython2.7-stdlib (= 2.7.5-1ubuntu2) but 2.7.5-5ubuntu1 is to be installed.
[16:09] <shadeslayer> how
[16:09] <shadeslayer> saucy has 2.7.5-5ubuntu1
[16:11] <shadeslayer> can't be archive skew, Uploaded by: Matthias Klose on 2013-06-05
[16:18] <shadeslayer> yofel: any ideas why this happens?
[16:20] <yofel> not really, unless you're using an out-of-date chroot
[16:25] <shadeslayer> hm well
[16:25] <shadeslayer> I ran --update
[16:27] <shadeslayer> yofel: http://paste.kde.org/777212/
[16:27] <shadeslayer> ahh
[16:27] <shadeslayer> marble
[16:58] <ahoneybun> hello people
[16:58] <shadeslayer> new symbols galore in marble
[17:00] <shadeslayer> hm
[17:00] <shadeslayer> there's a usr/bin/marble-qt
[17:00] <shadeslayer> yofel: ^ thoughts?
[17:10] <yofel> shadeslayer: make a marble-qt package (As I guess that's the same thing as quassel-qt4?)
[17:10] <shadeslayer> that's all fine and dandy ... but ...
[17:10] <shadeslayer> there is no other library or anything to go with it
[17:10] <shadeslayer> just marble-qt
[17:10] <shadeslayer> which is the perplexing part to me
[17:11] <yofel> well, it doesn't depend on kde I guess?
[17:11] <shadeslayer> and it has no shared libs?
[17:11] <yofel> libmarblewidget itself doesn't either
[17:11] <shadeslayer> hm
[17:11] <yofel> So I can see a purpose for it
[17:12] <yofel> you'll just have to make sure it works without 'marble' installed
[17:12] <shadeslayer> in  a non kde env
[17:13] <yofel> yeah. Using marble in unity would be cool :P
[17:13] <shadeslayer> hehe
[17:13] <shadeslayer> you know ... I've never tried out Unity
[17:13] <shadeslayer> like, never ever
[17:13] <shadeslayer> I've only seen screenshots
[17:13] <yofel> used it a few times.
[17:14] <yofel> it *is* usable, it just tends to annoy me because it gets in my way at a few places and I can't tell it not to
[17:14] <yofel> the look and feel though is nice
[17:15] <shadeslayer> interesting : http://www.ubuntu.com/phone/carrier-advisory-group
[17:15] <yofel> indeed
[17:15] <shadeslayer> can only mean one thing tbh :P
[17:17] <yofel> well, if they ever do make a really usable ubuntu phone I might even buy it ^^
[17:17] <shadeslayer> why this is odd
[17:17] <shadeslayer> dh_install: cp -a debian/tmp/usr/lib/kde4/plugins/marble/15/QtMobilityPositionProviderPlugin.so debian/marble-plugins//usr/lib/kde4/plugins/marble/15/ returned exit code 1
[17:17] <shadeslayer> except there is no QtMobilityPositionProviderPlugin.so in the install files
[17:17] <shadeslayer> anywhere
[17:17] <shadeslayer> oh
[17:17] <shadeslayer> debian/marble-plugins.install.linux:usr/lib/kde4/plugins/marble/15/QtMobilityPositionProviderPlugin.so
[17:18] <shadeslayer> what's install.linux ? 0.o
[17:18] <yofel> debian has !linux stuff
[17:21]  * yofel on the road, back in an hour
[17:23]  * shadeslayer will finish marble and be done for the day
[17:40] <ahoneybun> shadeslayer: Unity is ok and usable, it is just Compiz that is holding it back
[18:23]  * yofel wonders where vHanda went missing
[18:23] <vHanda> what's up?
[18:25] <yofel> vHanda: where's the current shared-desktop-ontologies repository? We have things failing to build in project neon as it needs s-d-o 0.11, but git://oscaf.git.sourceforge.net/gitroot/oscaf/shared-desktop-ontologies has 0.10.51
[18:25] <vHanda> git://git.code.sf.net/p/oscaf/shared-desktop-ontologies
[18:25] <vHanda> sourceforge :/
[18:26] <yofel> now that looks a lot better :)
[18:26] <yofel> thanks!
[18:36] <shadeslayer> he sent an email about this btw :P
[18:37] <shadeslayer> who wants to take care of marble symbols
[18:44] <shadeslayer> okay done
[18:46] <shadeslayer>  8 files changed, 5644 insertions(+), 4609 deletions(-)
[18:49] <shadeslayer> night
[18:56] <jessie> Damn. That's a lot of changes. ha
[18:56] <Quintasan> My imx died :(
[19:06] <yofel> shadeslayer: who, where, what mail?
[19:25]  * yofel puts kcm_pimactivity in kmail together with the identity manager
[19:30] <yofel> meh, I'll add a new package that kontact and kmail pull in. That's probably the most sensible thing (at least more sensible than putting it in libkdepim4)
[19:31] <Riddell> no other common package?
[19:34] <yofel> well, kdepim doesn't really have a common package. There's kdepim-kresources if anything
[19:37] <Riddell> nah that's not much use
[19:38] <yofel> my thought was to add kde-config-pimactivity as that's the only thing in there. I could add a kdepim-common, but for only 2 files...
[19:39] <Riddell> I'd think kde-config-pimactivity unless we expect more to be added
[20:49] <ahoneybun> Riddell: hello
[20:49] <Riddell> hi ahoneybun
[20:49] <ahoneybun> that was fast
[20:50] <ahoneybun>  lol
[21:29] <ScottK> Did anyone look if the libdcraw vulnerability that got a USN for 12.04 affected newer releases?
[23:23] <genii> What, if any, frontend to ufw is preferred now for Kubuntu? guarddog is gone ( but still referred to by ubottu )
[23:26] <yofel> gufw I think, there's no usable kde UI for firewall management that I know of.
[23:27] <genii> yofel: OK, thanks


[14:53] <redelmann> redelmann> hi there, im writing a charm with resources and start asking: ¿Can i set a default resource file?
 so if i deploy without setting any resource some default file will upload
 and later only if user want can change resource file
 it is possible?
[15:05] <perrito666> redelmann: the people that can answer that wont be here until monday morning around 9AM your time :)
[15:08] <redelmann> perrito666: they do not work on sundays?
[15:08] <redelmann> perrito666: :P
[15:09] <perrito666> actually around 20 you get people from nz and aus but none of them is a resources export
[15:11] <redelmann> perrito666: was a joke, thank you!
[15:11] <perrito666> redelmann: I know :p cu
[20:29] <mup> Bug #1591499 changed: Bootstrap timeout and fail on private cloud <cpe-sa> <juju-core:New> <https://launchpad.net/bugs/1591499>
[21:37] <thumper> O.M.G.... state tests are so painfully slow
[21:38] <perrito666> thumper: amen
[21:38] <thumper> o/ perrito666
[21:38] <thumper> perrito666: what are you doing here?
[21:38] <perrito666> thumper: I have too many irc channels open in my quassel to botter closing work ones during weekends
[21:39] <thumper> :)
[21:40] <perrito666> btw, you go often to london, any simcard you can recommend me to have 2 weeks of data+calls? (calls being optional)
[21:56]  * thumper thrashes machine with test runs
[22:30] <thumper> oh for the love of all that is holy
[22:30] <thumper> PASS: status_history_test.go:24: StatusHistorySuite.TestPruneStatusHistoryBySize - 32s
[22:36] <perrito666> I thought fwereade had refactored that
[22:37] <perrito666> thumper: that was me, sorry
[23:12] <menn0> thumper: would you mind having a quick look at http://reviews.vapour.ws/r/5036/
[23:12] <thumper> menn0: trade ya http://reviews.vapour.ws/r/5043/diff/#index_header
[23:12] <menn0> thumper: ok :)
[23:24] <menn0> thumper: Done. I suggested one more tiny cleanup.
[23:25] <menn0> thumper: That PR is a bit like squeezing a pimple ... gross yet satisying :)
[23:25] <thumper> yeah


[00:50] <bluesabre> Unit193: eat?
[01:21] <Unit193> I did, though wasn't that great.
[12:06] <bluesabre> knome: https://youtu.be/2lQnALrJ-0w
[14:15] <knome> bluesabre, mhm
[14:15] <knome> bluesabre, one thing i noticed there's no confirmation that the upload was ok
[14:17] <knome> bbl
[14:30] <sidi> Guys I really hope you plan on stopping shipping Abiword some day. This thing is  a joke. Updated a 15.04 to 15.10 and for some mysterious reason Abiword (which I literally have *never* run on that system) has writte 412GB of data into ~/.config/abiword (well till disk was full)
[14:30] <sidi> I suspect a bit of a mess-up with debian preinst/postinst scripts for the Wily package
[14:31]  * sidi is done complaining :p sorry
[14:47] <Unit193> sidi: preinst/postinst don't touch users home.  What was in that dir?  And we've already stopped shipping it in favor of LO.
[14:48] <sidi> Unit193, it'll remain a mystery, I needed to ditch it because my workstation was kind of not working anymore
[14:49] <sidi> can the postinst run the app or other utilities?
[14:49] <sidi> and the app then go AWOL?
[14:49] <Unit193> It can run stuff of course, but generally is run as root.
[16:14] <sidi> Is there anything special about the Thunar package on Xubuntu? I have the impression that Launchpad builds it without applying Quilt patches!?
[16:14] <sidi> I'm really confused...
[19:26] <flocculant> akxwi-dave: have you been watching the doodle poll for the next session at all?
[19:27] <akxwi-dave> not for a week or so
[19:28] <flocculant> k - currently the best is 3 for 16:00
[19:29] <flocculant> was going to ask the social media peeps to bump that next week, bump the mail lists then set date beginning of the week after that
[19:31] <akxwi-dave> sounds good mate
[19:31] <flocculant> I think those are the weeks anyway - basically bump and then set in the 6 days prior if that makes sense :)
[21:34] <ochosi> wow, gnome is really doing a rather big redesign of the settings dialog...
[21:35] <flocculant> no need for settings anymore?
[21:38] <ochosi> haha, almost
[21:39] <ochosi> well at least it seems more locked down, the approach they're taking doesn't really allow for meaningfully "plugging in" extra settings dialogs
[21:39] <flocculant> :)
[21:40] <ochosi> (and i guess that is the whole point: *they* want to decide what is important to the users, and to some extent that makes sense too. but only to some.)
[21:40] <Unit193> Well as long as they aren't messing with GTK, shouldn't matter.
[21:40] <flocculant> yea I know that - which is why I don't install gnome or ubuntu now
[21:40] <Unit193> ochosi: You have mail, btw.
[21:41] <flocculant> just makes me wonder just how useful this gnome replacement for the ubuntu software tool is actually going to be
[21:42] <Unit193> flocculant: You open it, it detects you aren't running GNOME and fixes it for you.  Doesn't actually do much else.
[21:42] <ochosi> tbh i've never seen gnome-software in action myself
[21:42] <flocculant> nope
[21:42] <Unit193> I gave a few screenies, wasn't too bad right?
[21:42] <ochosi> but since the ubuntu software center is not a revelation, my general level of expectation is fairly low
[21:42] <flocculant> I suppose I'll grab the ppa when it shows up
[21:42] <flocculant> yea
[21:43] <ochosi> yeah, me too
[21:43] <flocculant> ochosi: but should we use it
[21:43] <flocculant> if we've been using usc and it's not really been supported - what difference does keeping it make?
[21:44] <ochosi> dunno, i'll wait and see what gnome-software does
[21:44] <flocculant> I guess that's best
[21:44] <flocculant> hopefully it'll show up at eow
[21:47] <Unit193> bluesabre: Only FTBFS we have on the test rebuild/gcc6 rebuild is xubuntu-docs. \o/
[21:50] <Unit193> BTW, I can't login to the wiki to update the meetings page.
[21:50] <ochosi> a-ha a-ha
[21:50] <ochosi> from when on are we going to use the new wiki? (knome?)
[21:50] <flocculant> Unit193: I appear to have been logged out of there too
[21:51] <flocculant> ochosi: I didn't think we were using our wiki for everything?
[21:52] <ochosi> i dunno, i wasn't really around to follow the website transition discussion tbh
[21:52] <Unit193> I dunno, but one that actually works would be nice.
[21:53] <ochosi> i just presumed we would use our own wiki once we have one
[21:53] <flocculant> as long as it's open to everyone
[21:53] <ochosi> (why keep info in two places?)
[21:53] <flocculant> if it's not open to everyone then that's just plain wrong
[21:53] <ochosi> yeah, i'm sure we'll find a meaningful policy for openness
[21:53] <flocculant> well
[21:53] <Unit193> OpenID?
[21:54] <flocculant> ochosi: open is right - any sort of not open is wrong seems a good starting point
[21:54] <ochosi> what do you mean by "open" anyway?
[21:54] <ochosi> world-readable? world-writeable?
[21:54] <flocculant> that anyone can edit pages
[21:54] <Unit193> flocculant: Bad idea, because spam.
[21:54] <flocculant> just the same as the one we're replacing
[21:54] <ochosi> do they need accounts? can they edit any page?
[21:55] <flocculant> Unit193 then the same as the ubuntu one
[21:56] <flocculant> ochosi: nothing wrong with needing an account ofc - but nothing we currently have is immutable
[21:56] <flocculant> (when the ubuntu wiki works)
[21:57] <ochosi> yeah, the way to ubuntu wiki sometimes doesn't work sorta makes some pages feel immutable :p
[21:57] <flocculant> yea - but that's just canonical fail on wiki :)
[22:13] <flocculant> \o/
[22:13] <flocculant> logged in - set date now
[22:14] <Unit193> Thanks.  Mine had a proxy timeout when I tried.
[22:14] <flocculant> I'll try and populate the agenda vaguely
[22:16] <flocculant> any need to bring -themes up?
[22:16] <ochosi> i'd ask bluesabre
[22:16] <ochosi> but generally i think we're on tra k
[22:17] <ochosi> some greybird fixes have landed, others are still due
[22:17] <Unit193> Perhaps, but it highly stinks...
[22:17] <flocculant> ochosi: ok - just seems easier to add things to agenda while logged in then ignore it than fight to login again :p
[22:17] <ochosi> and the other part about not having >1 usable theme, well, it's still too early to tell
[22:19] <flocculant> added themes to the list
[22:20] <flocculant> we can ignore it :)
[22:20] <Unit193> ochosi: Can you make it to the scheduled time?
[22:20] <flocculant> Unit193: anyway - done, not fighting google calendar tonight though ... hint
[22:20] <Unit193> flocculant: Thanks.
[22:22] <flocculant> ochosi: my issue is that we don't introduce any sort of censorship into our wiki that isn't present in the one we use currently
[22:24] <Unit193> flocculant: BTW, current images fine?
[22:25] <flocculant> ish
[22:26] <Unit193> And thanks for reminding me about Numix, means I don't update 'alpha' :P
[22:26] <flocculant> Unit193: not checked today, yesterday all was good except black login screen after install, which went after login/out/in
[22:26] <flocculant> and blueman crash
[22:27] <Unit193> Was thinking about another core update, considering last one was 31-Dec-2015.
[22:28] <flocculant> yea
[22:28] <ochosi> Unit193: i'll try, can't promise though
[22:28] <ochosi> it's not totally unrealistic that i'll make it
[22:29] <flocculant> Unit193: that was the other thing I meant to add to agenda ...
[22:29] <Unit193> flocculant: Why bother?  No status updates since last time.
[22:29] <flocculant> getting really itchy with my hat on with that now
[22:29] <flocculant> because that ^^
[22:30] <flocculant> we should get it talked about - even if we end up thinking about 19.04 for it
[22:31] <flocculant> Unit193: you can update your one - I don't much push it, I think that slickymaster tries to look when he can
[22:31] <Unit193> flocculant: Sure, I don't mean to push you or others, but may as well have it up to date, I see random hits on it after all.
[22:32] <flocculant> yea
[22:32] <flocculant> I understand that - and I *do* try it out now and again too :)
[22:33] <flocculant> what I'm after is it being on the tracker properly so we can follow it properly
[22:35] <flocculant> we should perhaps look at the website pointer to IRC and tell people to hang about for at least 15 minutes ...
[22:37] <flocculant> "Due to the real-time nature of IRC, it is often the fastest way to get help" > "Due to the real-time nature of IRC, it is often best to wait for at least 30 minutes after asking a question before leaving, no need to repeat, just have some patience. In addition many of your questions would be answered just as easily in #ubuntu, try us for the xfce side of your installation queries"
[22:45] <pleia2> flocculant: shared package testing info on the social medias
[22:45] <flocculant> pleia2: thank you :)
[22:46] <flocculant> pleia2: next week sometime I'm going to have one last push of the irc session
[22:46] <flocculant> with the ordinary link
[22:46] <pleia2> hehe
[22:46] <pleia2> ok, I have travel+conference starting on wednesday, so I'll catch up when I am back at computer and not dead
[22:47] <flocculant> ok - I'll push it monday :)
[22:47] <pleia2> wfm
[22:47] <flocculant> then ask you social peeps to do your magic
[22:47] <flocculant> then set time on the 25th
[22:48] <flocculant> assuming more than 3 people ...
[22:48] <pleia2> I don't think I have people
[22:49] <flocculant> :)
[22:49] <flocculant> you're just one of the peeps :)
[23:05] <flocculant> knome: ^^^ "due to real time nature ..." just a thought and a draft one at that :p
[23:30] <flocculant> night all


[00:21] <hellslinger> anyone know where I can download the ota-12 image? I can't find it anywhere
[01:36] <ogra_> hellslinger, http://system-image.ubuntu.com/ubuntu-touch/stable/ has the metadata for the single bits (and the links to the files in the pool)
[08:49] <linmob> Hello, I am using a Nexus 4 (mako) on rc.proposed and managed to setup Libertine. Unfortunately, vivid is quite old (and obsolete), and some packages (e.g. the latest chromium-browser) are outdated (chromium-browser just segfaults). Is there any way to install a chroot that is on a newer or alternatively still supported version (trusty) of Ubuntu? Could I fix this by transitioning to another channel of Ubuntu Phone?
[09:32] <kaisoz> hi there!
[09:34] <mimecar> hi kaisoz
[10:11] <kaisoz> hey mimecar! didn't see your greetings :D
[13:38] <jgdx> mterry, hey, got five min to talk about uss/time-date?
[13:38] <mterry> jgdx: sure do
[13:38] <jgdx> mterry, specifically, I can't seem to locate the London timezone by writing "London, United Kingdom" into the search field.
[13:39] <jgdx> mterry, you did some changes to that panel, but do you recall if any of those changed the search code?
[13:40] <mterry> jgdx: they did change the search code (allowed it to search in translated names).  But I don't think we've ever searched using the country names and such.  It's trying to find a CITY called London United Kingdom in your case
[13:40] <jgdx> (either directly or indirectly by e.g. changing the db of timezones, etc)
[13:40] <mterry> jgdx: and the search isn't super smart, it just checks the beginning of the city for example, not sub phrasses
[13:41] <mterry> jgdx: I also updated the db of timezones too, when I made my other changes, yes
[13:41] <mterry> jgdx: but I don't think your search phrase would have ever worked
[13:41] <mterry> jgdx: it would be nice if it did.  It's a sensible search phrase
[13:42] <jgdx> mterry, well, we had a test using that exact phrase, but it's uncertain for how long it has failed, but now it does.
[13:42] <mterry> jgdx: ah interesting....
[13:42] <mterry> jgdx: that does surprise me.  Then I bet I probably did screw something up
[13:43] <jgdx> mterry, I guess the old search “engine” was a bit too coupled with the data
[13:45] <mterry> jgdx: well I don't *think* we ever searched over country names...  So I'm guessing that we would accept matches on just the first word?
[13:45] <mterry> jgdx: I can look into it.  That's the whole test, just typing that in?
[13:46] <jgdx> mterry, http://pastebin.ubuntu.com/23061630/ :)
[13:46] <jgdx> mterry, hey, great, thanks
[13:52] <mterry> jgdx: I *could* imagine a race there.  Like partial results come in from an earlier string and is still there before updating with no results once search_kb_type returns...  But I'll try and see what the old code did
[13:52] <mterry> jgdx: it would really help if you knew the last time that test worked
[13:53] <mterry> jgdx: also this isn't super urgent, I assume?
[13:55] <jgdx> mterry, we can't seem to find any bug reports for this, and I'm able to set all timezones I want using cities, so not 100% sure how urgent.
[13:55] <jgdx> mterry, but we want to fix the test asap
[13:57] <mani> HELLO
[13:57] <Guest64811> hello
[13:58] <Guest64811> i m using ubuntu phone
[13:58] <jgdx> Guest64811, how's it going?
[13:58] <Guest64811> igood
[13:58] <Guest64811> thANK YOU
[13:58] <Guest64811> I WANT TO INSTALL WHATS APP IN MY PHONE
[13:59] <Guest64811> DOES IT POSIBLE
[13:59] <jgdx> Guest64811, I don't think you can yet, Whats App hasn't created an app for uphone.
[14:00] <Guest64811> IS THERE ANY WAY TO INSTALL ANDROID APPS IN UPHONE
[14:01] <davmor2> Guest64811: no what's app on Ubuntu Phone, and no way to install android app on Ubuntu
[14:01] <Guest64811> http://www.whatsappfor.org/software/whatsapp-ubuntu-phone-touch/
[14:02] <Guest64811> DOES IT WORK
[14:02] <Guest64811> ??/
[14:02] <k1l_> Guest64811: that is not an official app
[14:03] <Guest64811> THIS IS THE WAY TO INSTALL WHATS APP IN
[14:03] <OerHeks> caps!
[14:09] <kaisoz> dpkg -L *
[14:14] <javier4_> make complains about the lack of member h_addr in struct hostent, but in my development/ndk/sources/android/libportable/common/include/netdb_portable.h ther's this line
[14:15] <javier4_> #define h_addr  h_addr_list[0]  /* address, for backward compatibility */
[14:15] <javier4_> inside hostent definition. What's the problem?
[14:20] <kaisoz> I'm planning about contributing to Ubuntu touch and I'm having a look at the band-aids project in launchpad
[14:21] <kaisoz> I'm having a look at this issue, just to have some idea
[14:21] <kaisoz> https://bugs.launchpad.net/band-aids-uphone/+bug/1234336
[14:22] <kaisoz> wow, that was fast :D
[14:22] <kaisoz> so, how would be the proper way to start working on this issue for example? should I contact Alejandro J. Cura to talk about it? I've been having a look at the unity-scope-click as well
[14:22] <dobey> Guest64811: there is a webapp for the whatsapp web site interface in the store i think, however you must have a separate device with android/ios running the official app to log in with, and you will not be able to receive push notifications or rely on other advanced features, from it
[14:24] <jgdx> kaisoz, yeah, alecu is the person to talk to there. And awesome that you wan't to contribute.
[14:24] <jgdx> want*
[14:25] <kaisoz> thank you :)
[14:25] <jgdx> kaisoz, checking out the unity-scope-click code, building and running it, then poking at it is probably the next best step :)
[14:27] <kaisoz> I currently have a full time job as a (embedded) software developer so I won't be able to contribute as often as I would like to :)
[14:27] <kaisoz> anyway I'll do my best. I've been following the project and now I have a Aquaris E5 so I can start playing :)
[14:30] <kaisoz> An I think the band-aids project is an excellent idea to get people involved easily
[14:31] <jgdx> kaisoz, cool, and yeah it is! :) If you're interested in app development, there's also #ubuntu-app-devel
[14:32] <jgdx> where you can discuss scope development as well
[14:33] <kaisoz> I'm really more interested about helping with the system itself, although I think this kind of bugs are the best way to get the feeling about it
[14:33] <kaisoz> maybe there's a better way, I don't know
[14:36] <kaisoz> I've only contributed to the kernel with a couple of patches to the drivers subsystem, but you work in different way there (as far as I know)
[14:46] <dobey> kaisoz: i'm not sure we want to fix that search queries "issue" exactly
[14:47] <kaisoz> ahh
[14:47] <dobey> hmm i didn't realize someone added it to band-aids
[14:47] <kaisoz> so it's a good thing that I asked before :D
[14:48] <kaisoz> I just went to the band aids project and It's already ordered by importance
[14:57] <kaisoz> so, all system related bugs are gathered in the canonical devices system image launchpad project right?
[14:57] <kaisoz> from there they are triaged to the respective projects
[14:58] <dobey> kaisoz: i explained that to you the other day.
[14:58] <dobey> but i also don't know what you are expecting is "system related" either
[15:00] <kaisoz> yeah, it's true, I didn't remember sorry
[15:03] <kaisoz> which systems related I mean all not related to apps or scopes
[15:04] <kaisoz> maybe it's not the proper word
[15:04] <kaisoz> :S
[15:08] <dobey> kaisoz: some apps and scopes are a core part of the system. c-d-s-i project has bugs linked which affect all levels of packages included in the system images
[15:09] <kaisoz> aha, well that's perfectly clear now, thanks :)
[15:12] <kaisoz> got to go, see you later. And many thanks for the info! :D
[15:44] <kaisoz> hi again
[17:07] <gb_mks> hi, I subscribe to this list<EMAIL_ADDRESS>and I´m sending a mail to it but doesn´t arrive or show in the mail list archive. can someone give me advice
[17:10] <dobey> gb_mks: if it was held for moderation you would have received an e-mail about it. otherwise, appearing in the archive on the web site is not instantaneous.
[17:11] <dobey> gb_mks: is your mail about android and forensiscs tool?
[17:12] <gb_mks> dobey: thanks, I sent a mail (and resend it twice). the first one was yesterday. It´s about a bug related with ubuntu-sdk in ubuntu 14.04
[17:13] <gb_mks> I didn´t received an email about moderation
[17:17] <gb_mks> I copy paste it here https://titanpad.com/bug138569
[17:18] <dobey> oh, i don't know why your mail wouldn't have gone through
[17:19] <dobey> mhall119: ^^ can you help gb_mks about why his mail didn't make it to the phone list?
[17:19] <gb_mks> yes it´s quite strange,.... I might have made a mistake
[17:20] <gb_mks> I sent it to<EMAIL_ADDRESS>is that correct?
[17:20] <dobey> yes
[17:21] <gb_mks> ummm strange .. I sent one, nothing happened, then subscribe to the list, sent it again, and nothing happened twice :$
[17:22] <mimecar> Are you using the same email address for launchpad
[17:22] <mimecar> and for the mail client?
[17:23] <gb_mks> that might be :D
[17:23] <gb_mks> gracias mimecar!
[17:49] <mhall119> gb_mks: dobey: checking on it now
[17:50] <gb_mks> thanks :)
[17:50] <mhall119> gb_mks: what was the subject line of your email?
[17:54] <mhall119> dobey: gb_mks: I'm not an admin there, you might need pmcgowan to help
[17:55] <gb_mks> I just resend it again and it work correctly.
[17:56] <gb_mks> thanks for the help :)
[17:56] <pmcgowan> gb_mks, it was sent ok but my guess is the subject hit everyones bug filter
[17:56] <pmcgowan> I know it hit mine
[17:57] <pmcgowan> gb_mks, actualy the one you just sent arrived
[17:58] <gb_mks> yes, take a look to it because it looks everyone using ubuntu 14.04 might be affected and unable to use ubuntu-sdk correctly
[18:05] <dobey> mhall119: oh sorry, thought you were an admin for it
[18:05] <mhall119> so did I, but nope :)
[18:06] <pmcgowan> mhall119, that can be fixed
[18:12]  * mhall119 accidentally volunteered for more responsibility :/
[18:14] <tsimonq2> mhall119: *way* too easy to do ;)
[20:02] <kvmmm> if I want to install a new DE, should I just use the Ubuntu Software Center?
[20:05] <PaulfraOSAA> Anybody got a project to compile/run on (K)ubuntu 16.04?
[20:13] <dobey> ?
[20:14] <dobey> kvmmm: install on a phone? or on a PC? the latter you should ask in #ubuntu but basically yes
[20:14] <kvmmm> yes, it was a mistake. Sorry
[20:15] <dobey> PaulfraOSAA: what do you mean?
[20:24] <PaulfraOSAA> dobey: After actually getting a couple of basic examples running in kubuntu 14.10 I upgraded to 16.04 and now i get problems with running  even the stariting example
[20:26] <dobey> PaulfraOSAA: 14.10? yikes. i have a pure qml app i'm working on and it runs ok under unity7 on 16.04
[20:27] <dobey> PaulfraOSAA: if you build a binary targetted for the 15.04 phone frameworks that uses c++ in the SDK, you probably won't be able to run that binary on a 16.04 PC, because it will be binary compatible
[20:27] <dobey> err
[20:27] <PaulfraOSAA> I ran LTS and got thoroughly tired of cmake 2.8 and the like. But it worked then, it doesn't now
[20:27] <dobey> because it will NOT be binary compatible
[20:27] <dobey> 14.10 wasn't LTS, 14.04 was
[20:27] <PaulfraOSAA> Oh, so then it was 14.04
[20:30] <dobey> but anyway, if you're compiling in the sdk with a kit with a 15.04 framework target, but for x86, you'll have to run that binary in a chroot/container to run it on 16.04.
[20:34] <PaulfraOSAA> I now get E: Failed to change to directory ‘/home/expert/programmering/UbuntuTouch/build-myFirstCmakeTouch-UbuntuSDK_for_armhf_GCC_ubuntu_sdk_15_04_vivid-Default’: No such file or directory
[20:34] <PaulfraOSAA> I: The directory does not exist inside the chroot.  Use the --directory option to run the command in a different directory.
[20:35] <PaulfraOSAA> Well the framework update has never worked for me
[20:36] <dobey> oh hmm, that looks like a problem with the sdk itself. i'd say file a bug against the ubuntu-sdk package
[20:37] <dobey> also, #ubuntu-app-devel might be a better channel for app dev specific questions
[20:47] <PaulfraOSAA> dobey: uhh, thanks for that heads up, I'll try that
[20:48] <PaulfraOSAA> At least now Qt Creator works on my tablet, so I'll be using it for that :)
[20:49] <dobey> cool
[21:42] <taiebot> Hello hello. Is there a command line to check the status of the brightness sensor ?
[23:58] <mariogrip> does anyone know what format the recovery ramdisk on arale (mx4) is?