coinst(1) [debian man page]
COINST(1) General Commands Manual COINST(1) NAME
Coinst - computes the co-installability kernel of a package repostory SYNOPSIS
coinst [options] DESCRIPTION
coinst reads a package repository in debian format or RPM format from standard input, and computes the co-installability kernel of the repository (see below). The graph of the kernel is written in dot format to a file, and a diagnostic is written to standard output. This diagnostic consists by default of: - the list of equivalence classes of packages - the list of non-installable packages - the list of not co-installable pairs of packages CO-INSTALLABILITY KERNELS A set of packages is called co-installable with respect to a repository R if it can be extended to a set of packages from R that satisfies all inter-package relations (dependencies, conflicts, etc.). In particular, a package p is installable if the set {p} consisting of p only is co-installable. This tool reduces a repository R to a much smaller one, its so-called co-installability kernel R', that behaves exactly the same as far as co-installability of package is concerned: Any set of packages P is co-installable with respect to P iff it co-installable with respect to R'. This is achieved by - dropping all relations that are not relevant for this purpose. For instance, dependencies that do not lead directly or indirectly to any conflicts are dropped. - identifying all packages that behave the same. For instance, packages that are not in conflict with any other package (even not through dependency chains) behave the same since they are co-installable together with any other co-installable set of packages, and packages that are not installable at all behave the same since they may never be part of any co-installable set of packages. A more precise explanation can be found in the original research article underlying this tool. The interest of computing the kernel is that it is typically orders of magnitude smaller than the original repository. OPTIONS
Options controlling the input -deb expect input in the format of a debian Packages file (default). -rpm expect input in the format of an RPM hdlist.cz file. -ignore package ignore the package named package. Options controlling the graph output -o file write the graph to file instead of graph.dot -all include all packages in the coinstallability graph -root p draw only the relevant portion of the graph around package p. Options controlling the diagnostic output -explain explain the list of non-installable pairs of packages. -stats show statistics regarding the input and output repositories Miscellaneous options -help, --help show command synopsis EXAMPLE
Reduce a current debian Packages file to its kernel: coinst -all -o raw.dot < sid_main_binary-amd64_Packages Layout the graph: dot raw.dot -o layout.dot: View the graph with dotty, or the viewer from the coinst_viewer package: dotty layout.dot coinst_viewer layout.dot AUTHOR
Coinst has been written by Jerome Vouillon. This manpage has been compiled by Ralf Treinen from the original coinst documentation. SEE ALSO
dot(1),dotty(1),coinst_viewer(1) http://coinst.irill.org The original research article decribing the algorithm behind this tool is Roberto Di Cosmo and Jerome Vouillon, On software component co- installability, 19th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-19) and ESEC'11: 13rd European Software Engi- neering Conference (ESEC-13), Szeged, Hungary, September 5-9, 2011, pages 256-266. COINST(1)
Check Out this Related Man Page
BUILDCHECK(1) DOSE Tools BUILDCHECK(1) NAME
dose-buildcheck - check installability of build-dependencies SYNOPSIS
dose-buildcheck [options] binary-repositories source-repository DESCRIPTION
dose-buildcheck determines, for a set of debian source package control stanzas, called the source repository, whether a build environment for the packages of the source repository can be installed by using packages from the binary repository. For this, only package meta- information is taken into account: build-dependencies and build-conflicts in the source package, and inter-package relationsships expressed in the binary repository. The constraint solving algorithm is complete, that is it finds a solution whenever there exists one, even for multiple disjunctive dependencies and deep package conflicts. This problem is computationally infeasible in theory (that is, NP-complete), but can be solved very efficiently for package repositories that actually occur in practice. Installability of binary packages is analyzed according to their Depends, Conflicts, and Provides fields with their meaning as of Debian policy version 3.9.0. Pre-depends are treated like Depends, and Breaks are treated like Conflicts. Input Format The binary-repositories argument is a list of filenames containing stanzas in the format of deb-control(5), separated by one blank line. For instance, the Packages files as found on a Debian mirror server, or in the directory /var/lib/apt/lists/ of a Debian system, are suitable. The source-repository argument is the name of a file containing debian source control stanzas, separated by one blank line. For instance, the Sources files as found on a Debian mirror server, or in the directory /var/lib/apt/lists/ of a Debian system, are suitable. Multi-arch annotations are correctly considered by distcheck. Packages whose's architecture is neither the native architecture nor in the list of foreign architectures (see below) are ignored. Here, native and foreign refers at the same time to the architecture on which the compilation will be run, and to the target architecture of the compilation. Cross-compilation is not supported in the current version. OPTIONS
--deb-native-arch=name Specify the native architecture. The default behavior is to deduce the native architecture from the first package stanza in the input that has an architecture different from all. --deb-foreign-archs=name [,name] ... Specify a comma-separated list of foreign architectures. The default is an empty list of foreign architectures. -f --failures Only show broken packages that fail the installability check. -v --successes Only show packages that do not fail the installability check. -e --explain Explain the results in more detail. -v Enable info / warnings / debug messages. This option may be repeated up to three times in order to increase verbosity. -h, --help Display this list of options. EXAMPLE
Compute the list of source packages in Sources for which it is not possible to install a build environment on i386, assuming that the binary packages described in file Packages are available: dose-builddebcheck -v -f -e --arch amd64 /var/lib/apt/lists/ftp.fr.debian.org_debian_dists_sid_main_binary-amd64_Packages /var/lib/apt/lists/ftp.fr.debian.org_debian_dists_sid_main_source_Sources AUTHOR
The current version has been rewritten on the basis of the dose3 library by Pietro Abate; it replaces an earlier version that was simply a wrapper for edos-distcheck. SEE ALSO
deb-control(5), dose-distcheck(1) <http://www.edos-project.org> is the home page of the EDOS project. <http://www.mancoosi.org> is the home page of the Mancoosi project. dose3 3.0.2 2012-10-03 BUILDCHECK(1)