[00:56] <lazyPower> jose: still kicking around?
[01:00] <jose> lazyPower: yep!
[01:00] <jose> lazyPower: I'm testing the newly-fixed charm :D
[01:01] <lazyPower> jose: right on! Did you still need to PM me?
[01:01] <lazyPower> or are you unblocked?
[01:02] <jose> I think I'm good to go by now
[01:02] <lazyPower> allright cool. I didn't want to leave you hanging
[01:02] <jose> thanks!
[01:05] <lazyPower> Thats how we roll jose. Charmers 4 lyfe
[01:05] <jose> :P
[01:15] <lazyPower> jose: good work on the queue too man, you're killin it with the quality MP's
[01:15] <jose> thanks, just trying to :)
[01:15] <jose> let me know if any of those are buggy, maybe a couple will be
[01:16] <lazyPower> We'll have feedback on improvements if they are :)
[01:59] <jose> lazyPower: still around?
[01:59] <lazyPower> jose: indeed. Whats up?
[01:59] <jose> I'm having some problems printing a variable
[01:59] <lazyPower> pastebin?
[01:59] <jose> sure, second
[02:00] <jose> lazyPower: http://bazaar.launchpad.net/~jose/charms/precise/mailman/trunk/revision/32
[02:00] <jose> those exact lines in the diff
[02:00] <jose> they're printing literally "$DOMAIN" instead of the domain
[02:03] <lazyPower> jose: http://paste.ubuntu.com/7160367/
[02:04] <lazyPower> there's an illustration of whats going on. What you're seeing is a symptom of how single quotes work in bash
[02:04] <lazyPower> they are string literal annotations.
[02:04] <jose> hmm, got it!
[02:04] <jose> thanks
[02:04] <jose> w0ot, manually fixing it makes it work!
[02:06] <lazyPower> jose: you have single quotes surrounding those blocks, thats why you're getting the "$DOMAIN" printed. I dont understand what the 'manual fix' is - but happy its working :)
[02:06] <jose> yep, testing another deployment now!
[06:50] <jose> arosales: thanks for the heads up! :)
[06:51] <arosales> jose: oh, np. Thanks for your contributions. I see you have been busy :-)
[06:51] <arosales> good stuff.
[06:51] <jose> well, I thought juju could use some of my time :)
[06:51] <arosales> I too say that issue with Bip and we were wondering why proof was having an isue with a 2 character yaml key
[06:51] <arosales> s/say/saw/
[06:52] <jose> Marco mentioned it was because of a yaml issue, it needs to be 3chars min
[06:52] <arosales> jose: well the help with improving the overally charm quality is very appreciated.
[06:52] <jose> \o/
[06:53] <arosales> ya we didn't find anything in the yaml spec, but I too saw when I changed ip to any char with 3 char or greater proof was happy
[06:53] <jose> :P
[06:53] <arosales> jose: We are in the midst of a charm audit so it was nice to see your merge requests
[06:54] <jose> I just need to learn how to write amulet tests and I'll give a hand with tests
[06:54] <jose> maybe it can be considered for a charm school? 'Writing amulet tests for your charms'
[06:56] <arosales> jose, for sure a good topic we should revist. We have an initial one @ https://juju.ubuntu.com/resources/videos/
[06:56] <arosales> http://www.youtube.com/watch?v=KlTeRjGv4E4
[06:57] <jose> oh, missed it as it wasn't at ubuntuonair, not subscribed to Jorge :P
[06:57] <jose> anyways, I'll take a look at that one and see what can I do
[06:58] <arosales> we trying to make the video page complete in case someone does miss a charm school or just joins and wants to catch up.
[06:58] <arosales> jose: docs are also at https://juju.ubuntu.com/docs/tools-amulet.html
[06:58] <jose> seems easy enough
[06:59] <arosales> if you pull the source for charms such as rabbitmq, haproxy, or memcached you'll see some code examples in /test of amulet based tests
[07:00] <arosales> jose: our of curosity were you following jcastro's charm audit email, https://lists.ubuntu.com/archives/juju/2013-December/003331.html ?
[07:01] <jose> arosales: not actually, I've been mostly involved with juju this last two or three weeks
[07:01] <arosales> ah ok well your timing on fixing charms is perfect :-)
[07:01] <jose> cool!
[07:02] <jose> I'm also trying to convert most (if not all) READMEs to Markdown
[07:03] <arosales> +1
[07:03] <arosales> and I see you are using the teamplate from charm tools which is nice
[07:04] <jose> makes life easier
[07:08] <arosales> for sure
[07:11] <jose> well, time for me to go to bed, laters!
[07:13] <arosales> good night jose, good to talk to virtually here
[08:50] <jamespage> gnuoy, https://code.launchpad.net/~openstack-charmers/charm-helpers/ssl-everywhere/+merge/209301
[08:50] <gnuoy> looking
[11:44] <jose> marcoceppi: hey! is the minecraft server charm still good?
[11:52] <marcoceppi> jose: not really. it works but the version mineshaft is old
[11:53] <jose> hmm, ok
[11:53] <jose> I'm thinking on integrating some basic tests on my pagekite charm before it gets to the store
[11:54] <jose> that charm school is really useful in that matter :)
[11:56] <jose> marco_traveling: have a safe travel!
[12:00] <jose> uh, guys, I have a problem here... I am trying to write tests for pagekite but a config option would be the kite's secret
[12:38] <yolanda> jamespage, i added testing for databases to my MP also
[12:38] <yolanda> MPs
[13:36] <jcastro> man, content-fetcher looks like a great idea
[13:46] <lazyPower> jose: read that from an external source
[13:46] <lazyPower> jose: scratch that idea
[13:46] <lazyPower> i dont know what i was thinking.. need coffee
[14:14] <mgz> jcastro: would be good to have a mini blog post about content-fetcher I think
[14:14] <jcastro> nod
[14:17] <tvansteenburgh> where are charm's hook files located on a deployed node?
[14:24] <tvansteenburgh> also, is this a bug or something i'm doing wrong:
[14:24] <tvansteenburgh> tvansteenburgh@trusty-vm:~/src/charms/precise⟫ juju debug-log
[14:24] <tvansteenburgh> ssh: connect to host localhost port 22: Connection refused
[14:24] <tvansteenburgh> ERROR rc: 255
[14:26] <tvansteenburgh> and which bug list would i consult to see if it's a reported bug?
[14:26] <rick_h_> tvansteenburgh: is this in an lxc environment? debug-log doesn't work in lxc if I recall
[14:26] <tvansteenburgh> rick_h_: ok, yeah, it is
[14:26] <rick_h_> tvansteenburgh: ok, that's a known issue then. Looking for the hook path
[14:27] <tvansteenburgh> ok, hook path i can figure out, was just being lazy, hoping someone knew offhand
[14:27] <rick_h_> tv so checking real quick I find it in /var/lib/juju/agents/unit-juju-gui-0/charm/hooks
[14:27] <rick_h_> :)
[14:27] <rick_h_> all good
[14:28] <tvansteenburgh> cool, thanks
[14:51] <jcastro> ERROR cannot use 37017 as state port, already in use
[14:51] <jcastro> How do we resolve that error with the local provider? ^^
[14:52] <rick_h_> jcastro: ps aux | grep mongo
[14:52] <rick_h_> kill pid
[14:52] <jcastro> man, still?
[14:53] <rick_h_> not sure if there's a different thing but it's what I know/use
[14:53] <rick_h_> normally it's something went boom
[14:53] <jcastro> yeah
[14:53] <jcastro> something went bada-boom
[15:11] <lazyPower> big bada-boom
[15:12] <lazyPower> <3 fifth element, just saying
[15:26] <rick_h_> marco_traveling: delete charm/bundle landed and removed those vms ones.
[15:30] <rick_h_> jcastro: we can garden out the old bundles with poor names now. let me know when you want to check it out
[15:34] <jcastro> rick_h_, busy with a mongo cluster ATM, just clean em!
[15:54] <frankban> rbasak, rick_h_: quickstart 1.3.0 with the --distro-only flag just released on PyPI
[15:55] <rbasak> frankban: thanks! Please could you update bug 1282630 to match? Then we can change the FFe and MIR bugs.
[15:55] <rbasak> s/change/chase
[15:57] <frankban> rbasak: done
[15:58] <rbasak> frankban: thanks! I'll chase in #ubuntu-devel.
[15:58] <frankban> rbasak: thank you!
[16:02] <rbasak> frankban: is the goal to get juju-quickstart on the desktop CD, on the server CD, or both?
[16:03] <frankban> rbasak: I guess both, rick_h_? ^^^
[16:04] <rbasak> I never considered this aspect before. We'll need to check with the release team to do this at this late stage, assuming the MIR is accepted.
[16:04] <rbasak> I'm not sure if it needs an FFe or not, and we'll miss beta2.
[16:04] <rbasak> (and I hope there's space, etc)
[16:04] <rbasak> jamespage: ^^ any advice here, please?
[16:05] <rbasak> jamespage: I presume this is higher priority now that juju-core looks unlikely for main?
[16:06] <jose> lazyPower: it'd still be public, yeah. any other ideas on how to do that?
[16:06] <jose> otherwise, a test wouldn't be possible unless some values are set manually
[16:06] <jamespage> rbasak, frankban: I think that's out of scope for 14.04 now
[16:06] <jamespage> if we don't mir juju-core, we won't do the mir for quickstart
[16:07] <lazyPower> jose: reach out to the support dept/mailing list for the service and see if there are testing credentials that can be used that dont "actually" work, but will allow you to mock the login
[16:07] <rbasak> jamespage: that confuses me a little. My understanding is that we'll want juju-quickstart more in this case?
[16:07] <rbasak> rick_h_: ^^
[16:08] <jamespage> rbasak, surely juju-quickstart depends on juju-core?
[16:08] <rbasak> jamespage: no - it installs juju-core from a PPA (by default). On discussion from the MIR, it can also install from the archive only as an option.
[16:08] <jose> lazyPower: hmm, the point is not about the login, but checking that the tunnel works... that would need some valid credentials
[16:08] <rbasak> jamespage: the underlying idea for juju-quickstart is that it's cross-distro multiplatform etc - eg. from PyPI.
[16:09] <rbasak> jamespage: there's some talk around this subject in the MIR bug.
[16:09] <jamespage> rbasak, yes - but not for the distro packages which should IMHO always install from the distro
[16:09] <lazyPower> jose: no idea bud, i thought you were doing unit tests, not amulet tests
[16:09] <jose> yep, I started those :)
[16:09] <lazyPower> theory states you could have a config option for them, that the user would have to input, but they would fail consistently in CI
[16:09] <rbasak> jamespage: please could you comment on the MIR bug in this? I did raise this point, so the option to only install from the distro was added. But I didn't ask for any particular default.
[16:10] <rbasak> jamespage: I think it makes sense for the user to at least be able to ask for a PPA installation as an option, even if it is decided that from distro is default.
[16:10] <rbasak> jamespage: in this case, juju-quickstart is still useful even without juju-core in main.
[16:10] <lazyPower> jose: let me ping marco about this when you get back, as I have a PAAS charm in the store that needs amulet tests too, that require sensitive credentials.
[16:10] <lazyPower> s/you/he/
[16:11] <jamespage> rbasak, agree that having ppa as an option is fine
[16:11] <jose> lazyPower: awesome, thanks!
[16:11] <jamespage> rbasak, but I'm not sure I see the value of including this in main without juju-core
[16:11] <jamespage> 'use this fully supported tool to install a tool that's not fully supported'
[16:12] <rbasak> jamespage: I think the goal is to have it on the CD, and that was the driver for main inclusion, rather than support.
[16:12] <rbasak> rick_h_, frankban: ^^
[16:12] <jamespage> rbasak, I see juju-core and quickstart tied tbh
[16:12] <rbasak> jamespage: I guess there's a mismatch of expecations here, so we should talk soon.
[16:13] <rbasak> jamespage: I understand what you're saying - it's just that rick_h_ seemed quite keen on having juju-quickstart on the CD anyway, even without juju-core in main.
[16:13] <frankban> rbasak, jamespage: the goal is to gice to users/developers the ability to go from zero to a fully deployed environment (including the GUI and bundles support) in a single command
[16:13] <frankban> give even
[16:13] <rbasak> frankban: you can more or less get that from universe though. Two commands - apt-get install juju-quickstart, and juju-quickstart. Right?
[16:14] <rbasak> frankban: so I think what jamespage is asking is what is the additional benefit of this being in main/on the CD?
[16:14] <jamespage> rbasak, frankban: I don't see this as any different to the objections being made on the juju-core MIR re tools coming from simplestreams
[16:14] <rbasak> (if juju-core is not)
[16:14] <rbasak> jamespage: we agree that PPA is OK to be an option, so what's left is what should be the default.
[16:14] <rbasak> Oh, I see.
[16:15] <rbasak> With juju-quickstart in main and juju-core in universe, there's a dependency from main to universe, even if it's not expressly stated in metadata.
[16:15] <rbasak> I hadn't considered that.
[16:16] <frankban> jamespage, rbasak: IC, could you please add a comment on that regard on the bug?
[16:16] <jamespage> rbasak, you got it
[16:16] <jamespage> frankban, will do
[16:16] <frankban> thanks
[16:23] <rick_h_> jamespage: rbasak sorry catching up, was in a meeting
[16:23] <rick_h_> jamespage: rbasak the goal for quickstart in 14.04 is not on any cd.
[16:23] <rick_h_> jamespage: rbasak It's a post 14.04 goal, so we want to keep it in mind
[16:24] <rick_h_> jamespage: rbasak I'd say first priority would be desktop cd vs server cd
[16:24] <rick_h_> jamespage: rbasak but I'm assuming on that one. I think it fits that use case more and it's part of our argument on why it's ok to use a ppa for getting juju
[16:25] <rick_h_> jamespage: rbasak and yes, the goal of quickstart is that something small is in main that users can use to get juju-core and juju-local even though it's not in main
[16:25] <jamespage> rick_h_, tbh I think that breaks the rules
[16:25] <rick_h_> jamespage: rbasak so with core not in main it's even more useful to end juju users to have that available to them
[16:25] <rbasak> jamespage: only sort of, though. Eg. "pip install <foo>" is permitted in main.
[16:25] <rbasak> (I assume it is)
[16:26] <rick_h_> jamespage: understand, that's what I'm trying to learn/get a grip on. I'm not sure on the rules. We've got a vision for a tool for end users to be able to get started with juju as easy as possible and we're working on what we can do to deliver that
[16:26] <rbasak> As is wget, to take it to the extreme. I'd like to identify some kind of underlying principle to this kind of thing.
[16:27] <rick_h_> jamespage: rbasak the more steps we can automate and move away from the user from a fresh ubuntu install the happier everyone gets as it eases juju adoption, which is quickstart's #1 goal
[16:28] <rbasak> The actual rule is from here: http://people.canonical.com/~cjwatson/ubuntu-policy/policy.html/ch-archive.html#s-main
[16:28] <rick_h_> looking
[16:28] <rbasak> "In addition, the packages in main...must not require a package outside of main for compilation or execution (thus, the package must not declare a "Depends", "Recommends", or "Build-Depends" relationship on a non-main package)"
[16:28] <rbasak> Now, what's the spirit of that, as well as the wording?
[16:28] <jamespage> rick_h_, rbasak: I think my argument is about how this adds value by being in main IF a) we don't want to get on the ISO and b) juju-core is not in main (think Recommends juju-core>juju-quickstart)
[16:29] <rbasak> juju-quickstart in main is useless without _some_ external source (eg. universe or PPA). Perhaps that's a factor.
[16:29] <rick_h_> jamespage: so if we can get it on the cd then awesome, but we set expectations it might take more time to make that happen.
[16:29] <rbasak> OTOH, so is "pip install".
[16:29] <rick_h_> jamespage: so if we can get it then let's assume the value add is there
[16:30] <rick_h_> jamespage: the end value is that "user installs ubuntu, wants to try out juju, juju-quickstart will get juju, configure a lxc environment, bootstrap, and bring up the gui in one single built in command
[16:30] <rbasak> jamespage: I don't hold Recommends juju-core>juju-quickstart as highly valuable. We should have it, but I imagine that docs could tell people to install juju-quickstart and go from there.
[16:30] <jamespage> rick_h_, I'm not comfortable proposing this for the ISO unless we also have juju-core in main
[16:31] <rick_h_> jamespage: ok, so you'd suggest we get quickstart into main as step #1 with juju in universe. Next release we work on getting juju into main and quickstart on the iso?
[16:31] <rick_h_> jamespage: I'm fine staging it out, but want to make sure we konw what we need to do to make the end vision happen
[16:31] <jamespage> rick_h_, no
[16:32] <jamespage> rick_h_, I think the policy that rbasak highlighted above applies even if the relationship is not declared in the package dependencies
[16:32] <jamespage> juju-quickstart depends on either universe or a PPA to function
[16:32] <jamespage> main can only depend on main
[16:33] <rick_h_> jamespage: ok, so we are in universe while juju is in univsere. When they get into main we can then also go for main & on the iso at that time?
[16:33] <jamespage> rick_h_, which is why I tie quickstart and juju-core together for main inclusion
[16:33] <jamespage> rick_h_, sure
[16:34] <rbasak> jamespage: what about stuff on the iso? Normally all dependencies are included, but they wouldn't be in this case.
[16:34] <rick_h_> jamespage: ok then. I can tell that story fine. I just need to know that we're on the right path per what we're supposed to be getting to
[16:34] <rbasak> jamespage: do you think the same bundling rule should apply to the iso? ie. require juju-core to be on it if juju-quickstart will be there?
[16:34] <jamespage> rbasak, I'm not sure tbh
[16:35] <rbasak> jamespage: I understand your point of view, but I'm not completely convinced about your position myself. I can see both sides. It's very fuzzy.
[16:35] <rbasak> It comes down to how to interpret the rule, and this is definitely a grey area.
[16:35] <jamespage> rbasak, good job its not actually up to us then :-)
[16:36] <rbasak> jamespage: perhaps we should open this up for wider discussion? ubuntu-devel ML?
[16:36] <jamespage> rbasak, I think the bug is fine
[16:40] <rick_h_> jamespage: rbasak ok, so 1) we'll have quickstart and juju-core in universe and quickstart's --distro-only flag will be ok for 14.04
[16:40] <rick_h_> jamespage: rbasak 2) Discussion is required to think on how/if quickstart can be in the iso once it and juju-core get into main in a subsequent release
[16:44]  * rick_h_ goes for lunch  afk
[16:49] <jose> lazyPower: btw, the charm is ready for review whenever you want
[17:05] <lazyPower> jose: Thanks. We're a bit slammed at the moment with stuff, we'll try to get the community charms out asap.
[17:05] <lazyPower> thanks for the heads up
[17:05] <jose> no worries
[17:05] <jose> and no hurries too
[17:19] <bloodearnest> hmm, is there anyway to assign a (fake?) public ip to a unit using local provider? From juju's pov, I mean
[17:20] <bloodearnest> some thing that will be returned from unit-get public-address
[17:58] <marco_traveling> rick_h_: ta!
[18:11] <jcastro> hazmat, any idea why -deployer would bail if you modify a charm locally?
[18:15] <hazmat> jcastro, see flags
[18:16] <hazmat> jcastro, its a safety valve with a cli flag
[18:16] <hazmat> jcastro, it should default to allowing local mods
[18:17] <hazmat> jcastro, there's a -L flag to disallow local mods afaicr
[18:23] <mbruzek> hazmat is there an opposite to the -L flag?
[18:23] <mbruzek> We want to allow local mods
[18:25] <hazmat> mbruzek, jcastro there's a bug that this is non obvious .. but try with and with out the -L flag ... one should work/toggle the behavior
[18:25] <jcastro> yeah I'll have to circle back
[18:25] <jcastro> the mysql charm is broken with master-slave for us anyway
[18:37] <blackboxsw> marcoceppi as a heads up,    we have gotten our storage proposal charm branches in order, reviewed and set to Fix Committed for block-storage-broker and storage subordinate charms.
[19:29] <Valduare> hi guys
[19:29] <Valduare> im new to juju
[19:29] <Valduare> how do I start
[19:38] <Valduare> trying to figure out how this all works, so I start a vm and install ubuntu server on it then install juju and then use juju to deploy a service I want on that specific server?
[20:12] <tvansteenburgh> Valduare: hi, i'm new here too
[20:12] <Valduare> hi
[20:13] <tvansteenburgh> https://juju.ubuntu.com/docs/ is a great place to start
[20:14] <tvansteenburgh> the machine you install juju on does not get services deployed to it. it's used to send commands to the environment that juju is controlling
[20:17] <Valduare> ah
[20:18] <Valduare> currently I have a freenas box serving storage through iscsi to an esxi host box that runs 14 vm’s
[20:24] <lazyPower> Valduare: using the manual provider you could use juju to power your workloads on that esxi host
[20:24] <lazyPower> create the vms manually, register them in juju, then juju deploy <service> --to <machine id>
[20:25] <Valduare> was just reading this http://insights.ubuntu.com/resources/tutorials/interested-in-maas-and-juju-heres-how-to-try-it-in-a-vm/
[20:25] <Valduare> looks like i could possibly make this all virtualized?
[20:26] <lazyPower> IMHO, remove the complexity of having maas as your provisioner and just use the manual provider
[20:26] <lazyPower> while maas is cool, its accomplishing the same thing youa re doing with ESXI, by registering the hosts yourself to juju
[20:27] <Valduare> gives an interface for rebooting vm’s and such too though?
[20:27] <lazyPower> actually, juju doesn't do machine management like that. Its pretty focused on service orchestration, so it sits a layer above configuration management.
[20:28] <lazyPower> in terms of the tech stack.
[20:28] <Valduare> I mean maas would
[20:29] <lazyPower> I'm not nearly as familiar with maas as I am with juju. Perhaps someone else with a bit more experience would be able to answer that.
[20:29] <lazyPower> sarnold: ^
[20:31] <Valduare> so on the juju subject, it lets you specify what machine to provision such and such service
[20:31] <lazyPower> Valduare: the intention behind maas is to turn bare metal into a cloud, so theres a domain controller to handle the provisioning via cloudinit so you get bare systems with an image, similar to what you would get by booting the ubuntu AMI's on aws.
[20:31] <Valduare> ie mysql
[20:31] <lazyPower> Correct, you pick a service from teh charm store, or charm up your existing app, and define what the relationships require to operate, such as a database name, host, user/pass combo, and juju handles setting up the services
[20:32] <lazyPower> eg: mediawiki has a sql dependency. You deploy mediawiki, teh charm does nothing, deploy mysql and relate it to mediawiki and whammo, you've got a functioning mediawiki installation being managed by juju
[20:32] <lazyPower> ready to scale up/down, and be configured via the juju settings.
[20:32] <lazyPower> and if you're using the gui, you have a nice network map to visualize your deployments
[20:33] <Valduare> so since I just have the one host right now
[20:33] <Valduare> I should deploy a juju bootstrap vm
[20:33] <Valduare> on there and then start migrating all my services over to vm’s provisioned by juju
[20:35] <lazyPower> if you use the manual provider, the provisioning would be manual.
[20:35] <lazyPower> juju would handle the configuration mangement and orchestration
[20:35] <lazyPower> ie: how a service should be deployed, and how relationships are handled with the service.
[20:37] <Valduare> does it launch a new vm for each service?
[20:37] <Valduare> ie mysql in its own ubuntu vm
[20:39] <lazyPower> It depends on your provider. Thats why i've been specific with terminology about the manual provider
[20:39] <lazyPower> as it implies, all provisioning is done manually with the manual provider
[20:39] <lazyPower> if you're using a maas provider, it pulls from the allocation pool in maas. if you're using a cloud provider like aws, hpcloud, or azure it performs the api calls to provision a new vm for you, so therefore yes it does it for you.
[20:40] <Valduare> so with the manual provider i’d specify I want mysql on such and such vm
[20:40] <lazyPower> correct
[20:41] <Valduare> and if I were using openstack?
[20:41] <Valduare> does it separate all services out to their own vm
[20:42] <lazyPower> openstack communicates to nova to spin up your machines for you. its got a provisioning api
[20:42] <lazyPower> sorry, juju communicates to nova to spin up your machines.
[20:42] <lazyPower> i mistyped.
[20:44] <Valduare> there are a ton of layers to do all this lol
[20:45] <lazyPower> It can be, however juju can spin up an openstack cluster in 25 minutes, i think we've benchmarked even shorter times
[20:45] <lazyPower> and hten, you're free to create a juju environment on top of that openstack cluster that juju deployed. Using juju to deploy juju. Juju ception?
[20:48] <sarnold> haha, jujuception :)
[20:48] <Valduare> lol
[20:49] <Valduare> how long would that take on amd e-350 processors :P
[20:50] <lazyPower> I haven't run any benchmarks on that, so good question
[20:50] <lazyPower> i actually dont have experience with those processors either
[20:52] <Valduare> amd version of atom processor basically
[20:53] <lazyPower> ah, well you wont be breaking any earth shattering speed records
[20:53] <lazyPower> but I would think it would do fine
[21:08] <Valduare> so juju sets up a full openstack system with storage and everything?
[21:20] <Valduare> hmm im not seeing a charm for nginx?
[21:20] <jose> Valduare: see bug #994699
[21:21] <_mup_> Bug #994699: Charm Needed: Nginx <Juju Charms Collection:Incomplete by imbrandon> <https://launchpad.net/bugs/994699>
[21:22] <Valduare> hmm
[21:24] <lazyPower> Valduare: thats been a very back and forth topic in the past, if we want to charm up nginx as a service and deploy content as subordinates or just include nginx in your service dpeloyment
[21:24] <lazyPower> thus far, including nginx as part of the service deployment has been the winner, but there are some new charms coming in that set a web host with subordinate based content deployments.
[21:25] <lazyPower> however, nothing thats landed in the store yet
[21:26] <Valduare> what kind of things are you using charms to deploy?
[21:26] <Valduare> im searching through the charms now and … there’s not much?
[21:26] <lazyPower> Valduare: what are you expecting to see thats not there? we have 158 services to date of charms promulgated
[21:28] <Valduare> things like gitlab, canvas-lms, openerp, nginx-php-fpm-mysql,
[21:28] <lazyPower> thare are give or take ~ 70 more in personal namespaces that are not in the store, as they dont follow the store guidelines, or are not ready for public consumption.
[21:28] <lazyPower> Valduare: gitlab is in there, openerp is in there
[21:28] <Valduare> just searched for gitlab 0 came up
[21:28] <Valduare> ah now it shows heh
[21:28] <lazyPower> i've actuallly got a prototype gitlab charm
[21:28] <lazyPower> er, gitlab-ci charm
[21:29] <lazyPower> its not ready for promulgation by any stretch, but ready for people to stress test and provide feedback
[21:30] <lazyPower> and there's an openrp bundle sitting int he review q waiting to be analized and acked for the store so its drag and drop deployment.
[21:30] <Valduare> whats the bundle do differently than the openerp charms already there?
[21:32] <lazyPower> the bundle is a deployment schema that has all the services required to utilize openERP in a client/server model
[21:32] <lazyPower> where the backend is split from the front end, ready to be scaled individually depending on your needs
[21:32] <lazyPower> Valduare: https://juju.ubuntu.com/docs/charms-bundles.html
[21:40] <Valduare> and it’d install it all on one vm?
[21:42] <sarnold> however many VMs are necessary..
[21:43] <Valduare> what specifies the necessity
[21:44] <tvansteenburgh> Gators#1
[21:44] <tvansteenburgh> gah. and now you all no the password to my vm
[21:44] <tvansteenburgh> s/no/know/
[21:45] <tvansteenburgh> if i had a nickel for every time...
[21:45] <Valduare> if you hadnt mentioned…. we’d all think you were rooting for a highschool basketball team or something...
[21:48] <tvansteenburgh> well, not high school: http://espn.go.com/mens-college-basketball/team/_/id/57/florida-gators
[22:01] <Valduare> lazyPower: I was just reading about juju some more :P they were talking about wordpress juju add-unit wordpress does juju have some sort of load balancing system in place?
[22:01] <lazyPower> you can deploy haproxy infront of it
[22:03] <Valduare> this is stuff i’ve never gotten into before.. :)
[22:03] <sarnold> .. and it all seems too good to be true when you just juju add-unit -n 10 wordpress or whatever AND IT JUST HAPPENS
[22:03] <Valduare> is there a way I could setup a remote server and haproxy between the two locations so if one goes down ie internet outage it’d serve from the other location>?
[22:03] <sarnold> scary :)
[22:08] <lazyPower> Valduare: actually, with manual provider, you can do cross datacenter orchestration like that
[22:09] <lazyPower> and haproxy already takes care of the load balancing in the event of an outage
[22:09] <lazyPower> but your latency will be a factor in that style of deployment
[22:10] <lazyPower> tvansteenburgh: whats your IP again?
[22:10] <lazyPower> ;)
[22:10] <Valduare> lol
[22:11] <Valduare> i sitll dont quite understand the logic behind the ha stuff
[22:12] <Valduare> things like a php process pegging out the cpu I could understand but internet outages that’d knock your ha proxy out too
[22:15] <sarnold> Valduare: normally something like haproxy would live in front of a dozen or two dozen machines in the same rack..
[22:15] <sarnold> Valduare: if you lose networking to the datacenter, so be it ;) hopefully your application has been designed to failover to another availability zone
[22:15] <Valduare> where would that be designed into? :P
[22:16] <Valduare> im only familar with bare metal hosting lol
[22:18] <sarnold> Valduare: it could be done at DNS level, you could do round-robin dns with haproxy IPs, one per data center..
[22:18] <sarnold> Valduare: or you could use IP Anycast if you're rich and powerful enough :)
[22:19] <lazyPower> sarnold: I couldn't have put it any better myself. *hat tip*
[22:19]  * sarnold bows
[22:19] <sarnold> lazyPower: thanks :) did I overlook another option?
[22:19] <lazyPower> sarnold: i'm giving a talk at CMU next friday and I need to get this abstract over to the orchestrator. Would you mind giving it a proof for me?
[22:19] <sarnold> it feels like there's got to be at least one more option. hehe.
[22:19] <sarnold> lazyPower: sure
[22:20] <lazyPower> sarnold: there are others, but round robin/latency based dns was my poison of choice.
[22:20] <lazyPower> it worked at the entry point of the stack, vs complex configuration over convention
[22:20] <lazyPower> and im a rails guy, so i'll always pick convention over configuration, any day of the week
[22:21] <sarnold> lazyPower: yeah, load-balanced DNS has worked awesome for OFTC for years; the servers periodically report their user load and above a certain number the server is pulled, below a certain number it's re-added, and when machines are going to be serviced, they can get taken out entirely two weeks ahead of time to let people gracefully age off the thing
[22:22] <sarnold> but "works for an irc network" vs "works for netflix" are two different things ;) hehe
[22:24] <Valduare> right now I got a djbdns vm running on my one mini itx server host :P
[22:24] <Valduare> godaddy points to that for the name server of all my domains
[22:24] <sarnold> djb <3
[22:25] <Valduare> coudlnt figure out bind for the life of me
[22:27] <lazyPower> bind is cool, until it stops being cool
[22:27] <lazyPower> then its a giant tree made of hate
[22:28] <Valduare> djbdns has been pretty darn good to me so far
[22:29] <sarnold> given all the wonderful alternatives, you'd have to pay me quite a lot to get me to use bind :) heh
[22:29] <Valduare> so I basically need to get a dns outside of my “data center” eh?
[22:30] <sarnold> heh I'm surprised you were able to convince godaddy to let you use only a single dns server :)
[22:30] <sarnold> I thought 'two servers in glue' was the requirement
[22:31] <lazyPower> thats easy enough of masquerade
[22:31] <lazyPower> s/of/to
[22:31] <sarnold> hahah
[22:31] <sarnold> evil :)
[22:35] <Valduare> you just put the same ip in both slots on godaddy
[23:23] <Valduare> sarnold: so with the wordpress example, and haproxy, how does it sync data
[23:24] <sarnold> Valduare: I've got no idea how you'd reasonably scale wordpress to multiple availability zones / datacenters ...
[23:24] <Valduare> http://www.jorgecastro.org/2013/07/31/deploying-wordpress-to-the-cloud-with-juju/
[23:24] <sarnold> Valduare: mysql data dumps on cold backups would be my first attempt if I didn't find something better from an expert :)
[23:29] <lazyPower> valduare read up on MySQL replication with master slave relations
[23:30] <lazyPower> with manual provider you deploy to multip!e azs or dcs and apply the theory we have already covered
[23:31] <Valduare> how would all the /var/www/sitedir sync?
[23:31] <Valduare> how do you deploy to multiple servers
[23:32] <sarnold> rsync from whatever host is used for authoring?
[23:40] <Valduare> and whatever host used for authoring is whatever host the haproxy connects you to?
[23:41] <Valduare> bear with me :P lol
[23:41] <sarnold> Valduare: It would be your laptop or something? :) I dunno how these things actually get -used- :)
[23:42] <Valduare> oh think I see whaty ou mean
[23:42] <Valduare> so from workstation rsync to all the hosts at same time?
[23:43] <sarnold> Valduare: ah! check out the "Handling wp-content" section here: http://manage.jujucharms.com/charms/precise/wordpress
[23:44] <sarnold> of course that makes more sense than rsync. haha.
[23:56] <Valduare> ok


