inspects a local Debian package archive and displays the versions of the
given packages found in each
in a brief but easily human-readable form.
It aims to be a drop-in replacement for the
utility (since renamed to
dak ls )
archive management suite that runs on the central Debian archive systems,
but one which can run without access to the archive's
The following options are available:
Read configuration from
and ignore the system configuration file
Quick configuration: use
as the top level of the Debian mirror.
Normally, parts of the
files in the archive are cached in
This option disables that behaviour.
Force caches of
files to be updated.
-S , --source-and-binary
as a source package name, and display versions of any associated binary
packages as well as of the source package.
-r , --regex
as a Perl regular expression anchored at the start of the package name
rather than as an exact name.
Make sure to quote any shell metacharacters such as
-a , --architecture architecture [, ...
Display only entries for packages built for these architectures.
Separate multiple architectures with commas or spaces.
-c , --component component [, ...
Display only entries in the given components.
Separate multiple components with commas or spaces.
-s , --suite suite [, ...
Display only entries in the given suites.
Separate multiple suites with commas or spaces.
reads configuration information from the file named by
or, if that is not supplied, from the first of
The following configuration directives are recognized:
Set the top-level directory of the local Debian mirror.
Relative directories in the
directive are interpreted relative to this directory.
Defaults to the current directory.
suite name directory [component [...
Defines the suite
containing the specified components (defaulting to all subdirectories of
Output is displayed following the order of
directives in the configuration file.
directives are present, then every subdirectory of the
is treated as a suite, with all of their subdirectories as components.
The Debian archive is structured such that the subdirectories of each
suite directory identify components (such as
Each of those in turn has subdirectories for each architecture
and so on),
each of which contains any or all of
files listing binary packages;
it also has a subdirectory called
which contains any or all of
files listing source packages.
The configuration file may contain comment lines, which start with a
Show versions of the
$ madison-lite coreutils
Show versions of all binary packages on
produced by the
$ madison-lite -S -a powerpc glibc
Show versions of all packages in the
suite whose names begin with
$ madison-lite -s unstable -r 'man.*'
An example configuration file for a simple local mirror:
suite unstable dists/unstable main
suite unstable-non-US non-US/dists/unstable non-US/main