On 5 August 2014 23:01, Paul Tagliamonte <[email protected]> wrote: > If it's something that's really needed, I'll update it (begrudgingly, > but happily, knowing it'll help folks out) and file an RC bug on it to > prevent testing migration (hopefully it'd be lagging behind a 10 day > migration; perhaps low urgency is good enough?) > > I'm pretty split. Thoughts, yoh, tianon?
I think the errors are serious enough and frequent enough that we should push forward with 1.1.2. Also, I've been rocking Go 1.3 + Docker on my local machine for a while and all's well, so I don't think we need to even mess around with an RC bug on it, especially since we'll just be pushing 1.2.0 so quickly afterwards unless something really serious explodes. So, libcontainer is located inside "vendor", so we can either do magic in repack to make it into a second tarball, or we can download the official tarball of libcontainer (whichever is simpler). My multi-tarball experience is currently zero, so I'm just throwing this out in the hopes that one of these two is easier than the other and we can move forward faster. :) Paul, if you can get the libcontainer stuff set up reasonably cleanly, I can do the rest and have this baby ready to upload in very short order (you know how crazy I am; let's get this bad boy pushed). ♥, - Tianon -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
