I think the remaining scenario is (b) (look up in the bug description), and (c) is just a wildcard scenario ("anything else I didn't think of").
For (b), I think the more likely case would be another base-files SRU without the fix from this bug here, and where the user would have: - base-files installed - motd-news-config NOT installed - ubuntu-server NOT installed In that scenario, the base-files postinst would create /etc/default /motd-news.wasremoved, with the consequence that a follow-up install of ubuntu-server/motd-news-config would install the motd-news config with ENABLED=0 instead of ENABLED=1. It's also possible the above would happen on a release upgrade, if only base-files is installed to begin with. That would ugrade base-files to the version in the next release, effectively behaving like just a base- files upgrade, and create the .wasremoved file as well. ** Changed in: base-files (Ubuntu Xenial) Status: Incomplete => In Progress ** Changed in: base-files (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: base-files (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895302 Title: groovy debootstrap leaves /e/d/motd-news.wasremoved around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1895302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs