About the d/changelog mention of removing .wasremoved, see it's about motd-news-config, not base-files:
- d/motd-news-config.postinst: always remove /e/d/motd-news.wasremoved
if present
I don't know if there is a way to have base-files safely remove .wasremoved if it was placed there unintentionally by the previous update. Unless I perhaps use another filename from now on (.wasremoved-new ick), and always delete the .wasremoved one, but this is getting a rabbit hole
About the d/changelog mention of removing .wasremoved, see it's about motd-news-config, not base-files:
- d/motd- news-config. postinst: always remove /e/d/motd- news.wasremoved
if present
I don't know if there is a way to have base-files safely remove .wasremoved if it was placed there unintentionally by the previous update. Unless I perhaps use another filename from now on (.wasremoved-new ick), and always delete the .wasremoved one, but this is getting a rabbit hole