so in detail this means the following:

If a nodump is found during the parser cleanup phase, cmpro checks:
- does a good dump for this exists within the current parent/clone relationship
- if yes, mark the nodump as gooddump, take size, crc32/sha1/md5 values from the found good one

This functionality is in since years, however with one of the last nodump updates it was partly disabled.

Optionally a prompt may appear asking the user if he actually agrees to this replacement.

If the nodump gets fixed, you won't see a 'can't merge x to y due to equal names/different hash' prompt for the set in question. If the user doesn't agree to the nodump fix, it will appear.



Roman Scherzer