[04:32] <mup> Issue operator#429 closed: Test harness set_leader erases relation data <Created by stub42> <Closed by stub42> <https://github.com/canonical/operator/issues/429>
[12:46]  * Chipaca brb
[13:31]  * facubatista didn't say hello today, shame on me
[13:32] <Chipaca> facubatista: i've been grumpy for days now it seems
[13:32] <Chipaca> facubatista: ｇｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｄ  ｍｏｒｎｉｎｇ！
[13:32] <facubatista> Chipaca, :)
[13:55]  * bthomas had IRC disruption due to 2.4ghz interference
[14:16]  * Chipaca had coffee, instead
[14:29] <bthomas> :)
[14:38]  * justinclark has a question
[14:38] <justinclark> Is there a way to create an event that is triggered when the app.status is Active? There's a configuration update that needs to take place after all k8s pods have settled and I'm struggling to find a good way to do that.
[14:39] <justinclark> I'm not tied to the app.status thing - really any way to have a piece of code run in a charm after all k8s pods are ready
[14:40] <justinclark> I've tried deferring events until that condition is true - and it kind of works. However, there could be several minutes before the deferred event re-fires.
[14:41] <bthomas> justinclark: How about tweaking liveness probe or adding a readyness probe ?
[14:42] <bthomas> justinclark: If Juju is forwarding requests to an application container that is not ready then either we are not doing the lifecyle management correctly or Juju has a bug or some behaviour has not been documented properly.
[14:45] <justinclark> I will try tweaking the probes. Though it looks like Juju is sending requests to pods that haven't completely started up yet.
[14:49] <Chipaca> justinclark: i think there is the intention of having juju events for that kind of thing but i don't know if it's planned yet
[14:49] <Chipaca> ^ jam?
[14:50] <Chipaca> also, aside, i'm going to make myself a lot of tea and have some paracetamol and lie down for a bit
[14:50] <bthomas> hope you get well soon
[14:53] <jam> @Chipaca, it is work on this cycle, though AIUI Mark is under the impression that Operator Framework could probably prototype it with the K8s integration already available inside the pod (by forking a process that would call back into juju-run to execute charm code)
[14:53] <jam> justinclark, bthomas ^
[14:53] <jam> The roadmap item is: https://docs.google.com/document/d/12aAYfhrKybaoWMV6HgTnJHP-sByqSurOj6PsNkdenRo/edit
[14:54] <jam> "lifecycle events as charm events"
[15:01] <bthomas> jam : With the current implementation can we assume Juju will set a application container's status as "active" only if both liveness and readiness probes pass ?
[15:02] <jam> bthomas, "set application container's status" what concrete field are you thinking about? (iow, what data are you trying to read)
[15:02] <jam> the value in "juju status"
[15:02] <jam> the contents of "self.model.app.status" ?
[15:02] <jam> some other field in K8s API?
[15:08] <bthomas> jam : following up on justinclark comment I was looking for a way we can ensure the load balanced ingress address does not forward an HTTP API request to an application container that was not yet ready to service it. I am thinking if we could do this by adding a readiness probe or tweaking the existing liveness probe. justinclark is sending an API request in response to a new peer relation and seems to be finding that it is bei
[15:08] <bthomas> forwarded to one of the new peers that are not yet ready to respond to it. I do not think the charm is doing any self.model.app.status check, and perhaps it does not need to since it is sending the request to the ingress address. justinclark : please correct me if I have misunderstood.
[15:09] <jam> bthomas, I am not sure how Juju is configuring the Service abstraction in front of the pods.
[15:09] <jam> https://kubernetes.io/docs/concepts/services-networking/service/ says that you should be using "readiness probes"
[15:09] <jam> so that K8s doesn't try to use a backend that isn't actually ready
[15:09] <jam> IIRC, *juju* can't know how to determine if an application is actually ready
[15:10] <bthomas> jam : agreed this is certainly one of the current shortcomings of our charm.
[15:10] <jam> so that is the responsibility of the charm to define the readiness of the application
[15:10] <bthomas> yes indeed
[15:11] <justinclark> bthomas - that is correct. And it does seem as though reducing the timeoutSeconds/initialDelaySeconds in the readiness probe helped things. The error will pop up once, but it always seems to resolve itself.
[15:12] <justinclark> This is using the ES Python module btw.
[15:12] <justinclark> This will all be unnecessary in ES 7.x :)
[15:13] <bthomas> justinclark: awesome! if readyness probe seems to work it saves us lot of clunky code logic. IMHO it may be a good idea to choose a timeout that does not lead to unpleasent behavior.
[15:13] <bthomas> justinclark: what will be unnecessary in ES 7.x ?
[15:14] <justinclark> Setting "minimum_master_nodes" is no longer necessary. We will probably still set some dynamic settings, but this one in particular is the issue.
[15:15] <bthomas> got it
[15:15] <justinclark> bthomas, we get this error: "illegal value can't update [discovery.zen.minimum_master_nodes] from [1] to [2]" because we're trying to set the value to be higher than the total number of nodes in the cluster.
[15:16] <justinclark> Anyways, I can continue this and give a more complete description in the Github issue.
[15:16] <bthomas> justinclark: will read . Can catch up after standup.
[15:16] <justinclark> Thanks bthomas, Chipaca, jam for helping out
[16:12] <justinclark> bthomas, holding off on the PR for a bit. Investigating some options to eliminate the error completely.
[16:28] <bthomas> justinclark: ack. enjoy the deep think :-)
[18:59] <mup> PR operator#430 opened: Docstrings for storage, log and model modules <Created by facundobatista> <https://github.com/canonical/operator/pull/430>
[22:12]  * facubatista eods


[21:00] <Maik> i find oxfuxxx's quit message a tad inappropriate: oxfuxxx<EMAIL_ADDRESS>has quit (Quit: Yankies Motherfuckers Cock Astroboys)


