> So, installing motd-news-config (e.g. after or independently from upgrading > base-files) should always remove /e/d/motd-news.wasremoved if it is present? > I don't think I'm seeing that though: > > root@triage-bionic+18.04:~# ll /etc/default/motd* > -rw-r--r-- 1 root root 0 Sep 17 22:26 /etc/default/motd-news.wasremoved ... (install base-files) ... > root@triage-bionic+18.04:~# !ll > ll /etc/default/motd* > -rw-r--r-- 1 root root 0 Sep 17 22:26 /etc/default/motd-news.wasremoved ... (install motd-news-config) ... > root@triage-bionic+18.04:~# apt-get install motd-news-config > Reading package lists... Done ... > root@triage-bionic+18.04:~# ll /etc/default/motd* > -rw-r--r-- 1 root root 779 Sep 18 16:57 /etc/default/motd-news > root@triage-bionic+18.04:~#
The .wasremoved file is gone, did you misread /etc/default/motd-news as /etc/default/motd-news.wasremoved?
« Back to merge proposal
> So, installing motd-news-config (e.g. after or independently from upgrading news.wasremoved if it is present? bionic+ 18.04:~ # ll /etc/default/motd* motd-news. wasremoved bionic+ 18.04:~ # !ll motd-news. wasremoved bionic+ 18.04:~ # apt-get install motd-news-config bionic+ 18.04:~ # ll /etc/default/motd* motd-news bionic+ 18.04:~ #
> base-files) should always remove /e/d/motd-
> I don't think I'm seeing that though:
>
> root@triage-
> -rw-r--r-- 1 root root 0 Sep 17 22:26 /etc/default/
...
(install base-files)
...
> root@triage-
> ll /etc/default/motd*
> -rw-r--r-- 1 root root 0 Sep 17 22:26 /etc/default/
...
(install motd-news-config)
...
> root@triage-
> Reading package lists... Done
...
> root@triage-
> -rw-r--r-- 1 root root 779 Sep 18 16:57 /etc/default/
> root@triage-
The .wasremoved file is gone, did you misread /etc/default/ motd-news as /etc/default/ motd-news. wasremoved?