Re: stable libc6-dev update

[Richard Kettlewell <rjk@greenend.org.uk>]

Matt Zimmerman writes:
> Scary.  Does the second one (9ffd0b4c6a15f0cc0f95bcb895f2685b)
> unpack correctly (dpkg-deb --extract libc6-dev_2.1.3-20_i386.deb
> tempdir)?  That should be save to try, and may detect whether the
> archive is corrupt.

    lyonesse$ dpkg-deb --extract libc6-dev_2.1.3-20_i386.deb.BAD tempdir
    tar: Unexpected EOF in archive
    tar: Unexpected EOF in archive
    tar: Error is not recoverable: exiting now
    dpkg-deb: subprocess tar returned error exit status 2
    lyonesse$ 

So... probably nothing more sinister than random data corruption.

Thanks to everyone who checked this was just a local phenomenon.

Brett Cundal writes:
> Maybe this ISP is having fun passively r00ting Debian boxes? :)

I think libc6 would be a better choice of package for that than
libc6-dev.

ttfn/rjk