1DEBI(1) General Commands Manual DEBI(1)
2
6 debi - install current version of generated Debian package
7
9 debi [options] [changes file] [package ...]
10
12 debi figures out the current version of a package and installs it. If
13 a .changes file is specified on the command line, the filename must end
14 with .changes, as this is how the program distinguishes it from package
15 names. If not, then debi has to be called from within the source code
16 directory tree. In this case, it will look for the .changes file cor‐
17 responding to the current package version (by determining the name and
18 version number from the changelog, and the architecture in the same way
19 as dpkg-buildpackage(1) does). It then runs dpkg -i on every .deb ar‐
20 chive listed in the .changes file to install them, assuming that all of
21 the .deb archives live in the same directory as the .changes file.
22 Note that you probably don't want to run this program on a .changes
23 file relating to a different architecture after cross-compiling the
24 package!
25 If a list of packages is given on the command line, then only those
27 debs with names in this list of packages will be installed.
28 Since installing a package requires root privileges, debi will only be
30 useful if it is either being run as root or dpkg can be run as root.
31
33 In common with several other scripts in the devscripts package, debi
34 will climb the directory tree until it finds a debian/changelog file.
35 As a safeguard against stray files causing potential problems, it will
36 examine the name of the parent directory once it finds the de‐
37 bian/changelog file, and check that the directory name corresponds to
38 the package name. Precisely how it does this is controlled by two con‐
39 figuration file variables DEVSCRIPTS_CHECK_DIRNAME_LEVEL and DE‐
40 VSCRIPTS_CHECK_DIRNAME_REGEX, and their corresponding command-line op‐
41 tions --check-dirname-level and --check-dirname-regex.
42 DEVSCRIPTS_CHECK_DIRNAME_LEVEL can take the following values:
44 0 Never check the directory name.
46 1 Only check the directory name if we have had to change directory
48 in our search for debian/changelog. This is the default behav‐
49 iour.
50 2 Always check the directory name.
52 The directory name is checked by testing whether the current directory
54 name (as determined by pwd(1)) matches the regex given by the configu‐
55 ration file option DEVSCRIPTS_CHECK_DIRNAME_REGEX or by the command
56 line option --check-dirname-regex regex. Here regex is a Perl regex
57 (see perlre(3perl)), which will be anchored at the beginning and the
58 end. If regex contains a '/', then it must match the full directory
59 path. If not, then it must match the full directory name. If regex
60 contains the string ´PACKAGE', this will be replaced by the source
61 package name, as determined from the changelog. The default value for
62 the regex is: ´PACKAGE(-.+)?', thus matching directory names such as
63 PACKAGE and PACKAGE-version.
64
66 -adebian-architecture, -tGNU-system-type
67 See dpkg-architecture(1) for a description of these options.
68 They affect the search for the .changes file. They are provided
69 to mimic the behaviour of dpkg-buildpackage when determining the
70 name of the .changes file.
71 --debs-dir directory
73 Look for the .changes and .deb files in directory instead of the
74 parent of the source directory. This should either be an abso‐
75 lute path or relative to the top of the source directory.
76 -m, --multi
78 Search for a multiarch .changes file, as created by dpkg-cross.
79 -u, --upgrade
81 Only upgrade packages already installed on the system, rather
82 than installing all packages listed in the .changes file. Use‐
83 ful for multi-binary packages when you don't want to have all
84 the binaries installed at once.
85 --check-dirname-level N
87 See the above section Directory name checking for an explanation
88 of this option.
89 --check-dirname-regex regex
91 See the above section Directory name checking for an explanation
92 of this option.
93 --with-depends
95 Attempt to satisfy the Depends of a package when installing it.
96 --tool tool
98 Use the specified tool for installing the dependencies of the
99 package(s) to be installed. By default, apt-get is used.
100 --no-conf, --noconf
102 Do not read any configuration files. This can only be used as
103 the first option given on the command-line.
104 --help, --version
106 Show help message and version information respectively.
107
109 The two configuration files /etc/devscripts.conf and ~/.devscripts are
110 sourced in that order to set configuration variables. Command line op‐
111 tions can be used to override configuration file settings. Environment
112 variable settings are ignored for this purpose. The currently recog‐
113 nised variables are:
114 DEBRELEASE_DEBS_DIR
116 This specifies the directory in which to look for the .changes
117 and .deb files, and is either an absolute path or relative to
118 the top of the source tree. This corresponds to the --debs-dir
119 command line option. This directive could be used, for example,
120 if you always use pbuilder or svn-buildpackage to build your
121 packages. Note that it also affects debrelease(1) in the same
122 way, hence the strange name of the option.
123 DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
125 See the above section Directory name checking for an explanation
126 of these variables. Note that these are package-wide configura‐
127 tion variables, and will therefore affect all devscripts scripts
128 which check their value, as described in their respective man‐
129 pages and in devscripts.conf(5).
130
132 devscripts.conf(5)
133
135 debi was originally written by Christoph Lameter <clameter@debian.org>.
136 The now-defunct script debit was originally written by James R. Van
137 Zandt <jrv@vanzandt.mv.com>. They have been moulded into one script
138 together with debc(1) and parts extensively modified by Julian Gilbey
139 <jdg@debian.org>.
140DEBIAN Debian Utilities DEBI(1)