[03:50] <stub> Can anyone confirm that if I run relation-list in a peer relation hook, that it might be listing dying units?
[11:42] <noodles775> mthaddon: Not sure if you review charmhelpers, but as per our conversation yesterday, here's an update for the salt support which doesn't install a daemon: https://code.launchpad.net/~michael.nelson/charm-helpers/depend-on-salt-common-only/+merge/170298
[11:42] <mthaddon> noodles775: I saw the comment in the RT, thanks. I'll leave the review to wedgwood and others for charm-helpers though
[11:43] <noodles775> Cool.
[12:38] <MarkDude> Is all off Juju's main code under Affero v1?
[12:46] <marcoceppi> MarkDude: yes, juju is licensed agpl
[12:49] <MarkDude> v1? not v3? marcoceppi ?
[12:50] <marcoceppi> Oh, I'm not sure the version exactly
[12:50] <MarkDude> Was that the license from the start
[12:50] <marcoceppi> juju-core is AGPLv3
[12:50] <marcoceppi> so is juju0.7
[12:51]  * MarkDude can email on it. I have been wanting to put juju in Fedora- and have seen v1 be an issue
[12:51] <MarkDude> Yay,
[12:51] <MarkDude> much easier, I can proceed now, I *might* need a clarification letter at some point so I could put it in the regular repos
[12:52] <MarkDude> A few of the other parts are not compatible with all the legal restrictions on my side.
[12:53] <MarkDude> But as far as the main part- I feel juju- used in concert with Kickstart (scripts for the Anaconda installer) has awesome possibilities
[13:00] <maxired> Hi everybody !
[13:00] <marcoceppi> Hi maxired
[13:01] <maxired> I'm trying to use "juju-gui", from cs:~juju-gui/precise/juju-gui-68 ,a dn i'm stuck on ""Connecting to the Juju environment"
[13:01] <maxired> I'm not sur how to check that the juju API is running, any idea ?
[13:07] <jcastro> MarkDude: you don't want that
[13:07] <jcastro> you want to use cloud init
[13:07] <jcastro> it's in fedora
[13:08] <MarkDude> Agreed, the cli client looks easy to integrate
[13:09] <MarkDude> the rest of the licenses appear to work, and I have a list of Juju items ALREADY available for Fedora
[13:09] <jcastro> how's the golang stack in fedora?
[13:09] <MarkDude> +1
[13:09]  * MarkDude expects no issues there
[13:09] <MarkDude> Well major ones, possible small fixes needed
[13:10]  * MarkDude started notes- and mostly saw a Affero v1 as issue- v3 means a bit of work on my side- but it should be fine
[13:10] <marcoceppi> maxired: what version of juju are you using?
[13:11]  * MarkDude was reviewing the code. Looks like there is a really nice base to build off of
[13:11]  * MarkDude has not so secret plan of linking (in idea only) juju charms and Kickstart
[13:11] <maxired> marcoceppi : I was precisly looking at this.
[13:12] <maxired> i'm on 0.7 from ppa:juju/pkgs on the master node
[13:12] <marcoceppi> MarkDude: charms are licensed sperately from juju, you'd need to check each charms license if that was the case ;)
[13:13] <maxired> but look's like juju 0.7 from default repository has been installed by MAAS
[13:13] <maxired> I'll try to change this
[13:13] <marcoceppi> Admittdly it's been a while since i've deployed the gui with 0.7
[13:14] <ehg> hey - is there an OS X build of go-juju anywhere?
[13:14] <marcoceppi> ehg: not for go-juju, not yet at least
[13:14] <ehg> marcoceppi: ah, would it compile?
[13:14] <MarkDude> The charms themsleves are not as intereresting as what Juju could do for helping make a dev environment, or a few other things more technical
[13:15] <MarkDude> Bonus being we get to keep the awesome part of getting folks to dev- on the easy route
[13:15] <marcoceppi> ehg: I don't see why not. I don't think there's anything platform dependant, but I'm not a juju-core developer nor do i own a mac to verify
[13:15] <ehg> cool, i'll get our CEO to try :)
[13:15] <marcoceppi> ehg: Let us know how it works out!
[13:15] <MarkDude> Juju is full of win. Charms made elsewhere may not work for various reasons - technical , license etc
[13:16] <MarkDude> Roll out on installs of servers is a possiblity at this point
[13:17]  * MarkDude is hoping to get a kickstart to create Juju- and go from there
[13:17] <MarkDude> Ty jcastro , marcoceppi , everyone
[13:18] <MarkDude> Back to study, do I send my "formal letter of intent" (yay Juju rocks) to jcastro  or someone else ?]\
[13:18] <jcastro> a letter for what?
[13:18] <jcastro> I don't know where you hang out man, but we're ubuntu, you don't need a letter, just go do awesome stuff. :p
[13:19] <maxired> MarkDude : I was wrong, i'm also running juju from ppa:juju/pkgs on the execution machine
[13:19] <maxired> marcoceppi : I was wrong, i'm also running juju from ppa:juju/pkgs on the execution machine
[13:20] <AskUbuntu> Ubuntu 12.04 MaaS and JUJU's proxy issues | http://askubuntu.com/q/310153
[13:20] <marcoceppi> maxired: Well, that all _should_ work. There was a rudimentary api added to 0.7 for the gui
[13:20]  * marcoceppi checks
[13:21] <MarkDude> I know jcastro but despite the awesomeness of Fedora, every so often I need to do formal shit
[13:22] <jcastro> ok let me know if you need anything
[13:22] <MarkDude> So I can forward to legal, and such- CYA on my side
[13:22]  * MarkDude hates having to use his title, but has to in the formal letter
[13:23]  * MarkDude really really wants to have Distros focus on our common themes- and juju has great possiblities
[13:24] <MarkDude> Ubuntu helps all of FOSS imho. and providing some concrete examples can help stop some sniping from at least a few troll types
[13:25] <MarkDude> Oh I should have an agreeable packager to help with this, so I can see about getting some momentum. Keep kickin ass Juju folks :D
[13:25] <jcastro> hey we do have some RPM packaging somewhere, but it's old and for pyju
[13:25] <jcastro> so not useful probably, just thought I'd mention it
[13:26] <marcoceppi> jcastro: I'd rather pyjuju not end up in some rpm distro somewhere :P
[13:26] <jcastro> hah yeah, we can't even get rid of it in ubuntu
[13:26] <jcastro> it's gone from the saucy though!
[13:27] <maxired> I got a process with " /usr/bin/python -m juju.agents.api --nodaemon --port 8080 --logfile /var/log/juju/api-agent.log --session-file /var/run/juju/api-agent.zksession --secure --keys /etc/ssl/juju-gui" , but not listening on 8080
[13:27] <gary_poster> maxired, hi.  I'm one of the GUI people.  We test against pyJuju 0.7 at least a couple times a day, but not against MAAS.  We've had similar reports to this, but we have resolved everything we know about previously.
[13:27] <gary_poster> ok that sounds promising/interesting.  this is on the GUI charm, I assume?
[13:28] <MarkDude> Where are they located?
[13:28]  * MarkDude is aware the pyju is the OLD method
[13:29] <MarkDude> Well we would look at pyju for reference, not to include :D
[13:29] <gary_poster> maxired, first question I'd have, if you've verified that nothing is listening on the gui charm on part 8080, is what you see in that logfile (/var/log/juju/api-agent.lo)
[13:29] <gary_poster> /var/log/juju/api-agent.log
[13:30] <gary_poster> ... *port
[13:31] <maxired> gary_poster : thanks for helping. yep, nothing actually listening on that port.
[13:31] <maxired> i'm am currently trying again, because there has bene previously an nginx on it
[13:31] <maarten__> When I do juju bootstrap, the bootstrap server does not have my openstack keypair and I can not log into it. What do I have to put to include the canonistack keypair?
[13:32] <gary_poster> ok maxired.  there's a (closed) bug for this, which has had some conversation.  I don't think it has anything interesting but will go find it.
[13:33] <gary_poster> maxired, https://bugs.launchpad.net/juju-gui/+bug/1180095 <shrug>
[13:33] <_mup_> Bug #1180095: GUI charm may have difficulties working with Juju on MAAS <juju-gui:Invalid> <https://launchpad.net/bugs/1180095>
[13:35] <maxired> gary_poster : thanks
[13:39] <marcoceppi> maarten__: You can add SSH keys to your environments.yaml file: http://askubuntu.com/q/205170/41
[13:40] <maarten__> thanks
[13:40] <marcoceppi> WIth that format, you'd just put one public key per line
[13:40] <marcoceppi> (if you had multiples)
[13:40] <maxired> gary_poster  : after a new deployment, the agent is listening, but i still stuck on "Connecting to the Juju environment"
[13:41] <maxired> do you know how can i get logs from haproxy ?
[13:42] <gary_poster> maxired, I don't.  looking.
[13:45] <gary_poster> maxired, benji has graciously offered to help
[13:46] <gary_poster> he'll be around presently
[13:46] <benji> hi, maxired; I'm reading the backlog to get cought up
[13:46] <maxired> hi benji ;) thanks for helping
[13:48] <maxired> benji : looks like it's working right now
[13:49] <maxired> the first connection to the websocket as been really long
[13:49] <maxired> but i could login the the web ui ;)
[13:49] <benji> my work here is done ;)
[13:51] <maxired> benji , gary_poster and marcoceppi, thanks for helping
[13:51] <marcoceppi> maxired: glad you got it working!
[13:51] <gary_poster> maxired, benji, lol, excellent
[13:51] <maxired> i'll check in the bug tracker, but looks like my probleme was a destroyed instance of 'wordpress' wich didn't remove the nginx
[13:52] <gary_poster> maxired, on the same box to which you deployed the GUI later, I'm guessing?
[13:52] <maxired> yep
[13:54] <gary_poster> ok, yeah.  FWIW, effectively fixed in Juju Core AIUI, maxired.
[13:56] <maxired> Good news i don't have to reproduce to be sure about that in order to fill a bug ;)
[13:58] <gary_poster> :-)
[13:59] <maxired> any link to the commit/bug ?
[13:59] <gary_poster> looking
[14:00] <gary_poster> maxired, https://bugs.launchpad.net/juju/+bug/872264
[14:00] <_mup_> Bug #872264: stop hook does not fire when units removed from service <goju-resolved> <juju:Confirmed> <juju-core:Fix Released by fwereade> <https://launchpad.net/bugs/872264>
[14:02] <gary_poster> (I believe you destroyed the service, but I also am 90% sure that the issue is the same)
[14:02] <fwereade> maxired, gary_poster: we do not currently implement an uninstall hook, which is what I'd expect would actually remove such things
[14:03] <fwereade> maxired, gary_poster: we are currently working on containerization, which would let you *really* remove things, rather than just trusting to the effect of the putative uninstall hook
[14:03] <maxired> gary_poster : thanks, i was looking for something more specific
[14:03] <gary_poster> fwereade, when you destroy a service, don't you do a lot more drastic clean up than pyJuju did up?  Or am I just thinking of containerization discussions?
[14:03] <gary_poster> maxired, ok, that's all I've got.  :-)
[14:04] <fwereade> gary_poster, we can do a lot more stuff in the DB; and we can actually guarantee that stop hooks will be run; but we don't go any further than that
[14:04] <maxired> fwereade : I guess you are write. stoping could be not enough if things for example start at reboot ;)
[14:04] <fwereade> maxired, I would hope that a well-implemented stop hook would prevent the service from autostarting ;)
[14:05] <gary_poster> fwereade, gotcha, thanks.
[14:17] <jcastro> jamespage: m_3: have either of you checked out that merge proposal from patrick hetu yet?
[14:18] <jamespage> jcastro, remind me again - which one is that?
[14:18] <jcastro> https://code.launchpad.net/~patrick-hetu/charms/precise/gunicorn/python-rewrite/+merge/167088
[14:18] <jamespage> stub, you are terrifying me with all of the postgresql MP's you have in flight
[14:18] <jcastro> rick_h: hey so sinzui isn't around so you're the closest, tldr, some merge proposals aren't getting in the charm review queue
[14:19] <rick_h> jcastro: yea, there's a bug for that. Sec let me find it.
[14:19] <rick_h> https://bugs.launchpad.net/charmworld/+bug/1191823 jcastro
[14:19] <_mup_> Bug #1191823: Merge proposals are missing from the review queue <charmers> <charmworld:Triaged> <https://launchpad.net/bugs/1191823>
[14:19] <rick_h> "But ~charmers isn't requested to review this proposal, only ~mark-mims."
[14:20] <jcastro> OOOHHHHH
[14:20] <rick_h> jcastro: so not a lot we can do atm about it.
[14:20] <jcastro> so this is a workflow bug
[14:20] <rick_h> jcastro: yea, at least for now until we can get time to check out a better way to generate the list
[14:20] <jcastro> ok so you know how we can "reset" a merge proposal to a non assigned to mims state?
[14:21] <rick_h> jcastro: moved to #juju-gui since aaron is there and he looked into it.
[14:21] <jamespage> jcastro, just fixed that
[14:22] <jcastro> right so basically after the first reviewer reviews it, and they ping pong, we need a way to stick it back into the pool instead of assignit to the first guy
[14:22] <jcastro> jamespage: oh awesome, so we just need to tell charmers when you're done you're first pass to do what you just did
[14:23] <jcastro> jamespage: what did you do> :)
[14:23] <jamespage> jcastro, requested 'charmers' review the MP
[14:23] <jamespage> 'Request another review'
[14:25] <jcastro> ack, found the docs, thanks, I'll send out a reminder and probably put this in newdocs
[14:25] <stub> jamespage: Big one coming up now I understand -broken/-departed hooks and can rewrite the horrible replication stuff
[14:26] <jamespage> stub, do you want to consolidate into a single merge proposal?
[14:27] <stub> jamespage: The ones in the queue will get the charm in the store actually working again
[14:27] <stub> jamespage: You actually prefer big MPs to smaller bite sized ones?
[14:28] <jamespage> stub, no - I just wanted to understand if whats in the queue is all valid
[14:28] <jamespage> time order right?
[14:29] <stub> yeah - I use a bzr pipeline so they each depends on the previous
[14:30] <stub> https://code.launchpad.net/~stub/charms/precise/postgresql/charm-helpers/+merge/169487 is likely rubber stamp, a separate MP to avoid noise in actual work
[14:30] <stub> https://code.launchpad.net/~stub/charms/precise/postgresql-psql/devel/+merge/169851 is teensy
[14:31] <stub> https://code.launchpad.net/~stub/charms/precise/postgresql/bug-1190141-client-access-fail/+merge/169928 is also teensy and fixes the worst bug atm
[14:32] <stub> yeah, nothing to be scared of yet ;)
[14:32] <fwereade> rvba, ping
[14:33] <jamespage> stub, there are two others in the queue
[14:33] <jamespage> https://code.launchpad.net/~stub/charms/precise/postgresql/bug-1084263-fix-broken-hooks/+merge/169486
[14:34] <jamespage> no - just that one actually
[14:34] <stub> https://code.launchpad.net/~stub/charms/precise/postgresql/bug-1084263-fix-broken-hooks/+merge/169486 may give you a wtf moment. I think I based my implementation on a misunderstanding. But the approach works.
[14:34] <stub> There is a test infrastructure one too
[14:34] <stub> https://code.launchpad.net/~stub/charms/precise/postgresql/tests/+merge/169866
[14:34] <stub> But nothing scary in there
[14:35] <jamespage> stub, OK - I'm completely confused
[14:35] <stub> :)
[14:35] <jamespage> stub, which one should I be reviewing first? charm-helpers?
[14:35] <stub> I'm not helping? ;)
[14:35] <stub> Yes, charm-helpers
[14:35] <jamespage> Ok - lemme start there then
[14:36] <stub> That is just upstream code I've copied in from lp:charm-helpers
[14:36] <jamespage> stub, yeah - I see - you sure you want to include the entire project? and not just the python package?
[14:38] <stub> jamespage: I don't know if it matters. Whatever best practice is considered.
[14:38] <jamespage> stub, not sure we have one just yet
[14:39] <stub> Pulling the whole thing gets the license etc.
[14:39] <jamespage> I know for the openstack charms we have been taking the approach of pulling in the bits we want
[14:40] <jamespage> stub,  see http://bazaar.launchpad.net/~gandelman-a/+junk/charm-helpers-sync/files
[14:40] <stub> I worry that will drift... people making their own little hacks. The PG charm already contains a hacked apon copy of charm-helper's ancestor.
[14:41] <stub> How does that helper help with charm-store charms?
[14:41] <stub> oh, I think I see
[14:42] <jamespage> all charm-helpers-sync does is provide a standardized way to described which bits you want from lp:charm-helpers
[14:42] <jamespage> and syncs them into your charm
[14:43] <jamespage> stub, I'll push adam_g to get that included in charm-helpers itself
[14:43] <jamespage> adam_g_, nudge ^^
[14:43] <stub> Right. So I don't see any reason not to switch to that. I'll go with whatever mechanism is preferred.
[14:45] <jamespage> stub, I'd prefer to see that rather than a sync of the entire branch
[14:45] <jamespage> wedgwood, any opinions on the above?
[14:48] <stub> A point for the whole tree is it is easier to merge fixes back, perhaps.
[14:48] <stub> Nah, ignore that
[14:50]  * wedgwood reads backscroll
[14:53] <wedgwood> jamespage: I've been doing my best to structure charm-helpers in a way that it can be included in pieces. +1
[14:54] <wedgwood> I envision it being packaged that way too. The cli, for example, might be a separate deb
[14:59] <stub> jamespage: Pushed that update anyway. Just running the test again (soon that will be tests, plural)
[15:07] <_mup_> Bug #1192598 was filed: pyjuju provision-agent hangs and fails to provision instances <juju:New> <https://launchpad.net/bugs/1192598>
[15:19] <jamespage> wedgwood, ack
[15:24] <jamespage> stub, guess I should review lp:~stub/charm-helpers/bug-1191002-local-unit-relation-data first as that is where you are pulling charm-helpers from
[15:25] <stub> jamespage: turtles, all the way down
[15:25] <jamespage> stub, coolio
[15:29] <jamespage> stub, that branch also adds the data that the local unit has set on a specific relation right?
[15:29] <jamespage> (thats the bit I did not even know you could do until last week)
[15:32] <stub> jamespage: Correct
[15:32] <jamespage> stub, OK - that works for me - do you want to rebase using lp:charm-helpers now?
[15:32] <jamespage> I think that would be good hygiene
[15:32] <stub> It has landed? Sure.
[15:34] <stub> jamespage: And done
[15:55] <jcastro> charm call in 5 minutes!
[15:55] <marcoceppi> jcastro: do you have the URL?
[15:56] <jcastro> setting it up now
[15:56] <jcastro> hey can one of you prep the etherpad for this week while I fire this up?
[15:57] <jcastro> https://plus.google.com/hangouts/_/9d5f2933f12c69245f97d157a4c372d4d61318bd?authuser=0&hl=en
[15:57] <jcastro> if you want to participate
[15:57] <jcastro> http://ubuntuonair.com if you want to just listen in
[15:58] <arosales> jcastro, I can work on the etherpad
[16:05] <marcoceppi> http://pad.ubuntu.com/7mf2jvKXNa
[16:54] <jamespage> stub, how worried are you about backwards compat with py-juju?
[17:04] <stub> jamespage: I will be worried, at least to the extent of migrating our existing systems
[17:05] <jamespage> stub, destroy-machines in the tests is a juju-core ish - py juju does terminate machines
[17:08] <stub> right, ta. Might as well change that.
[18:14] <stub> When I have a standard require/provides relation between client_service and server_service, is it possible for a unit in server_service to retrieve relation data set by other server_service units? From the server side, relation-list only appears to list client_service units and relation-get with the other unit listed explicitly seems to be failing.
[18:16] <marcoceppi> stub: I believe that's what peer relations are for
[18:16] <stub> This is relation state... it doesn't fit the peer relation
[18:17] <marcoceppi> stub: Units of the same service don't talk to each other (normally) when it's service -> client relation
[18:17] <stub> One of server_service is a master, and creates a user and password for the clients and publishes it to the relation with the client
[18:18] <stub> The other server_service units ideally will republish the same information
[18:19] <stub> I'm confused as I think this worked before. It might be racy in some way though.
[18:20]  * stub ponders about using the peer relation as a communication channel
[18:30] <wedgwood> stub: you want relation-ids
[18:30] <wedgwood> you'll need the right ID to go along with the unit
[18:32] <wedgwood> e.g. (service a) <- myrel:0 <- database -> myrel:1 -> (service b)
[18:33] <stub> hmm... maybe I'm using the wrong relation id. That would explain why it used to work.
[18:54] <MarkDude> Where were the RPM charms? I have someone reviewing now
[18:54]  * MarkDude knows they were done the old way with Pyju
[19:00] <jcastro> https://github.com/jujutools/rpm-juju
[19:30] <MarkDude> Ty


