387153 - make partial updates contain checksums for all files, so that if a checksum fails, we'll roll over into a complete update

Status: RESOLVED DUPLICATE of bug 376565

(Toolkit :: Application Update, defect)

Description

[(not reading, please use [e-mail] instead)]

make partial updates contain checksums for all files, so that if a checksunm fails, we'll roll over into a complete update

this is something that rob helmer / preed / nick thomas / etc talked about a while ago, but I couldn't find a bug.

for a partial update, we currently only .patch and therefore size and checksum onlu the files we are changing.

but for the dreaded frankenfox scenario (see bug #376407 and bug #360127) if the frankenfoxed files aren't part of the partial, we won't have .patch files, and we won't check sizes or checksums.  So you could have frankenfox 2.0.0.x and be partially updated to 2.0.0.x+1.  

But it would be better to detect this, and feed you a complete update to 2.0.0.x+1

If we could generate .patch that were no-ops, and our client side update code could handle them, what about making it so our partial mar contains no-op .patch for all files that we expect to be on disk?

If the user removed something we expected to be there, or modified a file, or was in frankenfox mode, this would attempt to fix the problem by ensure a complete state on disk.

thoughts?

Comment 1

[Robert Helmer [:rhelmer]]

Dup of bug 376565?

I like the summary of this one better though :)