This is the last call for comments for the review of debconf templates for apt-listchanges. The reviewed templates will be sent on Monday, December 10, 2007 to the package maintainer as a bug report and a mail will be sent to this list with "[BTS]" as a subject tag. --
Template: apt-listchanges/frontend Type: select __Choices: pager, browser, xterm-pager, xterm-browser, gtk, text, mail, none Default: pager _Description: Method for changes display: Package changes may be displayed by apt-listchanges in a number of different ways. . pager : display changes one page at a time; browser : display HTML-formatted changes using a web browser; xterm-pager : like pager, but in an xterm in the background; xterm-browser: like browser, but in an xterm in the background; gtk : Display changes in a GTK window; text : print changes to the terminal (without pausing); mail : only send changes via mail; none : do not run automatically from APT. . This setting can be overridden at execution time. All frontends but 'none' can also mail a copy. Template: apt-listchanges/email-address Type: string Default: root _Description: E-mail address(es) which will receive changes: Optionally, apt-listchanges can e-mail a copy of displayed changes to a specified address. . Multiple addresses may be specified, delimited by commas. Leaving this field empty disables mail notifications. Template: apt-listchanges/confirm Type: boolean Default: false _Description: Prompt for confirmation after displaying changes? After displaying the list of changes, apt-listchanges may pause with a confirmation prompt. This is useful when running from APT, as it offers an opportunity to abort the upgrade if a change is unwelcome. . This setting does not apply to the 'mail' or 'none' frontends, and can be overridden at execution time. Template: apt-listchanges/save-seen Type: boolean Default: true _Description: Should apt-listchanges skip changes that have already been seen? A record of already displayed changes can be kept in order to avoid displaying them again. This is useful, for example, when retrying an upgrade. Template: apt-listchanges/which Type: select __Choices: news, changelogs, both Default: news _Description: Changes displayed with APT: Please choose which type of changes should be displayed with APT. . news : important news items only; changelogs: detailed changelogs only; both : news and changelogs.
Source: apt-listchanges
Section: utils
Priority: optional
Maintainer: Pierre Habouzit <madcoder@debian.org>
Uploaders: Matt Zimmerman <mdz@debian.org>
Standards-Version: 3.7.2
Vcs-Browser: http://git.madism.org/?p=apt-listchanges.git;a=summary
Vcs-Git: git://git.madism.org/apt-listchanges.git
Build-Depends: debhelper (>= 5)
Build-Depends-Indep: docbook-to-man, gettext, python-dev, po-debconf,
python-support (>= 0.4.0), libexpat1-dev
Package: apt-listchanges
Architecture: all
Depends: ${python:Depends}, apt (>= 0.5.3), python-apt, debconf | debconf-2.0,
ucf (>= 0.28), debianutils (>= 2.0.2)
Recommends: exim4 | mail-transport-agent, python-glade2, python-gtk2
Suggests: x-terminal-emulator, www-browser
Description: package change history notification tool
The tool apt-listchanges can compare a new version of a
package with the one currently installed and show what has been
changed, by extracting the relevant entries from the Debian changelog
and NEWS files.
.
It can be run on several .deb archives at a time to get a list of all
changes that would be caused by installing or upgrading a group of
packages. When configured as an APT plugin it will do this
automatically during upgrades.
Attachment:
signature.asc
Description: Digital signature