[01:43] <c2tarun> need help with application texlive. I want to check whether it is in repository or not? please check bug 712521
[02:25] <dantti> to build i386 packages do I need a chroot? if so is it better to use something like virtual box?
[02:26] <persia> chroots are typically fine to build stuff.
[02:42] <ryanakca> Quintasan: see git://git.debian.org/pkg-kde/kde-extras/bangarang.git
[02:43] <ryanakca> Quintasan: It was quicker for me just to redo it than to rebase/merge the two very much diverged branches.
[03:36] <dantti> in the build-depends I have added qt4-qmake but findQ4.cmake fails to find it in my pbuilder chroot, what could be wrong?
[03:37] <dantti> it even downloaded qt4-qmake...
[04:31] <Tm_T> ScottK: testing atm
[04:56] <Tm_T> ScottK: all seems to work, wlan not tested, but broadband tested instead
[04:57] <Tm_T> ScottK: and as usual, installer not tested other than "it runs"
[06:18] <CIA-40> [docmessages] yurchor * 1218741 * trunk/l10n-kde4/uk/ (14 files in 9 dirs) SVN_SILENT Ukrainian translation update
[10:30] <CIA-40> [docmessages] zepires * 1218763 * trunk/l10n-kde4/pt/ (12 files in 8 dirs) Finished HEAD for now
[10:33] <CIA-40> [messages] pelcak * 1218765 * trunk/l10n-kde4/cs/messages/ (6 files in 2 dirs) Update from Summit
[11:40] <GHH> Which is basic KDE Package For Ubuntu (GNOME)?
[11:49] <c2tarun> hi
[11:50] <droidslayer> c2tarun: hi :)
[11:51] <c2tarun> hi droidslayer :)
[11:51] <droidslayer> Riddell: booked your tickets yet? :P ...
[11:51] <droidslayer> c2tarun: ssup?
[11:51] <c2tarun> droidslayer: you booked your tickets?
[11:52] <droidslayer> Yep
[11:52] <droidslayer> Just got a mail from indigo
[11:52] <c2tarun> droidslayer: grt :)
[11:53] <droidslayer> :)
[11:58] <yofel> droidslayer: look at bug 681582 ;)
[11:59] <droidslayer> Yayyyy
[11:59] <droidslayer> Now all we need is jelmer to release it into LP
[12:00] <yofel> droidslayer: he did that a few hours ago :P
[12:00] <droidslayer> Ahhh
[12:00] <droidslayer> Kewl
[12:00] <yofel> and works :D
[12:00] <droidslayer> Thats the best part
[12:00] <droidslayer> :)
[12:01] <droidslayer> I'll start on something in 90 mins
[13:12] <ScottK> Tm_T: Thanks.
[13:29] <ScottK> Tm_T: Released the image based on your testing.  Thanks again.
[13:38] <dantti> does anyone has a good link to how do I create simple upstart scripts? my googling is not being helpfull (at least I can't start my job yet :P )
[14:01] <yofel> dantti: there are enough examples in /etc/init/ - and there's http://upstart.ubuntu.com/
[14:02] <dantti> yofel: yep, I didn't know that there were stored at /etc/init/ :P , now I'm strugling on how to make cmake install it :P
[14:09] <persia> dantti, If you're packaging an app, use dh_installinit
[14:12] <dantti> persia: I'm going to but shouldn't I first install it in the right location with cmake?
[14:13] <persia> If you do that, you have to pass --onlyscripts to dh_installinit, which may complicate your packaging.
[14:59] <kshadeslayer> so i'll need someone to sponsor a upload of kdegames to natty soonish
[15:01] <ghostcube> hi folks i just noticed there is still no ubuntu-one kde interface
[15:01] <ghostcube> is this planned? cause in this bug report it doesnt seem so
[15:01] <ghostcube> https://bugs.launchpad.net/ubuntuone-client/+bug/375145
[15:05] <kshadeslayer> well ....
[15:05] <kshadeslayer> i'll let apachelogger answer that one
[15:05] <kshadeslayer> ghostcube: basically u1 api keeps getting broken and there is no way we can keep up with that
[15:06] <ghostcube> ah ok :) cause in the ubuntu mailing list there has been a question about ubuntu-one in kde and thats not working somehow
[15:06] <ghostcube> kshadeslayer: thx for the answer so far :)
[15:13] <debfx> gnaa, will the lp bug watch spam ever stop?!
[15:14] <shadeslayer> debfx: just unsubscribe from kubuntu-bugs
[15:14] <shadeslayer> i'll subscribe back in 4-5 days when everything returns to normal
[15:14] <debfx> shadeslayer: I'm not subscribed to that list, just individual bug reports
[15:14] <shadeslayer> ah
[15:15] <shadeslayer> i'm not subscribed to many individual bug reports ;)
[15:15] <debfx> lucky you ;)
[15:36] <shadeslayer> apachelogger: master ... i've read the Ubuntu Design guidelines ... ;)
[15:37] <ghostcube> shadeslayer: nah not master :) old man  lulz
[15:37] <ghostcube> *hide and run*
[15:37] <shadeslayer> haha :P
[15:38] <shadeslayer> ghostcube: he claims he is 19
[15:38] <ghostcube> born in 19xx
[15:38] <ghostcube> :D
[15:38] <shadeslayer> lol
[16:38] <shadeslayer> so can someone sponsor a upload of kdegames from  https://launchpad.net/~rohangarg/+archive/kde-extra when it lands there
[16:39] <debfx> I need some sponsoring too :)
[16:42] <debfx> hm maybe I should apply for kubuntu-dev ...
[16:43] <yofel> ah, you did the kajongg stuff
[16:43] <shadeslayer> yep
[16:43] <shadeslayer> yofel: oh do we close bugs with this package?
[16:45] <shadeslayer> doesn't look like it
[17:04] <c2tarun> hi
[17:04] <tazz> hi
[17:04] <c2tarun> tazz: do you know any tutorial that explains how to look at the diff file?
[17:04] <c2tarun> tazz: I mean diff output
[17:05] <tazz> c2tarun, http://www.linuxtutorialblog.com/post/introduction-using-diff-and-patch-tutorial
[17:06] <c2tarun> tazz: thanks a lot :)
[17:07] <c2tarun> Riddell: hi, I backported bluedevil to maverick yesterday. take a look at bug 712678
[17:07] <c2tarun> Riddell: I mean not backported :P requested :)
[17:21] <yofel> shadeslayer: nope, I never filed one on lp
[17:21] <shadeslayer> ok
[17:21] <shadeslayer> yofel: i fixed it for you ... go test :P
[17:22] <yofel> jussi wanted it, I just debugged it until I got stuck at cmake and had the kde folks fix it
[17:23] <shadeslayer> ah
[17:23] <c2tarun> can anyone please explain me this error: http://paste.ubuntu.com/562650/
[17:23] <shadeslayer> jussi: its fixed ... just needs to be uploaded to natty ;)
[17:23] <shadeslayer> c2tarun: Hunk #1 FAILED at 21.
[17:23] <shadeslayer> fix the patch
[17:24] <c2tarun> shadeslayer: how to fix the patch? can you please explain a bit.
[17:24] <shadeslayer> c2tarun: so patches are based ontop of existing code
[17:24] <shadeslayer> if the base code changes, your patch needs to be updated
[17:25] <c2tarun> we need to update the patch? not apply the patch>
[17:25] <c2tarun> the patch? *
[17:25] <yofel> well, your patch fails to apply
[17:26] <yofel> since the code has changed
[17:26] <yofel> so you either need to update or remove it depending on the upstream changes
[17:26] <yofel> spcifically debian/patches/02-string_h.patch
[17:27] <c2tarun> yofel: i removed it first, I thought it is already applied in upstream. but see the comment https://bugs.launchpad.net/ubuntu/+source/bibshelf/+bug/713023
[17:27] <yofel> c2tarun: maybe you dropped the wrong patch?
[17:28] <yofel> from the name of the failed one there seems to be more than one  patch
[17:29] <c2tarun> yofel: I usually dont get that how the patches work? Any suggestions where can i read about them?
[17:30] <yofel> patches are changes to the source
[17:30] <c2tarun> yofel: who create patches?
[17:30] <yofel> so if you find a bug in the upstream code, and need to fix it immediately you would add a patch to the package
[17:30] <yofel> depends
[17:30] <yofel> you can use a patch from upstream, or you can create your own one
[17:30] <yofel> depending on the situation
[17:31] <yofel> upstream patches would usually come from the version control system where upstream has fixed a bug, and you take the diff from that fix
[17:31] <c2tarun> yofel: why upstream introduce patches? can't they change the source code directly?
[17:32] <yofel> upstream doesn't usually introduce patches, they sometimes do if a fix has to be shipped immediately,  but they can't release a new upstream version, or that would take too much time
[17:33] <yofel> usually you would look at the upstream fix, and then create a patch yourself
[17:33] <yofel> another case for patches are when the upstream code doesn't work on your system without changes (for whatever reason)
[17:33] <yofel> or when you want to include a modification in the upstream program that upstream  isn't interested in
[17:34] <c2tarun> yofel: so what is meaning of a patch fails?
[17:35] <yofel> when you create a patch, the diff contains part of the code so when the patch is applied, the program knows *where* to apply those changes
[17:35] <shadeslayer> and if the file where the patch has to be applied changes
[17:35] <shadeslayer> kaboom ... ;)
[17:35] <yofel> if the code changes, those parts of the code that the patch remembers aren't there anymore, so the progam doesn't know what to do -> FAIL
[17:36] <yofel> c2tarun: as for your case...
[17:37] <yofel> c2tarun: new debian packages automatically apply patches when you unpack them, so if you want to see if a fix was included upstream, you need to look at the plain upstream source
[17:37] <yofel> so it seems that you somehow packaged it, the patch got applied, you checked if the fix was applied upstream after that and decided to drop the patch
[17:37] <yofel> so the patch still appeared in the packaging diff.gz
[17:38] <yofel> (that's what Chris tries to tell you on the bug)
[17:40] <c2tarun> yofel: how can i check whether a patch is applied to upstream?
[17:40] <c2tarun> yofel: and you said patches get automaticall applied while unpacking, if so then they should give error while unpacking only?
[17:40] <yofel> check what the patch does, and see if the upstream code already contains those changes
[17:41] <yofel> no, the unpacking process went fine, it seems you copied the debian/ folder in such a situation or something similiar and then tried to build that
[17:42] <c2tarun> yofel: ya i copied it.
[17:42] <yofel> and dpkg source format 3 will then create a debian/patches/debian-changes-1.6.0-0ubuntu1
[17:42] <yofel> you shouldn't have such a file unless you edited the source manually without patches
[17:42] <yofel> (necessary sometimes, but rarely)
[17:43] <c2tarun> yofel: can you please explain again how can i check whether a patch is applied or not?
[17:45] <c2tarun> yofel: ping
[17:45] <yofel> easy way? unpack the upstream source and try to apply the patch. If it fails like it did now you'll know you need to update
[17:45] <yofel> c2tarun: and please give me some time to type...
[17:45] <shadeslayer> yofel: hehe ... jelmer is on #launchpad right now
[17:45] <shadeslayer> good time to thank him :P
[17:45] <c2tarun> yofel: sure :) sorry i poked
[17:46] <c2tarun> yofel: is there anyother way to apply the patch without running debuild
[17:46] <yofel> c2tarun: ... update the patch, or remove it, for latter you'll have to read the files and check if the changes are the same
[17:46] <yofel> c2tarun: sure, 'patch -p<level> < patchfile', read the manpage on what level means
[17:47] <shadeslayer> usually the level is 1
[17:48] <yofel> c2tarun: also, since your package uses source format 3.0 (quilt) - you should read http://wiki.debian.org/Projects/DebSrc3.0 at least once, it has some links on how to use quilt too
[17:49] <yofel> (quilt is a patch management system)
[17:49] <c2tarun> yofel: sure
[17:49] <yofel> takes a bit getting used to, but it's much easier to manage than what we had before..
[17:55] <dantti> I asked this mornig but I guess ppl were sleeping :P , when I run debuild-pbuilder to build a package the compilations fails saying qt qmake was  not found (tho I use cmake and qmake is installed), any tips?
[17:56] <yofel> dantti: got the actual error?
[17:57] <dantti> yofel: CMake Error at /usr/share/cmake-2.8/Modules/FindQt4.cmake:1148 (MESSAGE):  Qt qmake not found!
[17:57] <dantti> isn't that?
[17:57] <shadeslayer> so i finally found out why apachelogger wants unicorns
[17:57] <shadeslayer> http://mingle2.com/dating/unicorn
[17:58] <yofel> lol
[17:59] <yofel> dantti: odd, should be fine as long as you have qmake-qt4...
[17:59] <dantti> yofel: very...
[18:00] <dantti> yofel: tbh I have just tried running cmake on the regular user and still the same issue, maybe kde4.6 related? lol :P
[18:01] <yofel> dantti: what are you trying to build?
[18:01] <yofel> (since this is FindQt4, do you have libqt4-dev installed?)
[18:02] <dantti> yes I do, actually I can build my qt4-app on my old build dir...
[18:02] <yofel> odd
[18:03] <c2tarun> Is it ok if I apply each patch to newer version one by one and then remove them all. and then pack?
[18:04] <shadeslayer> c2tarun: uh ... what?
[18:04] <shadeslayer> you need to check which patch is failing and fix that particular patch
[18:05] <c2tarun> how can I fix a patch, I don't know anything about the source code? :(
[18:05] <yofel> c2tarun: if you apply all patches before packaging it would defy the point of them being there...
[18:05] <c2tarun> Is there any way to check whether a patch is failing or not? without applying them?
[18:06] <yofel> I only know testapply and read the source, shadeslayer?
[18:06] <shadeslayer> same thing
[18:06] <shadeslayer> quilt too
[18:06] <shadeslayer> c2tarun: apply the patches using quilt, and check which one fails
[18:07] <shadeslayer> then go through the patch and then the source code and see what has changed
[18:08] <c2tarun> shadeslayer: why should I see what has changed? I mean what is use of it? :(
[18:09] <shadeslayer> c2tarun: like yofel said, if there was a critical fix that came out after upstream released the source code, we incorporate it in our packages via a patch system
[18:09] <yofel> well, someone had a reason to add the patch, so before you remove the patch you need to see if that reason still exists
[18:09] <shadeslayer> these patches need to be refreshed/dropped when packaging a new release etc
[18:10] <yofel> if in doubt, talk to the person that added the patch and have them look
[18:10] <shadeslayer> for that you need to look at the changelog ;)
[18:13] <c2tarun> That is what I am not able to understand :( If a patch applies properly than it is correct because I borrowed that patch from the previous version, if current version contains the old bug fixed by that particular patch we should apply the patch or leave it there. If patch fails then there is no point of using that patch as upstream may have changed the source code and fixed the bug. So in either cases we don't need to look at the source code :(
[18:13] <yofel> c2tarun: and what if they changed the source for a different reason and didn't fix the bug the patch is there for?
[18:14] <shadeslayer> exactly
[18:14] <yofel> so the patch is still needed but doesn't apply anymore and needs to be updated
[18:14] <shadeslayer> ( that's usually not the case tho ;) )
[18:14] <yofel> yeah, but does happen
[18:14] <yofel> anyway...
[18:14] <shadeslayer> yep
[18:15] <yofel> what happend in your case was a packaging mistake it seems
[18:15] <yofel> can you start from scratch and see if it still fails?
[18:15] <shadeslayer> yofel: take qtwebkit for example ... there are patches there which qtwebkit can't/won't apply upstream
[18:16] <yofel> yep
[18:16] <c2tarun> so first we check whether a patch is applying or not. If it fails then we have to fix that patch :( hmm....
[18:16] <shadeslayer> c2tarun: if it fails, check if the patch is needed or not
[18:16] <c2tarun> shadeslayer: that seems to be a daunting task :(
[18:16] <shadeslayer> and then if isn't, remove it, if it is, update it
[18:17] <shadeslayer> c2tarun: you'll get used to it ;)
[18:17] <c2tarun> shadeslayer: one more prob. :( I am not able to understand the format of patch file. Can u help me with that ?
[18:17] <shadeslayer> c2tarun: syre
[18:17] <shadeslayer> *sure
[18:17] <shadeslayer> one sec
[18:18] <c2tarun> shadeslayer: ok.
[18:18] <c2tarun> :)
[18:18] <yofel> usually it's the output created by 'diff' 'diff -ruN' usually
[18:18] <shadeslayer> c2tarun: a patch is basically a difference between 2 files, the old one and new one
[18:18] <shadeslayer> yofel: -ruNad
[18:18] <yofel> or you use quilt, then quilt will take care of creating the file containg your differences
[18:19] <c2tarun> shadeslayer: http://paste.ubuntu.com/562682/ look at this patch file
[18:19] <yofel> ah
[18:19] <yofel> didn't know ad ^^
[18:19] <shadeslayer> yofel: me neither ... apachelogger told me :P
[18:19] <yofel> heh
[18:19] <shadeslayer> that is one awesome looking patch i must say
[18:20] <c2tarun> shadeslayer: :/ suppose if this patch fails, can u explain please where to look?
[18:20] <shadeslayer> c2tarun: SigC namespace has been deprecated since libsigc++ 2.0.
[18:20] <shadeslayer> read line 2 ;)
[18:20] <ari-tczew> shadeslayer: do you merging ktorrent?
[18:21] <shadeslayer> ari-tczew: haven't looked at it yet ... im trying to fix some rekonq ssl errors
[18:21] <c2tarun> shadeslayer: got to go, roomies b'day. i'll be right back.
[18:21] <shadeslayer> cya :)
[18:21] <shadeslayer> i'm here all night :P
[18:21] <ari-tczew> shadeslayer: I'm interested in merge ktorrent.
[18:21] <shadeslayer> ari-tczew: feel free to take up
[18:24] <ari-tczew> ok
[18:40] <c2tarun> shadeslayer: u there?
[18:40] <shadeslayer> yep
[18:40] <shadeslayer> ssup
[18:40] <c2tarun> enjoyed the cake :) anyway you looked at that patch file?
[18:41] <shadeslayer> yep
[18:41] <shadeslayer> c2tarun: read line 2
[18:41] <shadeslayer> the SigC namespace was deprecated
[18:42] <shadeslayer> so basically SigC was renamed to sigc
[18:42] <c2tarun> ok. then
[18:49] <c2tarun> shadeslayer: actually I want to know that suppose this patch fails what to do then?
[18:50] <shadeslayer> c2tarun: right ... then you look at the sources
[18:50] <shadeslayer> open src/DialogBook.h
[18:50] <c2tarun> sources as like DialogBook.h?
[18:51] <shadeslayer> right now i'm wondering why they have function declaration in their header files o_O
[18:52] <shadeslayer> c2tarun: go to the extracted folder, and cd to src/DialogBook.h
[18:52] <shadeslayer> and then search for that particular line
[18:53] <c2tarun> ok wait
[18:53] <c2tarun> Ya i opened it
[18:53] <c2tarun> + means lines added and - means removed? right?
[18:53] <c2tarun> shadeslayer: ^
[18:53] <shadeslayer> yep
[18:54] <shadeslayer> c2tarun: keep highlighting me ... i tend to loose track of stuff :P
[18:54] <shadeslayer> yofel: http://paste.kde.org/~shadeslayer/4141/ << O_O
[18:55] <shadeslayer> need to fix the flipping style issues
[18:59] <Guest79423> shadeslayer: sorry i got disconnected. you there?
[18:59] <shadeslayer> c2tarun: yep
[19:00] <c2tarun> so + means lines added and - means lines removed?
[19:00] <shadeslayer> yep
[19:00] <shadeslayer> c2tarun: http://en.wikipedia.org/wiki/Diff
[19:00] <shadeslayer> read that
[19:00] <shadeslayer> shouldn't take alot of time
[19:00] <c2tarun> sure :)
[19:05] <c2tarun> shadeslayer: I got to go :( very sorry. I'll read your document. Can you please tell me any book on Qt programming?
[19:06] <shadeslayer> c2tarun: ever programmed in C++?
[19:06] <shadeslayer> http://qt.nokia.com/developer/books/ >>
[19:06] <c2tarun> shadeslayer: yup, C,C++ and JAVA but in all to basic level. I mean no networking or anything like that
[19:06] <shadeslayer> c2tarun: and i'm not talking about Turbo C++ :P
[19:07] <shadeslayer> ok .. shouldn't be much of a issue, im learning stuff myself ... so i'd say read tutorials from http://doc.qt.nokia.com/
[19:08] <Daskreech> jjesse: hi
[19:09] <c2tarun> shadeslayer: ya sure. I haven't used windows since last six months :)
[19:09] <shadeslayer> alright :D
[19:09] <shadeslayer> c2tarun: you'll  be fine :)
[19:09] <shadeslayer> read up on widgets and layouts
[19:09] <shadeslayer> signal's and slots too
[19:10] <c2tarun> shadeslayer: signals?
[19:11] <Quintasan> c2tarun: ping
[19:11] <Quintasan> apachelogger: ping
[19:12] <c2tarun> hi Quintasan :)
[19:12] <shadeslayer> Quintasan: apachelogger doesn't have interwebz ... he is in Egypt
[19:12] <Quintasan> like
[19:12] <Quintasan> what?
[19:12] <Quintasan> Why on earth is he in Egypt?
[19:12] <shadeslayer> Quintasan: jk
[19:13] <Quintasan> lol
[19:13] <shadeslayer> you're not on fb are you
[19:13] <Quintasan> I do own a fb account but I rarely use it
[19:13] <yofel> my wifi is seriously cursed
[19:13] <shadeslayer> Quintasan: lrn2socialize? :P
[19:13] <Quintasan> ryanakca: I will check the bangarang and upload it, apachelogger
[19:13] <yofel> hi Quintasan
[19:13] <davmor2> yofel: only when you use it though right :)
[19:14] <yofel> indeed
[19:14] <Quintasan> shadeslayer: lrn2togoingout instead of facebook :P
[19:14] <c2tarun> Quintasan: what are you going to do on bangarang?
[19:14] <shadeslayer> heh
[19:14] <shadeslayer> Quintasan: http://wstaw.org/m/2011/02/04/plasma-desktopJk1818.jpg
[19:15] <Quintasan> c2tarun: review the debian stuff that ryanakca commited and upload it to Ubuntu since we won't be getting it so fast in debian
[19:15] <Quintasan> ryanakca: What was blocking it again, KDE 4.6?
[19:15] <shadeslayer> OH
[19:15] <shadeslayer> Quintasan: plz upload kdegames
[19:16] <shadeslayer> Quintasan: fancy debs from https://launchpad.net/~rohangarg/+archive/kde-extra
[19:16] <Quintasan> only when I'm done with bangarang
[19:16]  * Quintasan introduced policy of not doing more than one package at once
[19:17] <shadeslayer> also ... don't package after 12 AM ... you can only code after 12 AM
[19:18] <shadeslayer> bug 710582
[19:18] <shadeslayer> O_O
[19:18] <yofel> wtf calls a namespace wtf o.O
[19:18] <shadeslayer> yofel: apple
[19:19] <shadeslayer> and yeah .. KDE has this namespace called WTF :P
[19:20] <shadeslayer> yofel: any ideas on how to test http://bugs.kde.org/show_bug.cgi?id=261337
[19:21] <shadeslayer> like some very shody site that has a untrusted certificate etc
[19:21] <yofel> hm, I did hit one a while ago, lemme find it
[19:21] <shadeslayer> bwahaha .... i dont have krunner
[19:22] <shadeslayer> notes.kde.org used to be untrusted
[19:22] <shadeslayer> then it was fixed
[19:22] <yofel> you're supposed to praise kde, not break it...
[19:24] <shadeslayer> yofel: known bug ... i reported it
[19:24] <shadeslayer> stupid spell check plugin
[19:24] <yofel> hahaha
[19:27] <yofel> shadeslayer: this gives me an  untrusted warning https://www.wzdftpd.net/blog/index.php?post/2008/02/05/3-quilt-a-patch-management-system-how-to-survive-with-many-patches
[19:27] <shadeslayer> *click*
[19:27] <shadeslayer> yofel: rekonq?
[19:27] <yofel> nope, ffx
[19:28] <DarkwingDuck> wait, rekonq has the built in spell check?
[19:28] <shadeslayer> hmm same on rekonq
[19:28] <DarkwingDuck> :P:P
[19:28] <shadeslayer> DarkwingDuck: you wish
[19:28] <shadeslayer> it's coming
[19:28] <DarkwingDuck> shadeslayer: didn't you say that at UDS? :P:P
[19:28] <shadeslayer> I know for a fact that the part that draws the squiggly lines is working
[19:28] <shadeslayer> DarkwingDuck: i also said it has to be done in webkit
[19:29] <shadeslayer> but yep, it's being actively developed
[19:29] <DarkwingDuck> shadeslayer: oh yeah... I pretty much pointed at apachelogger when you said that. hehehe
[19:29] <shadeslayer> hahah :D
[19:29] <shadeslayer> hmm
[19:30] <shadeslayer> so i need a kolab server for testing
[19:30] <shadeslayer> now how do i get one of those :S
[19:31] <maco> why does clicking that link result in the notifier thing in my panel starting to download it, instead of it just opening in firefox like *every other link*???
[19:31] <Quintasan> Riddell: ping
[19:31] <Quintasan> or JontheEchidna
[19:31] <shadeslayer> maco: doesn't it open a web browser?
[19:31] <maco> shadeslayer: no
[19:32] <shadeslayer> maco: 4.6?
[19:32] <maco> shadeslayer: nah normal maverick
[19:33] <shadeslayer> quite possibly that KDE 4.5 thinks that the link can be downloaded
[19:34] <shadeslayer> maco: in krunner : keditfiletype text/html
[19:34] <shadeslayer> Does it have anything in Application Preference order?
[19:34] <shadeslayer> ( Also ... i can't remember which KDE version, there was this bug where it would download URL's to /tmp )
[19:35] <maco> hrmph can i use a normal shell? krunner's not running
[19:35] <shadeslayer> yep
[19:53] <ryanakca> Quintasan: At least 4.5 to compile, but apachelogger said that it would be really crummy without 4.6
[19:53] <CIA-40> [messages] schlander * 1218816 * trunk/l10n-kde4/da/ (16 files in 8 dirs) translation update
[19:54] <maco> shadeslayer: it has firefox first
[19:54] <maco> shadeslayer: but it also says *.htm and *.html .... while that page lacks a file extension
[19:55] <shadeslayer> hmm
[19:55] <shadeslayer> maco: the mimetype of that page is text/html
[19:55] <shadeslayer> so it shouldn't matter
[19:55] <maco> shadeslayer: maybe 4.5 only uses extensions not mimetype?
[19:55] <shadeslayer> don't think so ... kio could be buggy
[19:58] <ari-tczew> ryanakca: are you going to merge offlineimap from Debian?
[20:02] <ryanakca> ari-tczew: I had completely forgotten about it. If you want to, feel free to nab it... I don't think I've touched it since maverick, I don't remember why I dropped it...
[20:07] <neversfelde> Debian-specific changes are no longer stored in a single .diff.gz but in multiple patches in debian/patches/. It is compatible with quilt (hence its name) but does not require its usage as dpkg-source is able to do everything needed by itself. It applies patches at extraction time and update the patch series at build time.
[20:07] <neversfelde> I am not sure about this?
[20:07] <neversfelde> when should those patches been removed in ubuntu?
[20:09] <neversfelde> it's because of bug 706409
[20:09] <shadeslayer> ok i'm sleeping
[20:09] <shadeslayer> night all
[20:11] <CIA-40> [docmessages] yurchor * 1218823 * trunk/l10n-kde4/uk/ (14 files in 8 dirs) SVN_SILENT Ukrainian translation update
[22:48] <JontheEchidna> http://i.imgur.com/13U8G.png KSpread is the most relevant result for "spreadsheet" :D
[23:17] <Quintasan> JontheEchidna: still there?
[23:17] <JontheEchidna> yup
[23:18] <Quintasan> JontheEchidna: http://dl.dropbox.com/u/69524/bangarang_2.0-0ubuntu1.debian.tar.gz
[23:18] <Quintasan> JontheEchidna: Care to review? I'm not sure if leaving the changelog this way would be alright
[23:19] <JontheEchidna> hmm
[23:20] <JontheEchidna> I'd remove that unreleased bit since its not relevant
[23:20] <JontheEchidna> !info bangarang natty
[23:21] <JontheEchidna> I'm seeing a 2.0-0ubuntu1 in natty already.
[23:21] <JontheEchidna> bug 712532
[23:21] <Quintasan> what?
[23:22] <Quintasan> damn apachelogger
[23:22] <JontheEchidna> I don't think he had anything to do with that (for once :P)
[23:22] <Quintasan> JontheEchidna: He was pestering me to do it since he wanted it for FOSDEM or something like this
[23:23] <JontheEchidna> oh
[23:23] <JontheEchidna> trollface.jpg
[23:23] <Quintasan> FFFFF
[23:24] <Quintasan> * Add the missing dependency on gstreamer0.10-x
[23:24] <Quintasan> I knew I missed something :S
[23:25] <JontheEchidna> you know
[23:25] <JontheEchidna> somebody could make a rageface emoticon theme for KDE
[23:25] <JontheEchidna> would be so boss
[23:25] <Quintasan> adn trollface
[23:26] <Quintasan> and*
[23:26] <CIA-40> [messages] alvarenga * 1218845 * trunk/l10n-kde4/pt_BR/messages/ (12 files in 8 dirs) [KDE-pt_BR]
[23:26] <JontheEchidna> http://i.imgur.com/vjZ6I.jpg
[23:27] <Quintasan> JontheEchidna: lol, good one
[23:27] <Quintasan> and hooray for broken x stack
[23:28] <Quintasan> I'm sooooo tired, I feel like sleeping all day tomorrow but we should kinda get Neon sorted
[23:28] <ScottK> Riddell: This kubuntu_news fellow on twitter really ought to update his branding ....
[23:30] <Quintasan> Okay, I'm going to bed, nothing good will come out of working in a half-asleep state
[23:30] <Quintasan> Good night. :)


