On 20 August 2014 15:27, Adam Hunt wrote:
> What's the word on this? 1.0 is ancient, well, maybe not ancient but 1.2.1
> was released almost a month ago and 1.0.1 was released over two months ago.
1.2 is only just now in the pipeline, so I think you meant 1.1.2.
Paul, did you get a chance to rev
What's the word on this? 1.0 is ancient, well, maybe not ancient but 1.2.1
was released almost a month ago and 1.0.1 was released over two months ago.
I've been running into https://github.com/docker/docker/issues/6348 and was
hoping that 1.2.1 compiled with Go 1.3 would help out, though, seeing as
Hi.
I also bumped into a bug that should be fixed in newer docker:
https://github.com/docker/docker/issues/6345
Any news when you would update the package?
Riku
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...
On Wed, Aug 06, 2014 at 04:06:27PM -0600, Tianon Gravi wrote:
> On 5 August 2014 23:01, Paul Tagliamonte 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 (hopefu
On 5 August 2014 23:01, Paul Tagliamonte 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 i
On Wed, Aug 06, 2014 at 12:12:29AM -0400, Yaroslav Halchenko wrote:
> On Tue, 05 Aug 2014, Tianon Gravi wrote:
> > Yeah, I think that's what Paul's thinking, but let's keep pinging him
> > here with more and more emails until he does it. :)
>
> Ok... let's continue then.
>
> Paul -- have you hea
On Tue, 05 Aug 2014, Tianon Gravi wrote:
> > FWIW, if they are still so co-dependent, might be worth just to carry a
> > multi-tarball source package and build both within the same source
> > package until libcontainer would become more "independent"?
> Yeah, I think that's what Paul's thinking,
On 5 August 2014 22:06, Yaroslav Halchenko wrote:
> FWIW, if they are still so co-dependent, might be worth just to carry a
> multi-tarball source package and build both within the same source
> package until libcontainer would become more "independent"?
Yeah, I think that's what Paul's thinking,
On Tue, 05 Aug 2014, Tianon Gravi wrote:
> retitle 757183 Please package 1.1.2 upstream release
> severity 757183 important
> block 757183 by 757024
> thanks
> On 5 August 2014 20:51, Yaroslav Halchenko wrote:
> > $> docker.io run -i -t -v $PWD:/tmp/tests debian:wheezy /bin/bash
> > 2014/08/06
retitle 757183 Please package 1.1.2 upstream release
severity 757183 important
block 757183 by 757024
thanks
On 5 August 2014 20:51, Yaroslav Halchenko wrote:
> $> docker.io run -i -t -v $PWD:/tmp/tests debian:wheezy /bin/bash
> 2014/08/06 02:43:34 finalize namespace drop capabilities read /proc/
Package: docker.io
Version: 1.0.0~dfsg1-1
Severity: normal
ran into
$> docker.io run -i -t -v $PWD:/tmp/tests debian:wheezy /bin/bash
2014/08/06 02:43:34 finalize namespace drop capabilities read /proc/1/status:
bad file descriptor
googled it up to be fixed in 1.1.2:
https://github.com/docker
11 matches
Mail list logo
