On Sat, Apr 10, 2010 at 01:15:07PM +0100, Joao Pinto wrote: > > I had a crash during a package install which resulted in multiple packages > being corrupted. > The corresponding .md5sums files where truncated to 0 bytes, this should be > reported as an error since the package files can not be verified. > During a crash I identified some packages where corrupted
This seems simple since debhelper is smart enough to not generate empty md5sums files, however when debsums generates missing md5sums files, it isn't that smart. Once debsums gets changed to stop generating empty md5sums files, it will also need new logic to check for when an md5sums file is unnecessary (so that it doesn't incorrectly complain about packages like "no md5sums for g++", which doesn't need one). It could then warn about 0 byte .md5sums files, but it would need to be smart enough about it to not complain about the empty md5sums files debsums may have created in the past.
signature.asc
Description: Digital signature
