I've verified the test case for an upgrade from Bionic to Cosmic.
bdmurray@clean-bionic-amd64:~$ grep vte /var/log/dist-upgrade/apt-term.log
Preparing to unpack .../143-libvte-2.91-common_0.52.2-1ubuntu1_all.deb ...
Unpacking libvte-2.91-common (0.52.2-1ubuntu1) over (0.52.2-1ubuntu1~18.04.2) ...
Preparing to unpack .../144-libvte-2.91-0_0.52.2-1ubuntu1_amd64.deb ...
Unpacking libvte-2.91-0:amd64 (0.52.2-1ubuntu1) over (0.52.2-1ubuntu1~18.04.2) ...
Preparing to unpack .../145-gir1.2-vte-2.91_0.52.2-1ubuntu1_amd64.deb ...
Unpacking gir1.2-vte-2.91:amd64 (0.52.2-1ubuntu1) over (0.52.2-1ubuntu1~18.04.2) ...
Setting up libvte-2.91-common (0.52.2-1ubuntu1) ...
Setting up libvte-2.91-0:amd64 (0.52.2-1ubuntu1) ...
Setting up gir1.2-vte-2.91:amd64 (0.52.2-1ubuntu1) ...
bdmurray@clean-bionic-amd64:~$ grep -C5 "/etc/issue" /var/log/dist-upgrade/apt-term.log
Warning: Stopping motd-news.service, but it can still be activated by:
motd-news.timer
Unpacking base-files (10.1ubuntu4) over (10.1ubuntu2) ...
Setting up base-files (10.1ubuntu4) ...
Configuration file '/etc/issue'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** issue (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/issue ...
However, given the potential for a regression some additional testing should be done.
I've verified the test case for an upgrade from Bionic to Cosmic.
bdmurray@ clean-bionic- amd64:~ $ grep vte /var/log/ dist-upgrade/ apt-term. log libvte- 2.91-common_ 0.52.2- 1ubuntu1_ all.deb ... 1ubuntu1~ 18.04.2) ... libvte- 2.91-0_ 0.52.2- 1ubuntu1_ amd64.deb ... 1ubuntu1~ 18.04.2) ... gir1.2- vte-2.91_ 0.52.2- 1ubuntu1_ amd64.deb ... vte-2.91: amd64 (0.52.2-1ubuntu1) over (0.52.2- 1ubuntu1~ 18.04.2) ... vte-2.91: amd64 (0.52.2-1ubuntu1) ...
Preparing to unpack .../143-
Unpacking libvte-2.91-common (0.52.2-1ubuntu1) over (0.52.2-
Preparing to unpack .../144-
Unpacking libvte-2.91-0:amd64 (0.52.2-1ubuntu1) over (0.52.2-
Preparing to unpack .../145-
Unpacking gir1.2-
Setting up libvte-2.91-common (0.52.2-1ubuntu1) ...
Setting up libvte-2.91-0:amd64 (0.52.2-1ubuntu1) ...
Setting up gir1.2-
bdmurray@ clean-bionic- amd64:~ $ grep -C5 "/etc/issue" /var/log/ dist-upgrade/ apt-term. log
Warning: Stopping motd-news.service, but it can still be activated by:
motd-news.timer
Unpacking base-files (10.1ubuntu4) over (10.1ubuntu2) ...
Setting up base-files (10.1ubuntu4) ...
Configuration file '/etc/issue'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** issue (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/issue ...
However, given the potential for a regression some additional testing should be done.