.. and warn when a definition does not match any known segment. When invalidating segments, if it doesn't exactly match the encoding we want, the hash will be wrong and we won't invalidate what we want (and will trigger archiving of a segment we don't want). This change allows better matching and warns in case it doesn't match.
Noticed this could potentially be a BC break for any automated uses of the command (since the user would have to add
--yes in that case) so not merging just yet.