[18:00] <charlie-tca> Do we know the date of the next meeting?
[18:10] <Pendulum> the next full team meeting is September 15th
[18:10] <Pendulum> (I actually remembered to put it in the topic for once!)
[18:16] <charlie-tca> heh, Everything happens given time...
[18:19] <charlie-tca> You mean I should have read it?
[18:19] <Pendulum> haha
[18:19] <charlie-tca> change the date here to update the meeting times on the wiki now
[18:19] <charlie-tca> https://wiki.ubuntu.com/Accessibility/Header
[18:19] <Pendulum> nah, I don't really expect people to read the topic if they've been around for a while
[18:19] <Pendulum> *nods*
[18:20] <Pendulum> charlie-tca: btw, since I'm sure you wouldn't have notcied the topic, we have logs now :P
[18:20] <charlie-tca> You are right! Thanks
[18:21] <Pendulum> they're on irclogs.ubuntu.com
[19:37] <webczat> Hey.
[19:37] <webczat> Why I can't access synaptic from ubuntu-10? I mean i can't use it with orca.
[19:48] <Pendulum> webczat: what exactly are you trying to do? could you potentially add the package you're looking for from the command line instead?
[19:48] <Pendulum> (Sorry, I have no real experience with Orca so can't tell you exactly what the problem is)
[19:49] <webczat> Pendulum: i can use command line but things like update manager use synaptics i think
[19:49] <Pendulum> ah, okay
[19:50] <Pendulum> you can also update by doing "sudo apt-get update" (without the quotation marks)
[19:51] <webczat> it's upgrade i think. i meant upgrading the system
[19:51] <webczat> it's update manager. or upgrade manager.
[19:51] <Pendulum> what are you trying to upgrade to?
[19:52] <webczat> not trying to upgrade to. it's just an example of a program using synaptics
[19:52] <Pendulum> ah, okay
[19:52] <webczat> also, language support when installing packages. i just can't see anything/any progress bar or whatever
[19:52] <Pendulum> *nods*
[19:53] <webczat> update manager also does the same but it just returns after updating. the language manager first notifies (when in root) that it installed the package and requires me to press close while nothing talks to me.
[19:53] <Pendulum> I'm really sorry, I wish I could help, but I really know nothing about Orca. Have you tried asking either on the mailing list, forums, or filing a bug?
[19:53] <AlanBell> oh, I know this one
[19:54] <AlanBell> I saw a bug about it today
[19:54] <AlanBell> it is because you run synaptic with sudo access
[19:54] <webczat> no, irc is faster if someone is on it
[19:54] <AlanBell> and the root user you switch to does not have at-spi (or orca or it is disconnected from your session or something)
[19:55] <Pendulum> oh dear, that's a rather major bug
[19:56] <AlanBell> it was a blueprint I saw, not a bug https://blueprints.launchpad.net/ubuntu/+spec/sudo-admin-atspi
[19:57] <Pendulum> that's really old, though
[19:57] <AlanBell> that is a 2006 blueprint, might be done by now
[19:57] <Pendulum> the whiteboard says it was done and submitted for Feisty
[19:58] <Pendulum> webczat: what version of Ubuntu are you using?
[19:58] <webczat> Pendulum: lucid.
[19:59] <Pendulum> hmm... this is a year old, but I wonder if the same fix would work<EMAIL_ADDRESS>[19:59] <Pendulum> webczat: have you tried running synaptic from the command line as "sudo synaptic"?
[20:00] <AlanBell> just trying it with orca on my laptop, it doesn't read synaptic after the gksudo prompt
[20:01] <Pendulum> yeah, that seems to be the issue
[20:01] <AlanBell> and sudo gedit from the command prompt doesn't read gedit
[20:01] <Pendulum> there's a question from this month on the Orca list, I think, but no one has answered
[20:03] <Pendulum> webczat: you're not the Milton who posted a question to orca-list about this issue last week, right?
[20:07] <webczat> no
[20:07] <webczat> what about making orbit enable ipv4 and disable unix? can someone try to enable it for both root and user?
[20:08] <AlanBell> that would make sense
[20:08] <AlanBell> I was trying to run orca with sudo but it doesn't want to start
[20:09] <webczat> AlanBell: Try it. Can you? If you'll enable this thing in orbit and relogin, it should probably use user's at-spi
[20:10] <webczat> I don't have the ubuntu laptop yet.
[20:10] <webczat> like, i have it but i currently can't use it
[20:11] <webczat> but i want to have it accessible at wednesday. also, i was required to manually set accessibility to true and as mandatory in gconf editor to be able to set accessible login in gdm
[20:11] <webczat> s/at/on
[20:11] <webczat> i mean i can set it but it doesn't really enable at-spi even if restarted
[20:13] <webczat> also, i can do sudo-u gdm <gconftoolusagehere) to enable accessibility in gdm, it doesn't do that itself. but it's cool that i can, for example, run orca preferences in gdm
[20:14] <charlie-tca> some work done on https://wiki.ubuntu.com/Accessibility ; review in progress
[20:19] <AlanBell> not sure how to get it to use IP sockets, all the documentation I see is about the move to dbus
[20:19] <AlanBell> just wondering if this has been addressed in vinux
[20:29] <webczat> AlanBell: wait, i'll give you the config
[20:30] <webczat> file is .orbitrc in homedir
[20:31] <webczat> http://equal.cluenet.org/~webczat/orbitconf do you get it?
[20:35] <webczat> AlanBell: try to put it in /root, if doesn't work, then also in your homedir and relogin then
[20:41] <AlanBell> ok, put that in /root/.orbitrc and /home/alan/.orbitrc and now rebooting
[20:44] <AlanBell> doesn't seem to help
[20:45] <AlanBell> just going to try booting into Maverick
[20:48] <AlanBell> broken in Maverick too
[20:50] <webczat> Wait for a while, i'm now trying to set up the workflow for bugs in trac repo. or i will try
[20:53] <webczat> Hmm, or not. anyway, going off.
[20:54] <AlanBell> ok, I will mention it to themuso if I see him online later webczat
[21:40] <webczat> re


