[00:29] <valorie> ops in #kubuntu please keep an eye on greasyfat
[00:29] <valorie> I've warned him in #kubuntu-offtopic, but am now leaving for dinner
=== emma_ is now known as em
[03:39] <jalcine> has anyone written an basic OS/kernel?
[03:39] <jalcine> like when you were in school (if you learned how to code in school)
[04:58] <ahoneybun> jalcine:no on learns that anymore 
[04:58] <ahoneybun> in normal school anyway
[06:54] <kubotu> ::workspace-bugs:: [1264821] kscreenlock_greet insecure with multiple X screens @ https://bugs.launchpad.net/bugs/1264821 (by TJ)
=== soee__ is now known as soee
[08:13] <ahoneybun> hello
[08:16] <valorie> happy new year, ahoneybun
=== rperier_ is now known as rperier
=== ikonia_ is now known as ikonia
[09:23] <ahoneybun> happy new year valorie
[09:23] <ahoneybun> I had a smirnoff ice
[09:24] <jalcine> what about the rum? vodka? not even a bit of jack?
[09:24] <jalcine> c'monnnn
[09:24]  * jalcine prods ahoneybun
[09:25] <apachelogger>  /me sighs a bit
[09:25] <ahoneybun> jalcine: nope
[09:25] <jalcine> that's it
[09:34] <valorie> ewww, smirnoff ice
[09:35] <valorie> although probably about as good as the 'kitchen sink' that my son in law made me, which I think is what sunk me....
[09:35] <valorie> :-)
[09:38] <apachelogger> any bored packager around?
[09:41] <apachelogger> oh, now I broke lunchpad
[09:42] <valorie> phooey, must be up early for the contractors
[09:42] <valorie> niters all
[09:43] <valorie> happy new years to all
[10:41] <apachelogger> qt4-x11_4.8.5+git192-g085f851+dfsg-2
[10:41] <apachelogger> the versions debian uses :@
[10:53]  * apachelogger sighs a bit more
[10:55] <apachelogger> bug 1251140
[10:55] <ubottu> bug 1251140 in kde-runtime (Ubuntu) "KDE "display settings" control panel module displays empty window" [Undecided,Confirmed] https://launchpad.net/bugs/1251140
[10:55] <apachelogger> I think the krandr split wasn't very successful
[10:55] <apachelogger> but that's a different thing
[10:55]  * apachelogger confused
[10:56] <yofel> that opens kgamma when I try it..
[10:57] <apachelogger> kde-workspace-bin: /usr/lib/kde4/kcm_display.so
[10:57] <apachelogger> yofel: depends on what krunner offers
[10:57] <apachelogger> but there definitely is a KCM for display
[10:57] <apachelogger> kde-workspace-bin: /usr/share/kde4/services/display.desktop
[10:57] <apachelogger> the bug makes no sense
[10:57] <apachelogger> both are in the same package
[10:58] <apachelogger> oh
[10:58] <apachelogger> but it is empty
[10:58]  * apachelogger wonders why
[10:59] <apachelogger> ohhhh
[10:59] <apachelogger> yofel: it's a metakcm ... it adds tabs for display related nonesense
[10:59] <yofel> ah, fun
[10:59] <apachelogger> http://paste.ubuntu.com/6677849/
[10:59] <apachelogger> supposedly none of those is present in a default install of kubuntu
[11:00] <apachelogger> easy enough to fix0r
[11:01] <apachelogger> yofel: btw, are you bored? :P
[11:01] <yofel> not really :P
[11:02] <apachelogger> meh
[11:02] <apachelogger> I need a minion to merge qt, I am too old for this shit
[11:02] <apachelogger> In the future, the preferred way will be to to use bzr with bzr-builddeb plugin to perform merging. 
[11:03] <apachelogger> ^ I wonder if 6 years is enough future to use that workflow
[11:05] <apachelogger> apparenlty not
[11:07] <apachelogger> yofel: I am actually not sure what the point of that KCM is
[11:07] <apachelogger> it's not used in systemsettings
[11:07] <apachelogger> and metakcms seem like a bad idea... it's like systemsettings categories implemented the wrong way (i.e. statically listing content rather than letting content attach)
[11:07] <apachelogger> content being other KCMs xD
[11:07] <shadeslayer> hey
[11:08] <apachelogger> shadeslayer: yo
[11:08] <apachelogger> shadeslayer: welcome to the future
[11:08] <shadeslayer> \o/
[11:08] <shadeslayer> where's my spaceship
[11:08] <shadeslayer> or hoverboard
[11:08] <shadeslayer> I was promised a hoverboard ...
[11:13] <shadeslayer> apachelogger: btw plz look at touchpad stuff again, author says he's fixed pretty much everything except for where he didn't since he doesn't agree with that
[11:14] <apachelogger> shadeslayer: what's the stuff he did not agree with?
[11:14] <shadeslayer> everything that's not fixed ? :P
[11:14] <apachelogger> list plz
[11:15] <shadeslayer> apachelogger: don't have one, email quote "
[11:15] <shadeslayer> I've found http://quickgit.kde.org/?p=scratch%2Fsitter%2Ftouchpad-review.git&a=commitdiff&h=caaed675a2ae302e35fcf0dae4cfff05ab14ee70
[11:15] <shadeslayer> I've fixed most of these issues. With some other of them I disagree."
[11:16] <apachelogger> get a list :@
[11:17] <shadeslayer> apachelogger: yeah, asked for one
[11:17] <apachelogger> oh
[11:17] <apachelogger> ahhhhh
[11:17] <apachelogger> I can't even fix that display kcm
[11:17] <apachelogger> would cause string changeroo which likely will result in fuzzy strings in the translations
[11:17] <apachelogger> :@
[11:25] <apachelogger> that thing doesn't even have a bugs product/component
[11:51] <kubotu> ::runtime-bugs:: [1251140] KDE "display settings" control panel module displays empty window @ https://bugs.launchpad.net/bugs/1251140 (by kolen)
[12:03] <apachelogger> any thoughts on bug 1265301
[12:03] <apachelogger> ?
[12:03] <ubottu> bug 1265301 in kppp (Ubuntu) "kppp doesn't need to run suid" [Undecided,New] https://launchpad.net/bugs/1265301
[12:04] <apachelogger> Riddell: thanks for not preserving the kdenetwork changelog when splitting kppp :'(
[12:08] <shadeslayer> apachelogger: working on it
[12:08] <apachelogger> shadeslayer: on the list?
[12:08] <shadeslayer> on the kppp bug
[12:09] <shadeslayer> just a matter of changing permissions from 4754 to 0754 afaict
[12:12] <apachelogger> dude
[12:12] <apachelogger> read comment.......
[12:13] <BluesKaj> Howdy all
[12:23] <apachelogger> MESSAGE(STATUS "Warning: kppp use setuid")
[12:23] <apachelogger> install(TARGETS kppp PERMISSIONS SETUID OWNER_EXECUTE OWNER_WRITE OWNER_READ GROUP_EXECUTE GROUP_READ WORLD_EXECUTE WORLD_READ  DESTINATION ${BIN_INSTALL_DIR} )
[12:24] <apachelogger> upstream intended suid
[12:27] <apachelogger> it's madness
[12:34] <apachelogger> or we remove suid and blame debian if stuff is broken xD
[12:41]  * apachelogger sighs at bzr
[12:41] <apachelogger> oh
[12:41] <apachelogger> shadeslayer: if you are bored
[12:41] <apachelogger> bug 1265301
[12:41] <ubottu> bug 1265301 in kppp (Ubuntu) "kppp doesn't need to run suid" [Undecided,New] https://launchpad.net/bugs/1265301
[12:41] <apachelogger> eh
[12:42] <apachelogger> bug 1264887
[12:42] <ubottu> bug 1264887 in ubuntu-release-upgrader (Ubuntu) "After upgrade 12.04 -> 14.04 there was no display manager (kdm or lightdm)" [High,Confirmed] https://launchpad.net/bugs/1264887
[12:42] <apachelogger> shadeslayer: or you could merge qt4-x11 from debian
[12:42] <apachelogger> then throw that at some ppa for testing (see qt/plasma crash mail stuff on list)
[12:42] <apachelogger>   Uploading kppp_4.12.0-0ubuntu2_source.changes: done.
[12:42] <apachelogger> Successfully uploaded packages.
[12:43] <apachelogger> kppp is now 754 root:dip (same as debian)
[12:43] <apachelogger> it may work, it may not, impossible to test
[12:43] <apachelogger> also TBH kppp bugs seem to get 0 attention upstream
[12:43] <apachelogger> makes me hope -.-
[12:44] <apachelogger> in case someone is running 12.04 with a nvidia/intel hybrid graphics bug 1263469 may need validation (i.e. does whatever weird thing they are backporting work with kdm)
[12:44] <ubottu> bug 1263469 in lightdm-kde (Ubuntu) "[backport-request] 12.04.4 needs a newer version of lightDM-KDE " [Undecided,Won't fix] https://launchpad.net/bugs/1263469
[12:45] <apachelogger> bug 1008991  -.-
[12:45] <ubottu> bug 1008991 in synaptiks (Ubuntu) "synaptikscfg crashed with UndefinedPropertyError in _get_property_atom(): u'Synaptics Circular Pad'" [Undecided,Confirmed] https://launchpad.net/bugs/1008991
[12:49] <apachelogger> Riddell, ScottK: bug 1263972
[12:49] <ubottu> bug 1263972 in pykde4 (Ubuntu) "pykde4 FTBFS" [High,Confirmed] https://launchpad.net/bugs/1263972
[13:02] <apachelogger> shadeslayer: kdevelop isn't in bzr?
[13:08] <kubotu> ::workspace-bugs:: [1264016] can't create pen tablet profile @ https://bugs.launchpad.net/bugs/1264016 (by Risto Pekkala)
[13:14] <mitya57> apachelogger: the currently built pykde4 in trusty is newer than that bugreport…
[13:20] <mitya57> xnox: ^ can I close it?
[13:20] <xnox> mitya57: yes, please.
[13:21] <apachelogger> groovy
[13:21] <xnox> mitya57: i don't think we do a good job at closing ftbfs bugs, after it starts building again....
[13:22] <mitya57> done
[13:24] <shadeslayer> apachelogger: dunno about kdevelop
[13:24] <shadeslayer> you stole my package upload :(
[13:24] <shadeslayer> now I have nothing to upload to the ubuntu archive :(
[13:24] <jalcine> lol
[13:24] <jalcine> I'd say steal it back
[13:25] <jalcine> but that's not nice
[13:26] <shadeslayer> apachelogger: kppp also fixed for precise?
[13:28] <apachelogger> shadeslayer: good luck finding a tester
[13:29] <apachelogger> but no, only fixed for trusty
[13:29] <apachelogger> shadeslayer: upload qt4-x11 merge will you? :P
[13:30] <apachelogger> when I got up I was all like "today I shall change the world by making kf5 build, triage all the bugs I did not want to look at over the holidays and then prepare a qt485 for testing"
[13:31] <apachelogger> kf5 turned out to be kaput upstream, bugs are terribly time consuming and I am out of coffee
[13:31] <apachelogger> life's hard :(
[13:31] <lordievader> Good afternoon.
[13:36] <shadeslayer> apachelogger: is qt4-x11 already merged ? Or do I have to merge it ?
[13:38] <apachelogger> Programming language : C++ , PHP , ( HTML,CSS,JavaScript ).
[13:39] <apachelogger> one doesn't belong, which one is it xD
[13:39] <apachelogger> shadeslayer: you have to
[13:39] <apachelogger> well
[13:39] <apachelogger> grab-merge.sh at least
[13:39] <apachelogger> I did not actually look at the diff
[13:39] <eagles0513875> apachelogger: c++
[13:41] <apachelogger> I think it's css because it's not a programming language but a style sheet language (hence the name) :P
[13:41] <apachelogger> well that being said HTML is also no programming language but markup, so...
[13:42] <shadeslayer> fun qt4-x11 versioning from debian
[13:44] <apachelogger> yes :S
=== greyback is now known as greyback|lunch
[13:44] <shadeslayer> apachelogger: I don't think I have time to do a whole qt4-x11 merge today
[13:45] <apachelogger> pff
[13:45] <apachelogger> like I do :P
[13:46] <apachelogger> shadeslayer: doesn't have to be finished today anyway
[13:46] <apachelogger> just soonishy
[13:46] <apachelogger> so we can then do PPA backports to raring so that people can test 
[13:49] <ScottK> apachelogger: It's apparently fixed.
[13:49] <apachelogger> yes
[13:49] <apachelogger> magic
[13:49] <apachelogger> xD
[13:51] <apachelogger> https://bugs.kde.org/show_bug.cgi?id=326480
[13:51] <apachelogger> :O
[13:51] <ubottu> KDE bug 326480 in server "Akonadi fails to start with nvidia binary drivers installed" [Normal,Resolved: upstream]
[13:52] <apachelogger> graphics broke the spam
[13:52] <apachelogger> outragous
[13:57] <shadeslayer> :D
[13:57] <shadeslayer> apachelogger: Breaks: libqt4-core (<< 4.4.0~beta1-1)
[13:57] <shadeslayer> Replaces: libqt4-core (<< 4.4.0~beta1-1)
[13:57] <shadeslayer> can be dropped right
[13:57] <yofel> ah, so that's what was breaking akonadi on my system here :D
[13:58] <ghostcube> hmm kdeconnect still 0.4.1? any info when it wil get o 0.4.2?
[13:58] <ghostcube> *to
[14:04] <apachelogger> yofel: but how
[14:04] <apachelogger> yofel: according to the kde report the versions in 13.10 should be fine
[14:04] <apachelogger> shadeslayer: why?
[14:04] <yofel> people installing nvidia drivers from PPAs?
[14:05] <yofel> I only encountered it with that driver version in trusty
[14:05] <apachelogger> shadeslayer: https://launchpad.net/ubuntu/precise/+source/qt4-x11/+changelog probably
[14:05] <apachelogger> 4.4 must be way old
[14:05] <shadeslayer> apachelogger: Precise has 4.8.1
[14:05] <shadeslayer> so can easily be dropped no?
[14:06] <apachelogger> yofel: someone needs to close the report then because I'd probably write something like 'serves you right'
[14:06] <apachelogger> shadeslayer: yes
[14:06] <apachelogger> shadeslayer: please say why you think stuff can be dropped when you ask, now I had to lookup what version precise has :P
[14:06] <shadeslayer> The version in precise is burned into my memory
[14:07] <apachelogger> ahoneybun: your kubuntu docs mail to the lists was about the release docs?
[14:08] <apachelogger> because you did not link to the new docs, so... ;)
[14:08] <apachelogger> also you might want to say where reports should be filed :P
[14:08] <apachelogger> shadeslayer: how so?
[14:09] <shadeslayer> multiple people have asked where they can get a newer Qt for precise, at which point I've had to lookup what version Precise has
[14:09] <shadeslayer> over the course of the last 2 years
[14:10] <apachelogger> the apachelogger answer to that would have been: upgrade :P
[14:10] <apachelogger> well then
[14:10] <apachelogger> I think I looked at all the bugs since dec 23
[14:10] <apachelogger> they are all rubbish
[14:11] <apachelogger> except for the precise -> trusty upgrade issue, that seems important
=== greyback|lunch is now known as greyback
[14:24] <BluesKaj> apachelogger, trusty upgrade issue?
[14:33] <apachelogger> yes
[14:47] <shadeslayer> apachelogger: want to sort out the bluedevil situation
[14:48] <apachelogger> shadeslayer: ?
[14:48] <apachelogger> I am haxx0ring
[14:48] <apachelogger> what's there to sort?
[14:48] <shadeslayer> BlueDevil 1.X is EOL
[14:48] <apachelogger> that's handy
[14:48] <shadeslayer> well, ~EOL
[14:49] <shadeslayer> so we either stick to EOL release or switch to bluez5 and bluedevil 2
[14:53] <apachelogger> mail to ubuntu-devel && ubuntu-bluetooth?
[14:53] <apachelogger> bluez updatability really depends on the other partys IMHO
[14:55] <shadeslayer> yep
[14:55] <shadeslayer> between a rock and a hard place
=== ryanakca_ is now known as ryanakca
[15:04] <shadeslayer> fun
[15:05] <shadeslayer> apachelogger: since when has Qt4 not been merged
[15:05] <shadeslayer> I've found changes going back to 4:4.7.3 that haven't been merged
[15:23] <yofel> if you find the merge too boring, you could first fix the symbol files, nobody seems to have cared about those for a long time
[15:31] <shadeslayer> yofel: well, mostly done with debian/{control,rules}
[15:31] <yofel> shadeslayer++
[15:31]  * shadeslayer injects caffeine
[15:55]  * shadeslayer can't bear to look at the diff for the symbols files
[15:56] <apachelogger> lol
[15:57] <apachelogger> http://paste.ubuntu.com/6679178/
[15:57] <apachelogger> I am not sure I understand what I did there
[15:58] <mitya57> shadeslayer: In Qt5, I usually take Debian symbols, build in PPA and apply the delta from builders (there usually is no delta)
[15:58] <shadeslayer> oh
[15:58] <shadeslayer> well, lets see how that goes
[15:58]  * mitya57 hugs shadeslayer
[15:59] <shadeslayer> *hugs*
[16:00] <shadeslayer> mitya57: do you recommend the same for debian/patches as well
[16:03] <mitya57> shadeslayer: feel free to grab some refreshed ubuntu patches from lp:~kubuntu-packagers/kubuntu-packaging/qt4.8.5
[16:03] <mitya57> that was my failed attempt to do what you're doing now :)
[16:07] <shadeslayer> okay
[16:07] <shadeslayer> mitya57: thoughts about http://pastebin.kde.org/puxlxahub
[16:08] <shadeslayer> oh huh, p.k.o supports comments now
[16:11] <apachelogger> good thing it still autoscrolls
[16:11] <apachelogger> :@
[16:12] <mitya57> shadeslayer: commented :)
[16:12] <mitya57> Using GL ES on arm* is one of the most important delta
[16:14] <shadeslayer> mitya57: you missed out libglu-dev [!armel !armhf],?
[16:14] <mitya57> libglu-dev:
[16:14] <mitya57>   Installed: (none)
[16:14] <mitya57>   Candidate: (none)
[16:15] <shadeslayer> ah, it's called libglu1-mesa-devnow
[16:15] <shadeslayer> maybe
[16:15]  * shadeslayer looks
[16:15] <mitya57> shadeslayer: actually, all other "alternate" dependencies are gone too
[16:16] <mitya57> So it'll be just:
[16:16] <shadeslayer> yeah
[16:16] <mitya57> libgl1-mesa-dev [!armel !armhf], libgles2-mesa-dev [armel armhf], libglu1-mesa-dev [!armel !armhf]
[16:16] <shadeslayer> roger roger
[16:18] <shadeslayer> apachelogger: fwiw bluez has 46 reverse deps
[16:18] <shadeslayer> *build deps*
[16:19] <apachelogger> dont you mean build dependees?
[16:19] <shadeslayer> I do
[16:19] <apachelogger> anyway, that's why I said a bump needs to be brought up at ubuntu-devel
[16:19] <shadeslayer> I think I should go home as well ...
[16:19] <shadeslayer> yep, Debian does have a bluez5 package
[16:19] <shadeslayer> but yeah, looks doubtful if we'll get it done this cycle
[16:20] <apachelogger> gut doesn't feel too good about a bluez transition that wasn't organized before cycle started
[16:20] <apachelogger> what we can do is have both in the archive... also kinda fishy and we'd have to maintain it
[16:20] <shadeslayer> *nod*
[16:20] <shadeslayer> that's what I was thinking as well
[16:20] <apachelogger> since when do we know about the EOL thing?
[16:20] <shadeslayer> apachelogger: kde-packager
[16:21] <apachelogger> not long enough then
[16:21] <apachelogger> must have a bad release manager that bluedevil thing
[16:21] <shadeslayer> afiestas argues that between a kf5 port, a kde4 port he has no time
[16:21] <shadeslayer> so if he supports bluez4 he'll have to maintain 3 branches
[16:22] <apachelogger> yeah, that doesn't make it better from a actual-user-support POV :P
[16:23] <apachelogger> shadeslayer: guess debian needs to do some sort of support though, so I really don't think that upstream EOL is that big a problem
[16:23] <apachelogger> (assuming 1.3 doesn't have present fatal bugs all future bugs would either be of a bitrot nature or low impact ones)
[16:24] <apachelogger> and it's not like we throw resources at latter, so even if we can't go for bluez5 and need to stay with bluedevil 1.3 it should(tm) be fine
[16:26] <shadeslayer> ok
[16:26] <apachelogger> shadeslayer: would still ask on ubuntu-devel and ubuntu-bluetooth
[16:26] <shadeslayer> ack
[16:26] <apachelogger> at the very least we'd need a timeline for +1
[16:26] <shadeslayer> maybe for LTS+1
[16:26] <shadeslayer> right
[16:27]  * apachelogger needs to cleanup releaseme -.-
[16:30] <apachelogger> mh
[16:30] <apachelogger> kdesudo l10n stuck in import queue since forever
[16:36] <shadeslayer> mitya57: yeah, patchery is screwed
[16:36] <shadeslayer> I'll have a look at them tomorrow
[16:37] <apachelogger> shadeslayer: for the time being you could simply drop our patches and push that to a PPA
[16:38] <apachelogger> (a special ppa just for that build)
[16:39] <apachelogger> pending SRUs cards for saucy should get looked at sometime
[16:39]  * apachelogger cringes at amount of cards in 14.04
[16:39] <apachelogger> shadeslayer: you have too much stuff in doing again btw
[16:39] <apachelogger> https://trello.com/b/s8tG9Zlf/14-04
[16:39] <apachelogger> plz fix
[16:39] <apachelogger> jussi: reminder about activity to explain activities
[16:52] <apachelogger> shadeslayer: is mister party still on vacation?
[16:52] <apachelogger> oh and for https://trello.com/c/EUHfjxSC didn't we have a .2 candidate already?
[16:53] <apachelogger> anyway, off for today ... going to do poking for pending SRUs tomorrow
[16:53] <apachelogger> also, I guess looking at pending SRU verfications... if we have any
=== sem_ is now known as Peace-
=== cmagina_ is now known as cmagina
[22:44]  * valorie had coffee to share with apachelogger but I guess it's too late for that
[22:44] <apachelogger> indd, almost bed time :P
[22:46]  * yofel steals the cup and puts a coffee candy at the place it was ;P