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 <[email protected]> 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/1/status: bad file descriptor > Hey Yaroslav, thanks for the report. Paul and I have both been > running into this on the 1.0.0 release and have actually been > discussing pushing a new version (see bug #757023 about 1.2.0, which > was due to come out this week, but has been pushed to next week). > I've retitled this bug to reflect that it's really 1.1.2 you're > wanting (since 1.2.1 must have been a typo), Thank you Tianon for a detailed reply. Indeed 1.2.1 was a typo, or to say more -- perceptual one -- I did "see" 1.2.1 in 1.1.2 while looking at https://github.com/docker/docker/releases ;) > and adjusted the severity > to important, but I'll leave it up to Paul to decide whether we should > get 1.1.2 in first or if he wants to wait for 1.2.0 still. I'd guess > that it likely depends on how soon he gets time to help me solve bug > #757024, which is our only major holdup for having 1.0.1+ right now. I will wait then on decision on #757024 -- I was not aware of the split. 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"? -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
