1PLOTCHANGELOG(1) General Commands Manual PLOTCHANGELOG(1)
2
6 plotchangelog - graph Debian changelogs
7
9 plotchangelog [options] changelog ...
10
12 plotchangelog is a tool to aid in visualizing a Debian changelog. The
13 changelogs are graphed with gnuplot(1) , with the X axis of the graph
14 denoting time of release and the Y axis denoting the Debian version
15 number of the package. Each individual release of the package is repre‐
16 sented by a point, and the points are color coded to indicate who
17 released that version of the package. The upstream version number of
18 the package can also be labeled on the graph.
19 Alternatively, the Y axis can be configured to display the size of the
21 changelog entry for each new version. Or it can be configured to dis‐
22 play approximately how many bugs were fixed for each new version.
23 Note that if the package is a Debian-specific package, the entire pack‐
25 age version will be used for the Y axis. This does not always work per‐
26 fectly.
27
29 The general outline of a package's graph is typically a series of
30 peaks, starting at 1, going up to n, and then returning abruptly to 1.
31 The higher the peaks, the more releases the maintainer made between new
32 upstream versions of the package. If a package is Debian-only, it's
33 graph will just grow upwards without ever falling (although a bug in
34 this program may cause it to fall sometimes, if the version number goes
35 from say, 0.9 to say, 0.10 - this is interpreted wrong...)
36 If the graph dips below 1, someone made a NMU of the package and
38 upgraded it to a new upstream version, thus setting the Debian version
39 to 0. NMU's in general appear as fractional points like 1.1, 2.1, etc.
40 A NMU can also be easily detected by looking at the points that repre‐
41 sent which maintainer uploaded the package -- a solitary point of a
42 different type than the points before and after it is typically a NMU.
43 It's also easy to tell by looking at the points when a package changes
45 maintainers.
46
48 -l, --linecount
49 Instead of using the Debian version number as the Y axis, use
50 the number of lines in the changelog entry for each version.
51 Cannot be used together with --bugcount.
52 -b, --bugcount
54 Instead of using the Debian version number as the Y axis, use
55 the number of bugs that were closed by each changelog entry.
56 Note that this number is obtained by searching for "#dddd" in
57 the changelog, and so it may be inaccurate. Cannot be used
58 together with --linecount.
59 -c, --cumulative
61 When used together with either --bugcount or --linecount, graphs
62 the cumulative count rather than the count in each individual
63 changelog entry.
64 -v, --no-version
66 Do not show upstream version labels. Useful if the graph gets
67 too crowded.
68 -m, --no-maint
70 Do not differentiate between different maintainers of the pack‐
71 age.
72 -s file, --save=file
74 Save the graph to file in PostScript format instead of immedi‐
75 ately displaying it.
76 -u, --urgency
78 Use larger points when displaying higher-urgency package
79 uploads.
80 --verbose
82 Output the gnuplot script that is fed into gnuplot (for debug‐
83 ging purposes).
84 -gcommands, --gnuplot=commands
86 This allows you to insert gnuplot(1) commands into the gnuplot
87 script that is used to generate the graph. The commands are
88 placed after all initialization but before the final plot com‐
89 mand. This can be used to override the default look provided by
90 this program in arbitrary ways. You can also use things like
91 "set terminal png color" to change the output file type, which
92 is useful in conjunction with the -s option.
93 --help Show a usage summary.
95 --version
97 Display version, author and copyright information.
98 --noconf, --no-conf
100 Do not read any configuration files (see below).
101 changelog ...
103 The changelog files to graph. If multiple files are specified
104 they will all be displayed on the same graph. The files may be
105 compressed with gzip. Any text in them that is not in Debian
106 changelog format will be ignored.
107
109 The two configuration files /etc/devscripts.conf and ~/.devscripts are
110 sourced by a shell in that order to set configuration variables. The
111 --no-conf option can be used to prevent reading these files. Environ‐
112 ment variable settings are ignored when these configuration files are
113 read. The currently recognised variables are:
114 PLOTCHANGELOG_OPTIONS
116 This is a space-separated list of options to always use, for
117 example -l -b. Do not include -g or --gnuplot among this list
118 as it may be ignored; see the next variable instead.
119 PLOTCHANGELOG_GNUPLOT
121 These are gnuplot commands which will be prepended to any such
122 commands given on the command line.
123
125 devscripts.conf(5)
126
128 Joey Hess <joey@kitenet.net>
129DEBIAN Debian Utilities PLOTCHANGELOG(1)