SpamapShazmat: quite common00:02
SpamapShazmat: it actually will come back.. you have to wait for whatever giant operation (probably an image upload) completes00:02
* SpamapS decides its time to call it a day.00:02
hazmatbcsaller1, is the lxc-lib branch ready to go back into review?00:26
bcsaller1hazmat: I think I can mark it again, yeah00:35
_mup_ensemble/local-ubuntu-provider r331 committed by kapil.thangavelu@canonical.com00:37
_mup_classify managed zk, add missing test package module00:37
_mup_ensemble/local-ubuntu-provider r332 committed by kapil.thangavelu@canonical.com01:17
_mup_refactor file storage out of dummy into common for lxc reuse01:17
_mup_ensemble/local-ubuntu-provider r333 committed by kapil.thangavelu@canonical.com01:18
_mup_switch lxc provider over to using providers.common.files01:18
_mup_ensemble/local-ubuntu-provider r334 committed by kapil.thangavelu@canonical.com01:38
_mup_local machine using /proc/uptime for launch time01:38
wrtpniemeyer: hiya13:59
niemeyerwrtp: Hey!13:59
fwereadeniemeyer: https://code.launchpad.net/~niemeyer/ensemble/go-final-formula-meta/+merge/7330414:43
fwereadeniemeyer: is the testrepo copied from the python one? and if so, why?14:44
niemeyerfwereade: It is.. and I don't get the question14:44
fwereadeniemeyer: there seem to be redundant formulas14:45
fwereadeniemeyer: it feels to me as if either the go and the python ones are conceptually different -- in which case we don't need the extra formulas like mysql214:45
fwereadeniemeyer: ...or fundamentally the same, in which case I feel nervous about the lack of any mechanism to keep them the same14:46
fwereadeniemeyer: does that make more sense?14:46
niemeyerfwereade: It does, thanks14:46
niemeyerfwereade: There's so such thing as "Go formula" and "Python formula"14:47
niemeyerfwereade: There is "Ensemble formula" only14:47
fwereadeniemeyer: indeed14:47
niemeyerfwereade: The repository there contains example Ensemble formulas for test purposes14:47
DavieyWhat would be a good formula to be beta 1 QA Guinea pig?  Ideally expected to work on bare metal.. OpenStack formula is too complicated for the QA team to scratch for this.14:47
niemeyerfwereade: We have two self-contained repositories.. one with a Python implementation, and one with a Go implementation14:48
fwereadeniemeyer: understood14:48
niemeyerfwereade: I'm not sure about what's your proposal.. are you suggesting we should merge both repositories in a single one?14:48
niemeyerDaviey: Hmm14:49
niemeyerSpamapS: any suggestions?14:49
fwereadeniemeyer: ...maybe -- I'm not really proposing anything so much as talking in the hope that I can feel comfortable with a verdict on the review14:51
m_3Daviey: anything will do.... mysql and mediawiki have the most history, but hadoop-master/slave are easy to install and more apropos to the openstack demo atm14:51
Davieym_3: Hmm.. mysql and mediawiki might be easier for someone that doesn't have prior experience with hadoop?14:52
niemeyerfwereade: No worries really.. I'm just explaining the problem we have14:53
niemeyerfwereade: and trying to investigate if you have anything in mind :)14:53
fwereadeniemeyer: I guess I would be happier if we had a common place for common stuff14:53
niemeyerfwereade: What's the problem you have in mind?14:54
m_3Daviey: sure... there're more moving parts with the mysql/mediawiki... hadoop has a little more of a mem requirement too14:54
Davieym_3: I'll present them as either/or then :)14:55
fwereadeniemeyer: just that someone will, sooner or later, change one but not the other, and I'm not sure what the worst possible consequences could be14:55
niemeyerDaviey, m_3: Hadoop feels sexy, if nothing else :)14:55
m_3Daviey: sure... hadoop's easy though... we have several blog posts about using it with ensemble in cloud.ubuntu.com14:55
m_3certainly has all the buzz14:55
niemeyerfwereade: That's a critical point we have to watch out for that indeed14:56
niemeyers/for that/for/14:56
Davieyniemeyer / m_3: Heh.. Ok.. Someone might want to have a chat with hggdh about QA effort ongoing. :)14:57
niemeyerfwereade: The test repository feels pretty minor, though14:57
niemeyerDaviey: Superb!14:57
niemeyerfwereade: This is a real issue across the board14:57
niemeyerfwereade: We are effectively duplicating logic14:57
fwereadeniemeyer: true, but the test repo will be the second thing I approve which could drift out of sync, and I don't want that to become a habit ;)14:57
niemeyerfwereade: I'm not sure the burden of separating out into different repositories pays off14:57
niemeyerfwereade: Given that we'll still have the burden either way14:58
niemeyerfwereade: Care from coders and reviewers is necessary14:58
niemeyerfwereade: Heh..14:58
niemeyerfwereade: Every single line in that source code can drift out of sync14:58
niemeyerfwereade: The real solution for that is to finish the port.14:59
fwereadeniemeyer: heh, yes14:59
niemeyerfwereade: After thinking some more, I also don't feel good about the suggestion of having a metadata format that is common for both14:59
niemeyerfwereade: for syncing up the schema15:00
niemeyerfwereade: Because that's _increasing_ the problem15:00
niemeyerfwereade: You're basically pushing the problem to a different level15:00
niemeyerfwereade: We'd have to develop a schema metadata format (a schema schema!)15:00
niemeyerfwereade: and a parser, etc15:00
niemeyerfwereade: and _that_ would have to stay in sync15:00
niemeyerfwereade: Doesn't feel like it'd pay off15:01
fwereadeniemeyer: well, I never proposed that :)15:01
niemeyerfwereade: I think you did?15:01
fwereadeniemeyer: not exactly15:01
fwereadeniemeyer: well, ok, I did :/ ...but I'm not convinced it actually makes the problem worse15:02
niemeyerfwereade: "A language-agnostic schema format (where we define any given schema OAOO, and load it in both Go and Python) would solve the second problem."15:02
_mup_Bug #833906: go and python schema implementations could drift out of sync <Ensemble:New> < https://launchpad.net/bugs/833906 >15:02
niemeyerfwereade: That's a schema schema15:03
fwereadeniemeyer: hmm, I wrote it badly: I mentioned that, and went on to describe something similar but less heavyweight15:03
niemeyerfwereade: The schema is in place.. formula metadata is in review15:04
niemeyerfwereade: Very small amount of code15:04
fwereadeniemeyer: just a common way of specifying tests -- ie we keep schemas native and readable, but ensure we're running the same tests for each implementation15:04
niemeyerfwereade: Diving into a significantly more complex implementation in *both* languages to solve a drift-away problem feels like going into the opposite direction15:05
fwereadeniemeyer: I don't believe that what we have is unworkable, otherwise I'd be making a lot more noise about it15:05
fwereadeniemeyer: but I'm fretting that the amount of things we need to remember to keep in sync will grow and grow15:06
niemeyerfwereade: Again, the way to avoid that is to not have duplication15:06
niemeyerfwereade: You seem to be worried about the metadata, but that's the simplest case15:06
niemeyerfwereade: Just cp -a solves it..  the real problem is in logic15:06
niemeyerfwereade: I'm also concerned for sure, but I'm more concerned about logic and thinking about approaches to solve that15:07
fwereadeniemeyer: I'm worried about the duplication, and the metadata is what set me off :)15:07
niemeyerfwereade: That's what I just said I think15:08
niemeyerfwereade: I want help on that.. how can we avoid duplication of _logic_15:08
fwereadeniemeyer: clearly we need a third language, which will generate both go and python for us15:09
* fwereade ducks15:09
niemeyerfwereade: The interesting thing is that this is exactly what the bug above is about ;-)15:09
fwereadeniemeyer: kind of, I don't think I've expressed myself very effectively there, I might have another go at it in a little while15:10
fwereadeniemeyer: anyway, thanks for the discussion, my nerves are soothed ;)15:10
niemeyerfwereade: :-)15:11
niemeyerfwereade: Mine are not.. I'm still concerned about duplication15:11
niemeyerfwereade: I just don't see a big deal in test data.. this can easily be copied15:12
fwereadeniemeyer: I'm still worried about that, but I'm reassured that you are too15:12
niemeyerfwereade: I've been thinking about potential ways to speed up a migration 15:12
niemeyerfwereade: The real solution would really be to finish the port15:13
niemeyerfwereade: We can have intermediate wins, though15:13
niemeyerfwereade: and port bits in a way we can kill the other side15:14
niemeyerfwereade: I have also been thinking about the possibility of _integrating_ both ports (!)15:14
niemeyerfwereade: There may be a way to do it nicely15:14
niemeyerfwereade: and I want to talk to you about that at some point.. I know you've made some very interesting work on that area before15:15
fwereadeniemeyer: hmm, that does sound interesting actually15:15
hazmatgopython ?15:15
niemeyerhazmat: Yep :)15:15
niemeyerfwereade, hazmat: http://labix.org/lunatic-python15:15
fwereadeniemeyer: nice :D15:16
niemeyerI'm still not entirely sure about it, since it might get so involved that simply porting things over could be easier/faster/simpler15:16
niemeyerBut, it's an idea..15:17
fwereadeniemeyer: > =python.eval("lua.eval('python.eval(\"lua.eval(\\'t\\')\")')")15:18
fwereadeniemeyer: you're clearly insane :)15:18
niemeyerfwereade: Yeah, it's sick, I know :-)15:18
fwereadeniemeyer: (but in a good way ;))15:18
SpamapSniemeyer: re suggestions for a formula.. I'm particularly fond of /usr/share/principia/tests/mediawiki.sh from principia-tools. :)15:23
niemeyerSpamapS: Sounds good15:23
SpamapSfor bare metal that might be too many machines tho15:25
SpamapSDaviey: re QA effort.. I've been writing automted tests for the wordpress/mysql example on EC2 and working on the mediawiki example as well. Maybe hggdb can use my scripts?15:28
SpamapShggdh even :-P15:28
DavieySpamapS: -> #ubuntu-testing ?15:29
SpamapSMan.. I gotta /part some channels and close some query windows.. I'm at 106 open.15:29
Daviey106.. is that all? :)15:31
_mup_Bug #837476 was filed: python2.6: /usr/lib/pymodules/python2.6/ensemble/providers/ec2/files.py:8: DeprecationWarning: the sha module is deprecated <Ensemble:New> < https://launchpad.net/bugs/837476 >15:33
_mup_ensemble/local-ubuntu-provider r335 committed by kapil.thangavelu@canonical.com15:52
_mup_pull ability to use release tarballs and src builds of zk from tests/common.py15:52
=== daker_ is now known as daker
hazmatSpamapS, interesting it doesn't do the same under 2.715:55
SpamapShazmat: yep totally weird16:02
SpamapShazmat: further, python2.6 can't run the test suite.16:02
SpamapSTho I'm pretty sure thats my fault ;)16:04
hazmatSpamapS, easy enough to fix though16:04
niemeyerLunch time..16:06
=== daker is now known as daker_
_mup_ensemble/local-ubuntu-provider r336 committed by kapil.thangavelu@canonical.com16:15
_mup_switch test runner to using lib/zookeeper16:15
SpamapSFAILED (failures=5, errors=8, successes=1417)16:16
SpamapSClearly we haven't been running the test suite against python 2.616:16
m_3SpamapS: we mentioned the other day freezing ensemble at something like 305 for oneiric?16:18
m_3there're changes in 326 that/re critical for config.yaml16:19
SpamapS306 is the version in Oneiric16:19
m_3can we make an exception?16:20
SpamapSIf it fixes a critical bug I can either cherry pick it in or go ahead and do a FFE16:20
m_3either cherr16:20
m_3it's pretty important... config.yaml defaults aren't picked up until then16:20
SpamapSgot a bug reference I can mark it as affecting the package (helps build the case for the FFE)16:20
m_3so every formula that has a config.yaml requires you to pass a --config16:20
SpamapSnot that we have to build a massive case16:20
SpamapSits universe and unseeded.. so there's really no reason for people to complain16:21
SpamapSm_3: just give me the bug # :)16:21
m_3ok, lemme find it... thanks!16:21
SpamapSm_3: you can mark it as affecting the package too, I think.16:21
m_3SpamapS: #82815216:24
_mup_Bug #828152: default formula config values not available to hooks <Ensemble:Fix Released by bcsaller> < https://launchpad.net/bugs/828152 >16:24
SpamapSm_3: yeah try clicking "Also affects distribution"16:26
m_3I think I did16:26
m_3ubuntu ensemble16:26
m_3should I 'target to a milestone' too?16:27
SpamapSm_3: cool thanks16:44
jcastrojamespage: aha! So it wasn't exposing the port? :)17:07
jamespagewell it was broken as well - but should be more stable now upstream have released 1.017:08
jcastrook so should I give it a shot now?17:08
jamespagesure - it should work17:08
jamespagejust finished my testing17:08
jcastrowant me to blog it?17:09
jcastroI think people would use the heck out of this17:09
SpamapSjamespage: the jenkins formula?17:35
SpamapSI added an open-port call last week.17:35
jamespagenope- the etherpad-lite one17:35
SpamapSahh cool. :)17:36
SpamapSwhats the official position on python 2.6 support?17:36
SpamapSShould I file bugs for all the broken stuff? :-P17:37
niemeyerSpamapS: https://blueprints.launchpad.net/ensemble/+spec/formula-store17:48
niemeyerSpamapS, hazmat: Both of you have demonstrated interest in blueprints several times17:49
niemeyerMy feeling is that it'll increase the workflow burden without much benefit17:49
niemeyerBut I'm willing to try it out..17:49
SpamapSI expect it will add a bit of management burden yes. The idea is to provide visibility from outside your team, so that dependent work can carry on without interruptions on either side.17:50
hazmatniemeyer, afaics the main benefit is just tracking features instead of implementation, but that's not an obvious one to the person doing the implementation, because they intuitively know it.17:51
niemeyerSpamapS: The kanban provides a lot of visibility already17:51
niemeyerSpamapS: and it's not like the major features we're working on change every day17:51
hazmatniemeyer, not at a feature level17:51
SpamapSlast I looked, there was no kanban for eureka.. but maybe I looked in the wrong place?17:51
niemeyerSpamapS: The conversation we had at the sprint is still valid17:51
hazmatSpamapS, link in channel topic17:52
SpamapSYeah this is good for right now.. it doesn't show anything that is on the "not now but later" list.. 17:52
SpamapSand it doesn't speak to dependencies.. I can't see there that LXC work has to finish before multi-unit-per-machine17:53
niemeyerSpamapS: You can find that here: https://bugs.launchpad.net/ensemble17:53
SpamapSLet me step back. The reason BP's are good is just to group efforts that don't fit into one implementation piece like a bug.17:53
SpamapSIts just an idea to help get over-arching change implemented.. not something I think is critical to the visibility of the project as a whole.17:55
SpamapSThe visibility problem that I see isn't real.. I think you're right that the kanban is "whats happening now" and the bugs list is "everything else"17:55
niemeyerSpamapS: I understand.. we went through that before.  The point I continue to make is that there's a point in the gradient of documentation boilerplate where it's easier to talk to someone on IRC.17:56
hazmati've experimented with just using tags as easy way to track larger works.. all the security impl bugs are tagged 'security'17:58
SpamapSyeah thats probably the lightest weight solution, and could even be visualized very easily17:58
niemeyerhazmat: It feels a bit off to be using tags to track chunks of work like that17:58
niemeyerhazmat: Tags should continue to be useful across the lifetime of the project17:59
niemeyerhazmat: security seems to make sense17:59
niemeyerhazmat: But e.g. "handle-ec2-firewall" is not a nice tag17:59
hazmatbut perhaps firewall does17:59
niemeyerhazmat: Sure, but you're addressing a different problem17:59
SpamapSRight, any defects in the firewall handling would be valid years later.17:59
niemeyerhazmat: You may have firewall in orchestra and in zookeeper handling of security18:00
niemeyerhazmat: It's orthogonal to the concept of features18:00
niemeyerand so is security18:00
SpamapSLikewise, if it were decided that disconnected operation is important.. one could identify the steps to do that as bugs.. and anything in the future that went against that, can also have said tag.18:00
SpamapSI agree that its orthogonal to features..18:01
SpamapSBut all the over arching changes that I can think of are actually just wide spread defects .. ;)18:01
niemeyerSpamapS: This is a good use for blueprints indeed18:01
SpamapSI think it would be worthwhile to use BP's to group bugs and show the dependencies in long term goals.18:02
SpamapSbut... not worth more than coding.. so.. I thin I'll just stop producing more bytes of text for all of you to consume.. :)18:03
* SpamapS returns to testing like its 199918:03
niemeyerSpamapS: I agree, this sounds like a sane approach, as long as we agree on what the blueprints are before starting to dump things on them18:04
niemeyerSpamapS: It's also different from the idea of blueprints I was against18:04
_mup_ensemble/lib-lxc-merge r336 committed by kapil.thangavelu@canonical.com18:21
_mup_merge lxc-lib18:21
_mup_ensemble/lib-zookeeper r337 committed by kapil.thangavelu@canonical.com18:40
_mup_extract managed zk into separate branch18:40
_mup_ensemble/lib-zookeeper r338 committed by kapil.thangavelu@canonical.com18:43
_mup_rename managed zk module to avoid name conflict18:43
_mup_Bug #837601 was filed: a zookeeper class for reuse by both local provider and tests <local-dev> <Ensemble:New for hazmat> < https://launchpad.net/bugs/837601 >18:46
_mup_ensemble/go-formulas r11 committed by gustavo@niemeyer.net19:16
_mup_Reorganized files so meta handling has its own file/tests.19:16
hazmatbcsaller1, got time for a catch-up?19:52
niemeyerhazmat, bcsaller1: Quick interface review: http://paste.ubuntu.com/678276/19:58
bcsaller1hazmat: yeah20:00
bcsaller1niemeyer: still leaving out the regex stuff (validator), is that intended?20:00
niemeyerbcsaller1: No, I was just going to figure it was missing down the road :)20:01
niemeyerThe title type is wrong as well, but otherwise the interface will look like this20:02
niemeyerI guess default should be anything rather than string20:03
niemeyerThese issues will be sorted out once I actually implement it, though20:03
hazmatniemeyer, agreed, else looks fine... is the goal to turn the config into a schema?20:04
hazmatfor validation?20:04
bcsaller1hazmat: a schema is already used for that 20:04
niemeyerhazmat: It is.. will work the same way as the Python side in that regard20:04
niemeyerhazmat: Well.. maybe, I guess what you say may be interpreted in a different way20:04
niemeyerhazmat: We have actual validator functions to validate the input against the config schema20:04
niemeyerhazmat: Against the config, sorry20:05
niemeyerhazmat: The config itself has a schema, though 20:05
hazmatright, which this is reading, i was just curious if this was going to use a separate mechanism to validate values then the go schema work already done20:05
niemeyerhazmat: So there are two levels.. config has a format and a schema to validate it.. the validated config *value* is used to validate the user input using validator functions20:05
niemeyerhazmat: That's how it works in Python, at least..20:06
niemeyerhazmat: What you say makes me curious though..20:06
niemeyerhazmat: Maybe we can use the schema to validate the input too20:06
hazmatniemeyer, indeed, but config is a schema, used to validate the user input20:06
niemeyerhazmat: Right20:06
niemeyerhazmat: It's not how it works today, but I'll see if that may simplify things as I write tests20:07
_mup_ensemble/go-formulas r12 committed by gustavo@niemeyer.net20:07
_mup_Got config support skeleton in place, and a failing test.20:07
hazmatbcsaller1, phone work for you?20:07
bcsaller1its fine, I'm on skype too20:07
robbiewbcsaller1: cool if we push our call back to the top of the hour?20:12
bcsaller1robbiew: was on the phone, anytime is fine20:29
_mup_ensemble/lib-files r339 committed by kapil.thangavelu@canonical.com21:00
_mup_extraact file storange into providers.common for use by local and dummy providers.21:00
_mup_Bug #837692 was filed: A common provider file storage for local and dummy providers <local-dev> <Ensemble:In Progress by hazmat> < https://launchpad.net/bugs/837692 >21:06
_mup_ensemble/local-machine r340 committed by kapil.thangavelu@canonical.com21:10
_mup_extract local machine into separate branch..21:10
niemeyer>>> sio.truncate()21:17
niemeyer>>> sio.getvalue()21:17
niemeyerThis is a pretty weird behavior in StringIO21:17
niemeyerAh, I misunderstand the interface21:18
niemeyertruncate(0) is what I'm looking for21:18
_mup_ensemble/no-regex-option r336 committed by gustavo@niemeyer.net21:25
_mup_Some consistency clean up in the config handling:21:25
_mup_- Removed regex type. It's uneven with the other types (the value of a21:25
_mup_  regex option is not a regex), and it's binding the generic formula21:25
_mup_  definition to a specific language.21:25
_mup_- Renamed 'str' type to 'string'. There's no value in saving the 3 chars21:25
_mup_  when we have e.g. 'float' already in the same context, and 'string'21:25
_mup_  is actually readable while 'str' is not.21:25
_mup_- Introduced backward compatibility handling for 'str' so that it21:25
_mup_  continues to work, but the user is warned about the fact that it's21:25
_mup_  obsolete so that we can pester authors to rename it timely before it's21:25
_mup_  too late and we can't go back. Tested this appropriately.21:25
_mup_Bug #837708 was filed: 'str' in config.yaml should be renamed to 'string' <Ensemble:New> < https://launchpad.net/bugs/837708 >21:30
_mup_Bug #837710 was filed: regex type should be dropped <Ensemble:In Progress by niemeyer> < https://launchpad.net/bugs/837710 >21:33
_mup_ensemble/no-regex-option r337 committed by gustavo@niemeyer.net21:38
_mup_Fixed examples.21:38
ameetpDoes anyone know if this tutorial is still valid?  https://ensemble.ubuntu.com/docs/user-tutorial.html21:39
ameetpI see the instances in my AWS console, but the relation never occurs.  well at least from what I see (rather don't see) in the debug logs21:39
niemeyerameetp: It should be valid, yeah21:41
niemeyerameetp: Note that the debug-log has to be started upfront21:41
ameetpniemeyer, yes, I started the logs in-line with the tutorial.  I don't see any relevant output21:44
niemeyerameetp: Cna you please paste it somewhere?21:44
ameetpniemeyer, https://pastebin.canonical.com/51984/21:46
hazmatameetp, you started the debug-log before you launched the machines?21:47
niemeyerameetp: That's pretty strange.. it's a completely empty log21:47
hazmator before adding the relation?21:47
niemeyerhazmat: Just asked that21:47
ameetpniemeyer, I was hoping to at least see 'Machine:1: ensemble.agents.machine DEBUG: Downloading formula' when I ran 'ensemble deploy --repository=examples mysql'21:48
niemeyerameetp: Yeah, it's quite weird.. it should definitely be showing that21:48
niemeyerameetp: Unless you deploying and then started the command21:48
* hazmat heads out to dinner, bbiab21:49
ameetpniemeyer, no.  I started the command after doing 'ensemble bootstrap' in another console21:49
niemeyerameetp: Ok.. then you kept the command running, and did something else in a different terminal?21:50
ameetpniemeyer, correct21:50
niemeyerameetp: What happens if you deploy mysql again?21:51
niemeyerameetp: Or add the relation?21:51
niemeyerhazmat: Enjoy21:51
ameetpniemeyer, https://pastebin.canonical.com/51985/21:52
niemeyerameetp: Use a different name..21:52
niemeyerensemble deploy --repository=examples mysql mysql221:52
niemeyerameetp: Second name is the service name21:53
niemeyerameetp: It defaults to the same name of the formula, if you don't provide it21:53
ameetpniemeyer, https://pastebin.canonical.com/51986/21:55
ameetpi see an new instance in AWS console as well.  21:55
niemeyerameetp: The debug-log seems completely off somehow..21:56
niemeyerameetp: Can I access the bootstrap instance to have a look?21:56
ameetpniemeyer, sure.  I can't give access to the system itself, but I can give you a file if you would like.  Or I can open a bug.  I went down this path because the relation never completes for me21:57
niemeyerameetp: What's the status?21:58
niemeyerameetp: You can open a bug, but without further information we won't be able to do much21:59
ameetpniemeyer, state always remains null.  Even after 4 hours 22:00
niemeyerameetp: :-)22:00
niemeyerameetp: It's quite fast when things are working22:00
niemeyerameetp: Debug log is the way to check this out, but it feels like things are really hosed there22:01
niemeyerameetp: Sorry about that.. can't really do much without further debugging22:01
ameetpniemeyer, is accessing the system the only way to debug?22:01
niemeyerameetp: Telepathy would be the other option, but I'm not very good with that ;-)22:02
ameetpniemeyer, :)  Okay let me see if I can get someone to recreate this 22:02
ameetpniemeyer, anyway.  Thanks for your assistance!22:03
niemeyerameetp: No problem, and sorry for the trouble22:04
_mup_Bug #837724 was filed: Relation already exists error message is bad <Ensemble:New> < https://launchpad.net/bugs/837724 >22:04
niemeyerameetp: Btw, if you manage to run this again and reproduce, please ping me22:08
ameetpniemeyer, sure22:08
_mup_ensemble/go-formulas r13 committed by gustavo@niemeyer.net22:50
_mup_Config parsing begins.22:50
niemeyerAlright.. I'm stepping off22:50
niemeyerMay be back later for other activities22:50
niemeyerCheers everyone22:50
=== adam_g is now known as foods
* niemeyer waves23:50

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!