2016-05-11 18:27 Christian Seiler:
On 05/11/2016 07:01 PM, Marc Haber wrote:
On Wed, 11 May 2016 17:03:05 +0200, Nicolas Dandrimont
<ol...@debian.org> wrote:
* Marc Haber <mh+debian-de...@zugschlus.de> [2016-05-11 10:47:52 +0200]:
We could have a "show-release-notes" package containing a script that
scans (pre-upgrade) the installed packages and shows all release-notes
relevant to those packages. This would need the release notes to be in
a somewhat automatically-selectable format, most easily a http-served
directory somewhere with a packagename.txt for each package that has
relevant text that went past the package maintainer and the release
team. Some thought needs to go in there for the cases where package
foo is superseded by foo2. Most easily this could be a simple symlink
in the releasenotes directory.
That really sounds like what apt-listchanges already does.
Yes.
Maybe I misremember and it was by reading the changelogs, or blog
entries or something else... but I think that I have seen such warnings
in apt-listchanges through NEWS.Debian in the past, when some Linux
kernel flavours were going to be removed or made incompatible with my
machine (related to PAE? or maybe this very issue?), and that I stopped
the upgrade and changed to the correct package for that machine.
I think that it's a good solution for cases like this. I don't know how
many people use apt-listchanges, though. (And I am not necessarily
saying that it has to be the only measure taken).
The only qualm I have with
it is that there appears to be no option to abort the install after
apt-listchanges displays the changes:
$ tail /etc/apt/listchanges.conf
[apt]
frontend=pager
email_address=
confirm=1
^^^^^^^^^
save_seen=/var/lib/apt/listchanges.db
which=both
IIRC it's asked by debconf, and can be changed with:
dpkg-reconfigure apt-listchanges
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
