On 27 June 2014 at 15:30, Michael Tautschnig <m...@debian.org> wrote: > So maybe a reasonable course of action is to leave things as they are, and > just > wait for further upstream releases? Those might well include fixes, even if > not > explicitly listing that problem. Feel free to ping me if such new releases > become available, in which case I will be happy to give that package (version) > another try.
Any chance I could convince you to give this another test now that we're several Docker releases _and_ several Go releases removed from when this bug was originally filed? :) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