[09:21] <asac> hi
[09:30] <nikolam> Hi.
[09:31] <nikolam> Could I use on Ubuntu packages from Debian, I compiled for Iceape/Seamonkey 1.1.11
[09:31] <nikolam> since there is no 1.1.11 Seamonkey in Ubuntu repo ?
[09:32] <nikolam> Should I post a bug about Newest Seamonkey not available in Ubuntu?
[09:33] <nikolam> There are many security-related things that are fixed in newer release
[09:42] <asac> hmm
[09:42] <asac> fta usually maintained the seamonkey package we have. I think he is still on holiday, so i guess that we should take over this release
[09:44] <asac> nikolam: was 1.1.10 skipped upstream?
[09:44] <asac> https://code.edge.launchpad.net/~mozillateam/seamonkey/seamonkey-1.1.dev
[09:44] <asac> thats our branch
[09:44] <asac> we could do the 1.1.11 packaging in their and then upload
[09:45] <asac> and create a .hardy branch based on that so we can do the "stable" maintenance in a "mature" branch ;)
[09:45] <nikolam> YES thats it! :)
[09:49] <nikolam> I never used to do that things with .diffs
[09:49] <asac> nikolam: i think first step is to post a bug about "security updates available"
[09:49] <asac> then update the branches and get that uploaded
[09:49] <nikolam> Ok will do that.
[09:50] <asac> nikolam: basically how it works is: bzr branch URL
[09:50] <asac> then dch -v1.1.11+nobinonly-0ubuntu1 -DUNRELEASED
[09:51] <asac> bzr commit -m "* open tree for 1.1.11 packaging"
[09:51] <asac> then do the required packaging, documentingin changelog etc.
[09:51] <asac> when done you do a
[09:51] <asac> dch -r -Dintrepid
[09:51] <asac> bzr commit -m "* RELEASE 1.1.11+nobinonly-0ubuntu1 to ubuntu/intrepid"
[09:52] <asac> and bzr push to lp:~YOURLPID/seamonkey/seamonkey-1.1.dev
[09:52] <asac> and let me know so i can review and merge that to our release branches
[09:53] <asac> to get a proper orig.tar.gz you probably have to do:
[09:53] <asac> ./debian/rules get-orig-source DEBIAN_TAG=SEAMONKEY_1_1_11_RELEASE=1.1.11
[09:54] <asac> this should get the right tarball, stripped with the binary only files we dont want
[09:55] <asac> for hardy you would do the same excpet that you would use s/intrepid/hardy-security/
[09:55] <asac> and as version
[09:55] <asac> 1.1.11+nobinonly-0ubuntu<IP_ADDRESS>
[09:56] <asac> and the branch to use to push to would be lp:~YOURLPID/seamonkey/seamonkey-1.1.hardy
[09:57] <asac> i dont think you need to change much on the packaging side. most likely its just documenting the release in changelog ... and maybe drop one patch or so if there was something applied upstream
[10:02] <nikolam> I wrote down every word you were saying. And installed bzr
[10:11] <asac> nikolam: instll bzr-builddeb as well
[10:12] <asac> we dont have full-source trees, so you  basically put the orig.tar.gz in a tarballs directory next to your branch directory
[10:12] <asac> and run bzr bd --merge --dont-purge
[10:12] <asac> e.g.
[10:12] <asac> seamonkey-1.1.dev
[10:12] <asac> tarballs
[10:12] <asac> and then run the comment above in the seamonkey dir
[10:30] <nikolam> Will get something to eat. get back later. Thanks.
[11:10] <Volans> asac: there?
[11:10] <asac> Volans: yeah
[11:11] <Volans> automatic alert received, I have just now added the date to the wiki page that was still TBA
[11:11] <asac> yep
[11:11] <asac> have that too
[11:11] <asac> fine
[11:11] <Volans> I have just checked now the fridge agenda... but does not appear our meeting
[11:13] <asac> Volans: just pinged cody on -devel about it
[11:14] <asac> lets see what comes out of it
[11:14] <Volans> ok, I know that gnomefreak asked cody and tell him to ping himself or me when done
[11:14] <Volans> some days ago
[11:14] <asac> yeah. i am not even sure if he is the right to ask. if he doesnt reply ill see whoelse to ask
[11:16] <asac> asked on #ubuntu-news too now
[11:17] <Volans> in sunday is always diffult to have reply I think ;)
[11:17] <Volans> s/is/on/
[11:18] <asac> sure. hope they read the backlog ;)
[11:21]  * asac taking shower
[12:23]  * Volans lunch time bye
[17:57] <asac> @time EDT
[17:57] <asac> @time America/Pacific
[17:57] <Volans> 9:57 ;)
[17:57] <Volans> los angeles
[17:58] <Volans> but EST is eastern... atlantic...
[17:58] <asac> @time America/Los_Angeles
[17:58] <Volans> and now at New York is 12:58 in the morning
[17:58] <asac> @time America/Los_Angeles 20:50
[17:58] <asac> @time America/Los_Angeles 20:50 UTC
[17:58] <asac> ;)
[17:58] <asac> damn
[17:58] <Volans> LOL
[17:58] <Volans> you are testing the bot or you need something?
[17:59] <asac> ubottu: what is 13:00 EDT in UTC+2?
[17:59] <asac> ;)
[17:59] <asac> i think the info above is enough
[17:59] <asac> but i felt lazy ;)
[18:00] <asac> oh ... they took my editor privileges away from ubottu
[18:00] <asac> hmm .... most likely its just that i never had that status with the new bot
[18:00] <Volans> LOL, maybe with ubottu3?
[18:00] <Volans> sorry ubot3
[18:01] <asac> so whats 1pm EDT for me ;)
[18:01] <Volans> NOW
[18:01] <Volans> 19
[18:01] <asac> really?
[18:02] <Volans> if EST is New York yes
[18:02] <asac> its 10am now
[18:02] <Volans> eastern USA time
[18:02] <asac> thats what i thought ;)
[18:02] <asac> but i mixed up the diretion  ;)
[18:02] <asac> though eastern time was at "west coast" ;) lol
[18:02] <Volans> LOL
[18:02] <Volans> :D
[18:28] <asac> Volans:
[18:28] <asac> 12:51 < cody-somerville> asac,
[18:28] <asac> http://www.google.com/calendar/event?eid=amNzaXFybXAyaHIxZ25qcDg5bWY2NmR2cDQgajVxODVtbWk2dWp2anRpaTVzMW4zbGk1aW9AZw&ctz=Etc/GMT
[18:28] <asac> 12:51 < cody-somerville> asac, appears to exist to me
[18:29] <Volans> http://fridge.ubuntu.com/event/2008/08/01/month/all/all/1
[18:29] <asac> hmm
[18:29]  * asac asks
[18:29] <Volans> ok :)
[18:36] <Volans> /TOPIC #ubuntu-mozillateam Welcome to the Ubuntu Mozilla Team: | Mailing List<EMAIL_ADDRESS>| Please help Mozilla QA tracker: http://tinyurl.com/6yo6g7 | Firefox 3 released to hardy-updates! | Next meeting will be held on Sunday, 3rd August, 18:00 UTC (agenda available at: http://tinyurl.com/2ekzoq )
[18:42] <asac> Volans: ok appears to be that they moved to a google calendar, but the webste is not integrated yet
[18:43] <asac> he will  add it to the old db as well for now
[18:43] <asac> at least i think that he will ;)
[18:43] <Volans> ok, no problem, and the bot in the meeting channel il related to the google calendar?
[18:44] <Volans> I have added the date to this channel topic
[18:57] <armin76> buuuuuuuuuuumb!
[18:57] <armin76> !info firefox-3.0
[18:57] <armin76> omg not bumbed! :D
[19:03] <Volans> asac: he have added the meeting to the fridge calendar ;)
[19:04] <Volans> ehm.. Etc/GMT??? perhaps UTC/GMT -> http://fridge.ubuntu.com/node/1595
[19:09]  * Volans go to dinner... see you
[19:09] <Volans> maybe we can put the agenda page on the announce in the fridge like others announcemet
[19:09] <Volans> bye
[21:53] <fretchen> Hello, I try to build sunbird from source. Two days ago everything worked fine, so I should have installed all the libs. But if i try to built the trunk or the 0.8 release, I get the following error message : /usr/include/pango-1.0/pango/pangocairo.h:71: erreur: «cairo_font_type_t» does not name a type . Does anyone know help for this ?
[22:08] <Jazzva> asac, what are we gonna do with extensions' merges? Are we gonna blacklist them on mom/dad?
[22:34] <asac> Jazzva: depends on whether we moved the extension to the new infrastructure yet I'd say
[22:34] <Jazzva> asac, moz-devscr and xpi.template? that infrastructure?
[22:48] <Jazzva> asac, can we check which extensions have been moved and then to ask for those to be blacklisted?
[22:49] <asac> Jazzva: hmm. if there is no debian package we probably dont need to blacklist them ;)
[22:49] <asac> Jazzva: yeha. moz-devscript + our branches
[22:49] <Jazzva> asac, of course... for those that have a package in debian ;))
[22:49] <Jazzva> there are few of them
[22:58] <asac> Jazzva: yeah. i guess we should start a first round of updates in the next week ;)
[22:58] <asac> Jazzva: does the check-extension script still work?
[22:58]  * asac runs it ;)
[22:59] <asac> lets see what happens
[23:00] <asac> hmm upstream version is always empty
[23:01] <Jazzva> not sure... haven't tested it...
[23:01] <Jazzva> :)
[23:01] <asac> too bad still no upstream version
[23:01] <asac> http://paste.ubuntu.com/28823/
[23:02] <asac> thats what i got so far
[23:02] <asac> apparently lal branches are checked
[23:02] <Jazzva> am I stupid, or there is no reason why some branches are indented?
[23:04] <Jazzva> yes, upstream missing...
[23:04] <asac> not sure
[23:05] <asac> it looks that way on the terminal
[23:05] <asac> some columns appear to be right-indent
[23:05] <asac> maybe that one is pseudo-center ;)
[23:05] <Jazzva> hehe
[23:05] <fta> hi
[23:05] <asac> but looks strange ;)
[23:05] <fta> i'm back
[23:06] <asac> hah, right on time ;)
[23:06] <Jazzva> hey, fta :)
[23:06] <asac> fta: welcome
[23:06] <Jazzva> welcome back
[23:06] <fta> my desktop is all broken :( bad intrepid
[23:06] <asac> oh
[23:06] <asac> mine is still working ;)
[23:07] <asac> havent updated for a few days though iirc
[23:08] <Jazzva> i'm still on hardy :P
[23:08] <Jazzva> (and seems like i'm gonna stay on it for a while :(. because of projects for school i have to write, i need it stable)
[23:08] <fta> nvidia-glx-new is gone, and the new one is buggy (of course, the transition didn't work at all, i ended-up in 800x600 vesa), now I have huge stripes on the screen when i play videos
[23:08] <fta> pulse audio is once again broken
[23:09] <fta> it plays by default on the pc speaker
[23:09] <fta> ff3 is once again fighting for the dsp
[23:10] <fta> xchat is no longer using the default browser for opening links
[23:10] <fta> i get ephy instead of ff
[23:10] <asac> yeah nvidia is busted
[23:10] <asac> fta: oh. is ephy configured as x-www-browser or gnome-www-browser ?
[23:11] <fta> lrwxrwxrwx 1 root root 23 2008-07-17 22:57 /etc/alternatives/x-www-browser -> /usr/bin/epiphany-gecko*
[23:11] <asac> see
[23:11] <asac> ;)
[23:11] <fta> lrwxrwxrwx 1 root root 23 2008-07-15 22:20 /etc/alternatives/gnome-www-browser -> /usr/bin/epiphany-gecko*
[23:12] <asac> fta: either ephy greedily set itself as new default in recent upgrades or xchat lost ability to use gnome config
[23:12] <fta> in my gnome prefs, i have ff
[23:12] <asac> yeah
[23:13] <asac> maybe there was a xchat-gnome which is now gone?
[23:13] <fta> my fonts are bad, i guess they broke fontconfig once again (the lcd filter)
[23:13] <fta> far too many problem in the last 2-3 weeks
[23:13] <fta> +s
[23:14] <fta> even my laptop is broken
[23:14] <fta> brightness now makes the desktop unusable
[23:14] <fta> damn
[23:14] <asac> yeah. i guess too few core-devs already running intrepid. most likely will change right after alpha 2
[23:16] <fta> btw, in my script, urls are aligned on firefox-extensions, no particular reason, looked nicer to me
[23:16] <fta> if upstream version is no longer there, amo changed something
[23:24] <asac> most likely
[23:34] <fta> fixed
[23:34]  * asac pull
[23:34] <asac> in devtools branch?
[23:34] <asac> or  was that about something else ;)
[23:34] <fta> not commit yet, testing
[23:34] <fta> +ted
[23:35] <asac> ah
[23:38] <fta> pushed
[23:47] <asac> fta: did nss upgrade in intrepid kick your a
[23:47] <asac> ***? :)
[23:47] <asac> just wonder because i think three days ago there was a bogus control in intrepid too
[23:48] <fta> don't think so.
[23:48] <asac> good. then the cure came in time for you ;)
[23:59] <asac> fta: Bug 220568
[23:59] <asac> is that related to your font issues?
[23:59] <fta> my whole desktop changed


