Ubuntu
base-files package

  1. Xenial (16.04)
  2. Bug #1895302
  3. Comment #5

Comment 5 for bug 1895302

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

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.