1DEBC(1) General Commands Manual DEBC(1)
2
6 debc - view contents of a generated Debian package
7
9 debc [options] [changes file] [package ...]
10
12 debc figures out the current version of a package and displays informa‐
13 tion about the .deb and .udeb files which have been generated in the
14 current build process. If a .changes file is specified on the command
15 line, the filename must end with .changes, as this is how the program
16 distinguishes it from package names. If not, then debc has to be
17 called from within the source code directory tree. In this case, it
18 will look for the .changes file corresponding to the current package
19 version (by determining the name and version number from the changelog,
20 and the architecture in the same way as dpkg-buildpackage(1) does). It
21 then runs dpkg-deb -I and dpkg-deb -c on every .deb and .udeb archive
22 listed in the .changes file to display information about the contents
23 of the .deb / .udeb files. It precedes every .deb or .udeb file with
24 the name of the file. It assumes that all of the .deb / .udeb archives
25 live in the same directory as the .changes file. It is useful for
26 ensuring that the expected files have ended up in the Debian package.
27 If a list of packages is given on the command line, then only those
29 debs or udebs with names in this list of packages will be processed.
30
32 In common with several other scripts in the devscripts package, debc
33 will climb the directory tree until it finds a debian/changelog file.
34 As a safeguard against stray files causing potential problems, it will
35 examine the name of the parent directory once it finds the
36 debian/changelog file, and check that the directory name corresponds to
37 the package name. Precisely how it does this is controlled by two con‐
38 figuration file variables DEVSCRIPTS_CHECK_DIRNAME_LEVEL and
39 DEVSCRIPTS_CHECK_DIRNAME_REGEX, and their corresponding command-line
40 options --check-dirname-level and --check-dirname-regex.
41 DEVSCRIPTS_CHECK_DIRNAME_LEVEL can take the following values:
43 0 Never check the directory name.
45 1 Only check the directory name if we have had to change directory
47 in our search for debian/changelog. This is the default behav‐
48 iour.
49 2 Always check the directory name.
51 The directory name is checked by testing whether the current directory
53 name (as determined by pwd(1)) matches the regex given by the configu‐
54 ration file option DEVSCRIPTS_CHECK_DIRNAME_REGEX or by the command
55 line option --check-dirname-regex regex. Here regex is a Perl regex
56 (see perlre(3perl)), which will be anchored at the beginning and the
57 end. If regex contains a '/', then it must match the full directory
58 path. If not, then it must match the full directory name. If regex
59 contains the string ´PACKAGE', this will be replaced by the source
60 package name, as determined from the changelog. The default value for
61 the regex is: ´PACKAGE(-.+)?', thus matching directory names such as
62 PACKAGE and PACKAGE-version.
63
65 -adebian-architecture, -tGNU-system-type
66 See dpkg-architecture(1) for a description of these options.
67 They affect the search for the .changes file. They are provided
68 to mimic the behaviour of dpkg-buildpackage when determining the
69 name of the .changes file.
70 --debs-dir directory
72 Look for the .changes, .deb and .udeb files in directory instead
73 of the parent of the source directory. This should either be an
74 absolute path or relative to the top of the source directory.
75 --check-dirname-level N
77 See the above section Directory name checking for an explanation
78 of this option.
79 --check-dirname-regex regex
81 See the above section Directory name checking for an explanation
82 of this option.
83 --list-changes
85 List the filename of the .changes file, and do not display any‐
86 thing else. This option only makes sense if a .changes file is
87 NOT passed explicitly in the command line. This can be used for
88 example in a script that needs to reference the .changes file,
89 without having to duplicate the heuristics for finding it that
90 debc already implements.
91 --list-debs
93 List the filenames of the .deb packages, and do not display
94 their contents.
95 --no-conf, --noconf
97 Do not read any configuration files. This can only be used as
98 the first option given on the command-line.
99 --help, --version
101 Show help message and version information respectively.
102
104 The two configuration files /etc/devscripts.conf and ~/.devscripts are
105 sourced in that order to set configuration variables. Command line
106 options can be used to override configuration file settings. Environ‐
107 ment variable settings are ignored for this purpose. The currently
108 recognised variables are:
109 DEBRELEASE_DEBS_DIR
111 This specifies the directory in which to look for the .changes,
112 .deb and .udeb files, and is either an absolute path or relative
113 to the top of the source tree. This corresponds to the
114 --debs-dir command line option. This directive could be used,
115 for example, if you always use pbuilder or svn-buildpackage to
116 build your packages. Note that it also affects debrelease(1) in
117 the same way, hence the strange name of the option.
118 DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
120 See the above section Directory name checking for an explanation
121 of these variables. Note that these are package-wide configura‐
122 tion variables, and will therefore affect all devscripts scripts
123 which check their value, as described in their respective man‐
124 pages and in devscripts.conf(5).
125
127 debdiff(1), dpkg-deb(1), devscripts.conf(5)
128
130 Julian Gilbey <jdg@debian.org>, based on an original script by
131 Christoph Lameter <clameter@debian.org>.
132DEBIAN Debian Utilities DEBC(1)