[11:53] <BluesKaj> Hi all
 https://irc-attachments.kde.org/040a1615/file_55492.jpg
 \o/
 I will start with new frameworks upload once the chaos of auto-sync has calmed
[22:07] <mamarley> "influx" <--They are aware that the buildfarm is still busted, right?


[04:00] <micahg> skellat: do we really want apt-offline in the desktop seed?
[04:00] <micahg> now I remember why I didn't merge it before
[04:01] <Unit193> It doesn't have you tagged, but just so you know as well in case you missed the mail: https://code.launchpad.net/~unit193/xubuntu-default-settings/xubuntu-default-settings/+merge/174852
[04:10] <micahg> Unit193: do we now have a xfce4-popup-applicationsmenu application?
[04:11] <Unit193> micahg: Of course, it's xfce4-panel.
[04:13] <micahg> Unit193: xfce4-panel installs that?
[04:13] <Unit193> micahg: Yes sir, xfce4-panel: /usr/bin/xfce4-popup-applicationsmenu
[04:14] <Unit193> (And this isn't some package I mangled.)
[04:15] <micahg> heh, ok, I've never seen it before (then again, I'm still running quantal on my bleeding edge machine)
[04:16] <Unit193> Heh, nice.  I've already set it on the computers here, mainly because it's faster for me.
[04:17] <skellat> micahg: Yes, yes we do want apt-offline in the desktop seed
[04:17] <micahg> skellat: ok, I'm thinking to make it a recommends then
[04:17] <micahg> I don't think it's critical to the desktop
[04:17] <Unit193> It was in "Depends"? 0_o
[04:17] <skellat> Prevents a chicken-and-the-egg problem if somebody gets a disc, installs a system, and then finds it is disconnected
[04:18] <skellat> Prior discs didn't give you a good way to handle bandwidth-constrained cases including updating the view of the repositories.
[04:20] <micahg> skellat: recommends ok?
[04:20] <skellat> As long as it gets on the shipping disc, I'm cool with it
[04:20] <micahg> skellat: you know, we can install it on the disc without having it on the desktop seed?
[04:21] <micahg> desktop seed == xubuntu-desktop metapackage
[04:21] <skellat> Okay
[04:22] <micahg> ship == on CD and can be installed w/out making everyone have it
[04:22] <micahg> oops, no, that's live I think
[04:22] <skellat> We ship documentation for it now for everybody
[04:23] <micahg> ok, I'll add it as a recommends then
[04:23] <skellat> :-)
[04:24] <micahg> the catch with recommends is that it won't be installed on upgrades from one release to the next
[04:24] <skellat> We'll burn that bridge when we get to it
[04:24] <micahg> but I don't think that's a problem as the main use case is new installs, right?
[04:24] <skellat> Bingo.  New installs is the biggest worry at this point.
[04:25] <skellat> If somebody is bandwidth constrained, they're not going to upgrade except via dist-upgrade which apt-offline would handle anyhow.
[04:25] <skellat> As to notation, I should have wrapped it in parenthesis to make it a Recommends then?
[04:25] <micahg> yes
[04:25] <skellat> Okay
[04:25] <skellat> Do you want me to update my branch real quick to do that?
[04:26] <micahg> skellat: sure, can you get rid of the long comment as well?
[04:26] <skellat> Yes
[04:26] <skellat> I'm sitting at my BeagleBoard-xM which is on Debian now so this might take a moment or two
[04:27] <micahg> ok
[04:28] <Unit193> I think it'd make sense to just have it in ship and live, but that's me.
[04:29] <skellat> Pushed rev 939 back up to LP
[04:30] <micahg> Unit193: oops, you forgot to add the new .in file :)
[04:30] <skellat> I see pastebinit is a Recommends too
[04:30] <micahg> the main difference with recommends is that it's removable
[04:31] <skellat> Yep
[04:31] <Unit193> It's supposed to be jockey.desktop.in, I didn't rename it. >_<
[04:31] <Unit193> Thanks.
[04:31] <micahg> Unit193: you familiar with bzr mv?
[04:31] <Unit193> micahg: I'd assume it works the same as with git.
[04:32] <micahg> yep
[04:32] <micahg> just not everyone uses it :)
[04:33] <Unit193> Thanks for the reminder, I'm not great with VCS.
[04:33] <skellat> I've been learning bzr the hard way...through usage...
[04:33] <skellat> micahg: LP is showing the diff on the merge proposal now
[04:34] <micahg> skellat: can you run bzr rebase :parent on your branch>
[04:34] <skellat> Crap
[04:34] <skellat> Hold on
[04:35] <micahg> I'll be back in a few minutes
[04:35] <Unit193> Hopefully I un-failed myself...
[04:37] <micahg> skellat: actually, I can just merge it in as is (I was going to do a pull, but am thinking otherwise now)
[04:38] <skellat> I just found that bzr rebase is missing from the version of bzr in Debian Testing at the moment
[04:38] <skellat> Had to find my netbook and boot it up
[04:38] <micahg> hrm, weird
[04:38] <micahg> it's called bzr-rewrite now
[04:39] <micahg> skellat: it's fine, I can do a merge, pull is good when the commits are all good, I think merge is better in this case
[04:40] <skellat> Just ran it on my Xubuntu netbook and it said no revisions to rebase
[04:41] <micahg> skellat: oh, well, :parent would only be set correctly if it was the original checkout, otherwise, you'd probably need to reference the to merge into branch by name
[04:41] <micahg> skellat: it's ok, I'm doing a merge
[04:41] <skellat> Cool
[04:43]  * micahg has gotten used to git as of later
[04:43] <micahg> *late
[04:43]  * micahg will give that a couple minutes and then update the seeds
[04:45] <micahg> Unit193: also, no changelog entry...
[04:46] <Unit193> Yes, that I didn't add in, it's whatever anyone else wanted.
[04:47] <micahg> Unit193: dch -i -DUNRELEASED and add an appropriate description (usually better to update this as you add stuff for future reference)
[05:09] <Unit193> Pushed up to revision 439.
[05:15] <Unit193> (Version is in oddly, but it's marked as unreleased anyway.)
[05:15] <micahg> hrm, I'll fix
[05:16] <Unit193> (I don't normally use dch too much)
[05:16] <micahg> yeah, I guess -i does do that..
[05:18] <Unit193> Picks up name and email from env too. :/
[05:19] <Unit193> (Tried fixing it in .devscripts, didn't work.)
[05:19] <micahg> was that name wrong?
[05:20] <Unit193> It was until I fixed it, pushed one is right.
[05:20] <micahg> ok
[05:21] <micahg> Unit193: I'm creating a team for gtk-theme-config and adding you to it and pushing up what I have
[05:22] <Unit193> OK.
[05:31] <micahg> and here we are: https://code.launchpad.net/~gtk-theme-config-maintainers/gtk-theme-config/debian
[05:32] <Unit193> Might not look at it tonight (01:31), and in a way I kind of hope I don't get to it tomorrow. :P
[05:32] <micahg> Unit193: heh, ok, BTW, I can't upload settings yet as it needs some lintian fixes, can pastebin if you lik
[05:33] <Unit193> Sure, or I could try it, but would have to pbuild it as I don't have translation things setup.
[05:35] <micahg> Unit193: http://paste.ubuntu.com/5883129/
[05:55] <Unit193> Weird, I didn't get that...
[06:00] <Unit193> micahg: http://paste.openstack.org/show/40641/ that's all I got.
[06:01] <micahg> Unit193: right, you need to run lintian on the binaries produced by the test build :)
[06:02] <Unit193> Ala lintian -I --pedantic ../xubuntu-default-settings_13.10.2ubuntu1*deb ?
[06:03] <Unit193> (Normally run it on the binary/source changes files of course, which is the paste.
[06:03] <Unit193> )
[06:04] <micahg> something like that
[06:04] <Unit193> Yep, that's all I got.
[06:08] <micahg> I use lintian -iIEv --pedantic
[06:09] <micahg> ah, that check was removed...
[06:09] <micahg> in lintian 2.5.11
[06:10] <Unit193> Going to say that your output was E, not X, so -E wouldn't have done it.
[06:10] <micahg> I'm on precise ATM
[06:10] <Unit193> (Maybe I should start using -E too?_
[06:11] <micahg> hrm, I'd say we still need that check as lucid doesn't have a high enough dpkg, /me sends mail to -devel
[06:13] <Unit193> Heh, fun indeed.  If you mean ubuntu-devel, I'll read it tomorrow. :)
[06:15] <micahg> yeah
[06:16] <Noskcaj> micahg, Can you have a look at the latest xfce-indicator-plugin from debian? i couldn't work out the conflict
[06:16] <micahg> Noskcaj: yeah, on my list, but not tonight
[06:16] <Noskcaj> ok
[06:16] <micahg> the patch probably needs to be reworked for the new upstream version
[06:20] <Noskcaj> It does, that's part of why i ran away from it
[06:52] <micahg> bluesabre: you're working on catfish, right?
[06:57] <micahg> bluesabre: Bug #1202085
[07:39] <Noskcaj> Why do we still keep the old patch files is xfce4-datetime-plugin?
[08:16] <Noskcaj> Unless i've missed something, the datetime plugin no longer needs the patches it has
[09:51] <bluesabre> micahg, I've recently learned an even better way to remove the dependency, I'll introduce it soon.
[19:42] <pleia2> knome knome knome
[19:42] <pleia2> http://xubuntu.org/?p=1753&preview=true
[20:13] <knome> pleia2 pleia2 pleia2
[20:14] <knome> aha, wow
[20:14] <knome> that'll take some time
[20:18] <pleia2> :)
[20:18] <pleia2> oh, pictures!
[20:19] <knome> pleia2, are the quotes after the first subheader intentional, and if yes, why them abut not the next paragraphs
[20:20]  * pleia2 looks
[20:20] <knome> i'd also tweak the links
[20:20] <pleia2> ah, I think that was him quoting the mission statement of the org
[20:20] <knome> ah, right
[20:20] <knome> that's a bit weird
[20:21]  * pleia2 clarifies that
[20:21] <knome> thanks
[20:22] <knome> Ubtunu
[20:22] <knome> milwaukee (case)
[20:23] <knome> opensource (no space)
[20:23] <pleia2> that's how we spell it now
[20:23] <knome> really?
[20:23] <pleia2> no :)
[20:23] <knome> haha
[20:23] <knome> .
[20:24] <knome> so the links
[20:24] <knome> they are just URLs now
[20:24] <pleia2> yeah
[20:25] <knome> i'd rather change to "Read more about Project: Community Computers" (first link) etc.
[20:26] <knome> and i'm thinking we might want to move the "if your organization..." to the top
[20:26] <pleia2> yeah, I was split on that
[20:26] <pleia2> I think I had it all at the bottom before
[20:26] <knome> the bottom part is boo because it's not separated any way from the content
[20:27] <knome> (yeah, i should get some theme improvements in so we could handle these things better)
[20:28] <knome> other than those mentions it looks good to go
[20:30] <pleia2> knome: ok, refresh
[20:30] <pleia2> it has pictures now too!
[20:31] <knome> woo
[20:31] <knome> we could align those
[20:31]  * pleia2 fixes up last link
[20:31] <pleia2> I tried to do center in wordpress magic, but it no likey
[20:31] <knome> hmm. okay. i'll see
[20:31] <knome> might be again something in the theme
[20:31] <knome> looks like i really should get the stuff done ASAP
[20:31] <pleia2> I'm going to close editing, you can edit if you want
[20:31] <pleia2> planning on publishing Friday morning (alreayd had sticker news today)
[20:31] <knome> i'll look at the pics, then publish
[20:32] <knome> oh, ok
[20:32] <knome> i'll look at the pics then ;)
[20:32] <pleia2> thanks :)
[20:32] <knome> hmph, right
[20:32] <knome> yeah, we need a theme update
[20:32] <knome> and i should send those question to tero at the local uni
[20:32] <pleia2> ah, title should be "Xubuntu at Project: Community Computers in Milwaukee"
[20:33] <pleia2> since that's their formal name
[20:33] <pleia2> yes, you should!
[20:33] <knome> boo
[20:33] <knome> ;)
[20:33] <knome> i don't have an edit lock
[20:35] <knome> how long are you going to be around today?
[20:37] <knome> brb
[20:38] <pleia2> I'm working but I should be around all evneing
[20:39]  * pleia2 laundry
[20:39] <Unit193> Oh yeah, I need to do that too. :?
[20:48] <knome> ok, good
[20:49] <knome> i'll do some improvements soon then and let you see them
[20:49] <knome> and i hope we can get to send IS a mail about them before i'm off to the summer cottage again on friday :)
[20:52] <pleia2> :)
[20:58] <knome> jjfrv8, hello :)
[20:58] <jjfrv8> Hi, knome
[21:01] <pleia2> doc hero, jjfrv8!
[21:01] <jjfrv8> Don't know about that :)
[21:02] <pleia2> :)
[21:03] <jjfrv8> I think it's doable to finish the P docs before 8/1.  Does it look that way from your end, knome ?
[21:03] <knome> jjfrv8, at this speed, definitely
[21:04] <jjfrv8> Ok.  I've got chs 5, 7 & 8 ready whenever, I don't think 9 needs any work (if you and skellat still want to include it). 10 and the rest look easy
[21:05] <jjfrv8> I'm going to work on networking (ch 4) this weekend when I get a machine with wireless
[21:15] <jjfrv8> * I meant chapter 6 for networking
[21:15] <knome> :)
[21:50] <knome> ok, some improvements in http://xstaging.lallinaho.fi/
[21:52] <Noskcaj> Translating the xubuntu docs is officially the most tedious thing that can be done
[21:52] <knome> Noskcaj, stop doing that. the australian translation is probably the most useless :P
[21:53] <Noskcaj> We matter...
[21:53] <knome> Noskcaj, i mean, if you think that it's tedious, then stop
[21:53] <Noskcaj> I did
[21:53] <knome> your effort is more valuable elsewhere.
[22:41] <knome> pleia2, ding ding ding!
[22:42] <pleia2> hello knome!
[22:42] <knome> look at the link i posted
[22:42] <pleia2> oh I didn't look at the thing
[22:42] <knome> the footer is off and not "everything" is there, but does the top part look better now?
[22:43] <pleia2> yeah that looks fine
[22:43] <knome> good
[22:43] <knome> i also fixed some of the editor styles
[22:43] <knome> so you should have a semi-WYSIWYG view
[22:43] <knome> but there's still a lot to do
[22:43] <pleia2> okie
[22:44] <knome> i want to change the navigation
[22:44] <knome> http://temp.knome.fi/xubuntu/saucy_website/newnavi.png
[22:44] <knome> that's one proposal, but i'm not 100% happy with it
[22:44] <pleia2> I like it
[22:44] <knome> what do you think of the activities/blog part in that though?
[22:45] <pleia2> I am sometimes blind to menus on the top of the screen, so I lke repeating them later
[22:45] <knome> like in the bottom of the page?
[22:45] <pleia2> yeah
[22:45] <knome> that might work
[22:46] <pleia2> or even the Get Started links currently under the screenshot in our site now
[22:46] <knome> umh, yeah
[22:46] <knome> i want to get rid of the graphical navigation though if at all possible
[22:46] <knome> or change the way we're doing it
[22:46] <knome> it's a pain to maintain
[22:47] <pleia2> yeah
[22:47] <pleia2> I don't care if it's graphical, just enjoy that they exist where my eyeballs go
[22:47] <knome> heh
[22:47] <knome> i hope they stay where they are
[22:47] <knome> for your comfort ;)
[22:47] <pleia2> much appreciated ;)
[22:48] <knome> so, what about the activities bar?
[22:48] <knome> if that looks good, i could throw that in
[22:48] <pleia2> bar?
[22:48] <knome> it does waste some vertical space..
[22:48] <knome> the whiter bg
[22:48] <pleia2> oh, look at that
[22:48] <pleia2> it's too bright in this room for me to have noticed
[22:48] <knome> heh
[22:49] <pleia2> and with that, I think it's too subtle
[22:49] <knome> heh, ok
[22:50] <knome> otoh, if you don't see it... then you don't
[22:50] <pleia2> yeah
[22:50] <knome> i'd have to look at it with my laptop screen
[22:50] <knome> but it does give some structure for the frontpage
[23:50] <knome> pleia2, ping
[23:50] <pleia2> hey
[23:50] <knome> http://temp.knome.fi/xubuntu/saucy_website/editor.png
[23:50] <knome> you comfortable with those options?
[23:50] <pleia2> yeah, I don't really like wysiwyg editors anyway
[23:50] <knome> yeah, me neither
[23:51] <knome> the styles menu is also useful
[23:52] <knome> has blockquote, code (block and inline), style that we can use to mark parts that need review and preformatted text
[23:52] <knome> and we can add anything we want
[23:52] <knome> eg. tell WP to have an item named "Elizabeth" and with that, create a p.pink element :P
[23:53] <pleia2> \o/
[23:54] <knome> and yeah, <h1> is disabled from "format"
[23:54] <pleia2> ah
[23:54] <knome> so you don't need to remind yourself what the "highest" header was you should use
[23:55] <knome> (you can still a <h1> element with the text mode)
[23:55] <knome> +add


