verify problems in package collections
is used to check a collection of
packages for problems that cannot be noticed in individual packages, such as
conflict and directory registration issues.
A conflict is a file that belongs to two distinct packages.
By default, packages with the same stem (see
are registered to conflict. This can be changed to add or remove extra
conflict registration with @option
Conflicts between packages mean that a user can't have both packages installed
at the same time. In some cases (same software, different version), this is
expected, but the packages should be marked as conflicting, so that
how to deal with it. In other cases, this is an oversight from the ports
maintainer, and action should be taken to make sure both packages can be
installed simultaneously. Conflicts also interact with dependencies, and
sometimes a missing dependency will show up as an unregistered conflict.
Directories can belong to distinct packages, as long as they are registered
somewhere. Every directory that is not part of the standard
appear in a packing-list somewhere.
Contrary to files, directories can be shared between several packages.
knows enough about packages to trace
directories back to a common dependency, or to not flag two packages as
conflicting when they depend on already conflicting packages.
requires a set of packing-lists to
operate, which it can obtain from several sources. The preferred source is the
packing-list databases (see
as it persists over time and can be used to fix update information as well as
current version information.
It should be supplemented with the ports tree itself in order to figure out
Options are as follows:
- Do not compute conflict information.
- Do not compute common dir information.
- Check for extra logical conflicts, by adding supplementary
formatted/unformatted manpages, as same name manpages under the same base
directory will shadow one another.
- Save results to output file as well as writing it on the
- Be silent.
- Be verbose.
- Scan directory plist-dir
- Traverse the ports directory for packing-lists, using
print-plist-all. More than one directory
could be specified by delimiting them by colon, e.g.:
plist-dir is also used, traverse only the
directories corresponding to the packages under
plist-dir to figure out current pkgnames,
and annotate those with a ‘!’ in the report.
Dependency not found zarafa-webaccess-7.1.11p2
Dependency not found kwebkitpart-1.2p3
- Dependency not found: means some package names could not
be found. Most often happens because of panic issues, and fsck not
recovering some dependency files.
- claws-mail directory: missing directory registration.
check-problems could not find a common
ancestor to claws-mail-gdata and claws-mail-pdfviewer, so it should be
added to both.
- Conflict between arm-non-eabi-gdb and gdb: note that
both packages are current. Two choices: either remove the offending files
from one package (might break the other), or mark an explicit conflict
between the packages (will prevent people from installing both at the same
- Conflict between libnet-...v0 and libnet: Note that only
the v0 version is current. People forgot to augment the
@option no-default-conflict with conflicts
against the old version when bumping the