PLOTCHANGELOGSection: User Commands (1)
Updated: Debian Utilities
Return to Main Contents
NAMEplotchangelog - graph debian changelogs
SYNOPSISplotchangelog [options] changelog ...
DESCRIPTIONplotchangelog is a tool to aid in visualizing a Debian changelog. The changelogs are graphed with gnuplot(1) , with the X axis of the graph denoting time of release and the Y axis denoting the debian version number of the package. Each individual release of the package is represented by a point, and the points are color coded to indicate who released that version of the package. The upstream version number of the package can also be labeled on the graph.
Alternativly, the Y axis can be configured to display the size of the changelog entry for each new version. Or it can be configured to display approximatly how many bugs were fixed for each new version.
Note that if the package is a debian-specific package, the entire package version will be used for the Y axis. This does not always work perfectly.
READING THE GRAPHThe general outline of a package's graph is typically a series of peaks, starting at 1, going up to n, and then returning abruptly to 1. The higher the peaks, the more releases the maintainer made between new upstream versions of the package. If a package is debian-only, it's graph will just grow upwards without ever falling (although a bug in this program may cause it to fall sometimes, if the version number goes from say, 0.9 to say, 0.10 - this is interpreted wrong..)
If the graph dips below 1, someone made a NMU of the package and upgraded it to a new upstream version, thus setting the debian version to 0. NMU's in general appear as fractional points like 1.1, 2.1, etc. A NMU can also be easily detected by looking at the points that represent which maintainer uploaded the package -- a solitary point of a different type than the points before and after it is typically a NMU.
CONFIGURATION VARIABLESThe two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables. The --no-conf option can be used to prevent reading these files. Environment variable settings are ignored when these configuration files are read. The currently recognised variables are:
AUTHORJoey Hess <firstname.lastname@example.org>
This document was created by man2html, using the manual pages.
Time: 01:55:33 GMT, July 08, 2020