[05:56] <didrocks> happyaron: hey! a reminder that I'm going on holidays by EOD, so if the MIR isn't closed by then, it may be more difficult to proceed it (I didn't see any answer on my feedbacks)
[06:19] <happyaron> didrocks: will get back to you very soon, didn't see you on IRC when I saw your replies
[06:19] <didrocks> great
[07:20] <willcooke> hi folks
[07:21] <didrocks> morning willcooke
[07:46] <seb128> good morning desktopers
[07:47] <didrocks> morning seb128
[07:47] <seb128> lut didrocks
[08:04] <Laney> guten morgen
[08:04] <seb128> hey Laney, wie gehts?
[08:04] <didrocks> morning Laney
[08:05] <Laney> Jenkins Fixed - utopic-adt-ubuntu-system-settings-online-accounts 151
[08:05] <Laney> weeeeeeee
[08:05] <Laney> hey seb128 & didrocks
[08:05] <seb128> nice
[08:05] <Laney> doing good thanks, how are you?
[08:05] <seb128> I'm good, thanks
[08:07] <willcooke> how was $pub Laney ?
[08:08] <Laney> and desktop-next built too
[08:08] <Laney> good stuff
[08:08] <seb128> great
[08:09] <Laney> willcooke: good, had Nottingham EPA and Oakham ... Inferno I think
[08:09] <Laney> we went to the Gladstone in Carrington, not sure if you know it
[08:09] <Laney> cool pub
[08:09] <willcooke> Oakham FTW!
[08:09] <Laney> I heard Citra won a silver prize at the GBBF
[08:09]  * willcooke loves Citra
[08:10] <Laney> tis a good pint
[08:10] <willcooke> my local has a beer festival August bank holiday, and they must have some arrangement with Oakham because they always have 2 different beers from them
[08:10] <willcooke> plus it's not far away
[08:12] <Laney> I thought it was in Rutland for some reason
[08:13] <willcooke> I think it might be - it used to be in Peterborough - which is probably 1/2 way between you and me
[08:13] <Laney> good old P-town
[08:13] <Laney> we used to go out there of a weekend
[08:13] <willcooke> ha!
[08:14] <Laney> (grew up in Alconbury)
[08:15] <willcooke> zomg - I used to live there
[08:15] <willcooke> when I worked in Huntingdon
[08:15] <willcooke> we bought our first house there in about, erm, 2004
[08:15] <willcooke> The Manor!
[08:15] <Laney> small world
[08:16] <Laney> my dad drinks there
[08:16] <willcooke> :)
[08:38] <willcooke> attente_, are you up very early or very late?
[08:38] <attente_> willcooke, i just woke up
[08:38] <willcooke> :(
[08:39] <Laney> maybe he never left paris!
[08:39] <willcooke> ha!
[09:41]  * Sweetshark is back.
[09:42] <Sweetshark> (still coughing a bit and such, but that will be dealt with)
[09:45] <Sweetshark> seb128: I kicked off a fixed build on my machine yesterday evening and it died with a compiler error -- which is weird for the changes I did. I didnt run it on the cooling stack for the notebook, so it might just have been overheating. A new build is running right now.
[09:48] <Laney> hey Sweetshark
[09:50] <willcooke> hey Sweetshark
[10:06] <laze1989> Any chance that the AppIndicator's API will change with Unity 8? I see limitations that the indicators are now traditional menus (e.g., in Chrome's new Notification Icon). Windows and OS X got it right.
[10:07] <seb128> hey Sweetshark, k
[10:08] <seb128> laze1989, better to ask on #ubuntu-unity, not sure if things are fully defined yet
[10:08] <laze1989> seb128, thank you. While googling I just find old design documents...
[10:11] <seb128> yet, not sure anyone revisited those yet for unity8
[10:11] <seb128> larsu (who is off this week) wanted to maybe change the server/client model for those
[10:40] <Sweetshark> meh, a different internal compiler error segv. Lets hope I have no dying hardware here ....
[10:41]  * Sweetshark tries to slow things down ...
[10:50] <willcooke> is this on your massive super powered box?
[10:53]  * didrocks is going for some exercising
[10:57] <Sweetshark> willcooke: nah, I do the release builds on the notebook.
[10:59] <Sweetshark> willcooke: those are running inside an Jenkins CI-Server, so I dont move them around easily. And I need to be able to do them when on the road, so -> notebook.
[11:00] <Sweetshark> that notebook is quite decent still, it just doesnt have enough cooling for what the power supply is pumping into it.
[11:00] <willcooke> ahh
[11:01]  * Sweetshark should dockerfy the Jenkins thing, then I could more easily move that around.
[11:01] <Sweetshark> ( .... "one day" ....)
[11:01] <willcooke> :D
[11:52] <willcooke> boo.
[11:53] <willcooke> I go for some golf practice and the moment I get there is starts thundering and lightning, so I think "this is a bad idea" and come home.  Get home and the sun comes out.
[12:03] <Sweetshark> willcooke: Its still thundering and lightning at the golf practice. The sun just likes your home.
[12:03]  * Sweetshark nods.
[12:03] <willcooke> :D
[15:48] <Laney> hey RAOF, I re-uploaded webkitgtk/trusty without the gl change if you'd be so kind as to review it again
[16:13] <cyphermox> seb128: the NM sru is running in sbuild right now, as soon as that's done I'll upload
[16:13] <seb128> good afternoon desktopers
[16:13] <seb128> cyphermox, thanks
[16:29] <willcooke> hey seb128
[16:34] <seb128> hey willcooke
[16:35] <willcooke> seb128, how's the swap day going :/
[16:36] <dobey> Laney: hey. i added you to the ubuntuone-client-engineering team on lp to make it easier to land your branches when you make random small fixes for pep8 changes and such
[16:36] <Laney> dobey: thanks, I saw because I started getting 9999999 emails :P
[16:36] <dobey> heh
[16:37] <Laney> I think I managed to /dev/null most of the teams now
[16:38] <Laney> srsly, usn-website-team? :-)
[16:38] <Laney> dobey: Is there some procedure for uploading stuff?
[16:38] <dobey> i have too. but i'm sending too much to /dev/null and sometimes miss assignments and such
[16:38] <seb128> willcooke, good, I'm visiting a friend and was on the road for the afternoon, I arrived now
[16:38] <dobey> Laney: uploading to ubuntu archive you mean?
[16:38] <Laney> dobey: yup
[16:39] <dobey> Laney: not really. i generally prefer to have things landed upstream before they get uploaded to the archive, but for super obvious things like pep8 fixes or for emergency fixes, it's ok to shove the patch in debian/patches first.
[16:40] <dobey> ubuntu-sso-client isn't on the ci train or such. it's on a tarmac still
[16:40] <Laney> dobey: I mean - just bzr push lp:whatever; bzr bd -S; dput?
[16:40] <Laney> or does tarmac do merging?
[16:41] <dobey> Laney: tarmac doesn't merge to the archive. for the archive, i just branch lp:ubuntu/ubuntu-sso-client, shove the patches in debian/patches and update changelog, bzr bd -S it, test build with pbuilder, and dput the changes
[16:42] <Laney> I figure being added to the team means I can merge things to trunk properly
[16:42] <dobey> Laney: tarmac just manages the upstream branches. you don't have direct write access to them.
[16:42] <dobey> Laney: adding to the team is because the bot can't see the canonical team (as it's a bot not an employee), and the upstream is CLAed, so tarmac checks for that when landing
[16:43] <Laney> ah
[17:35] <seb128> qengho, how is fixing chromium on utopic going? do you know if there is any workaround I could use to have a working browser while waiting for the issue to be resolved?
[21:24] <attente_> happyaron, hey, awake? :)
[21:28] <attente_> happyaron, what kind of status tracking is fcitx doing?
[23:12] <RAOF> Laney: Enjoy your webkitgtk


