Section: dpkg utilities (1)
Return to Main Contents
dpkg-scanpackages - create Packages index files
sorts through a tree of Debian binary packages and creates a Packages
file, used by
etc, to tell the user what packages are available for installation. These
Packages files are the same as those found on Debian archive sites
and CD-ROMs. You might use
yourself if making a directory of local packages to install on a cluster
If you want to access the generated Packages file with
you will probably need to compress the file with
(generating a Packages.bz2 file) or
(generating a Packages.gz file). apt ignores uncompressed Packages
files except on local access (i.e.
is the name of the tree of the binary packages to process (for example,
It is best to make this relative to the root of the Debian archive,
because every Filename field in the new Packages file will start with
is the name of a file to read which contains information about how the
package fits into the distribution (it can be a compressed file); see
is an optional string to be prepended to the Filename fields.
If more than one version of a package is found only the newest one
is included in the output. If they have the same version and only
differ in architecture only the first one found is used.
- -t, --type type
Scan for *.type packages, instead of *.deb.
- -e, --extra-override file
Scan file to find supplementary overrides (the file can be
for more information on its format.
- -a, --arch arch
Use a pattern consisting of *_all.deb and *_arch.deb instead of
scanning for all debs.
- -h, --hash hash-list
Only generate file hashes for the comma-specified list specified.
The default is to generate all currently supported hashes.
Supported values: md5, sha1, sha256.
- -m, --multiversion
Include all found packages in the output.
- -M, --medium id-string
Add an X-Medium field containing the value id-string. This field
is required if you want to generate Packages.cd files for use
by the multicd access method of dselect.
- -?, --help
Show the usage message and exit.
Show the version and exit.
outputs the usual self-explanatory errors. It also warns about packages
that are in the wrong subdirectory, are duplicated, have a Filename
field in their control file, are missing from the override file, or have
maintainer substitutions which do not take effect.
- SEE ALSO