1DEBI(1) General Commands Manual DEBI(1)
2
3
4
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 debpkg -i on every .deb
20 archive listed in the .changes file to install them, assuming that all
21 of 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
26 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
29 Since installing a package requires root privileges, debi calls debpkg
30 rather than dpkg directly. Thus debi will only be useful if it is
31 either being run as root or debpkg can be run as root. See debpkg(1)
32 for more details.
33
35 In common with several other scripts in the devscripts package, debi
36 will climb the directory tree until it finds a debian/changelog file.
37 As a safeguard against stray files causing potential problems, it will
38 examine the name of the parent directory once it finds the
39 debian/changelog file, and check that the directory name corresponds to
40 the package name. Precisely how it does this is controlled by two con‐
41 figuration file variables DEVSCRIPTS_CHECK_DIRNAME_LEVEL and
42 DEVSCRIPTS_CHECK_DIRNAME_REGEX, and their corresponding command-line
43 options --check-dirname-level and --check-dirname-regex.
44
45 DEVSCRIPTS_CHECK_DIRNAME_LEVEL can take the following values:
46
47 0 Never check the directory name.
48
49 1 Only check the directory name if we have had to change directory
50 in our search for debian/changelog. This is the default behav‐
51 iour.
52
53 2 Always check the directory name.
54
55 The directory name is checked by testing whether the current directory
56 name (as determined by pwd(1)) matches the regex given by the configu‐
57 ration file option DEVSCRIPTS_CHECK_DIRNAME_REGEX or by the command
58 line option --check-dirname-regex regex. Here regex is a Perl regex
59 (see perlre(3perl)), which will be anchored at the beginning and the
60 end. If regex contains a '/', then it must match the full directory
61 path. If not, then it must match the full directory name. If regex
62 contains the string ´PACKAGE', this will be replaced by the source
63 package name, as determined from the changelog. The default value for
64 the regex is: ´PACKAGE(-.+)?', thus matching directory names such as
65 PACKAGE and PACKAGE-version.
66
68 -adebian-architecture, -tGNU-system-type
69 See dpkg-architecture(1) for a description of these options.
70 They affect the search for the .changes file. They are provided
71 to mimic the behaviour of dpkg-buildpackage when determining the
72 name of the .changes file.
73
74 --debs-dir directory
75 Look for the .changes and .deb files in directory instead of the
76 parent of the source directory. This should either be an abso‐
77 lute path or relative to the top of the source directory.
78
79 -m, --multi
80 Search for a multiarch .changes file, as created by dpkg-cross.
81
82 -u, --upgrade
83 Only upgrade packages already installed on the system, rather
84 than installing all packages listed in the .changes file. Use‐
85 ful for multi-binary packages when you don't want to have all
86 the binaries installed at once.
87
88 --check-dirname-level N
89 See the above section Directory name checking for an explanation
90 of this option.
91
92 --check-dirname-regex regex
93 See the above section Directory name checking for an explanation
94 of this option.
95
96 --with-depends
97 Attempt to satisfy the Depends of a package when installing it.
98
99 --tool tool
100 Use the specified tool for installing the dependencies of the
101 package(s) to be installed. By default, apt-get is used.
102
103 --no-conf, --noconf
104 Do not read any configuration files. This can only be used as
105 the first option given on the command-line.
106
107 --help, --version
108 Show help message and version information respectively.
109
111 The two configuration files /etc/devscripts.conf and ~/.devscripts are
112 sourced in that order to set configuration variables. Command line
113 options can be used to override configuration file settings. Environ‐
114 ment variable settings are ignored for this purpose. The currently
115 recognised variables are:
116
117 DEBRELEASE_DEBS_DIR
118 This specifies the directory in which to look for the .changes
119 and .deb files, and is either an absolute path or relative to
120 the top of the source tree. This corresponds to the --debs-dir
121 command line option. This directive could be used, for example,
122 if you always use pbuilder or svn-buildpackage to build your
123 packages. Note that it also affects debrelease(1) in the same
124 way, hence the strange name of the option.
125
126 DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
127 See the above section Directory name checking for an explanation
128 of these variables. Note that these are package-wide configura‐
129 tion variables, and will therefore affect all devscripts scripts
130 which check their value, as described in their respective man‐
131 pages and in devscripts.conf(5).
132
134 debpkg(1), devscripts.conf(5)
135
137 debi was originally written by Christoph Lameter <clameter@debian.org>.
138 The now-defunct script debit was originally written by James R. Van
139 Zandt <jrv@vanzandt.mv.com>. They have been moulded into one script
140 together with debc(1) and parts extensively modified by Julian Gilbey
141 <jdg@debian.org>.
142
143
144
145DEBIAN Debian Utilities DEBI(1)