/srv/irclogs.ubuntu.com/2011/09/01/#ubuntu-ensemble.txt

niemeyerMan.. the interaction between Launchpad pieces to create our workflow is never-ending00:08
hazmat:-)00:08
niemeyerSeriously.. bugs, bug tasks, milestones, projects, series, proposals, people, branches.. we use it all00:12
_mup_ensemble/managed-agent r344 committed by kapil.thangavelu@canonical.com00:15
_mup_managed machine agent00:15
SpamapSniemeyer: OOHHH YEAHHH <FLEX>00:18
niemeyerSpamapS: :)00:19
hazmatniemeyer, like i said.. i found it easier to just sync everything local.. 00:25
hazmatwhen working with any sort of report/ui on top of lp00:26
hazmatand then factoring in the speed of the average rest call.. and becomes a quick win00:26
_mup_Bug #838472 was filed: local-dev needs to manage/inspect the network <local-dev> <Ensemble:In Progress by hazmat> < https://launchpad.net/bugs/838472 >00:32
_mup_Bug #838476 was filed: local-dev provider needs a provider machine <local-dev> <Ensemble:In Progress by hazmat> < https://launchpad.net/bugs/838476 >00:37
_mup_ensemble/managed-agent r345 committed by kapil.thangavelu@canonical.com00:45
_mup_verify agent/process controls can be called multiple times00:45
niemeyerhazmat: It'd not help much I think.. even if you sync up everything locally, you still have all the linkage between the multitude of types00:46
hazmatniemeyer, you can collapse the types into app oriented docs/objs when syncing00:47
hazmats/types/links00:47
niemeyerhazmat: Sure, but you're still processing everything up00:47
niemeyerhazmat: Almost done: http://goneat.org/pkg/launchpad.net/lpad/00:48
niemeyerIt _looks_ like I just need to sort out series now00:48
_mup_Bug #838480 was filed: local-dev needs a way to manage a machine agent <Ensemble:New> < https://launchpad.net/bugs/838480 >00:48
niemeyerAnd then "push-review" is done.. :)00:49
hazmatniemeyer, nice00:54
hazmatniemeyer, re lpad.. looking much more complete00:54
niemeyerhazmat: Goes from branch to ready for review with no interaction00:55
niemeyerhazmat: Following all of our conventions00:55
niemeyerhazmat: Opens the preferred text editor for summary/desc00:55
hazmatniemeyer, awesome.. bug report + lp ?00:55
hazmater mp00:55
niemeyerhazmat: push, bug report, mp, link everything00:55
hazmatniemeyer, great00:56
hazmatniemeyer, can i get a copy i? :-)  i just did like 4 of those by hand00:56
niemeyerhazmat: Oh, most definitely.. I'm doing that for the team00:57
hazmatniemeyer, nice that you can group all the lp interactions in parallel as well, really cuts down on the command time i would guess00:57
niemeyerhazmat: Exactly.. it does quite a few things in parallel00:58
niemeyerhazmat: With nice reporting to stdout and all00:58
niemeyerhazmat: It was also a good way to push the Launchpad API a bit forward.. I'll need it to continue on the store00:58
niemeyerThat was my day today..00:59
hazmatniemeyer, yeah. that's great.. i know bcsaller was interested in using it, but needed alot of boilerplate classes to get going00:59
niemeyerhazmat: There's still a ton missing because the API is so huge, but the foundation is more laid down now01:00
hazmatniemeyer, good stuff.. i've done pretty well by local dev today.. i'm going to finish up some test for the provider, and move on to the service unit deployment with lxc tomorrow01:00
niemeyerhazmat: Wow, neat01:00
hazmati'm very excited to start using it01:00
hazmatit will actually totally justify me getting an ssd01:00
niemeyerhazmat: I noticed a lot of things flying by today01:00
niemeyerhazmat: Feels like a good wave :)01:00
niemeyerhazmat: Haha :)01:01
niemeyerhazmat: It's worth it :)01:01
hazmatniemeyer, yeah... nice to get some interrupted time.. i've been neglecting the review queue though, i'll have a look at that tomorrow morning01:01
hazmati know both you and william have some branches there that need attention01:02
niemeyerhazmat: Thanks, there are a few things we have to push forward there indeed01:03
_mup_ensemble/local-provider r345 committed by kapil.thangavelu@canonical.com01:58
_mup_wire in the managed machine agent and zk state initialization into provider bootstrap01:58
_mup_ensemble/local-provider r346 committed by kapil.thangavelu@canonical.com03:09
_mup_store zookeeper address into local provider storage, implement connect03:09
hazmati started having this problem w/ lxc03:13
hazmat ssh root@192.168.122.23503:13
hazmatroot@192.168.122.235's password: 03:13
hazmatPTY allocation request failed on channel 003:13
hazmatbcsaller, you seen that?03:14
bcsallerthats the issue with add-apt-repo asking for you to press enter I'd guess03:14
bcsallerhttp://paste.ubuntu.com/679240/03:15
bcsallerbut not sure, if you change it off the ppa (where it doesn't add the repo) does it work?03:15
hazmatbcsaller, we're using cloud init in the container now?03:15
hazmator is this something just inherent?03:15
bcsallerI don't use it for anything 03:15
hazmatthese are just on oneiric containers that used to be working for me03:15
bcsallerthis isn't a cloud-init issue, its a change in python-softwareproperties03:16
bcsalleradd-apt-repo started asking for confirmation when its got a tty on stdin03:16
bcsallermight be able to close stdin first and fake it out, not sure yet03:16
bcsalleror echo y | add-apt-repo... 03:18
bcsallersince it only checks that it gets a newline03:18
hazmatugh03:21
_mup_Bug #838565 was filed: Testing push-review <Ensemble:New> < https://launchpad.net/bugs/838565 >03:38
_mup_ensemble/local-provider r347 committed by kapil.thangavelu@canonical.com03:39
_mup_lxc utility to get a python dict mapping container name to runtime boolean status03:39
_mup_Bug #838566 was filed: push-review must be tested <Ensemble:In Progress by niemeyer> < https://launchpad.net/bugs/838566 >03:44
_mup_ensemble/local-provider r348 committed by kapil.thangavelu@canonical.com03:44
_mup_shutdown and destroy all containers when destroying environment.03:44
_mup_Bug #838568 was filed: push-review must be tested again <Ensemble:In Progress by niemeyer> < https://launchpad.net/bugs/838568 >03:45
_mup_ensemble/local-provider r349 committed by kapil.thangavelu@canonical.com03:59
_mup_check required packages installed with python-apt03:59
niemeyerAlright.. that was a loooong day..04:02
niemeyerHave a good time everybody04:02
hazmatniemeyer, indeed.. it was.. looking forward to using the new tool.. cheers04:02
niemeyerhazmat: Cheers!04:03
_mup_ensemble/local-unit-deploy r350 committed by kapil.thangavelu@canonical.com06:24
_mup_unit deployment with containers06:24
=== _mup__ is now known as _mup_
smoserSpamapS, bug 831505 should be fixed. we chose to redirect output to /dev/null rather than add '-y' as older versions of apt-add-repository dont know that flag.07:56
_mup_Bug #831505: add-apt-repository blocks cloud-init on oneiric <cloud-init (Ubuntu):Fix Released> < https://launchpad.net/bugs/831505 >07:56
=== kim0|holiday is now known as kim0
fwereadeis there any consensus solution (heh, I'd take any solution) to the problem of multiple methods with intentionally identical docstrings (eg MachineProviderBase.connect and ZookeeperConnect.run)?11:42
fwereadeor is this just another "the price is eternal vigilance" situation?11:43
hazmatg'morning12:17
hazmatfwereade, i was wondering about that12:18
hazmatfwereade, i thought about using a decorator that pulled from the base class doc string12:18
hazmatits more relevant with abstract base classes that document the protocol12:18
fwereadehazmat: I had a similar thought, but it seemed a bit icky ;)12:19
fwereadehazmat: true12:19
fwereadehazmat: but then there are cases where the base specifies (say) :class:`ProviderMachine` and the base will want to say :class:`OrchestraMachine`12:20
hazmatfwereade, i used to use zope.interfaces as a primary doc point, and let the implementation stand alone, with a see ``interface.method`` 12:20
fwereadehazmat: I couldn't see anything that would be useful in enough cases to make it feel worth bothering12:21
fwereadehazmat: mm, handy in the right context12:22
fwereadehazmat: hey, is sphinx smart enough to connect things with unique names?12:24
fwereadehazmat: so :exc:`ProviderInteractionError` rather than :exc:`ensemble.errors.ProviderInteractionError`?12:24
fwereadehazmat: feels like a bit too much to expect, but if not I have to go back and fully qualify a bunch of stuff12:25
fwereadeah well12:25
hazmatfwereade, i believe it is12:27
hazmatwe need to start genering the docs from source to find out12:27
hazmatjim mentioned he had an issue with it earlier12:27
* hazmat tries to find a place in sf to stay next week for the lxc sprint12:28
fwereadehazmat: hm, I guess I should actually try generating them :/12:32
=== Hussain is now known as Guest84341
hazmatniemeyer, morning14:03
niemeyerhazmat: Morning!14:03
fwereademorning niemeyer14:05
niemeyerfwereade: yo!14:05
niemeyerHow's everyone doing this morning?14:05
niemeyerOr rather, this X? :-)14:05
hazmatfwereade, great reviews, thanks14:06
fwereadenot too bad :) and you?14:06
hazmatniemeyer, i'm still recovering from a  late night, but early wake up14:06
fwereadehazmat: cool, glad they're helpful -- I got a bit overwhelmed by the test failures so I kinda stopped half way through14:07
hazmatfwereade, yeah those suck14:07
niemeyerhazmat: Indeed! This must be pretty early for you given how late we were yesterday14:07
hazmatfwereade, i'm looking at the control deploy failures now14:07
hazmatvery odd14:07
hazmatKeyInteruption in the middle of a test without hitting a keyboard14:07
fwereadehazmat: incidentally, should I WIP them when I mark them "needs fixing"? it seemed presumptuous, but on balance I think it's less helpful *not* to14:07
fwereadehazmat: (if that makes sense)14:08
hazmatfwereade, i think its appropriate when there's a test failure like this14:08
fwereadehazmat: cool, cheers14:08
niemeyerfwereade: Yeah, you have to take a decision there, of whether it'd be beneficial for the next reviewer to look at the changed branch, or if it doesn't make a difference14:08
hazmatfwereade, it really depends imo, if the changes for the review are substantial enough that a second reviewer would be better to have a look after the changes14:08
fwereadehazmat: sounds sensible14:09
hazmatlooks like there was something in the lxc-lib branch which has a delta to trunk regarding placement policies14:26
_mup_ensemble/lib-zookeeper r340 committed by kapil.thangavelu@canonical.com14:37
_mup_revert changes from lxc-lib to ensemble/control, resolves some deploy test failures14:37
jimbakerhazmat, trial can raise a KeyboardInterrupt in _wait, see twisted.trial.unittest: http://paste.ubuntu.com/679811/14:40
hazmatjimbaker, thanks, thats very useful to know14:49
fwereadejimbaker: I've just been poking at sphinx docstring-grabbing; hazmat mentioned you might know of some problems15:00
jimbakerfwereade, indeed i did experience problems in generating docs using autodoc15:01
jimbakerfwereade, so did you just do the basic stuff of setting up autodoc through conf.py and linking in packages to be doc'ed?15:02
fwereadejimbaker: basically yes15:02
fwereadejimbaker: what was the problem?15:03
jimbakerfwereade, when i did that, i ran into a recursion error in docutils15:03
jimbakerfwereade, i assumed it was just bad some docstring that was breaking things and just needed to be isolated15:04
fwereadejimbaker: heh, haven't hit that yet -- btw, have I missed some option that will cause it to find and document *all* the docstrings?15:07
jimbakerfwereade, you expected that? ;)15:07
fwereadejimbaker: kinda :p15:07
fwereadejimbaker: the "auto" bit of the name "autodoc" got my hopes up a bit15:08
jimbakerfwereade, in fact so did i. but the sphinx project apparently thinks this is not so useful. there is a third party script to do that which i found15:08
jimbakerfwereade, to be honest, the mechanism they do have which is to require this be done in __init__.py is not so bad15:09
fwereadejimbaker: I noticed something like that, and then I started thinking about stripping test docstrings, and then I started doing something else15:09
fwereadejimbaker: indeed, quite sensible, may as well go with that then15:09
fwereadejimbaker: and I guess I'll build after every change and hopefully spot the recursing thing that way15:10
fwereadejimbaker: cheers :)15:10
jimbakerfwereade, indeed, i think it should pop out quickly15:10
niemeyerHoly crap.. our review queue is _amazing_15:20
niemeyerI'll step out for lunch.. may be a few minutes late for our meeting15:23
robbiewfyi, tweaked https://ensemble.ubuntu.com/ a bit last night....holler if there's an issue15:31
_mup_ensemble/lib-files r341 committed by kapil.thangavelu@canonical.com15:32
_mup_remove use of file_storage.path by some tests.15:32
* niemeyer is around16:12
niemeyerrobbiew: Ohh, video16:13
niemeyerrobbiew: Great stuff, thanks man16:13
robbiewnp16:13
niemeyerbcsaller, jimbaker, fwereade, hazmat: Call time?16:14
fwereadeniemeyer: sounds goood16:15
niemeyerrobbiew: Wanna join?16:15
bcsallerniemeyer: I'm around16:15
jcastrog+? I wouldn't mind listening in if you guys have the room16:15
niemeyerjcastro: We can put a few things away to accommodate you for sure16:15
jimbakerniemeyer, cool16:16
robbiewniemeyer: invite me...I'll join later, on a call16:16
niemeyerjcastro: Not entirely sure if I did the right thing when inviting you.. I used your canonical addres16:17
niemeyers16:17
niemeyerWeird..16:18
niemeyerIt broke down16:18
jcastroodd, never seen that error before16:18
hazmatjust sent out a new invite16:19
hazmatg+ hangouts have been flakey for me on occasion16:19
bcsallermy camera isn't working, going to relog16:20
jimbakerstill waiting on a g+ hangout16:21
=== daker_ is now known as daker
=== daker is now known as daker_
hazmatthese leaking temp files and dirs are a problem19:21
hazmatseeing lots of them19:21
niemeyerjimbaker: ping19:23
niemeyerbcsaller, hazmat: I've renamed a couple of blueprints to remove the redundant "ensemble-" prefix.. feel free to change further please19:24
=== daker_ is now known as daker
jimbakerniemeyer, hi19:32
niemeyerjimbaker: Sent some private comments19:33
=== daker is now known as daker_
SpamapShttp://paste.ubuntu.com/680072/19:53
SpamapS^^ this test fails for me sometimes.. but not all the time19:53
SpamapSactually it fails every time19:54
hazmatSpamapS, interesting20:33
hazmatSpamapS, that's one of the tests that i found leaks files as well20:33
hazmatactuall a temp directory20:33
_mup_ensemble/ftests r1 committed by gustavo@niemeyer.net20:54
_mup_Bootstraped simplistic functional test suite.20:54
niemeyerjimbaker: https://launchpad.net/ensemble/ftests20:57
jimbakerniemeyer, thanks20:58
niemeyerjimbaker: mkdir ensemble-ftests; cd ensemble-ftests; bzr init-repo .; bzr branch lp:ensemble/ftests ftests20:58
niemeyerjimbaker: Different line of development20:58
niemeyerjimbaker: Branches, merge proposals, etc, all as usual..20:58
niemeyerjimbaker: http://bazaar.launchpad.net/~ensemble/ensemble/ftests/files20:59
niemeyerjimbaker: Please preserve the structure and spirit in there.. churn should continue to be a shell-script too20:59
niemeyerjimbaker: Generate the html out of the output directory.. should be trivial21:00
jimbakerniemeyer, ok, taking a look at the skeleton21:00
niemeyerjimbaker: Leave environments.yaml and AWS credentials outside of the test suite itself, for now21:01
niemeyerjimbaker: So that it works with any deployment method based on who sets it up21:01
jimbakerniemeyer, sure21:01
niemeyerjimbaker: Not sure if that'll be a good idea, but let's try it21:01
niemeyerjimbaker: The tool to generate the html can be in Python or whatever you please, for convenience21:02
niemeyerjimbaker: It'll also have to take into account different runs of the tool21:03
niemeyerjimbaker: To produce the waterfall21:03
jimbakerniemeyer, i'm certainly glad i don't have to write everything in bash21:03
niemeyerjimbaker: :-)21:03
SpamapSdevops_borat.. "If you are still do manual deployment, you need of know in devops we call it 'hand job'"21:03
jimbakerniemeyer, is it really necessary to have churn (what we discussed as the runner) be a shell script too?21:04
niemeyerjimbaker: Yes, it is, because it'll ensure you keep it simple21:05
jimbakerseems like a painful lesson in bash scripting, but ok21:06
SpamapSHmm, so.. working on bug 813112 so I can make the package builds fail on test failure..21:07
_mup_Bug #813112: test suite cannot run without an ssh key <Ensemble:New> < https://launchpad.net/bugs/813112 >21:07
niemeyerjimbaker: It's more than that.. it's a lesson in simplicity.  I don't expect you'll need much more than what's there to solve our problem.21:07
niemeyerjimbaker: If anything at all.21:07
SpamapShttp://paste.ubuntu.com/680131/21:07
jimbakerniemeyer, i'll see what it takes21:08
SpamapSThat fixes it.. 21:08
SpamapSI suppose I should just throw it in the review queue.21:08
* SpamapS waves his hands... nothing to see here21:08
jimbakerniemeyer, in particular, why are log/fatal defined in churn?21:08
niemeyerjimbaker: I don't get what you mean.. the functions seem self-obvious to me?21:09
jimbakerniemeyer, well why would you need them there? shouldn't it be the responsibility of the tests to produce output, as they do in the examples now?21:11
niemeyerjimbaker: Again, I don't understand what you mean..21:12
niemeyerjimbaker: I want to be able to type ./churn and have reasonable output presented to me21:13
niemeyerjimbaker: log is an incredibly trivial function that simply presents a message with a timestamp in it.. 21:14
niemeyerjimbaker: Why does that sound strange?21:14
jimbakerniemeyer, never mind21:15
niemeyerjimbaker: Done21:15
niemeyerI'll get some coffee21:18
hazmatniemeyer, is there a reason why the golang-weekly hasn't been updated in a month? does it depend on an upstream weekly release?21:27
hazmatyeah.. it looks like no recent weeklies21:27
niemeyerhazmat: I've been slacking21:28
niemeyerhazmat: I was just updating it _today_ though21:28
niemeyerhazmat: After lucio asked about it21:28
niemeyerhazmat: tip has been updated.. I'll poke the weekly now21:29
hazmatniemeyer, cool.. where does goinstall put files on disk for a go-lang package install?21:38
hazmatgot it /usr/lib/go/pkg21:39
niemeyerhazmat: $GOPATH, if you set it as a user21:41
niemeyerhazmat: Otherwise it'll try to put in $GOROOT21:41
hazmatniemeyer, ic, just doing the package install21:41
hazmatniemeyer, so do you manipulate GOPATH when you have multiple packages in the same source tree21:41
hazmatniemeyer, i'm trying to run the formula tests, but it won't find the schema package for example21:41
niemeyerhazmat: Hmm21:42
hazmatdo i need to goinstall the schema package? and then continually update it ?21:42
niemeyerhazmat: I may have to tweak that to work with GOPATH21:42
niemeyerhazmat: What I've been doing, and which should work, is to make install within the schema package21:42
niemeyerhazmat: The detail is that I have a local tip branch 21:42
niemeyerof go21:43
niemeyerhazmat: This should work with GOPATH as well, though21:43
niemeyerhazmat: But I'll have to fix it21:43
niemeyerhazmat: The design was made in such a way that you can goinstall straight from Launchpad21:43
niemeyerhazmat: goinstall launchad.net/ensemble/go/schema works21:43
niemeyerhazmat: and so does goinstall launchad.net/ensemble/go/formula21:44
niemeyerhazmat: the latter will automatically perform the former even21:44
hazmatniemeyer, sure.. but if i'm testing a source tree which has multiple packages, then i'll need to constantly update those21:44
niemeyerhazmat: There are just some minor inconveniences right now because $GOPATH is a recent thing and hasn't been introduced across the board in all tools, so I'll have to tweak the Makefile a bit21:45
hazmatniemeyer, cool, it would definitely be a benefit to have packages tested together from the same tree, instead of having to version manage the installed against the src tree.21:46
niemeyerhazmat: How do you mean?  As I just explained, there are some details right now, but the design is that you'll have to do nothing besides goinstalling21:46
niemeyerhazmat: I think we misunderstand each other.. they are in the same tree21:46
hazmatniemeyer, goinstalling puts files in into the $GOROOT/pkg tree.. but say i have two interdependent package changes in the same src tree, i want to run make test, and have it use the src tree for both packages, not manually update the $GOROOT/pkg beforehand21:47
niemeyerhazmat: As I explained, you should use $GOPATH, not $GOROOT, and they'll all be in $GOPATH/src, in the same tree21:48
niemeyerhazmat: goinstall will soon also figure changes in dependent packages automatically, and rebuild/reinstall21:49
niemeyerhazmat: It's flaky right now because this area is being worked on, but the plan is pretty good21:49
niemeyerhazmat: Soon we'll need no Makefile iether21:49
niemeyereither21:49
* hazmat looks up gopath21:50
hazmatinteresting, sort of like an encapsulation of virtualenv into an environment variable21:51
niemeyerhazmat: Yeah21:53
niemeyerhazmat: If you want to test the code quick & fast without worrying about anything else, you can just install Go from tip with: hg clone https://go.googlecode.com/hg go; cd go; export GOROOT=$PWD; cd src; ./make.bash21:56
niemeyerhazmat: This will mean GOROOT is writable21:57
niemeyerhazmat: and it's why it works..21:57
niemeyerhazmat: I'll sort out the Makefiles in the future, though, so that GOPATH is taken care of in the Makefiles21:57
niemeyerhazmat: Sorry for the trouble there21:57
hazmatniemeyer, no worries, thanks for the info, i'll see if i can run the tests with that.. the remote version of launchpad.net/ensemble/go/schema is more recent than the one in the branch, so it gets undefined symbols for the renames21:59
niemeyerhazmat: Hmm22:00
niemeyerhazmat: Have you noticed that schema and formula are in the same branch?22:00
hazmatniemeyer, i have22:00
hazmatniemeyer, how do you install a src package with goinstall22:01
niemeyerhazmat: Have I screwed up something then?  Any branch should be self-consistent22:01
hazmatafaics, i have to rename the directories into import paths to use GOPATH22:01
niemeyerhazmat: goinstall "server.com/import/path"22:01
niemeyerhazmat: Why?22:01
hazmatniemeyer, that installs the remote version22:01
niemeyerhazmat: Unless you have a local version22:02
hazmatniemeyer, the remote version is incompatible with one of the packages in the branch, it needs to compile against the other package in the branch22:02
hazmatniemeyer, i'm just running make test from the formulas directory22:02
hazmatniemeyer, if there's a way to install the local version of the package that would work22:03
niemeyerhazmat: I don't understand.. the remote version works with the remote version.. branches work with the content of the branch22:03
niemeyerhazmat: It's like Python22:03
niemeyerhazmat: If you have a branch, ensemble.provider works with ensemble.state of the same branch22:03
niemeyerhazmat: There's no difference there22:03
hazmatniemeyer, is there some path variable you have to define for that? .. i'm trying to run 'make test' in the formula directory22:03
niemeyerhazmat: No.. as I explained, what I do is to: cd schema; make install; cd ../formula; gotest22:04
hazmatniemeyer thanks, that's what i needed22:06
niemeyerhazmat: http://paste.ubuntu.com/680159/22:07
niemeyerhazmat: And again, this is still pretty clumsy compared to what we'll have shortly..22:08
niemeyerhazmat: Once $GOPATH and gomake come fully to life, it'll be brainless..22:09
hazmatniemeyer, indeed that will be much easier22:09
niemeyerhazmat: Just gomake inside schema will do everything22:09
hazmatniemeyer, http://paste.ubuntu.com/680163/22:09
niemeyerhazmat: Define GOROOT22:09
hazmatk22:09
niemeyerhazmat: export GOROOT=/usr/lib/go22:09
niemeyerhazmat: If you're using the package22:09
niemeyergomake would do that for you already, by the way22:10
niemeyerBut since you'll be playing with it often, it's worth putting it in the profile22:11
hazmatniemeyer, i've got the standard go variables defined pointing at the system path22:11
hazmats22:11
hazmat/usr/lib/go for goroot /usr/bin for gobin22:12
niemeyerCool22:12
hazmati've got  a previous install of the newer remote package version in goroot22:12
hazmatwhich is causing the problem22:12
niemeyerhazmat: But it was undefined in that paste, right?22:12
hazmatniemeyer, oh.. i assumed the newer version has the renames already in it.. it would have a different error regarding the package import if it wasn't installed22:14
hazmatif i remove the pkg from $GOHOME, and do the cd schema; make install; cd ../formula; gotest it fails with http://paste.ubuntu.com/680165/22:15
niemeyerhazmat: DEFINE $GOROOT!22:16
niemeyer:-)22:16
niemeyerMakefile:1: /src/Make.inc: No such file or directory22:16
niemeyerThere's a $GOROOT variable before the /src/ in that line.. which is empty!22:16
hazmathmm.. but its defined.. make test in the schema works fine22:16
niemeyerIt's not defined, no22:17
niemeyerexport GOROOT=/usr/lib/go22:17
niemeyerOr whatever it is22:17
hazmathttp://paste.ubuntu.com/680169/22:17
hazmatyeah22:17
niemeyerhazmat: It's not defined..22:17
niemeyerhazmat: That's the error you're getting22:17
niemeyerhazmat: This is the first line in the Makefile:22:18
hazmatniemeyer, that's env | grep GO in the shell. it is defined22:18
niemeyerinclude $(GOROOT)/src/Make.inc22:18
hazmatah22:18
niemeyerhazmat: Works now?22:24
niemeyerhazmat: Can't find a way to link blueprints and bugs in the API :-(22:39
hazmatniemeyer, nope.22:39
niemeyerhazmat: What's wrong now?22:39
hazmatniemeyer, same problems, if i install it complains about undefined schema.M, if i uninstall it.. it complains about it not being found22:41
niemeyerhazmat: Can you please paste the error?22:41
hazmatniemeyer, it was the sudo.. killing the env  variable i think22:43
hazmatnope.. still an error22:43
niemeyerhazmat: Same error?22:44
hazmathttp://paste.ubuntu.com/680178/22:44
niemeyerhazmat: It's the same error.. GOROOT not defined22:44
niemeyerhazmat: Use gomake.. it'll export the variable fo ryou22:44
hazmatniemeyer, sweet! that works22:45
niemeyerhazmat: Woohay22:45
* hazmat grabs some dinner22:46
hazmatniemeyer, yeah i don't see any way to attach a bug to the blueprint/spec via the api23:26
hazmatbummer23:27
niemeyerhazmat: Sadness.. let's see if the LP folks can give us a hand23:27

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