Comment 4 for bug 1915547

> For this SRU, I'd therefore expect to see being added only the hashes involved in the specific issue being fixed - presumably only one - rather than 117. Usually the above never comes up, but I think it's relevant when there are 117, rather than the one or two entries that are common.

> Similarly, for Hirsute, I'd have expected only the hashes since Focal and onwards to be included.

Agreed Robie, I think this project needs that release-specific set of md5sums to add. Lucas will limit this SRU to just the needed md5sum for trusty -> xenial to avoid prompting.

Ultimately I'd like to track an upstream bug for the md5sum filtering per release because there are 5 different versions of 50unattended-upgrades for Debian/Raspbian/SteamOS/Devuan and the tooling to generate these md5sum files should be distribution and release aware. This is risk that we don't want to inadvertently add to this SRU.

So, let's track that upstream feature as LP:# 1917677

I think you are right that a subset of md5sums should be