On 24 Feb 2017, at 12:25 AM, Ricardo Sateler <rsate...@gmail.com> wrote: > > Package: containerd > Version: 0.2.3~git20161117.78.03e5862~ds1-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > After upgrading containerd from 0.2.1~ds1-3 to > 0.2.3~git20161117.78.03e5862~ds1-1, docker service does not start correctly > (hangs).
> Downgrading containerd to 0.2.1-ds1-3 fixes the issue Hi Ricardo. Thanks for the bug report. I messed up by uploading some of the Docker 1.13 dependencies to unstable instead of experimental - my apologies. I've done a new upload with a Breaks line to avoid this bug occurring until I finish testing 1.13 and uploading to unstable. Regards, Tim. > > > > -- System Information: > Debian Release: 9.0 > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages containerd depends on: > ii libc6 2.24-9 > ii runc 0.1.1+dfsg1-2 > > containerd recommends no packages. > > containerd suggests no packages. > > -- no debconf information > > _______________________________________________ > Pkg-go-maintainers mailing list > pkg-go-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
signature.asc
Description: Message signed with OpenPGP using GPGMail
