Imagine a package shipping config file with contents "foo: true; bar: false". You might put the md5 of that in the ucf history, so that packaging that later changes to "foo: true; bar: true" knows that if the user has anything other than "foo: true; bar: false" then it is a customisation that should be preserved.
However, if packaging has iterated between all four possibilities, then list of all possible hashes defeats the purpose. Packaging will believe that whatever the user changed, it isn't a customisation because it was shipped previously by the packaging. Customisations will therefore get lost, contrary to our intention. Therefore, it follows that the list of hashes shipped should be minimally what packaging did actually previously ship; anything more unnecessarily increases the risk of a collision with a user customisation. Since we don't support upgrade leaps beyond LTS-to-LTS, historical hashes can therefore be dropped to keep this minimal. 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. I did ask on IRC how to reproduce the hashes, and Balint pointed out that an explanation exists in README.source. Sorry I didn't see this before - the explanation is in Hirsute but not in this SRU upload. I think this reference to that from this bug comment is sufficient for reproducibility. Perhaps I'm completely wrong here, in which case I'd appreciate a correction. Otherwise, please adjust the upload to minimally fix the specific issue here by only including the required hashes. I also suggest rethinking the Hirsute upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915547 Title: Users are prompted by ucf on upgrade from Trusty to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