[02:32] <linuxdude> hello
[02:34] <linuxdude> testing
[02:34] <linuxdude> Am i live?
[03:07] <linuxdude> hello
[03:07] <linuxdude> can you guys see my text?
[03:08] <JoseeAntonioR> linuxdude: yes, but this is not live right now
[03:09] <linuxdude> I know, I'm just now setting up Empathy
[03:09] <JoseeAntonioR> oh, ok
[03:10] <linuxdude> just testing things out
[03:10] <linuxdude> I want to be able to catch the next one live
[03:10] <JoseeAntonioR> linuxdude: you should use #test to test
[03:11] <linuxdude> yes yes lol
[07:24] <dholbach> good morning
[14:49] <yogi__> hello
[15:06] <GuidoPallemans> isn't there a hangout?
[15:07] <tetris4> GuidoPallemans: its every wednesday, (next week it will be Thursday)
[15:07] <GuidoPallemans> but now
[15:07] <GuidoPallemans> with mhall and David planella


[00:00] <Havenstance> waf, so far so good. I'd have to venture a guess that the SSD is actually bad either that or Ubuntu's support for SSD's in 13.10 is sub par but idk
[00:16] <Havenstance> works like a charm :)
[00:16] <Havenstance> updated, rebooted, installed more then half my software no freezes or even any hiccups
[00:32] <waf> awesome, glad everything seems to be working out. sort of :)
[00:43] <Havenstance> well tbh im not really a fan of the SSD, since it was a christmas gift last year and I paid nothing for it im not too sad to see it go, they are quick but not muchfaster then a 7200 RPM Drive. least not much noticably faster
[00:44] <Havenstance> new technology and the bus speeds haven't really evolved for them much less the drive life times...
[04:09] <cmaloney> Happy almost a new year
[04:45] <Havenstance> cmaloney waf thanks for your help guys, its been stable thus far all night
[04:45] <Havenstance> bad SSD, happy new year to all of you too
[04:46] <cmaloney> Havenstance: Sorry to hear about the SSD but glad it was a simple fix.
[04:51] <Havenstance> eh, tbh im not that upset about it. it was a free drive anyway
[04:51] <Havenstance> its still in the box and it still works just not for gaming or anything crazy so I can use it for a flash drive :)
[05:00] <Havenstance> happy new year Michiganders
[05:06] <_stink_> this is the first new year in like 4 that i've stayed up until midnight
[05:06] <_stink_> and let me say
[05:06] <_stink_> i'm really angry i'm still awake
[05:13] <greg-g> _stink_: :(
[05:19] <cmaloney> _stink_: But look on the bright side...
[05:20] <cmaloney> Um... we have milk and cookies this late.
[05:39] <greg-g> speak for yourself
[05:39] <greg-g> we have water and tea
[05:41] <cmaloney> greg-g: We have Meijer to fix that.
[05:43] <greg-g> no meijer here
[05:43] <greg-g> I don't think the farmers markets are open this late
[05:43] <cmaloney> Who's fault is that? :)
[05:43] <greg-g> the farmers, obviously
[05:44] <greg-g> lazy gits
[05:44] <cmaloney> yeah, they should be out there selling their milk and their home-grown cookies.
[05:44] <greg-g> exactly
[05:45] <greg-g> 100% grass fed and finished, organic, no antibiotic/gbh, raw milk and cookies
[05:48] <cmaloney> I'm totally feeding Rowan Oreos when you guys visit. ;)
[06:02] <greg-g> and we'll kick you
[06:02] <greg-g> only softly
[15:08] <wolfger> Happy new year!
[15:35] <cmaloney> Happy new year wolfger
[15:36] <cmaloney> And to every one else in the channel. :)
[17:11] <rick_h_> new year party party
[17:17] <cmaloney> woo woo
[17:18] <cmaloney> Was playing Game Dev Tycoon
[17:18] <cmaloney> pretty fun. :)
[17:24] <jrwren_> nice hair greg-g
[21:15] <cmaloney> Afternoon
[22:16] <rick_h_> wheee
[22:40] <jrwren_> snow!
[23:13] <greg-g> it's 65 here