[08:08] <apachelogger> kubotu: where did u go :'<
[08:08] <apachelogger> Riddell: https://launchpad.net/~kubuntu-packagers <- please make the group invite only + clear the pending list + add neon-builder (so that I can try to build automerging logic)
[08:09] <valorie> apachelogger: he might already have left for his holiday
[08:09] <apachelogger> Oo
[08:10] <lordievader> Good moorning.
[08:10]  * apachelogger thinks bluesystems people should need to send mails when they go on holidays :S
[08:10] <apachelogger> valorie: ur on the council are you not?
[08:13] <valorie> yes
[08:13] <apachelogger> valorie: https://launchpad.net/~kubuntu-packagers/+addmember
[08:14] <apachelogger> please add neon-builder there
[08:14] <valorie> he told Scarlett and me as we ate together for the final time in Brno
[08:14] <valorie> done
[08:15] <valorie> can I do the other things as well?
[08:15] <apachelogger> valorie: if you know where, I sent a mail to the council list if not :)
[08:15] <apachelogger> valorie: thanks for the adding
[08:15] <valorie> I see 8 pending members, but I know none of them
[08:15] <apachelogger> yeah, kick them all
[08:16] <valorie> oh, except howard
[08:16] <Riddell> valorie: the ones who applied this year might be good to e-mail and say to join us here
[08:16] <apachelogger> all our teams are invite-only anyway, and the applying thing only encourages people to randomly apply and cause spam and make it appear to the outside as though there might be some association
[08:16] <apachelogger> there's the Riddell
[08:16] <Riddell> apachelogger: yes I'm on holiday this week in the pyranees
[08:16] <apachelogger> Riddell: uh, lovely
[08:17] <apachelogger> Riddell: have fun and stuff :)
[08:18] <valorie> Riddell: done
[08:20] <apachelogger> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging-unstable/extra-cmake-modules/revision/35 =D
[08:22] <valorie> apachelogger: the team is already restricted
[08:23] <valorie> hmmm, opposum on my front porch
[08:24] <valorie> unsure how I feel about that
[08:24] <apachelogger> https://www.youtube.com/watch?v=gkofwx2liHM
[08:30] <valorie> omg, pet possum
[08:30] <valorie> I should find that cute
[08:30] <valorie> but I cannot get past the rat tail
[08:35]  * apachelogger rolls a dice on how to deal with changelogs in CI
[08:35] <apachelogger> we should totally have discussed this
[08:35] <apachelogger> #boffail
[08:39] <valorie> we talked a lot about changelogs
[08:40] <valorie> at least Rohan and Pino did at the party
[08:43] <shadeslayer_> apachelogger: ~kubuntu-packagers is already restricted
[08:45] <apachelogger> valorie: with CI the thing gets slightly more complicated though
[08:45] <apachelogger> albeit the notion of putting the changelog in a weird format in the VCS is a tad shitty to begin with
[08:46] <valorie> damn it, the last 2014 applicant has now disappeared before I could write hir
[08:46] <valorie> I did write to two of them
[08:47] <apachelogger> the problem might possibly autoresolve once we actually develop using CI, but right now the CI branches could have changes ontop of the PPA branches and then the changelog gets all sorts of weirdly screwed when merging
[08:47] <apachelogger> gives me a headache alright
[08:47]  * apachelogger should have continued reading mails
[08:47] <shadeslayer_> it's worse
[08:47] <shadeslayer_> emails are worse
[08:47] <shadeslayer_> distributions are hard to do, lets go shopping
[08:48] <apachelogger> valorie: fwiw, the mailing is not so useful, I used to do that for -members when it was not restricted and no one ever applied
[08:48] <valorie> how do other distros do it?
[08:48] <apachelogger> and I surely sent some 50 mails all in all
[08:48] <valorie> eh, I hate to just write them off
[08:48] <shadeslayer_> kubotu: botsnack
[08:48] <kubotu> shadeslayer_: schweet!
[08:49] <valorie> gives them one more chance if nothing else
[08:50] <apachelogger> well
[08:51] <apachelogger> the thing is, unless you know the person already they are most likely just badge hunters
[08:51] <apachelogger> like a lot of the people who are member of kubuntu-bugs actually ;)
[08:52] <valorie> sure
[08:52] <valorie> although the two to whom I did write were members of no other team
[08:52] <valorie> so who knows
[08:52] <apachelogger> that makes it even more likely :P
[08:52] <apachelogger> or they are drunk
[08:53] <apachelogger> like that person who assigned a long since fixed bug to themself and wanted information on how to fix it :P
[08:53] <valorie> lol
[08:53] <valorie> totally could be
[08:54] <valorie> in any case, can I help you in any other way?
[08:54] <apachelogger> nope, all good now
[08:54] <apachelogger> hugs!
[08:54] <apachelogger> Upload was likely rejected, we've been waiting for well over 20 minutes!
[08:55] <apachelogger> :@
[08:55] <apachelogger> my ppa script is broken again
[08:55] <apachelogger> and I dunno why
[08:55] <valorie> then /me heads to bed
[08:55] <valorie> have a good holiday, Riddell
[08:56] <valorie> I hope scarlett shows up all non-jetlagged
[09:09] <kfunk> Riddell: do you have any idea if there are some issues with gpg-agent in neon5?
[09:09] <kfunk> I've seen some mentioning of 'gpg-agent' in this channel a few months ago online.
[09:10] <kfunk> can you tell me where gpg-agent is normally started from?
[09:10] <apachelogger> ^ entirely possible since neon doesn't provide a lot of integration with the rest of the system
[09:10] <yofel> I had gpg-agent issues in utopic months ago, seem to have resolved themselves though
[09:10] <yofel> and it's started by /etc/X11/Xsession.d/90gpg-agent
[09:12] <kfunk> for me, it seems like gpg-agent is started (at least I see it running in ps), but apparently my KDE session doesn't contain the GPG_AGENT_INFO env variable
[09:12] <apachelogger> yofel, shadeslayer: who was assigned to moving frameworks to git.debian btw
[09:13] <shadeslayer> no one :O
[09:13] <yofel> ^
[09:13] <shadeslayer> AFAICR
[09:13] <apachelogger> that sounds wrong :P
[09:13] <yofel> also, Scott proposed using git-dpm, anyone of you guys familiar with that?
[09:13] <kfunk> ah, yeah. that's the issue. in my KDE4 session, I have GPG_AGENT_INFO set.
[09:13]  * apachelogger doesn't even know what a git-dpm is
[09:14] <apachelogger> ah yes
[09:14] <apachelogger> well
[09:14] <apachelogger> yes
[09:14] <apachelogger> yofel: we use bzr-buildpackage now so we'd use git-buildpackage with git :P
[09:14] <yofel> right, currently that was the plan
[09:14] <yofel> git-dpm seems a bit special with all the branch naming though
[09:15] <yofel> also, did you read my ping on #d-q-k?
[09:15] <apachelogger> dunno how it relates to git-buildpackage but generally everything is very configurable
[09:15] <apachelogger> that being said if the proposal is to hold the source in git I'd very much object to that
[09:15] <yofel> well, git-dpm has the upstream source in git, a branch for debian, and another one for all the patches which are then exported for quilt
[09:16] <apachelogger> if anything we'd want to have a repo clone of upstream
[09:16] <apachelogger> yofel: possibly something to look into
[09:16] <apachelogger> certainly not first stage of rollout though
[09:17] <apachelogger> also that reqiures one to first understand how git remotes work as otherwise people have to reclone stuff all the time, so I'd rather not spring that on Riddell for the time being ;)
[09:17] <apachelogger> yofel: I have no highlight btw in dqk
[09:18] <yofel> it's from saturday I think
[09:18] <yofel> anyway
[09:18] <yofel> our phonon4qt5-backend-gstreamer ships no service desktop file, correct or wrong?
[09:20] <apachelogger> correcto (I think)
[09:21] <apachelogger> mhm
[09:21] <apachelogger> correcto
[09:21]  * apachelogger didn't remember that he actually ported the KCM to the new lookup method xD
[09:22] <apachelogger> also it has silly debug
[09:22] <apachelogger> someone should fix that
[09:22] <shadeslayer> yofel: question, how did you find out the old scripts were broken
[09:22] <yofel> lets actually answer that on debian so diane gets the message
[09:22] <shadeslayer> ( I just fixed it in git
[09:22] <shadeslayer> )
[09:22] <shadeslayer> https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1369220/comments/7
[09:23] <shadeslayer> what's a genuine install
[09:23] <yofel> shadeslayer: I was trying to build debians phonon-backend-gstreamer and couldn't even build the source
[09:23] <shadeslayer> is my install not genuine?
[09:23] <shadeslayer> yofel: ah :)
[09:23]  * shadeslayer is fix0ring
[09:25] <shadeslayer> yofel: done btw
[09:25] <yofel> thanks :)
[09:26] <apachelogger> shadeslayer: what is that guy babbling on about anyway
[09:26] <shadeslayer> idk
[09:27] <shadeslayer> genuine ubuntu installs
[09:27] <shadeslayer> idk how one does genuine ubuntu installs
[09:27] <apachelogger> if bzr diff; then echo "ALL HAIL THE MIGHTY DIFF"; exit 1; fi
[09:27] <apachelogger> you know
[09:27] <apachelogger> the amount of code I don't remember writing is quite concerning
[09:27] <apachelogger> LISTEN
[09:27] <shadeslayer> :D
[09:30] <shadeslayer> oh much fun
[09:30] <shadeslayer> add header guards for firefox
[09:30] <shadeslayer> error: 'nsCommonRegistry' has not been declared
[09:30] <shadeslayer> well screw u
[09:31] <apachelogger> show me tha code
[09:32] <apachelogger> shadeslayer: cooooooooooooooode
[09:33] <shadeslayer> https://launchpad.net/~rohangarg/+archive/ubuntu/firefox/+files/firefox_32.0%2Bbuild1-0ubuntu0.14.04.2%7Eppa3%7Etrusty1.dsc
[09:33] <shadeslayer> food
[09:33] <shadeslayer> I need food
[09:34] <shadeslayer> snack
[09:34] <shadeslayer> someone find me a snack
[09:35] <apachelogger> https://www.youtube.com/watch?v=ly7PONiKGUs
[09:35] <shadeslayer> mm
[09:35] <shadeslayer> same thing on the i386 build
[09:36] <apachelogger> mate
[09:36] <apachelogger> can you give me a diff
[09:36] <apachelogger> I aint downloading no huge tar just to look at a diff
[09:36] <shadeslayer> apachelogger: the diff between old stuff vs new stuff or just the patch?
[09:37] <apachelogger> patch
[09:38] <shadeslayer> apachelogger: http://paste.ubuntu.com/8349290/
[09:39] <shadeslayer> hm
[09:39] <shadeslayer> that doesn't have the header guards
[09:39] <shadeslayer> moment
[09:40] <apachelogger> mh
[09:40] <apachelogger> shadeslayer: are you sure pkg-kde is in staging?
[09:40] <apachelogger> I added staging and CI still fails
[09:41] <apachelogger> ah dang
[09:41] <apachelogger> wrong stage -.-
[09:41] <shadeslayer> :p
[09:41] <apachelogger> I knew we should have made it a different group :P
[09:42] <shadeslayer> apachelogger: http://paste.ubuntu.com/8349316/
[09:43] <shadeslayer> ah
[09:43] <shadeslayer> aha
[09:43] <shadeslayer> +#ifdef nsCommonRegistry_h__
[09:43] <shadeslayer> bollocks
[09:44] <apachelogger> ?
[09:44] <shadeslayer> should be #ifndef
[09:44] <apachelogger> ah yes xD
[09:45] <shadeslayer> :p
[09:45] <apachelogger> u really should learn to copynpaste :P
[09:45] <shadeslayer> I was too drunk to do that clearly
[09:49] <apachelogger> so who's doing the git thing?
[09:49] <shadeslayer> Riddell
[09:49] <shadeslayer> because he's not here
[09:49] <shadeslayer> :p
[09:49] <apachelogger> that won't work :P
[09:52] <shadeslayer> apachelogger: sign me up
[09:52] <shadeslayer> someone has to do it
[09:52]  * shadeslayer will write up a plan
[09:58] <apachelogger> talking about singing up for things
[09:58] <apachelogger> someone needs to make the notes into cards I guess
[09:58]  * apachelogger beats CI into shape and does the cards afterwards
[10:02] <apachelogger> shadeslayer: it's still pending
[10:02] <apachelogger> ...
[10:02] <apachelogger>  Missing build dependencies: pkg-kde-tools (>= 0.15.15ubuntu1) 
[10:03] <apachelogger> pkg-kde-tools - 0.15.15ubuntu1~ppa3 
[10:03] <apachelogger> whoop whoop whoop whoop whoop 
[10:03] <apachelogger> and that is why we need CI, frameworks packages in staging do not actually reflect what is in bzr
[10:03] <shadeslayer> :/
[10:03] <apachelogger> some pile of hore poo this is
[10:04] <shadeslayer> idk what Riddell did
[10:04] <apachelogger> I lost an s
[10:04] <shadeslayer> yes
[10:04] <apachelogger> shadeslayer: it's what you did
[10:04] <shadeslayer> I didn't do anything
[10:04] <shadeslayer> wat
[10:04] <apachelogger> you twiddled the brancehs to dep >= ver while it should have been >= ver~
[10:04] <shadeslayer> no I did not
[10:04] <shadeslayer> those deps were reverted
[10:04] <apachelogger> shadeslayer: why is my ecm broken again
[10:05] <shadeslayer> define broken
[10:05] <apachelogger> cannot resolve dep
[10:05] <apachelogger> because it wants >= but can only get >= ~
[10:06] <shadeslayer> oh that
[10:06] <shadeslayer> wait
[10:06] <apachelogger> what the
[10:06] <apachelogger> Build-dep on pkg-kde-tools >= 0.15.15ubuntu1
[10:06] <apachelogger> Riddell: broke it
[10:06] <shadeslayer> told you
[10:06] <apachelogger> FFS
[10:07] <shadeslayer> apachelogger: I'm fixing it
[10:07] <shadeslayer> actually
[10:07] <shadeslayer> apachelogger: your jenkins bot broke it
[10:08] <apachelogger> what?
[10:08] <apachelogger> shadeslayer: the bot only commits to unstable
[10:08] <shadeslayer> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging-unstable/extra-cmake-modules/revision/35
[10:08] <shadeslayer> oh
[10:08] <shadeslayer> but that's what introduced the dep
[10:08] <apachelogger> from -next
[10:08] <apachelogger> unstable is not the live packaging we work on right now
[10:09] <shadeslayer> ok
[10:09] <shadeslayer> fixing
[10:09] <apachelogger> waits
[10:09] <apachelogger> ah yes
[10:09] <apachelogger> shadeslayer: plz be fixing
[10:10] <apachelogger> it appears jr actually used ver~ in the other packages
[10:10] <apachelogger> only ecm has ver without ~
[10:10] <shadeslayer> heh
[10:10] <shadeslayer> pushing
[10:10] <shadeslayer> apachelogger: fixed
[10:11] <apachelogger> uh uh
[10:11] <apachelogger> testing my new scripting 
[10:11] <apachelogger> let's see if the bot figures it out xD
[10:11] <apachelogger> if bzr wasn't so sloooo....
[10:11] <shadeslayer> use git bzr
[10:11] <shadeslayer> it's le fast
[10:12] <apachelogger> jenkins prolly won't want to do that 
[10:14] <shadeslayer> why not
[10:14] <apachelogger> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging-unstable/extra-cmake-modules/revision/36
[10:15] <apachelogger> much magic
[10:15] <apachelogger> interesting fact: if you bzr whoami with whatever email you can actually make launchpad show commits as though they had been made by someone else
[10:15] <shadeslayer> yes, sawn
[10:15] <shadeslayer> heh
[10:48] <BluesKaj> Hiyas all
[11:33] <apachelogger> http://paste.ubuntu.com/8349876/
[11:38] <apachelogger> shadeslayer: ^
[13:41] <mcstr_> listaller package is depending on some defective package here in kubuntu 14.04.1 can anyone confirm this?
[14:37] <mcstr_> listaller package is depending on some defective package here in kubuntu 14.04.1 can anyone confirm this?
[14:45] <ScottK> mcstr_: That's not something specific to Kubuntu, so this is likely not the best place to ask (the Kubuntu installer/updater doesn't even use packagekit).
[14:55] <apachelogger> wgrant: can I please get a quota bump to 5gib on https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable 
[14:56] <apachelogger> shadeslayer, yofel: I am expanding coverage to all frameworks now
[14:57] <apachelogger> if all goes well we should be able to throw away neon by the end of the month
[14:57] <shadeslayer> yay
[14:57] <apachelogger> mh
[14:57] <apachelogger> or maybe not
[14:58] <apachelogger> possibly worth to keep it for trusty until release
[14:58] <apachelogger> then ditch the trusty build and continue with ci builds for utopic and utopic+1
[14:58] <apachelogger> seeing as we'll want to backport frameworks to utopic but not trusty
[15:07] <ScottK> apachelogger: Why not trusty?  Last LTS seems like a good target for developers wanting a stable base to work off of.
[15:07] <apachelogger> because we'd need to backport qt
[15:08] <apachelogger> and I feel like it is entirely possibly that plasma might soon require 5.4 even because of DPI tech that landed there
[15:08] <ScottK> Ah.  Good reason.
[15:09] <apachelogger> we could possibly keep neon for trusty going a while longer and reduce the build scheduling from daily to weekly
[16:53] <genii> I found something odd. When trying to understand why kcmshell4 kcm_lightdm was not working in gdb, it complained about mismatched versions of ld-2.19.so  between /lib64/ld-2.19.so and the /lib/x86_64-linux-gnu/ld-2.19.so  complaining one is 64bit and one is PAE. Some digging reveals that libc6-amd64 has only a 32bit which it installs to /lib64/ for some reason, and the other is the stock libc6:amd64
[16:54] <genii> I must have installed something which required libc6-amd64 and it created this problem. 
[16:55] <genii> Replacing the /lib64/  32bit version with the proper 64bit version made everything work again.
[16:55]  * genii goes back to making coffee
[16:56]  * ScottK thought we didn't use /usr/lib64?
[16:58] <apachelogger> oh oh oh, that again reminds me of gdb being broken
[16:58]  * apachelogger runs into wall
[16:58] <genii> ScottK: When I do dpkg -S /lib64/ld-2.19.20 it reports:  libc-amd64 which apt-cache policy reports:         500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages
[16:58] <ScottK> Why do you have libc-amd64 installed?
[16:58] <ScottK> AIUI, that's ~obsolete.
[16:59] <genii> ScottK: I did not specifically install it, something else recently must have required it
[16:59] <genii> I could go back over install logs and take a look for it
[16:59] <ScottK> See what happens if you try to remove it.
[16:59] <genii> OK, 1 minute
[16:59] <ScottK> If it doesn't take anything with it, it ~should be fine.
[17:00] <genii> Should I purge?
[17:00] <ScottK> No
[17:02] <genii> ScottK: It removed fine, and now there's a symlink in /lib64 which points to /lib/x86_64-linux-gnu/ld-2.19.so
[17:03] <genii> Extremely weird.
[17:05] <snele> guys libreoffice kde file dialog integration seems to be broken on 14.04
[17:05] <snele> http://www.dodaj.rs/f/22/pb/1Vu8cW0n/snapshot58.png
[17:05] <apachelogger> things happen
[17:06] <apachelogger> jmux: do we need a qt patch to make it work again?
[17:09] <jmux> apachelogger: Not as far as I know
[17:13] <apachelogger> peculiar breakage then
[17:13] <apachelogger> snele: file a bug against libreoffice I guess
[17:13] <jmux> apachelogger: I just checked qt changelog and it seems it just contains one patch (out of three, with two mandatory)
[17:13] <apachelogger> :S
[17:14] <apachelogger> jmux: got a url for the second patch?
[17:14] <snele> apachelogger: against libreoffice or libreoffice-kde*
[17:14] <snele> ?
[17:14] <apachelogger> snele: same source package anyway
[17:16] <jmux> apachelogger: https://bugreports.qt-project.org/browse/QTBUG-34614
[17:16] <jmux> https://bugreports.qt-project.org/secure/attachment/40123/l-qclipboard_fix_recursive.patch
[17:17] <apachelogger> thanks, I'll prep a fix tomorrow
[17:17] <jmux> https://bugreports.qt-project.org/browse/QTBUG-38585
[17:17] <jmux> That is mandatory
[17:17] <jmux> No - lats one is optional...
[17:20] <jmux> And tehere is a new version of the first patch in the Qt5 queue, which I would like to backport, once it's accapted https://codereview.qt-project.org/#/c/94646/
[17:20] <jmux> Probably that'll happen this year ...
[17:21] <snele> apachelogger: done https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1369673
[17:22] <jmux> apachelogger: The old patch should still be fine, but has some busy waiting.
[17:28] <sgclark> hi all, can't seem to stop sleeping heh
[17:29] <Riddell> sgclark: jet lag will do that
[17:29] <sgclark> :(
[17:29] <Peace-> hola !
[17:30] <Riddell> sgclark: in the worst case melatonin does the trick and it's not even prescription in the US
[17:31] <sgclark> ok, will try that ty
[17:31] <sgclark> if I can stay awake long enough to go to store
[18:19] <apachelogger> whatever happened to santa
[18:21] <sgclark> Riddell: http://paste.ubuntu.com/8352225/
[18:22] <apachelogger> dafuq
[18:22] <apachelogger> what's with the cheating all the time
[18:25] <sgclark> Riddell: removing it, can add back if need be.
[18:26] <apachelogger> sgclark: that will break things
[18:27] <sgclark> apachelogger: i see ok...
[18:27] <apachelogger> sgclark: what that hack does is make every package that links against libsolidfoo *also* link against the qml thingy (which might not be needed, but OTOH that also sneaks it when it is needed, so removing it will potentially break applications)
[18:28] <apachelogger> to fix this properly we'd have to look at every package that currently links against libsolid and check whether it contains qml bits that use solid and if so manually introduce a dependency to the qml plugin package
[18:29] <apachelogger> or well, you know, move the qml things into the libsolid package and provide a fake package so that nothing could possibly break ;)
[18:29] <sgclark> ah ha. ok, sounds like something I can do at another time when I am less jet lagged. thanks for the explaination apachelogger
[18:30] <apachelogger> sgclark: yeah, alternatively maybe shadeslayer or I find the time to run a grep over all sources
[18:30] <apachelogger> on that note
[18:30] <apachelogger> shadeslayer: have I yet made a brain dump of how to detect qml dependencies?
[18:30] <apachelogger> I feel like I wrote some proof of concept code at some point
[18:31] <apachelogger> kfunk: did you get your gpg issue sorteD?
[18:32] <kfunk> not really.
[18:32] <kfunk> sec, phone
[18:51] <kfunk> apachelogger: so. I was wondering if $KDEHOME/env/* is still sourced as in KDE4. (because that's where I've started gpg-agent, usually)
[18:55] <apachelogger> kfunk: not impossible, terrbily unlikely though
[18:56] <apachelogger> also I am not sure why the env would get lost assuming gpg-agent should be started through an xsession file by deafult
[18:56] <apachelogger> could be a sddm defect though
[18:56] <apachelogger> unless you are not using sddm then it is even weirder
[18:58] <kfunk> i'm using sddm
[18:58] <kfunk> with the unholy ugly default theme
[18:58] <kfunk> (I never figured out how to install the breeze theme)
[19:01] <apachelogger> needs /etc/sddm.conf xD
[19:01] <apachelogger> anywho
[19:01] <apachelogger> kfunk: maybe try with lightdm
[19:01] <apachelogger> if that doesn't work then we'll have to take a deeper look 
[20:16] <Riddell> sgclark, apachelogger: what's wrong with that implicit dependency on qml-module-org-kde-solid?  me and shadeslayer did ask frameworks people in the office who said we should have the qml installed if the library is installed
[20:17] <sgclark> Riddell: I left it in for now. Lintian apparently thinks it should not be that way. apachelogger has better explaination above ^
[20:19] <Riddell> sgclark: yeah lintian will moan, override that I say
[20:20] <Riddell> else let apachelogger and vishesh fight it out
[20:20] <Riddell> but we have no magic way to detect dependencies on qml modules for now so it's far safer to leave it in
[20:58]  * Riddell snoozes
[20:59] <soee> :)
[20:59] <soee> can i display comment to last updat eof a packange in terminal ?
[22:33] <apachelogger> Riddell: right, then put the qml plugin in the library package
[22:34] <apachelogger> transitive symbols dependencies are wrong in 99.99999% of all the cases where you'd think "oh, I should use a symbols dep here"
[23:10] <ahoneybun> hey jose 
[23:10] <ahoneybun> whois inetpro 
[23:11] <ahoneybun> hey ovidiu-florin_ 
[23:16] <ahoneybun> should we update wordpress on the test site?
[23:16] <wgrant> apachelogger: Done.