[03:42] <kubotu> feed branches-next had 9 updates, showing the latest 6
[04:41] <kubotu> feed branches-next had 7 updates, showing the latest 6
[05:40] <kubotu> feed branches-next had 19 updates, showing the latest 6
[06:13] <soee> good morning
[06:41] <kubotu> feed branches-next had 8 updates, showing the latest 6
[08:40] <Riddell> looking blue http://starsky.19inch.net/~jr/tmp/build_status_5.0.0_utopic.html
[08:48] <soee> Riddell: this is final not some RC ?
[08:48] <Riddell> yep
[08:49] <Riddell> ah and all the soversions have changed, hense scarlett's updates last night
[08:55] <Riddell> but I worry she missed some * off the library .install files
[10:31] <BluesKaj> 'Morning
[10:41] <kubotu> feed branches-next had 12 updates, showing the latest 6
[10:46] <shadeslayer> ScottK: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1328049 & https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/1327591?comments=all
[10:59] <shadeslayer> xnox: better http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/sddm/view/head:/debian/sddm.service
[11:01] <xnox> shadeslayer: yes, but given that it is identical to the upstream systemd unit, why are you making a custom distro one? can you not install/use upstream one directly? https://github.com/sddm/sddm/blob/master/services/sddm.service.in
[11:03] <xnox> shadeslayer: that way, for example, when upstream gainst plymouth integration support they will update the systemd unit to conflict/replace plymouth-quit and ubuntu will get it updated at the same time newer sddm gets uploaded.
[11:06] <shadeslayer> xnox: is there a dev package for systemd?
[11:10] <shadeslayer> libsystemd-daemon-dev maybe
[11:11] <xnox> shadeslayer: i don't understand. What do you mean by a dev package for systemd? there a multiple shared libraries and static code headers that systemd src package ships in multiple dev packages.
[11:11] <xnox> shadeslayer: what are you after?
[11:12] <shadeslayer> xnox: cmake output from sddm http://paste.ubuntu.com/7736213/
[11:12] <shadeslayer> --   package 'systemd' not found
[11:12] <shadeslayer> and it does : pkg_check_modules(SYSTEMD "systemd")
[11:13] <xnox> shadeslayer: http://packages.ubuntu.com/search?suite=utopic&arch=any&searchon=contents&keywords=systemd.pc
[11:13] <xnox> shadeslayer: that's shipped in systemd package. "systemd.pc"
[11:13] <shadeslayer> aha
[11:13] <shadeslayer> thx
[11:14] <mparillo> On the project neon ISO from files.kde.org, is the greeter still Light DM? When my live session seemed to thrash too much, I used to ctrl alt F1, then sudo service lightdm restart, but that service was not found on the Neon ISO. Did it change?
[11:14] <shadeslayer> not sure why I didn't think of that, since I usually do that for cmake files
[11:14] <xnox> shadeslayer: i always simply search for the "foo.pc" file name to see which package i need to build-depend. That's the most reliable way.
[11:15] <shadeslayer> xnox: right, I do that for cmake files, but didn't think of doing it for pkgconfig files
[11:18] <apachelogger> with rpm you can builddep on pkgconfig names :P
[11:22] <xnox> apachelogger: which is excellent, until in debian & ubuntu we support multiple competing implementations to ship identical pkgconfig name ;-)
[11:22] <apachelogger> pft details :P
[11:30] <shadeslayer> can someone explain what this lintian warning means : http://lintian.debian.org/tags/init.d-script-not-marked-as-conffile.html
[11:30] <shadeslayer> I have /etc/init.d/sddm.conf which is generating that warning I guess
[11:31] <shadeslayer> E: sddm: init.d-script-not-included-in-package etc/init.d/sddm < 0.o
[11:32] <xnox> shadeslayer: per policy, one must have an init.d script, if there is an upstart and/or systemd files.
[11:32] <shadeslayer> ah
[11:32] <xnox> shadeslayer: and if there is init.d script shipped, it must be declared as a conffile and update-rc.d called in the postinst.
[11:32] <shadeslayer> now I need to write a init script
[11:32] <shadeslayer> great
[11:33] <xnox> shadeslayer: for ubuntu you don't, for debian you must. I will be encouraging you to file ITP in debian and I would be willing to sponsor sddm into Debian. Thus it's mandatory to write a compatible init script.
[11:34] <shadeslayer> I have no motivation to write a init script tbh :p
[11:34] <xnox> shadeslayer: otherwise it would be a waste of time further down the road, when someone else packages this for debian, differently from ubuntu, and someone (well, you as a touch it last) to do a complex three-way merge of diverged packaging.
[11:35] <shadeslayer> not to mention that the current init script I have is broken, since it doesn't stop sddm, and I don't know why
[11:35] <xnox> shadeslayer: it's not that hard, you just need to copy the sceleton, fill in /usr/bin/sddm, find a DM which doesn't integrate with plymouth and copy the lsb-headers essentially
[11:35] <xnox> shadeslayer: if you have one, I can help you debug it / review it.
[11:36] <shadeslayer> xnox: http://paste.ubuntu.com/7736340/
[11:37] <shadeslayer> xnox: fwiw sddm has a bug where it doesn't kill the X server when it shuts down
[11:37] <shadeslayer> so in case you plan on debugging that script, it's useful to know that :P
[11:41] <xnox> shadeslayer: pid should be in /run, not /var/run
[11:42] <xnox> shadeslayer: shouldn't have -> || echo -n "already running"; why is "--background" used?; any messages should use standard message helpers log_* as those know how to correctly print to terminal, serial console, and pass messages to plymouth
[11:43] <xnox> failing to stop error should not be ignored
[11:43] <xnox> nor reload
[11:44] <xnox> restart & force realod are broken in different ways.
[11:44] <xnox> (a) shouldn't sleep
[11:44] <xnox> (b) restart, can act on a different sddm, when that will fail 
[11:45] <xnox> (c) stop/start should be functions that can be called, instead of recalling the full init script
[11:45] <xnox> shadeslayer: the lsb headers on top are fine.
[11:46] <xnox> shadeslayer: i think you will have more luck with taking a clean skeleton, reuse lsb headers, reuse default display manager check
[11:46] <xnox> shadeslayer: but otherwise write start/stop/reload/status/restart from scratch based on stock template.
[12:31] <shadeslayer> xnox: ok
[12:31] <shadeslayer> ( sorry, was afk, lunching )
[13:17] <sgclark> Riddell: good morning, sorry I was up very late fixing install files, where are we at? did you find kcoreaddons?
[13:20] <Riddell> hola sgclark 
[13:21] <Riddell> no what's up with kcoreaddons?
[13:21] <sgclark> still @ 4.100.0
[13:21] <Riddell> mm
[13:21] <sgclark> all the frameworks that dpend on it are held up looking for 5.0.0
[13:23]  * Riddell looks
[13:24] <sgclark> Riddell: I can't for the life of me get into depot.kde.org or I would have looked myself
[13:28] <Riddell> sgclark: your ssh key is in the account for ftpubuntu@depot.kde.org
[13:28] <Riddell> sgclark: it was a patch was had been upstreamed, removed and uploaded
[13:30] <sgclark> Riddell: oh I have recently changed my ssh key, can you  use scarlett-Lappy https://launchpad.net/~sgclark
[13:33] <Riddell> sgclark: voila
[13:51] <sgclark> Riddell: kcoreaddons does not match what is in bazaar, and failed on install file
[13:52] <Riddell> sgclark: you want to fix or shall I?
[13:52] <sgclark> Riddell: i can
[14:13] <shadeslayer> xnox: where would I find a skeleton init script btw
[14:14] <yofel> shadeslayer: /etc/init.d/skeleton
[14:15] <yofel> also see /etc/init.d/README :P
[14:15] <shadeslayer> oh
[14:15] <shadeslayer> hehe
[14:15] <xnox> yofel:  ;-) two thumbs up
[14:15]  * xnox reads it again
[14:15] <xnox> it seems to be getting better and better, it offers more things the right way than what it did last time i looked at it ;-)
[14:24] <ghostcube> uhh nice kdeconnect 0.7.1 works very well
[14:30] <mcstr_> is it released yet?
[14:34] <mcstr_> oh yep it is :)
[14:47] <manchicken> Is there a telepathy ktp-text-ui plugin package that I'm not seeing? Telepathy seems like it's missing a whole bunch of stuff that I could have sworn was there before.
[14:53] <shadeslayer> manchicken: kde-telepathy-text-ui
[14:53] <shadeslayer> should be the package
[14:54] <manchicken> Does telepathy have the ability to highlight keywords and open IM windows on double-click of names in chat?
[14:54] <shadeslayer> wrong channel for support questions
[14:54] <shadeslayer> you want #kde-telepathy
[15:00] <manchicken> I'm just confused... I think I may have gotten the clients confused...
[15:00] <shadeslayer> Riddell: http://192.168.1.37:8000/
[15:43] <shadeslayer> hmm
[15:44] <shadeslayer> atleast my systemd unit works
[15:44] <shadeslayer> as does my init script
[15:45] <shadeslayer> xnox: for some reason plymouth doesn't quit on upstart
[15:46] <shadeslayer> so sddm doesn't start automatically
[15:52] <xnox> shadeslayer: what's your upstart job look like?
[15:52] <xnox> shadeslayer: it will not work at all, if you e.g. copied lightdm one.
[15:52] <xnox> shadeslayer: as i previously told you, since lightdm stops plymouth itself. For sddm you'd need to stop plymouth instead.
[15:52] <shadeslayer> xnox: that's what I was using
[15:53] <shadeslayer> http://paste.ubuntu.com/7737405/
[15:53] <xnox> shadeslayer: i think we'd need to modify plymouth-stop.conf to "start on starting ssdm" to one of it's conditions.
[15:54] <shadeslayer> ah yeah
[15:54] <xnox> or ssdm pre-start should do $ start plymouth-stop JOB=ssdm
[15:54] <shadeslayer> xnox: OTOH upstart script does call plymouth quit
[15:54] <xnox> to be compatible with previous non-modified plymouth's
[15:54] <shadeslayer> roger
[15:55] <xnox> shadeslayer: the upstart job looks wrong.
[15:55] <xnox> shadeslayer: the start on conditions are never satisfied, are they?
[15:55] <shadeslayer> because plymouth-stop is never called?
[15:56] <xnox> and your script does not call plymouth quit.
[15:56] <xnox> it only calls it conditionally, and you actually need to call it unconditionally.
[16:46] <shadeslayer> Riddell: http://192.168.1.37:8000/
[16:52] <sgclark> is anyone available to look at kauth, when I build locally the files are there.
[16:53] <sgclark> Riddell: ^
[16:53] <lordievader> Good evening.
[16:56] <Riddell> sgclark: let me look
[16:56] <Riddell> ki18n needs some love I think
[16:56] <Riddell> also I need a proofreader for http://kde.org/info/kde-frameworks-5.0.0.php
[16:57] <sgclark> Riddell: ummm 
[16:57] <sgclark> ki18n 1 hour 10 minutes ago 
[16:57] <sgclark> Successfully built
[16:58] <sgclark> not sure why red
[16:59] <Riddell> oh it's not automatically updating that page
[16:59] <Riddell> I need to do it manually
[16:59] <sgclark> ahh I have fixed several
[16:59] <sgclark> just having issues with kauth which is the current bottleneck
[17:01] <Riddell> updated
[17:01] <Riddell> now ki18n is a nice amber for new symbols
[17:06] <Riddell> sgclark: the build system for that code says # Compile only if fake backend has not been selected
[17:07] <sgclark> Riddell: I don't know what that means :(
[17:08] <Riddell> shadeslayer: was at http://cdimage.ubuntu.com/kubuntu-kde4/releases/hardy/
[17:08] <Riddell> sgclark: I would guess you have somthing like polkit-qt installed so it thinks there's another backend being compiled
[17:09] <Riddell> sgclark: since no backends work for kauth and it's generally broken, we'll just not install that file
[17:09]  * Riddell makes it so
[17:09] <sgclark> Riddell: ahh , ok, thanks!
[17:10]  * sgclark fixes ki18n symbols
[17:11] <shadeslayer> xnox: http://paste.ubuntu.com/7737738/
[17:11] <shadeslayer> does that look alright?
[17:26] <sgclark> Riddell: I have noticed etc/xdg files are beng installed in usr/etc/xdg triggering FSSTND-dir-in-usr , what is the proper way of dealing with this?
[17:28] <shadeslayer> that sounds wrong
[17:28] <sgclark> indeed
[17:28] <shadeslayer> which project?
[17:28] <sgclark> kf5
[17:28] <shadeslayer> which framework?
[17:29] <sgclark> two so far, kservice and kauth
[17:36] <Riddell> hmm, sounds like a problem in extra-cmake-modules
[17:39] <Riddell> sgclark: your last commite to ecm removed it http://paste.kde.org/pmvwyzdwo
[17:39] <Riddell> shadeslayer: ^
[17:39] <sgclark> Riddell: that broke the build altogether
[17:39] <sgclark> Riddell: it needs to be adjusted or something
[17:39]  * Riddell investigates
[17:57] <Riddell> sgclark: ecm ppa3 up with fixed patch, click rebuild on the failing packages when it's in
[17:57] <Riddell> sgclark: best not to remove patches unless you know they're no longer needed :)
[18:00] <Riddell> sgclark: where's your latest pmc?
[18:02] <sgclark> Riddell: that patched blocked the entire build process last night, could not move forward. Sorry I made the wrong decision to be able to get some packages done
[18:03] <Riddell> sgclark: actually I think it's my fault for removing the part of the patch to the test
[18:03]  * Riddell hangs head in shame
[18:03] <sgclark> Riddell: it is still in https://launchpad.net/~sgclark/+archive/kubuntu-utopic
[18:05] <Riddell> sgclark: you sure? that version doesn't have the NO_LINK_PLASMA set
[18:05] <sgclark> hmm, no I am not sure, looking
[18:07] <sgclark> Riddell: sorry in staging https://launchpad.net/~kubuntu-ppa/+archive/staging
[18:26] <Riddell> ScottK: bug 1334595 updated with SRU for plasma-mediacentre
[18:26]  * Riddell high fives sgclark on PMC win
[18:29]  * Riddell updates http://starsky.19inch.net/~jr/tmp/build_status_5.0.0_utopic.html
[18:29] <Riddell> sgclark: that's made with kubuntu-ppa-build-status in kubuntu-automation if you ever want to update it yourself
[18:29] <Riddell> ./kubuntu-ppa-build-status -p kubuntu-ppa/next -d utopic -v 5.0.0 > build_status_5.0.0_utopic.html
[18:32] <sgclark> Riddell: ahh ok, was wondering
[18:33] <sgclark> Riddell: unfortunately I have to step out for an hour or so :( kio needs a rebuild once kservice posts
[18:35] <sgclark> Riddell: nevermind looks like kservice is posting. I can get that before I go
[18:35] <Riddell> sgclark: I'm getting hungry and need to go home for my tea, ping me on gtalk or similar if you need me.  thanks for doing so much on this
[18:35] <sgclark> Riddell: ok, have a good day, I will resume when I get back :)
[20:15] <Quintasan> sgclark, Riddell: Do we have UPnP support in KDE now?
[20:26] <shadeslayer> Quintasan: yo
[20:26] <shadeslayer> Quintasan: plz review SDDM packaging
[20:26] <Quintasan> shadeslayer: \o
[20:26] <Quintasan> shadeslayer: gibe link
[20:26] <shadeslayer> while I learn rust
[20:26] <shadeslayer> Quintasan: git clone bzr::lp:~kubuntu-packagers/kubuntu-packaging-next/sddm
[20:27] <Quintasan> >git clone
[20:27] <Quintasan> >bzr
[20:27] <Quintasan> shadeslayer: You drunk?
[20:27] <shadeslayer> Quintasan: nope, just install git-bzr
[20:27]  * shadeslayer uses git everywhere now
[20:28] <Quintasan> ok
[20:28] <Quintasan> brb
[20:28] <Quintasan> shadeslayer: wtf is rust?
[20:29] <shadeslayer> Quintasan: http://www.rust-lang.org/
[20:29] <shadeslayer> Quintasan: http://doc.rust-lang.org/master/intro.html
[20:29] <shadeslayer> awesome stuff right there ^^, with all the goodness of pattern matching magic
[20:30]  * shadeslayer throws a keyboard at easyjet
[20:45] <shadeslayer> Quintasan: anyway, let me know what you think of SDDM
[20:45] <shadeslayer> I'll file a ITP tomorrow to get it into Debian
[20:51] <soee> do we have latest kde connect in repos already ?
[20:52] <Quintasan> soee: In utopic yest
[20:52] <Quintasan> yes*
[20:53] <Quintasan> shadeslayer: sorry, got caught up in zillons of conversations
[20:53] <Quintasan> looking
[20:53] <soee> Quintasan: what about backoprts?
[20:53] <shadeslayer> it is in backports
[20:53] <shadeslayer> !info kdeconnect trusty
[20:53] <shadeslayer> !info kdeconnect trusty-backports
[20:53] <shadeslayer> ^^
[20:53] <soee> :D
[20:53] <shadeslayer> soee: sudo apt-get install kdeconnect=0.7.1-0ubuntu3~ubuntu14.04.1
[20:54] <Quintasan> shadeslayer: TBH it should be a systemd unit not a init script
[20:54] <shadeslayer> Quintasan: it has all of the things
[20:54] <shadeslayer> ALL of the things!
[20:54] <shadeslayer> lesspipe the deb :)
[20:54] <Quintasan> I don't see systemd unit
[20:55] <Quintasan> well
[20:55] <shadeslayer> there is one
[20:56] <Quintasan> not in debian/ or I'm blind
[20:56] <shadeslayer> nope
[20:56] <shadeslayer> it's installed by upstream
[20:56] <Quintasan> shadeslayer: Anyways, no glaring mistakes I think
[20:57] <Quintasan> shadeslayer: You want me to comaintain that in Debian or you're going solo with this?
[20:57] <shadeslayer> Quintasan: I'll file the ITP tomorrow
[20:58] <shadeslayer> unless you want to do it now
[20:58] <Quintasan> shadeslayer: I'm going to take a look at it tomorrow too
[20:58] <shadeslayer> ok
[20:58] <Quintasan> Since I'm a tired like hell and might have missed something
[20:58]  * Quintasan had two exams today
[21:02] <soee> im on the daily snapshots of plasma-next now
[21:03] <soee> as i said yesterday all works nice except shortcuts ;)
[21:03] <soee> for example i can't take screenshot using prtscr button etc
[21:03] <soee> any idea what can cause this