[21:25] <cyberanger> I didn't ask for a wake up call, and if I had then clearly I'd have ignored it for a few days.


[00:23] <timClicks> fmarier, are you back at work?
[00:31] <fmarier> timClicks: yup
[18:45] <ibeardslee> morning
[19:00] <Atamira> mornin
[20:27] <thumper> morning
[21:21] <mwhudson> morning
[21:21] <ajmitch> morning


[06:31] -ChanServ(ChanServ@services.)- [#ubuntu-ops]  Welcome to #ubuntu-ops - Home of the operators for official K/X/Ed/Ubuntu channels. Questions, requests and complaints about Ubuntu related channels and their people can be filed here"
[06:31] -ChanServ(ChanServ@services.)- [#ubuntu]  Welcome to #ubuntu! Please read the channel topic and consider spending some time on the FAQ mentioned there
[06:31] -ChanServ(ChanServ@services.)- [#ubuntu-server]  Ubuntu Server Discussions (development and support)


[00:43] <thomi> cjwatson: wgrant, blr: For your consideration, when you have time: https://code.launchpad.net/~thomir/launchpad/devel-set-content-type/+merge/248207
[19:59] <cjwatson> thomi: Morning.  Do you need help landing your set-content-type branch?
[21:08] <thomi> cjwatson: hi - wgrant approved it. I was going to ask - what's the process here? Do I need 2 reviews or something?
[21:44] <cjwatson> thomi: No, one is fine.  (That was true even when there were lots of developers.)
[21:44] <thomi> so, I can top-approve?
[21:45] <cjwatson> Some of https://dev.launchpad.net/PreMergeReviews and linked stuff is probably still up to date.
[21:46] <cjwatson> Right, top-approve and then I can land it for you (presumably your key isn't yet in PQM).
[21:46] <thomi> cool
[21:46] <thomi> I believe it's not
[21:46] <thomi> cjwatson: I don't have perms to top-approve :-/
[21:46] <cjwatson> OK, I've done that for you
[21:47] <thomi> thanks :D
[21:48] <cjwatson> It's on its way now.  You should shortly see it appear on http://lpbuildbot.canonical.com/waterfall, and you'll be e-mailed with the result of testing.  Please take action if it fails


[07:38] <jibel> sil2100, I'm reverting the upstart job added yesterday, I'm wondering if that's what prevent lightdm from starting
[07:39] <sil2100> jibel: looks like that's the only change we made, so ACK - but not sure why that's happening ;/
[07:39] <sil2100> jibel: on the other hand...
[07:40] <sil2100> jibel: yeah, let's do that
[07:40] <sil2100> jibel: too bad we can't really check if the new upstart job ran or not - maybe there's some error in the  config file?
[07:41] <jibel> sil2100, the job didn't even start
[07:42] <jibel> sil2100, I'll move the addgroup to the test setup and logout/in before running the tests
[07:42] <sil2100> jibel: ok, thanks
[07:43] <sil2100> jibel: btw. in this case, is there a way of getting the container of the test when it times out? Since I don't see the link to the archive
[07:45] <jibel> sil2100, the archive is here for ATI http://<IP_ADDRESS>/otto/saucy-i386-20130624-0916/archive/
[07:45] <jibel> for example the tarball for the latest platform test is http://<IP_ADDRESS>/otto/saucy-i386-20130624-0916/archive/ubuntu_13.10_saucy_salamander_alpha_i386_20130624.1372137898.otto
[07:47] <sil2100> jibel: how do I extract the link id? Since the date of the link I can guess, but then it's -0916 <- are these the hours?
[07:47] <sil2100> jibel: normally otto says at the end where to look for the container
[07:48] <jibel> sil2100, right, and that's where I found it. Which job doesn't have the link?
[07:48] <didrocks> sil2100: hours, yeah ;)
[07:49] <sil2100> jibel: http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/203/label=autopilot-ati/console <- here, but I see a mention to "Container 'saucy-i386-20130624-0916' stopped", so I guess I know what to use now ;)
[07:51] <jibel> sil2100, interesting, it looks like a bug that the link is not displayed on timeout :)
[07:53] <tsdgeos> greyback: did you have time to have some look at the LVWPH thing?
[07:56] <greyback> tsdgeos: I didn't, but I will today
[07:59] <greyback> tsdgeos: let me do a quick read to get familiar with the code, then we can chat so you can explain to me how it actually works
[07:59] <tsdgeos> oka
[08:07] <sil2100> jibel: give me a sign once it's reverted, ok? :)
[08:07] <sil2100> I'll re-run the stacks then
[08:09] <jibel> sil2100, it's reverted. I'm trying to do the same differently but currently facing gtk and gobject segfaults when the session restarts
[08:09] <sil2100> huh
[08:12] <mzanetti> katie: good morning. the lockscreen tweaks you suggested are landed
[08:13] <katie> mzanetti, good morning
[08:13] <katie> mzanetti, great news
[08:14] <sil2100> jibel: any way I can help?
[08:15] <dpm> morning mhr3, pstolowski, for the scopes tutorial, we're installing the binary on /usr/lib/x86_64-linux-gnu/unity-scope-openclipart/openclipart - that makes the tutorial a bit more complex, as we then require a build system to determine the x86_64-linux-gnu part in the path and replace it in the Exec= line of the DBUS .service file. Would it be ok to install to /usr/bin instead?
[08:15] <dpm> I'd like to make the tutorial simple, but at the same time, I'd like to make sure we install to the standard location for scopes
[08:15] <jibel> sil2100, that's fine, I'm testing a fix and should have something working within 15min
[08:16] <mhr3> dpm, once the scope loader branch lands, you'll be installing a .so, and that should definitely go somewhere in /usr/lib/...
[08:17] <mhr3> +arch_triplet of course
[08:18] <dpm> mhr3, gotcha. But as we're not yet creating a .so, I guess for the purposes of the first tutorial iteration, it should be ok to install to /usr/bin, and then update the tutorial and code when the scope loader branch lands?
[08:21] <mhr3> dpm, why complicate it later, when it can remain the same? :)
[08:21] <mhr3> ie be complicated from the start :P
[08:23] <dpm> mhr3, if I understood it correctly, the .service file will go away, so if that's the case, we won't need to do the .service.in file Exec= line replacement in the tutorial's makefile, so things should even be easier. Is this assumption correct?
[08:23] <mhr3> dpm, probably not in the first iteration, might happen later
[08:24] <mhr3> for now we'll still have the .service file even once it's a module
[08:25] <mhr3> and it'll say something like Exec=scope-dbus-runner /path/to/the.so
[08:25] <dpm> mhr3, ok, thanks, I'll bring the Exec line replacement bits back into the tutorial, then
[08:25] <mhr3> or maybe scope-dbus-runner /path/to/the.scope
[08:25] <dpm> ok, that makes it clearer, thanks!
[08:26] <mhr3> dpm, well the latter would allow you to get rid of the arch triplet
[08:26] <mhr3> as .scope files are not arch-specific
[08:28] <mhr3> although ultimately that only means that the .scope file will need to include path to the .so together with the triplet, so you just can't get rid of it :)
[08:28] <dpm> bummer
[08:29] <mhr3> well, unless you convince platform that scopes don't need to be tripeltted
[08:30] <seb128> mhr3, well, if those are not arch specific, they can go to /usr/share?
[08:30] <mhr3> fwiw compiz's plugins aren't
[08:31] <mhr3> seb128, they're native binaries
[08:31] <seb128> mhr3, binary = arch specific (e.g compiled code)?
[08:31] <nic-doffay> mzanetti, looks like the one branch didn't land.
[08:31] <nic-doffay> Reapproving now
[08:31] <jibel> sil2100, I added the notion of setup-hook to otto, place any executable in ./usr/local/share/otto/setup-hooks/ and it will be executed at the end of otto-setup
[08:31] <mzanetti> nic-doffay: wait
[08:31] <nic-doffay> Jenkins.
[08:31] <mhr3> seb128, yes
[08:31] <nic-doffay> mzanetti, ?
[08:31] <mhr3> "native binary"
[08:31] <mzanetti> nic-doffay: Saviq wanted to give it a look too
[08:31] <jibel> sil2100, I added a hook that adds ubuntu to group autopilot
[08:32] <mzanetti> nic-doffay: or which one are you talking about?
[08:32] <jibel> sil2100, you can re-run the stacks
[08:32] <sil2100> jibel: \o/ Good idea :)
[08:32] <nic-doffay> mzanetti, launcher folding.
[08:32] <sil2100> jibel: excellent! Awesomeness
[08:32] <seb128> mhr3, right, I misread your ".scope files are not arch-specific"
[08:32] <seb128> mhr3, ignore me ;-)
[08:33] <Saviq> nic-doffay, mzanetti yeah, I'll have a quick look soon
[08:38] <sil2100> jibel: seems to work! I ran the QA stack and the tests started running correctly :)
[08:40] <jibel> sil2100, great, no segfault from compiz or a libg(tk|object) ?
[08:42] <sil2100> jibel: hmmm, no segfault, but I got a UInputError('"/dev/uinput" does not exist or is not a character device file - verify that the uinput module is loaded',) again on autopilot autopilot tests, let me check the container
[08:43] <sil2100> jibel: i.e. as if the ubuntu user was not added to the autopilot group again
[08:44] <sil2100> Will know in a moment
[08:44] <nic-doffay> Saviq, I'm writing a small test to compare the TV with the current ListItems (since even I'm unfamiliar with exactly what they look like once implemented) are there any off the top of your head that you think I can just skip?
[08:44] <sil2100> jibel: although I see /var/log/upstart/otto-setup.log: I: Adding user ubuntu to group autopilot
[08:44] <nic-doffay> By TV I mean the sidebar..
[08:44] <Saviq> nic-doffay, not sure what you mean?
[08:45] <Saviq> nic-doffay, they're really completely different components, only thing to compare is the behaviour
[08:45] <Saviq> nic-doffay, which is kind of visual
[08:45] <nic-doffay> Saviq, yeah that's why I'm doing this test.
[08:45] <nic-doffay> So design can see the behaviour side by side.
[08:46] <Saviq> nic-doffay, mhm
[08:46] <sil2100> Strrrange
[08:46] <sil2100> jibel: it seems that the ubuntu user is correctly added to autopilot
[08:46] <Saviq> nic-doffay, biggest issue with the sidebar is it doesn't do mouse input (on purpose)
[08:46] <nic-doffay> Saviq, so in your opinion should just that be worked on and then shown?
[08:46] <Saviq> nic-doffay, so comparing side-by-side is gonna be difficult
[08:47] <sil2100> jibel: I'll look into why, but on your side all is ok ;) Diving in!
[08:47] <Saviq> nic-doffay, just compare what the doc describes, and the SDK ListItems
[08:47] <Saviq> nic-doffay, I don't think the UTV implementation has anything to do here - it's just something we could start working off of when we decide what needs to be worked on
[08:47] <vesar> I'm getting module "Unity.Notifications" is not installed". Any pointers what to install to  get around it?
[08:48] <Saviq> vesar, qtdeclarative5-unity-notifications-plugin
[08:48] <vesar> Saviq, thanks
[08:48] <Saviq> vesar, should have gotten installed through ./build -s, did it not?
[08:49] <jibel> sil2100, the device is probably protected by the container. It should by allowed in the config and bindmounted from the host, let me try something
[08:49] <vesar> Saviq, no it didn't for me at least. I ran rm -rf ../unity_build, ./build -s, ./build -c
[08:50] <sil2100> jibel: that makes sense and would rationally explain what's going on
[08:51] <Saviq> vesar, are you on trunk? from lp:unity/8.0?
[08:51] <vesar> Saviq, no. That is one of mzanettis launcher branches
[08:52] <dednick> Saviq: ping. would you happen to have anymore review of indicators-client branch yet?
[08:52] <Saviq> dednick, never got to it yet, but it's at the top of my TODO, so something'll be there for sure
[08:53] <dednick> Saviq: :) ok. no prob
[08:53] <Saviq> dednick, there's one thing that you replied to, though, the setSource() with properties
[08:53] <Saviq> dednick, you wrote that they're dynamic, but what's the problem there?
[08:53] <Saviq> dednick, I didn't mean that you should just write js objects {prop: "value"} in QML
[08:54] <Saviq> dednick, but export a compatible map from C++
[08:54] <Saviq> dednick, and just pass it to setSource instead of doing the thing in onLoaded
[08:55] <jibel> sil2100, http://paste.ubuntu.com/5797934/ in r226
[08:55] <jibel> applied and deployed
[08:55] <sil2100> uh :)
[08:56] <sil2100> I wonder how those tests passed in the past?
[08:58] <dednick> Saviq: ok. were you meaning doing a:
[08:58] <dednick> Loader.setSource("x.qml", { "indicatorProperties": indicatorProperties } )    OR,
[08:58] <dednick> Loader.setSource("x.qml", { "busName" : indicatorProperties["busName"]; ... })
[08:58] <dednick> excuse the bad qml.
[08:58] <sil2100> jibel: let me re-run QA then, thanks!
[08:59] <Saviq> dednick, the latter, but the { } object built in C++
[08:59] <jibel> sil2100, if it fails again, I'm out of idea :)
[08:59] <Saviq> dednick, so, Loader.setSource("x.qml", indicatorProperties), ideally
[09:01] <sil2100> jibel: ouch!
[09:01] <sil2100> http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/215/label=autopilot-ati/console
[09:01] <sil2100> jibel: 2013-06-25 09:00:39,573 ERROR Can't start lxc container
[09:02] <jibel> bah
[09:08] <dednick> Saviq: I'm not exactly sure what you mean by the c++ map. Is it a specific type of object which does the "property transfer"?
[09:09] <Cimi> mzanetti, doing your review, sorry yesterday afternoon got headache and mostly stop working...
[09:10] <Saviq> dednick, I *think* a QVariantMap should work
[09:11] <dednick> Saviq: ok. i'll give it a try
[09:12] <dednick> Saviq: i actually click what you mean now. I didnt realise you can just pass a map and it would set all the individual props for you.
[09:12] <Saviq> dednick, yeah, I felt there was some misunderstanding
[09:15] <jibel> sil2100, I re-ran QA http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/label=autopilot-ati/216/console
[09:16] <jibel> but it failed, can you check why
[09:17] <Saviq> dednick, I was trying to read through the code to find out whether it would work http://qt.gitorious.org/qt/qtdeclarative/blobs/5f1b7bf39298dafdd07e576eec2a6a367e80b264/src/quick/items/qquickloader.cpp#line463
[09:18] <Saviq> dednick, and as long as http://qt.gitorious.org/qt/qtdeclarative/blobs/5f1b7bf39298dafdd07e576eec2a6a367e80b264/src/quick/items/qquickloader.cpp#line899 can deal with it
[09:18] <Saviq> dednick, then it should
[09:18] <dednick> Saviq: yeah, i think it should be ok
[09:18] <dednick> will know in a few minutes
[09:18] <Saviq> dednick, cool, thanks
[09:22] <nic-doffay> Saviq, just added the ExpandingDropDown item to a test. Thing is it references the dropDown component which is null. Do you have an idea why this is the case?
[09:23] <Saviq> nic-doffay, it needs to talk to the Sidebar, to be able to find out how far it can / has to expand
[09:23] <Saviq> nic-doffay, actually
[09:24] <Saviq> dropDown in ExpandingDropDown is just an internal object (AbstractExpandingDropDown)
[09:24] <Saviq> nic-doffay, you need to make sure it's available, too
[09:24] <jibel> sil2100, hm, inside the container the device uinput simply doesn't exits
[09:25] <nic-doffay> Saviq, so the dropDown properties are set by the parent sidebar item?
[09:26] <nic-doffay> Because atm it has all the aliases which reference the dropDown.
[09:26] <Saviq> nic-doffay, by whatever uses ExpandingDropDown, yes
[09:27] <Saviq> nic-doffay, EDD is just a wrapper around the Abstract one
[09:27] <Saviq> nic-doffay, so it's not necessarily the sidebar, but just something that sets it up correctly
[09:27] <nic-doffay> Saviq, got it.
[09:29] <dednick> Saviq: needs to be an object :(
[09:30] <Saviq> dednick, yeah, that's what I was afraid of, we'd need to cast ourselves
[09:30] <Saviq> dednick, not worth it, probably
[09:35] <sil2100> jibel: hmm
[09:35] <sil2100> jibel: I thought that every Ubuntu system has that device, as the module should be built in?
[09:37] <greyback> tsdgeos: found 1 bug, can you check it: https://code.launchpad.net/~aacid/unity/UseC++LVWPH/+merge/168073/comments/381628
[09:37] <tsdgeos> greyback: is it the one opening the app?
[09:37] <tsdgeos> just found that myself
[09:37] <tsdgeos> ok, so no :D
[09:37] <greyback> tsdgeos: I resize the LVWPH, but it doesn't redraw
[09:38] <tsdgeos> true, that's easy to fix
[09:38] <greyback> yep, should be
[09:38]  * tsdgeos investigates the open bug he just found first
[09:38] <greyback> I'm doing more functional testing, and have read about 30% of the code so far
[09:39] <greyback> I'm gathering questions, so I'll be bothering you later
[09:42] <tsdgeos> oki
[09:43] <sil2100> jibel: actually... hmmm!
[09:46] <nic-doffay> Saviq, here's what my test looks like at the moment. I'm getting a label at the top but nothing's being appended to the dropDown.
[09:46] <nic-doffay> https://pastebin.canonical.com/93345/
[09:47] <sil2100> jibel: I'm investigating that, since maybe we shouldn't even run those tests
[09:47] <Saviq> nic-doffay, unless you have an isolated issue, I'm afraid I can't help, just dig through it - put some console.log()s in ther eto see what's happening
[09:50] <jibel> sil2100, ok, but I don't understand why this device is not there while it's on the host. what we do is pretty straightforward. it's a bindmount udev, cp the content, umount. Unless it's removed afterwards it should be there
[09:53] <sil2100> jibel: we could probably work-around it by creating the device with mknod by ourselves, but I wonder why it's not being copied
[09:53] <sil2100> jibel: since I confirmed with the guys and having /dev/uinput seems essential
[10:09] <jibel> sil2100, that's what I did to unblock the situation, now I get /var/local/autopilot/autopilot.log: UInput: UInputError('"/dev/uinput" cannot be opened for writing',)
[10:09] <jibel> pushing another fix
[10:09] <jibel> at some point we'll succeed
[10:14] <jibel> sil2100, this run should be good http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/label=autopilot-ati/222/console
[10:14] <jibel> at least it'll get rid of that uinput error
[10:15] <jibel> it's like if the udev rule from python-autopilot didn't apply actually
[10:24] <sil2100> \o/
[10:25] <sil2100> jibel: oh?
[10:25] <sil2100> Maybe because we're doing that copy of the container
[10:28] <sil2100> mlankhorst: hi!
[10:28] <sil2100> mlankhorst: do you know how the testing of the new X-stack is proceeding?
[10:29] <mlankhorst> afaik it's ready
[10:29] <sil2100> \o/
[10:30] <sil2100> seb128: ^ ? Do you know anything about that?
[10:30] <seb128> sil2100, did you read the call from testing email from mlankhorst on ubuntu-devel@?
[10:31] <sil2100> seb128: uuh, no, but let me make sure I'm on that list then? I thought I was
[10:31] <mlankhorst> but it seems people are more interested in retiring pandaboard than x-stack, so I have all the test results I need ;)
[10:31] <seb128> sil2100, https://lists.ubuntu.com/archives/ubuntu-devel/2013-June/037386.html
[10:32] <seb128> mlankhorst, well, people are more interested in making sure that the xorg upgrade doesn't break unity or Mir or slow down work from other teams by breaking the system of the engineers working there
[10:32] <mlankhorst> mir's not really affected, it is just a small patch on top of X
[10:33] <sil2100> seb128: thanks, it seems I was not subscribed to that mailing list sadly...
[10:33] <seb128> sil2100, you should subscribe ;-)
[10:33] <sil2100> seb128: I did just now ;)
[10:34] <mlankhorst> and their ddx's would need another rebuild too, but that should be about it..
[10:34] <seb128> mlankhorst, ok, let's wait to hear back from olli today and give them a few extra days of testing then we can copy the xorg update to saucy
[10:34] <sil2100> mlankhorst: so, when do you think we could get things pushed to -proposed ?
[10:35] <mlankhorst> when seb128 thinks it's ok really, I looked at the mir xorg parts before and it seems that the ddx's would just need another rebuild bump, and the xserver patch rebased :/
[10:37] <sil2100> jibel: I see that the uinput error is no more on the -ati machine - did you also do the same for -intel? Since in the latest QA test result -intel was still failing because of that
[10:37] <sil2100> jibel: thanks for dealing with this issue btw.!
[10:38] <mlankhorst> brb, food
[10:42] <jibel> sil2100, done, deployed everywhere
[10:42] <sil2100> \o/
[10:43] <sil2100> Re-running stuff then!
[10:45] <mhr3> didrocks, gentle reminder about master scopes virtual pkg :)
[10:46] <didrocks> mhr3: do you mind gently reminding me that in ~2 hours? :)
[10:46] <didrocks> I think I'll handle it then!
[10:47] <sil2100> mhr3: were you able to find out something regarding the DBus issues with unity? ;)
[10:47] <didrocks> sil2100: did you gently reminding him? :)
[10:48] <mhr3> didrocks, reminder set up ;)
[10:49] <didrocks> ;)
[10:50] <mhr3> sil2100, nope, didn't see you guys ping me about a live system that can be diagnosed
[10:51] <sil2100> Didn't know you were waiting for that! Ok, let me remind you next time we run and run into that
[10:55] <Cimi> MacSlow_, file:///home/cimi/Development/unity/8-launcher-new-folding/Shell.qml:31:1: module "Unity.Notifications" is not installed
[10:55] <Cimi>      import Unity.Notifications 1.0 as NotificationBackend
[10:55] <Cimi> MacSlow_, which is the package? :)
[10:56] <MacSlow_> Cimi, it's...
[10:56] <MacSlow_> Cimi, qtdeclarative5-unity-notifications-plugin
[10:56] <Cimi> MacSlow_, we should add to ./build -s
[10:57] <MacSlow_> Cimi, well it is part of the build-script
[10:57] <Cimi> MacSlow_, it didn't install here
[10:57] <MacSlow_> Cimi, when did you pull from trunk last time?
[10:57] <Cimi> MacSlow_, mmm I used this branch
[10:57] <Cimi> 8-launcher-new-folding
[10:57] <MacSlow> Cimi, don't know that one :)
[10:58] <sil2100> jibel: all passed \o/ Awesome!
[10:58] <sil2100> jibel: for the qa stack, re-running all the others now!
[10:58] <Cimi> in any case doesn't start here :\
[10:58] <MacSlow> Cimi, perhaps it does not have the fixes regarding the build-script
[10:58] <MacSlow> Cimi, did you install it?
[10:58] <MacSlow> Cimi, manually I mean
[10:59] <jibel> sil2100, Good news, now trying to find why the udev rule doesn't create that device.
[10:59] <Cimi> I did apt-get install
[11:00] <MacSlow> Cimi, do you have /usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Notifications.1 ?
[11:00] <MacSlow> Cimi, well path of course depends on you machine architecture
[11:01] <Cimi> I'm trying with trunk
[11:10] <Cimi> who codes in a vm?
[11:10] <Cimi> I run ./run and nothing happens
[11:10] <Cimi> oh no, it does now
[11:11]  * Cimi shuts up
[11:11] <Cimi> mzanetti, ping
[11:13] <MacSlow> Cimi, you have you dependency-issue sorted out now?
[11:13] <Cimi> MacSlow, yep
[11:13] <mzanetti> Cimi: hey!
[11:13] <Cimi> hey boss
[11:14] <mzanetti> boss? there's a misunderstanding somewhere
[11:14] <Cimi> lol
[11:14] <mzanetti> :D
[11:14] <Cimi> anyway slave
[11:14] <mzanetti> better now :D
[11:14] <Cimi> I am not sure the thin divider asset is correct
[11:14] <Cimi> is it?
[11:15] <Cimi> looks opposite to the other dividers we have, white on top and black at bottom
[11:15] <mzanetti> Cimi: wow! good catch!
[11:15]  * mzanetti fixes
[11:15] <mzanetti> Cimi: this happens because the launcher can be inverted
[11:15] <Cimi> ok
[11:16] <mzanetti> which in fact rotates the whole thing by 180 degrees and I forgot swapping the divider in that case
[11:21] <Trevinho> fginther: this should fix your issues https://code.launchpad.net/~3v1n0/bamf/ignore-autostart-desktop-files/+merge/171274
[11:22] <Trevinho> seb128: yours as well ^^ ;)
[11:22] <seb128> Trevinho, great! do you need testing for that fix?
[11:24] <Saviq> tsdgeos, mzanetti, looking at QQuickLoader::setSource() http://qt.gitorious.org/qt/qtdeclarative/blobs/5f1b7bf39298dafdd07e576eec2a6a367e80b264/src/quick/items/qquickloader.cpp#line525
[11:25] <Saviq> can you think of something we could build in C++ to pass as the second argument?
[11:25] <Saviq> other than v8::Object, that is
[11:28] <tsdgeos> Saviq: nope, why you need that?
[11:28] <Saviq> tsdgeos, we need to set some properties on the item when it's Loaded
[11:28] <Saviq> tsdgeos, but that's fine, we're just doing it in a loop
[11:28] <tsdgeos> for my LVWPH tests i needed to excercise one of those functions that took a v8thing and i ended up going the C++ -> metaCall to JS -> function
[11:28] <tsdgeos> :D
[11:28] <Saviq> was hoping there would be a better way with Loader.setSource()
[11:29] <Saviq> tsdgeos, nice...
[11:31] <sil2100> didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/fix_sdk_graphicaleffects/+merge/171276 <- quick-fix
[11:32] <didrocks> sil2100: approved, please redeploy :)
[11:32] <sil2100> didrocks: thanks :)
[11:32] <didrocks> sil2100: FYI, I'm changing the versioning scheme as per #ubuntu-release, more on that soon
[11:34] <mzanetti> Saviq: sorry. was focused on something. is the question still valid?
[11:34] <Saviq> mzanetti, if you can come up with something, sure
[11:35] <mzanetti> Saviq: I don't understand the use case yet
[11:35] <Saviq> mzanetti, you have a Loader
[11:35] <Roxastry> hello all. Who know, how set icon in system tray without save in file system form application if this icon storage in pixbuf in application.
[11:35] <Roxastry> sorry for my bad English =)
[11:35] <Saviq> mzanetti, a source url, and a set of properties to set on Loader.item when it's constructed
[11:35] <Saviq> mzanetti, that's exactly what Loader.setSource(url, properties) is for
[11:36] <mzanetti> Saviq: something like pageStack.push("MyPage.qml", {foo: "bar}) ?
[11:36] <Saviq> mzanetti, yeah
[11:36] <Saviq> mzanetti, but in our case we'd need to provide the properties map from C++
[11:36] <Saviq> mzanetti, and AFAICS that's impossible short of building a v8::Object in our C++, which I'd rather not do :)
[11:37] <Saviq> mzanetti, and we have a "workaround" by the means of a loop, so it's mostly an academic problem
[11:37] <mzanetti> Saviq: can I see the workaround?
[11:40] <Saviq> mzanetti, sure
[11:40] <Saviq> mzanetti, https://code.launchpad.net/~nick-dedekind/unity/8.indicators-client/+merge/168022/comments/377685
[11:41] <Saviq> mzanetti, line 55 of the diff mentioned
[11:42] <mzanetti> Saviq: didn't you say in C++?
[11:42] <Saviq> mzanetti, the workaround is in QML ;)
[11:43] <Saviq> mzanetti, but "indicatorProperties" come from C++
[12:20] <didrocks> mhr3: it's already on its own binary package in fact
[12:21] <didrocks> (the -common one)
[12:21] <didrocks> it just needs to provide a virtual package to be changeable I guess
[12:24] <didrocks> mhr3: so, this should be enough: https://code.launchpad.net/~didrocks/libunity/provides-untity-scopes-json-def/+merge/171288
[12:24] <didrocks> sil2100: I've deployed the new versionning scheme on all stack, but unity/head
[12:26] <didrocks> sil2100: if you want to build a new package from this stack, you'll have to redeploy it (from latest cupstream2distro-config trunk) first
[12:28] <didrocks> sil2100: ah, unity stopped, so deploying
[12:32] <jibel> sil2100, FYI the problem with uinput is that udev doesn't create input devices in the container (other input devices under /dev/input are bind mounted from the host).
[12:32] <jibel> So our workaround with mknod is good enough, I'll just move it to autopilot setup instead of otto.
[12:44] <sil2100> didrocks: ACK, thanks!
[12:45] <sil2100> jibel: excellent, thanks for the heads-up, I guess this workaround is good enough for us for now
[12:47] <sil2100> didrocks: is a re-run for every stack required, or can I publish those with the old versioning still?
[12:47] <dednick> dandrader: ping
[12:47] <dandrader> dednick, pong
[12:47] <dednick> dandrader: hey. how's the dda work going?
[12:48] <dandrader> dednick, it's done. but I can't propose it as it depends on https://code.launchpad.net/~dandrader/unity/8_dragHandle/+merge/170172
[12:48] <dandrader> which no one reviewed yet
[12:49] <dednick> dandrader: i can take a look if you want
[12:49] <dandrader> dednick, that would be great
[12:52] <mhr3> didrocks, nooooo
[12:53] <mhr3> didrocks, should have provided more details, sorry, i was talking about the home scope
[12:53] <mhr3> didrocks, there we have a bunch of .scope files, and want to split them up into a separate bin pkg
[12:54] <mhr3> didrocks, but since you already did that for the json definition as well, i think that's useful, afterall there should be different client-scopes for desktop and phone :)
[12:57] <dednick> dandrader: one quick one. there is a conflict with trunk.
[13:02] <Saviq> mzanetti, re: snapping... shouldn't the preferredHighlightBegin/End do exactly that? i.e. you need to set it to values that make sure that it's flat initially?
[13:02] <mzanetti> Saviq: yeah... but the preferredhighlight should be in the center
[13:03] <mzanetti> the design requirement is to distribute space equally at top/bottom
[13:03] <mzanetti> actually I think this is a bug in the ListView
[13:03] <Saviq> mzanetti, ah, so currentItem is always in the middle?
[13:03] <mzanetti> because if you drag it manually you can well make it stick unfolded at the end
[13:04] <mzanetti> but setting contentY does not do the trick
[13:04] <mzanetti> Saviq: yes. currentItem is in the middle - but I don't use the currentItem/Index notation here
[13:05] <mzanetti> Saviq: hmm... wait a sec... I have an idea...
[13:05] <Saviq> mzanetti, you could always try flick() - it seems to do the trick when tapping on bottom/top
[13:05] <mzanetti> Saviq: yeah... just not a fan of such stuff... feels like a bad hack. but yeah. that would be my last-resort thing I guess
[13:06] <dandrader> dednick, fixed
[13:06] <Saviq> mzanetti, perfectly agree
[13:10] <tvoss_> didrocks, ping
[13:12] <mzanetti> Saviq: found it: ListView.ApplyRange - the view attempts to maintain the highlight within the range. However, the highlight can move outside of the range at the ends of the list or due to mouse interaction.
[13:12] <Saviq> mzanetti, yup
[13:12] <mzanetti> Saviq: thats why it only works when dragging/flicking
[13:20] <fginther> sil2100, thanks for fixing the uinput permissions issue, what was the problem?
[13:22] <sil2100> fginther: hi! jibel did most of the fixing, since adding ubuntu user autopilot permissions was not enough, as it seemed that the otto container did not have /dev/uinput at all
[13:22] <mzanetti> Saviq: ok... giving up. If you don't mind I'll go with the flick() in onCompleted. seems to work prefectly fine
[13:22] <sil2100> fginther: we worked around that by creating it with mknod during otto autopilot setup
[13:22] <sil2100> And it works!
[13:23] <fginther> sil2100, that is strange. I thought uinput was one of the default udev rules. hmmm
[13:23] <sil2100> fginther: since /dev/uinput is on the machine, but gets lost during the copy
[13:23] <Saviq> mzanetti, yeah, just add a comment what it does
[13:23] <tedg> sil2100, Did the dbusmenu stuff pass last night?
[13:23] <fginther> sil2100, oh, so is that a consequence of the fs overlay?
[13:24] <sil2100> tedg: yes! I think it did, as I saw build was OK for indicators - how were you able to fix that flacky problem?
[13:24] <sil2100> fginther: most probably
[13:24] <tedg> sil2100, One of the flaky ones were timeouts, one test we decided to disable until we can figure out more info.
[13:25] <Saviq> jeez django-users... "how can I do something in a function after return"...
[13:25] <Saviq> it's like the worst place to be subscribed to
[13:26] <sil2100> tedg: that's a good choice I guess, since it wouldn't make sense to block the indicator stack just because of this one test
[13:31] <mterry> kgunn, Saviq: I have to skip standup, will fill in minutes later
[13:31] <Saviq> mterry, k
[13:32] <kgunn> mterry: later
[13:32] <Saviq> paulliu, standup
[13:33] <mterry> (i moved yesterday, am waiting for internet hookup to arrive, but it is late)
[13:42] <mzanetti> MacSlow: bottomline: sync with veebers
[13:43] <didrocks> sil2100: yes :)
[13:44] <MacSlow> mzanetti, ok... funny that there's an stand-up entry for my from yesterday although I had a day off :)
[13:44] <didrocks> mhr3: hum, that json file is used for what in the upstream side?
[13:44] <mzanetti> MacSlow: hehe
[13:44] <MacSlow> mzanetti, thanks for the heads up!
[13:44] <mzanetti> MacSlow: yeah... mostly because we were syncing with chris on autopilot and you're on that too currently
[13:44] <didrocks> tvoss_: pong
[13:45] <mmrazik> didrocks: shall we add mc-return to "trusted" users? Otherwise (unless somebody re-approves) the following will stay where it is:
[13:45] <mmrazik> https://code.launchpad.net/~ivenvd/compiz/compiz.fix_1193792/+merge/170975
[13:45] <mhr3> didrocks, to know which scopes are installed by default
[13:45] <didrocks> mhr3: oh right, then, we have the diff
[13:46] <didrocks> mmrazik: I think he can be trusted for compiz
[13:46] <didrocks> mmrazik: is it a global thing or per project?
[13:46] <MacSlow> mzanetti, ah... just saw that branch... that's my python regressions-tests put there
[13:46] <mmrazik> didrocks: its a global thing. It essentially says who is allowed to run code on the private jenkins
[13:47] <mmrazik> once there it is not a big difference against which project you create the MP
[13:47] <didrocks> mmrazik: ok, I think it's fine in that case, as long as this is not linked to merge approval rights :)
[13:47] <mzanetti> MacSlow: not sure about what branch you are talking, but yes, such a regression-tests branch has been mentioned in the meeting yesterday
[13:47] <mmrazik> didrocks: nope. You still need to be part of the right launchpad team to do that
[13:47] <didrocks> mhr3: you want one binary package per master scope file?
[13:48] <mmrazik> fginther: FYI -- I'm adding mc-return to the jenkins config as trusted
[13:48] <mmrazik> (see above)
[13:48] <mhr3> didrocks, nah, keep them all in one pkg
[13:48] <MacSlow> mzanetti, it's the notification-backend branch from the api-team, where I put my python-based regression tests... I guess they'll be used as a starting point for the autopilot-tests
[13:50] <MacSlow> mzanetti, ah... veebers is Chris from NZ
[13:51] <didrocks> mhr3: ok, then creating unity-scopes-master virtual package?
[13:51] <didrocks> mhr3: sorry, btw, but with /usr/share/unity/scopes/info.scope, shouldn't I have an info master scope?
[13:52] <mhr3> didrocks, perhaps unity-scopes-master-default ?
[13:52] <mzanetti> MacSlow: it might make sense if you just ping him in the morning when you join the channel. usually he's around for half an hour or so
[13:52] <mhr3> didrocks, cause there can be more master scopes in different pkgs
[13:53] <MacSlow> mzanetti, yeah... also just writing him an eMail.
[13:53] <mzanetti> cool
[13:53] <didrocks> mhr3: but each master scope doesn't mean we will see them in the dash, right?
[13:53] <didrocks> mhr3: I don't have an "info" icon at the bottom
[13:54] <mhr3> didrocks, no, but you have it in the Categories filter in home
[13:54] <didrocks> in my mind, there were a 1 to 1 mapping
[13:55] <mhr3> time to change your mind :)
[13:55] <didrocks> mhr3: so, it's because of no "Icon/SearchHint/ContentHint"?
[13:57] <mhr3> didrocks, we have lots of scopes, so ones that are actually visible in the dash bar is a separate setting these days
[13:57] <fginther> mmrazik, ack
[13:57] <mhr3> didrocks, (in dconf)
[13:57] <didrocks> mhr3: ah, but the choice of what to display is made within the master scope list only, right?
[13:59] <mhr3> didrocks, no, it's not limited just to master scopes, you can put "subscopes" there as well
[14:00] <didrocks> mhr3: so master scopes are just defining the categories (for deduplication) in a view (being home scope or a particular view, like the video ones)
[14:00] <didrocks> one*
[14:01] <mhr3> didrocks, yep, but all scopes expose everything that's needed for them to be displayed in the view
[14:01] <didrocks> mhr3: excellent, I think I got it then :)
[14:01] <didrocks> let me split quickly the unity-scope-home
[14:01] <didrocks> (I prefer to get it right in my mind first ;))
[14:02] <mhr3> sure, it's good when you know what you're doing :)
[14:02] <didrocks> mhr3: isn't it?
[14:14] <didrocks> mhr3: https://code.launchpad.net/~didrocks/unity-scope-home/ship-master-scopes-def/+merge/171311
[14:16] <mhr3> didrocks, shouldn't there be a hard dep?
[14:17] <mhr3> didrocks, i mean, the master scopes are now just recommended, right?
[14:17] <mhr3> i think we can easily do hard dep, if there's a virtual pkg, no?
[14:17] <didrocks> mhr3: right, with the alternative, it can be dep, but I think recommends would be more appropriate?
[14:18] <didrocks> mhr3: I don't really want to do a circular dep, so that would mean the definition won't dep on the service
[14:18] <didrocks> if you are fine with that, I can change it
[14:18] <mhr3> didrocks, hmmm, well without home scope the definitions are pretty useless
[14:19] <didrocks> mhr3: right, that's why there is the second dep
[14:19] <didrocks> mhr3: but they are not harmful either :)
[14:19] <mhr3> didrocks, the primary reason i don't like recommends is upgrades
[14:20] <didrocks> mhr3: ah, well, in that case, both will be delivered at the same time
[14:20] <mhr3> but if you tell me it's fine, i'll be fine :)
[14:20] <didrocks> mhr3: no, I can remove the deps the other way around
[14:20] <didrocks> let me push this
[14:20] <didrocks> mhr3: rev 128
[14:21] <mhr3> ok, i think i'm happy with that
[14:22] <mhr3> didrocks, thx a lot
[14:22] <didrocks> mhr3: yw ;)
[14:23] <mhr3> didrocks, btw i expected there's more magic associated with virtual pkgs... :)
[14:25] <didrocks> mhr3: there is some implicit :)
[14:26] <didrocks> mhr3: like for the iso to build, you need to have the real package first
[14:26] <didrocks> and no dep versionning on a virtual package :p
[14:34] <Saviq> dednick, you made me almost go down in the review progress with the indicators-client move :P
[14:34] <Saviq> s/down/back/
[14:34] <dednick> Saviq: :)
[15:13] <dandrader> mzanetti, ping
[15:13] <mzanetti> dandrader: pong
[15:14] <dandrader> mzanetti, is it by design that dragging the launcher beyond the middle of the screen causes it to hide itself on release?
[15:14] <mzanetti> dandrader: hmm... probably not. don't have anything that would specify that.
[15:16] <mzanetti> dandrader: well, it should do that when minimizing an app... but I know, it does it without an app too
[15:16] <mzanetti> which is probably not the really good
[15:43] <mhr3> Saviq, should be a quick one - https://code.launchpad.net/~mhr3/unity/category_content_type/+merge/171343
[15:45] <Saviq> mhr3, we're wrapping at 120 columns, can you please un-wrap line 33 of the diff?
[15:47] <mhr3> are you saying i have to resize my terminal? :-O
[15:47] <mhr3> Saviq, pushed
[15:48] <Saviq> mhr3, you need to stop living in the '80s ;P
[15:52] <mhr3> Saviq, lol, good one
[15:56] <Saviq> mhr3, I hate to be doing this to you... but we're doing 4 space indents...
[15:57] <Saviq> /we need astyle config around
[15:57] <mhr3> Saviq, eh, my bad, modelines would be nice though
[15:57] <Saviq> mhr3, indeed
[15:58] <tsdgeos> pre-commit hook, not sure if possible in bzr, gstreamer had it afair
[15:58] <tsdgeos> in git
[15:59] <Saviq> tsdgeos, not possible in bzr (unless you install it in your ~/.bzr)
[16:00] <Saviq> tsdgeos, I could think of a generic hook for your ~/.bzr that would use some config file checked into your repository
[16:00] <Saviq> tsdgeos, so possible in that sense
[16:01] <mhr3> Saviq, hope the newline between the case and the { is fine
[16:01] <tsdgeos> sure, would still need "manual intervention"
[16:01] <mhr3> Saviq, "case Foo: {" just looks wrong :P
[16:01] <tsdgeos> so people that are not "the usual hackers" still would have the problem
[16:01] <Saviq> mhr3, +1
[16:01] <seb128> tedg, mhr3: jbicha just pinged us about lp #1155968 ... is the new version fine for unity's stack?
[16:01] <seb128> or do you guys would need to port your stuff first?
[16:01] <Saviq> mhr3, we don't yet have a clear style guide in there, am trying to get to that sooner rather than later
[16:02] <tedg> seb128, They can be dual installed (I have that on my system now).  But, yes, I'd like the new version.
[16:02] <Saviq> mhr3, it's most probably gonna be Qt style, though, as it's all just Qt code, really
[16:02] <seb128> tedg, ok, thanks, I will have a look to that then
[16:02] <mhr3> Saviq, yea, whatever, it just a style... i'll get slapped for the first commit, but hopefully then i'll remember
[16:02] <Saviq> mhr3, :)
[16:04] <mhr3> Saviq, but i have no problems with it only cause it's a 20line diff commit ;P
[16:05] <Saviq> mhr3, I do feel I'd be bitten by the lack of braces around single-line case blocks
[16:05] <Saviq> mhr3, but at least in that case it dies on compilation
[16:06] <Saviq> so yeah +1
[16:07] <mhr3> Saviq, it's not common to do braces around cases, needs to be done only when you have a new variable there
[16:07] <Saviq> mhr3, right
[16:08] <Saviq> mhr3, but yeah, my point - here you can't be bitten the same as with if
[16:09] <mhr3> right, i just like switches, it's miles easier to read
[16:10] <mhr3> seb128, eh, sorry, i'm not aware of breakage that new zg would cause
[16:11] <mhr3> seb128, is it needed for something? or just jbicha wants the latest and greatest?
[16:11] <seb128> mhr3, k, let's see
[16:13] <seb128> mhr3, well, both, I had to patch e.g gedit's back to undo https://git.gnome.org/browse/gedit/commit/?id=20d860b6500e8f9a8143be4df306225e206664d6
[16:13] <seb128> mhr3, tedg seems keen to get the new version as well (I think they said the performances are improved)
[16:13] <seb128> tedg, you wanted the update for specific reason?
[16:14] <mhr3> seb128, yea, ted wanted the no-dbus db reading
[16:14] <tedg> seb128, I'd like to use it for tracking in HUD.  Not sure I'll get to the port this cycle as I'm getting bogged down with other stuff.  :-(
[16:14] <tedg> But that's why I'm interested
[16:14] <mhr3> tedg, you don't need new zg for that ;)
[16:15] <tedg> mhr3, I need it for it to be reasonably performant.  The DBus reading is why we didn't use ZG at the start.
[16:16] <mhr3> tedg, oh, i thought you just wanted the new ontology...
[16:16] <tedg> mhr3, No, that's just #defines, I can steal that easily enough :-)
[16:16] <mhr3> indeed
[16:16]  * tedg already knows of that evil <evil laugh>
[16:18] <mzanetti> Saviq: tested this, works fine: https://code.launchpad.net/~saviq/unity/8.flipped-support/+merge/171061
[16:18] <mzanetti> Saviq: want me to top-approve?
[16:19] <mzanetti> or wait a bit in the hope that the adb-over-tcp gets supported before we switch to flipped containers?
[16:19] <mzanetti> ah, screw it.
[16:19] <mzanetti> I'll top-approve
[16:26] <Saviq> mzanetti, yeah, it's ready to top-approve
[16:26] <Saviq> mzanetti, it supports both, so it's fine
[19:02] <mterry> Kaleo, heyo.  Do you know if there's an API in Qt that will expose whether the display device is on or not?  I haven't found one, but I thought I'd ask someone that knew Qt well
[19:20] <mhall119> tvoss_: loved those screenshots of other DEs on XMir
[19:21] <mhall119> tvoss_: can I safely s/Unity Next/Unity 8/ on unity.ubuntu.com?
[19:22] <mhall119> also, we have documentation up there about running tests, do we have any documentation about writing them?
[19:23] <tvoss_> mhall119, glad you liked them, the replace should be fine! kgunn, any objections?
[19:24] <kgunn> mhall119: go for it
[19:26] <tvoss_> mhall119, blender works, too :) but need to take a video, screenshot is a bit boring in this case
[19:29] <mhall119> tvoss_: kgunn: on http://unity.ubuntu.com/getinvolved/development/unitynext/ under "Build dependencies" it says that build -s will:
[19:29] <mhall119> Build and install lp:libunity/phablet, lp:unity/phablet-mods, lp:hud/phablet and lp:unity-lens-people locally
[19:29] <mhall119> are those project branches still correct?
[19:31] <kgunn> mhall119: i was just looking this over
[19:31] <kgunn> i don't think they are right anymore...
[19:35] <dandrader> mhall119, check the latest state of the build script. it has changed quite a bit overtime.
[19:36] <dandrader> mhall119, If I'm not mistaken it also works only in saucy now
[19:36] <kgunn> dandrader: yep...
[19:36] <kgunn> i was actually changing the wiki atm
[19:37] <kgunn> but then feeling lost....as i think lots of stuff has changed
[19:37] <kgunn> mhall119: sorry...just realized you're editing too...i just bailed out
[19:38] <mhall119> kgunn: let me save my edits, then you can jump in
[19:38] <mhall119> kgunn: I'm only editing the WP page, not the wiki
[19:38] <kgunn> mzanetti: do you have a quick decoder ring for the ./run options ? wrt lockscreen (e.g. if set...is there a default pin & passphrase)
[19:38] <kgunn> and how to set lock (on the desktop)
[19:39] <kgunn> mhall119: that's what i meant...i was in WP
[19:43] <mhall119> kgunn: okay, I'm done now, you can go in and make any changes you need
[19:49] <mterry> kgunn, pin is 1234
[19:50] <mterry> kgunn, password is password I believe
[19:50] <kgunn> mterry: ta
[19:55] <kgunn> mterry: are you able to run on desktop (e.g. ./run)
[19:55] <kgunn> ?
[19:56] <mterry> kgunn, you need -f for that
[19:56] <kgunn> mterry: actually same result
[19:57] <mterry> kgunn, what's the result?
[19:57] <kgunn> unless you tell me i screwed up by trying to run w/o -f one time
[19:57] <mterry> no
[19:57] <kgunn> mterry: it complains about unity.notifications not installed (shell.qml:31:1)
[19:58] <mterry> kgunn, oh yeah, that's new.  I got that last Friday when I was playing with trunk.  I didn't investigate, since it wasn't blocking me, but I thought it was unusual
[19:58] <kgunn> mterry: so did the shell window actually launch for you ? (i get nothing)
[19:59] <mterry> Saviq, mzanetti : do you know what package Unity.Notifications is in?  Seems to be missing from ./build -s run because ./run -f complains about missing Unity.Notifications.  ^
[19:59] <mterry> kgunn, no
[20:00] <mterry> kgunn, I also get nothing, just the error about notifications
[20:00] <mterry> MacSlow wrote the notification stuff, but he's not on here now
[20:06] <kgunn> mterry: not sure why it failed....weird....just manually did a apt-get install of unity-notifications-impl-1 (per the ./build script...) and it worked
[20:06] <kgunn> i now see a shell
[20:08] <mterry> kgunn, aw awesome
[20:09] <mterry> I guess I need to do that too
[20:20] <kgunn> mterry: ah-ha...because its not really "unity-notifications-impl-1"...its "qtdeclarative5-unity-notifications-plugin"
[20:21] <dandrader> the missing unity.notifications was added to the "build --setup" script on revision 36
[20:21] <dandrader> kgunn, mterry ^
[20:22] <mhall119> is there a reason why Search isn't enabled on the Unity 8 home lens?
[20:22] <mhall119> and a way to enable it
[20:23] <Saviq_> mhall119, because it's not the real home scope
[20:24] <Saviq_> mhall119, you could drop it from the list of mappings in DashContent.qml
[20:24] <Saviq_> mhall119, but that would probably kill your dash due to the amount of data (we're fixing that)
[20:24] <mhall119> ah, ok
[20:24] <mhall119> I'm really looking forward to using the smart scopes on my N7
[20:33] <kgunn> mterry: dandrader ....acutally, figured it out...if you have any failures from the apt-get update after the build add's ppas....then it bails out
[20:33] <kgunn> e.g. i had some armhf failures lingering in there
[20:34] <kgunn> once i cleaned that up...it installs notifications just fine
[20:36] <kgunn> dandrader: last one...what diff does  -m "no mouse touch" make...tested both, at least i can't see a real diff
[20:37] <kgunn> dandrader: actually...at least no mouse touch doesn't reveal the launcher once in the dash
[20:38] <dandrader> kgunn, if you disable the conversion of MouseEvents into TouchEvents then components that handle only touch won't work (such as DirectionalDragArea)
[20:39] <dandrader> kgunn, right not part of the edge drags is MouseArea based and part DirectionalDragArea based, so you get mixed results
[20:39] <dandrader> s/not/now
[20:39] <kgunn> dandrader: ok...is there some specific way that's useful ?
[20:40] <kgunn> like why would you ever want to use -m (sorry if its obvious)
[20:40] <dandrader> kgunn, well, if you wanna a setup that matches the device you will want to disable that conversion
[20:41] <dandrader> kgunn, but it's more of an hypothetical scenario than a real one
[20:42] <kgunn> dandrader: yeah...i guess from a perception point of view...no -m seems to work just fine (and more like i'd expect)
[22:07] <kgunn> mhall119: hey, i was getting around to looking at updating instructions....but....seems the page has gone missing
[22:07] <kgunn> http://unity.ubuntu.com/getinvolved/unitynext
[22:07] <kgunn> nvmd....
[22:07] <kgunn> i see
[22:07] <kgunn> unity8
[22:07] <kgunn> cool