/srv/irclogs.ubuntu.com/2013/11/29/#juju-dev.txt

wallyworld_bigjools: https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.3tn7jebub5jn5mhuh5sf8acd7001:43
rogpeppemornin' all09:01
dimiternmorning09:09
* fwereade needs to go out for a bit and catch up with some lifey things that have taken a back seat this week09:19
fwereadebbl09:19
* dimitern needs to dash to the post office - back in a bit09:19
* dimitern is back09:52
dimiternTheMue, standup?10:47
* dimitern lunch11:14
* rogpeppe1 goes for lunch12:34
rogpeppe1i may be a little longer than usual12:35
mattywfwereade, I've updated my latest owner-tag cl - when you have a moment could you take another look? https://codereview.appspot.com/14699043/12:54
rogpeppe1back13:35
=== rogpeppe1 is now known as rogpeppe
* TheMue fights with f*cking headaches today. :/ at least his tailer looks nice so far.13:38
rogpeppefwereade: you might be interested to know that that environment in the recent thread in #juju was initially bootstrapped in May...13:57
hazmatis this a known issue.. WARNING no tools available, attempting to retrieve from https://streams.canonical.com/juju  ERROR cannot find bootstrap tools: XML syntax error on line 9: element <hr> closed by </body>14:09
rogpeppehazmat: i believe it is14:10
rogpeppehazmat: i think the issue is that we're trying to parse something as XML that isn't actually xml14:11
rogpeppehazmat: but i don't know much more than that14:11
rogpeppedimitern: what version do you think we should recommend that peter waller upgrade to (agents currently on 0.13.2)?14:11
hazmatrogpeppe, thanks, found the bug report14:12
rogpeppedimitern: i'm thinking of seeing how it goes with 1.10, but i can't remember anything about the characteristics of any version14:12
rogpeppehazmat: which bug?14:12
hazmatbug 125440114:12
_mup_Bug #1254401: error reading from streams.canonical.com <bootstrap> <juju-core:Triaged> <https://launchpad.net/bugs/1254401>14:12
rogpeppehazmat: ah looks like a) there are no tools there and b) we don't react well to the error it supplies in that case14:13
rogpeppedimitern: i guess it must be better than 1.17!14:14
hazmatrogpeppe, re the guy on list..14:16
hazmatrogpeppe, so afaics. he just needs to upgrade --version=1.1414:16
hazmat?14:16
rogpeppehazmat: yeah, probably.14:16
hazmater, 1.14.?14:16
rogpeppehazmat: i was wondering whether 0.13->1.10->1.14 might be more likely to work14:16
rogpeppehazmat: but i'll suggest 1.14.114:17
hazmatwhy do we have terminate-machine when every else is labeled destroy-* ?14:20
hazmatnm.. i guess we have an alias14:21
dimiternrogpeppe, why not the latest trunk?14:23
rogpeppedimitern: because i'm not sure that we should upgrade all that way in one step14:24
dimiternrogpeppe, then 0.14 first, then 0.1614:24
rogpeppedimitern: yeah14:25
rogpeppedimitern: when he verifies that his environment has come back up, i'll suggest that14:25
dimiternrogpeppe, while checking logs, etc. to make sure all hell did not break loose14:25
rogpeppedimitern: yeah, i've been looking at his logs14:25
rogpeppedimitern: the environment was bootstrapped in may...14:25
rogpeppedimitern: which is kinda cool14:25
dimiternrogpeppe, wow!14:26
dimiternrogpeppe, and still working? :)14:26
rogpeppedimitern: well, no, that's the point :-)14:26
rogpeppedimitern: but was until recently14:26
dimiternrogpeppe, i see14:27
hazmatrogpeppe, btw do you still test/use juju with pre-release go versions?14:55
rogpeppehazmat: yeah14:55
rogpeppehazmat: currently i'm using go1.2rc214:56
hazmatdimitern, there are numerous incompatible changes along the way to trunk in terms of tool discovery that the env agents loop on due to lack of finding on in my experience.14:57
hazmati think we changed the look up like 3 times from 0.13 to 0.1614:57
hazmatmaybe just twice.14:58
dimiternhazmat, yes, true15:02
dimiternhazmat, perhaps digging through the old release notes on the mailing list might provide some clues for possible issues that might happen between upgrades15:03
rogpeppedoes anyone know where the downloads for any of the non-dev releases are? i'm looking at https://launchpad.net/juju-core/+download and i only see dev release downloads apart from 1.1616:40
rogpeppei'm looking for 1.12 or 1.14 download16:40
mgzrogpeppe: I've always just grabbed 'em from s316:41
rogpeppemgz: is the juju client command there too?16:41
mgzah, good point.16:41
hatchare there any juju builds which have a working manual provider?16:49
rogpeppehmm, dammit16:50
rogpeppecan anyone verify if the download link on this page works for them? https://launchpad.net/juju-core/+milestone/1.10.017:07
rogpeppe(the .tag.gz file)17:07
rogpeppetar.gz17:07
rogpeppei just get an empty file17:07
rogpeppethis is most frustrating17:07
rogpeppesurely we can resurrect *some* earlier juju client?17:08
hatchrogpeppe checking17:08
hatchyup there is stuff in it17:08
hatchwant me to re-up it somewhere?17:08
hatchrogpeppe see pm17:09
rogpepperight, i'm done for the day.18:34
rogpeppehappy weekends all18:34
hazmatrogpeppe, the only real archive is the various forms of stream data19:21
hazmatit would be so much easier if we could bypass all the simplestream cruft, and just give it a tools tarball19:22
hazmatfiled bug 1256413 wrt19:25
_mup_Bug #1256413: provide an option when upgrading or bootstraping to bypass simplestreams cruft and just use a given tarball <juju-core:New> <https://launchpad.net/bugs/1256413>19:25
hazmatdid someone wipe the old s3 bucket?19:28

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