[01:43] bigjools: https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.3tn7jebub5jn5mhuh5sf8acd70 [09:01] mornin' all [09:09] morning [09:19] * fwereade needs to go out for a bit and catch up with some lifey things that have taken a back seat this week [09:19] bbl [09:19] * dimitern needs to dash to the post office - back in a bit [09:52] * dimitern is back [10:47] TheMue, standup? [11:14] * dimitern lunch [12:34] * rogpeppe1 goes for lunch [12:35] i may be a little longer than usual [12:54] fwereade, I've updated my latest owner-tag cl - when you have a moment could you take another look? https://codereview.appspot.com/14699043/ [13:35] back === rogpeppe1 is now known as rogpeppe [13:38] * TheMue fights with f*cking headaches today. :/ at least his tailer looks nice so far. [13:57] fwereade: you might be interested to know that that environment in the recent thread in #juju was initially bootstrapped in May... [14:09] is 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
closed by [14:10] hazmat: i believe it is [14:11] hazmat: i think the issue is that we're trying to parse something as XML that isn't actually xml [14:11] hazmat: but i don't know much more than that [14:11] dimitern: what version do you think we should recommend that peter waller upgrade to (agents currently on 0.13.2)? [14:12] rogpeppe, thanks, found the bug report [14:12] dimitern: i'm thinking of seeing how it goes with 1.10, but i can't remember anything about the characteristics of any version [14:12] hazmat: which bug? [14:12] bug 1254401 [14:12] <_mup_> Bug #1254401: error reading from streams.canonical.com [14:13] hazmat: ah looks like a) there are no tools there and b) we don't react well to the error it supplies in that case [14:14] dimitern: i guess it must be better than 1.17! [14:16] rogpeppe, re the guy on list.. [14:16] rogpeppe, so afaics. he just needs to upgrade --version=1.14 [14:16] ? [14:16] hazmat: yeah, probably. [14:16] er, 1.14.? [14:16] hazmat: i was wondering whether 0.13->1.10->1.14 might be more likely to work [14:17] hazmat: but i'll suggest 1.14.1 [14:20] why do we have terminate-machine when every else is labeled destroy-* ? [14:21] nm.. i guess we have an alias [14:23] rogpeppe, why not the latest trunk? [14:24] dimitern: because i'm not sure that we should upgrade all that way in one step [14:24] rogpeppe, then 0.14 first, then 0.16 [14:25] dimitern: yeah [14:25] dimitern: when he verifies that his environment has come back up, i'll suggest that [14:25] rogpeppe, while checking logs, etc. to make sure all hell did not break loose [14:25] dimitern: yeah, i've been looking at his logs [14:25] dimitern: the environment was bootstrapped in may... [14:25] dimitern: which is kinda cool [14:26] rogpeppe, wow! [14:26] rogpeppe, and still working? :) [14:26] dimitern: well, no, that's the point :-) [14:26] dimitern: but was until recently [14:27] rogpeppe, i see [14:55] rogpeppe, btw do you still test/use juju with pre-release go versions? [14:55] hazmat: yeah [14:56] hazmat: currently i'm using go1.2rc2 [14:57] dimitern, 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] i think we changed the look up like 3 times from 0.13 to 0.16 [14:58] maybe just twice. [15:02] hazmat, yes, true [15:03] hazmat, perhaps digging through the old release notes on the mailing list might provide some clues for possible issues that might happen between upgrades [16:40] does 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.16 [16:40] i'm looking for 1.12 or 1.14 download [16:41] rogpeppe: I've always just grabbed 'em from s3 [16:41] mgz: is the juju client command there too? [16:41] ah, good point. [16:49] are there any juju builds which have a working manual provider? [16:50] hmm, dammit [17:07] can anyone verify if the download link on this page works for them? https://launchpad.net/juju-core/+milestone/1.10.0 [17:07] (the .tag.gz file) [17:07] tar.gz [17:07] i just get an empty file [17:07] this is most frustrating [17:08] surely we can resurrect *some* earlier juju client? [17:08] rogpeppe checking [17:08] yup there is stuff in it [17:08] want me to re-up it somewhere? [17:09] rogpeppe see pm [18:34] right, i'm done for the day. [18:34] happy weekends all [19:21] rogpeppe, the only real archive is the various forms of stream data [19:22] it would be so much easier if we could bypass all the simplestream cruft, and just give it a tools tarball [19:25] filed bug 1256413 wrt [19:25] <_mup_> Bug #1256413: provide an option when upgrading or bootstraping to bypass simplestreams cruft and just use a given tarball [19:28] did someone wipe the old s3 bucket?