CHALLENGED(1) DOSE Tools CHALLENGED(1)NAME
dose-challenged - detect broken packages due to obsolete dependencies
SYNOPSIS
dose-challenged [options] Packages file(s)
DESCRIPTION
dose-challenged performs a speculative analysis of the repository to identify those packages that, if upgraded to a specific version, would
break a large number of other packages in the repository. This tool would be particularly useful during the upgrade of a specific component
to evaluate its impact on the software archive.
Input Specification
The input of dose-challenged is a list of Debian Packages files
Output Specification
The output of dose-challenged is in the yaml format.
Options-b --broken
Print the list of broken packages
-d --downgrade
Check package downgrades
-c Print the list of packages in a cluster
--checkonly
Select a subset of packages to check. By default all packages are checked.
-v Enable info / warnings / debug messages. This option may be repeated up to three times in order to increase verbosity.
--progress
Enable progress bars.
-h, --help
Display this list of options.
EXAMPLE
dose-challenged -v --progress Packages.bz2 > result.yaml
NOTE AUTHOR
Pietro Abate and Roberto Di Cosmo
SEE ALSO dose-distcheck(1)dose-outdated(1)
<http://www.mancoosi.org> is the home page of the Mancoosi project.
dose3 3.0.2 2012-10-03 CHALLENGED(1)
Check Out this Related Man Page
CEVE(1) DOSE Tools CEVE(1)NAME
dose-ceve - parse package metadata
SYNOPSIS
dose-ceve [-h] [-v] [-e pkgspec] [-c pkgspec] [-r pkgspec] [--depth=n] [-t format] [-o filename] input-spec
DESCRIPTION
Dose-ceve is a generalized metadata parser. It reads package specifications, extracts package metadata from them, performs some
manipulations, and outputs the package metadata in one of several formats.
OPTIONS -h This option displays the help message. Can also be specified as --help.
-v Be verbose. This option can be repeated for more verbosity.
-e pkgspec
(Option Not Implemented Yet) Extract the transitive closure of packages connected (by conflict or dependency) to any of the packages
that satisfy pkgspec. Such a package specification is a list of packages (separated by a semicolon), where each package is specified as
follows: (name,version). This option can also be specified as --extract=pkgspec.
-c pkgspec
Similar to the -c option, but only uses the dependency relation to make the transitive closure. This option can also be specified as
--cone=pkgspec.
-r pkgspec
Similar to the -e and -c options, but uses the reverse dependency relation to make the transitive closure. This option can also be
specified as --rcone=pkgspec.
--depth=n
In combination with the -e, -c or -r options, this specifies the maximum depth for the transitive closure. =item -t format
Specifies the output format to use. Possible values are dot for a graph output in Dot/GraphViz format, cnf for an output in CNF format,
dimacs for an output in the DIMACS format for CNF formulae, and cudf for a pretty-print output in an RFC 822-like format. This option
can also be specified as --outtype=format.
-o filename
Instead of stdout, send output to the file filename. This option can also be specified as --outfile=filename. =item input-spec
This is a URL specifying both the input format and the file to get the input from. Possible schemes are: =item *
cudf for cudf files =item *
deb for Debian package files (possibly compressed with gzip(1) or bzip2(1), depending on compile-time options for dose3) =item *
debstdin for Debian package files read from standard input =item *
eclipse for Eclipse (p2) package files =item *
pgsql for PostgreSQL databasess =item *
sqlite for sqlite databases
* hdlist for RPM hdlists =item *
synth for urpmi synthesis hdlists
Some examples of URLs:
* deb://Packages.gz (the Debian file packages.gz in the current directory)
* cudf:///home/examples/cudf/test.cudf (the CUDF file /home/examples/cudf/test.cudf)
* psql://user@db.mancoosi.org:723/packages (the database packages on host db.mancoosi.org on port 723, accessed as user user)
dose3 3.0.2 2012-10-03 CEVE(1)