[10:36] <maxiaojun> ubuntu-desktop meta package shouldn't recommend ibus*
[10:38] <maxiaojun> ibus-pinyin struck in an old version in debian/ubuntu pretty annoying and useless
[10:38] <maxiaojun> ibus-table is also useless by itself, it is meta engine that requires some data file to work
[10:40] <maxiaojun> https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1164252
[10:40] <ubot2> Launchpad bug 1164252 in ubuntu-meta (Ubuntu) "Improve default selection of IBus related packages" [Undecided,New]


 Making decent coffee is an art
[13:54] <Maaz> Coffee's ready for Kilos!
[13:54] <Kilos> Maaz, ty buddy
[13:54] <Maaz> Dont get familiar now Kilos
[14:14] <nlsthzn-work> Kilos: Hey :p
[15:10] <n8wulf> Eish... me thinks me needs to get me some Weeds
[15:15] <n8wulf> O:-)
[15:22] <superfly> n8wulf: most people like to get rid of weeds - I don't want them in my garden
[17:02] <n8wulf> superfly: haven't you heard, "don't drink & Drive... rather smoke and Fly".... Mango Airline here I come
[17:02] <n8wulf> well... anyway, I had to settle for Captain & Cola
[17:03] <n8wulf> freakin stressful week is finally over
[19:00] <Kilos> lo kbmonkey
[19:01] <kbmonkey> hello :)
[19:01] <Kilos> i installed maverick alongside again and it fixed the old one too
[19:01] <Kilos> so now i happy again
[19:01] <Kilos> but freezing
[19:02] <kbmonkey> oh thats good news!
[19:02] <Kilos> yeah
[19:03] <kbmonkey> I was trying this window manager called Awesome, it tiles windows automagically
[19:15] <nlsthzn> kbmonkey: had a look @ awesome scared me :p
[19:17] <kbmonkey> ye its way different hay
[19:45] <superfly> *very* different
[19:46] <superfly> -_- freebsd is a bit of a pain if you don't know it


