I can confirm that Subversion (on update) and "aptitude update" (or the underlying dpkg?) can also be left in an inconsistent/broken state when this occurs. Subversion ends up with many truncated ".entries" files leaving the working copy unusable. Aptitude/dpkg ends up with truncated versions of the files being upgraded (e.g. libpng12.so.0.27.0).
I can confirm that Subversion (on update) and "aptitude update" (or the underlying dpkg?) can also be left in an inconsistent/broken state when this occurs. Subversion ends up with many truncated ".entries" files leaving the working copy unusable. Aptitude/dpkg ends up with truncated versions of the files being upgraded (e.g. libpng12. so.0.27. 0).