[00:06] <Prezident> Whats wrong, you cant connect to wifi stormpython ?
[00:07] <Prezident> Or you need a program that handle the wpa connection?
[06:14] <lordievader> Good morning.
[06:38] <Lightsword> hi, I symlinked a fil to my nginx html folder but I get a 403 error every time I try and access it
[06:38] <Lightsword> I tried chown -h www-data:www-data but it didn’t help
[06:38] <Lightsword> for the file
[06:42] <lordievader> Lightsword: Not sure if nginx is configured the same, but for Apache the directory linked to needs to be configured. So Apache know to whom it can be displayed, etc.
[06:42] <Lightsword> lordievader, its just a file symlink not a directory symlink
[06:43] <Lightsword> it works if I run nginx as root
[06:43] <Lightsword> but not when I run it as www-data
[06:43] <lordievader> Hmm, so www-data has no read access to the file.
[06:44] <Lightsword> seems like it but no idea why
[06:45] <lordievader> Lightsword: Could you give me a 'ls -l' of the file?
[06:45] <Lightsword> lrwxrwxrwx 1 www-data www-data   27 Feb  6 00:04 index.html -> /root/logs/pool/pool.status
[06:45] <lordievader> That is the symlink, I want the file ;)
[06:46] <Lightsword> -rw-r--r-- 1 www-data www-data 387 Feb 18 01:45 pool.status
[06:46] <lordievader> Lightsword: On second thought make it: ls -la /root/logs/pool/
[06:46] <lordievader> !paste | Lightsword
[06:47] <Lightsword> http://paste.ubuntu.com/10286034/
[06:48] <lordievader> Lightsword: Likely the problem is that nginx cannot traverse the directory.
[06:48] <Lightsword> any idea why?
[06:49] <Lightsword> its some sort of permissions issue it seems since I’m getting a 403
[06:49] <lordievader> Lightsword: Because the directories don't have the x flag set for other.
[06:50] <Lightsword> what would be the command to fix that?
[06:51] <lordievader> Lightsword: Set execute bits on those directories.
[06:51] <Lightsword> chmod + x /root/logs/pool/ ?
[06:52] <lordievader> Lightsword: Read the man page ;)
[06:54] <Lightsword> am I supposed to flag it as executable?
[06:55] <lordievader> Lightsword: The directories, yes.
[06:56] <lordievader> From the man page "execute (or search for directories) (x)".
[06:59] <Lightsword> I switched to hardlinking the file and it worked
[06:59] <lordievader> No wonder...
[07:00] <Lightsword> yeah, didn’t know it made a difference for nginx
[07:01] <lordievader> Nginx doesn't really have anything to do with that. You made a new pointer to the data, likely with different permissions.
[08:52] <Repox> Hi guys. I'm having an issue with a service, and since the service I'm trying to start doesn't actually start, I was hoping someone would know where I should start looking instead? http://serverfault.com/questions/669522/elasticsearch-wont-start-as-a-service-no-log-is-created
[09:52] <spidernik> hello. I have a bit of a problem with the debian-installer. I'm fetching the preseed file via https from our server. We use self-signed certs and the installer fails because the cert is not considered trusted... I'm not sure what would be the best approach to solve this while retaining https
[10:01] <TJ-> spidernik: I'd think the certificate, or your local CA cert, would need rolling into the installer image
[10:18] <spidernik> TJ-: Thanks. That's making things tricky. I'm a bit surprised because I'm having this issue only with the trusty-installer, not with the precise one.
[10:19] <TJ-> spidernik: Maybe because with all the stories about MITM, everyone's been tightening up transport security and ensuring certificates are validated
[11:02] <frawg> Can you use juju to deploy charms to the maas-controller? Or can it only be used to deploy to nodes?
[11:16] <spidernik> TJ-: it makes sense! Thank you, I'll do some research to implement this
[12:26] <Cosan> hi
[12:30] <hadifarnoud> can someone help me modify this script to install nginx and php-fpm instead of apache?
[12:30] <hadifarnoud> https://gist.github.com/JeffreyWay/9244714
[12:35] <lordievader> hadifarnoud: Change line 10 & 24?
[12:35] <hadifarnoud> lordievader: so I keep everything else?
[12:36] <hadifarnoud> line 18
[12:36] <hadifarnoud> 12
[12:36] <lordievader> Ah, yes 18 too.
[12:37] <hadifarnoud> 12 should be ok, right?
[12:37] <lordievader> Does that repo offer php5-fpm?
[12:37] <hadifarnoud> not sure. this is someone else's script
[12:37] <hadifarnoud> did not try it
[12:37] <lordievader> You might want to change 21 too.
[12:39] <lordievader> Try the steps manually, you'll see soon enough if things fail.
[13:02] <White_Cat> Is it a bad idea to tinroduce GUI to an ubuntu server?
[13:03] <rbasak> White_Cat: it's not very useful, and can complicate things. If you want a desktop environment, install Ubuntu desktop on a separate machine.
[13:03] <White_Cat> no I already have a server
[13:04] <White_Cat> I am not exactly linux proficient
[13:04] <rbasak> There aren't many (if any) GUI tools that will help you run a server.
[13:04] <White_Cat> oh okay
[13:05] <rbasak> What does exist generally expects you to run the GUI locally, and the GUI will connect over the network to the server.
[13:05] <White_Cat> I am currently strugling to introduce a new drive to the server :/
[13:05] <White_Cat> rbasak thats fine too :)
[13:05] <White_Cat> in fact preferable
[13:09] <White_Cat> it would be nice to use gparted for example
[13:09] <White_Cat> :/
[13:10] <ogra_> cfdisk isnt that much harder to use
[13:13] <rbasak> You could try booting the live ISO, using gparted and then booting back.
[13:13] <White_Cat> no I tink cfdisk can get the job done
[13:13] <White_Cat> so I will use this disk as backup
[13:14] <White_Cat> should I configure it as primary or logical?
[13:14] <White_Cat> I think I will use grandfather-father-son backup rotatoin scheme
[13:33] <lordievader> White_Cat: Even parted isn't hard to use.
[13:37] <Lumia930> Hi : (http://testsvr:3343/csvn/) admini console is accessible using host name but (http://svn.testsvr.com:18080/svn/) Repository parent is unable to access via hostname ... when i change that IP am able to get access !!!!
[13:38] <White_Cat> lordievader hmm
[13:38] <White_Cat> I dont think the new drive is detected
[13:39] <White_Cat> maybe my difficulty is that there is a problem
[13:41] <rbasak> White_Cat: lsblk or "cat /proc/partitions" will tell you what drives the system sees.
[14:07] <White_Cat> rbanffy it only sees sda
[14:07] <White_Cat> sdb hasnt been initilised yet though
[14:07] <White_Cat> it doesnt even have a partition table
[14:08] <rbanffy> White_Cat, wrong rb*
[14:08] <rbanffy> rbasak, White_Cat is actually mentioning you
[14:09] <White_Cat> oh
[14:09] <White_Cat> sorry
[14:09] <White_Cat> that was embarassing
[14:10] <lordievader> White_Cat: Is it an internal of external drive?
[14:12] <White_Cat> internal
[14:12] <White_Cat> I have a raid 5 configuration which is running ubuntu
[14:12] <White_Cat> I have a seperate 2tb drive that will serve as backup
[14:45] <coreycb> jamespage, zul: testing has completed on 2014.2.2 juno
[14:45] <coreycb> successfully
[14:45] <jamespage> coreycb, in utopic?
[14:45] <coreycb> jamespage, yes
[14:45] <jamespage> coreycb, urgh - we should flush that into the CA earlier
[14:46] <jamespage> coreycb, it won't auto-backport until it hits updates...
[14:46] <jamespage> coreycb, but that's still awesome
[14:46] <coreycb> jamespage, hmm, ok so in the future should we move it into the CA when it gets into utopic-proposed?
[14:47] <jamespage> coreycb, I think so
[14:47] <jamespage> coreycb, you can do that manually with the backport_package job in the jenkins qa lab
[14:47] <jamespage> just tick the proposed option and list the pkgs you want
[14:48] <coreycb> jamespage, sounds ok to me - I'd been waiting for tests to complete on utopic-proposed first but this makes sense
[14:48] <coreycb> jamespage, where do I tick?
[14:49] <jamespage> coreycb, build the backport_package job
[14:49] <jamespage> and then it presents you with options
[14:57] <jamespage> coreycb, beisner: can we confirm that the 2014.2.2 testing covered the ceph in proposed as well?
[14:57] <coreycb> jamespage, yes it was part of the deployment
[14:58] <jamespage> coreycb, awesome
[14:58] <coreycb> jamespage, yeah default.yaml was the config
[14:58] <Lumia930>  is that possible that i can use my office 360 mail accout in SVN notification server
[15:18] <hackeron> hey, anyone have any ideas about this issue with non interactive do-release-upgrade? < http://ubuntuforums.org/showthread.php?t=2265877
[17:05] <jamespage> zul, hey - could you check out the qemu build failure for kilo trusty backport please?
[17:05] <jamespage> something seccomp related but I've not managed to get time to look today
[17:42] <zul> jamespage:  sure
[19:05] <roaksoax> win 2


[18:27] <shoonya> what package provides "ubuntumenuproxy.h" file ?
[18:27] <shoonya> trying to compile appmenu-gtk
[19:42] <kklimonda> !find ubuntumenuproxy.h
[19:42] <kklimonda> ah, it's from appmenu


[06:51] <dholbach> good morning
[08:22] <iulian> Morning dholbach.
[08:28] <dholbach> hi iulian
[17:04] <jtaylor> barry, ScottK: pyparsing can now be synced from debian, bug 1220921
[17:05] <ScottK> jtaylor: Thanks.
[17:08] <ScottK> jtaylor: Done.
[17:08] <jtaylor> thx
[19:08] <ScottK> jtaylor: Would you please look at the pyparsing autopkgtest failure.
[19:08] <jtaylor> looks like a adt failure
[19:08] <jtaylor> no log, just says dependencies did not install
[19:09] <ScottK> OK.
[19:10] <jtaylor> its arch all, so if i386 works amd64 not its not unlikely an issue in pyparsing
[19:10] <jtaylor> (also it works locally)
[19:13] <ScottK> ADT issue, so I forced it.
[20:50] <jbicha> Noskcaj: if you don't have anything else to do, you could fix the packages that depend on ttf-liberation from bug 1214777
[20:50] <Noskcaj> jbicha, I'll do that now, gambit-c isn't urgent
[20:54] <Noskcaj> jbicha, Should i just try and go through that list an fix the depends?
[20:56] <jbicha> yes please, a few have already been fixed and I filed Debian bugs for some of them but we don't need to wait for Debian to fix them
[21:11] <Noskcaj> jbicha, The first fix is at lp:~noskcaj/ubuntu/saucy/spotweb/liberation , along with refreshes to some patches (they weren't applying cleanly)
[21:13] <jbicha> Just hit the 'propose for merging' button and I believe it will be added to the sponsoring queue