1bpkg-pkg-status(1) General Commands Manual bpkg-pkg-status(1)
2
6 bpkg-pkg-status - print package status
7
9 bpkg pkg-status|status [options] [pkg[/ver]...]
10
12 The pkg-status command prints the status of the specified packages or,
13 if ver is specified, package versions. If no packages were specified,
14 then pkg-status prints the status of all the held packages (which are
15 the packages that were explicitly built; see bpkg-pkg-build(1)). Addi‐
16 tionally, the status of immediate or all dependencies of the above
17 packages can be printed by specifying the --immediate|-i or --recur‐
18 sive|-r options, respectively. Note that the status is written to std‐
19 out, not stderr.
20 The status output format is regular with components separated with spa‐
22 ces. Each line starts with the package name (and version, if speci‐
23 fied) followed by one of the status words listed below. Some of them
24 can be optionally followed by ',' (no spaces) and a sub-status word.
25 unknown
27 Package is not part of the configuration nor available from any
28 of the repositories.
29 available
31 Package is not part of the configuration but is available from
32 one of the repositories.
33 fetched
35 Package is part of the configuration and is fetched.
36 unpacked
38 Package is part of the configuration and is unpacked.
39 configured
41 Package is part of the configuration and is configured. May be
42 followed by the system sub-status indicating a package coming
43 from the system. The version of such a system package (described
44 below) may be the special '*' value indicating a wildcard ver‐
45 sion.
46 broken
48 Package is part of the configuration and is broken (broken pack‐
49 ages can only be purged; see bpkg-pkg-purge(1)).
50 If only the package name was specified without the package version,
52 then the available status word is followed by the list of available
53 versions. Versions that are only available for up/down-grading are
54 printed in '[]' (such version are only available as dependencies from
55 prerequisite repositories of other repositories). If the --system
56 option is specified, then the last version in this list may have the
57 sys: prefix indicating an available system version. Such a system ver‐
58 sion may be the special '?' value indicating that a package may or may
59 not be available from the system and that its version is unknown.
60 Similarly, if only the package name was specified, then the fetched,
62 unpacked, configured, and broken status words are followed by the ver‐
63 sion of the package. If newer versions are available, then the package
64 version is followed by the available status word and the list of newer
65 versions. To instead see a list of all versions, including the older
66 ones, specify the --old-available|-o option. In this case the currently
67 selected version is printed in '()'.
68 If the package name was specified with the version, then only the sta‐
70 tus (such as, configured, available, etc.) of this version is consid‐
71 ered.
72 If a package is being held, then its name is printed prefixed with '!'.
74 Similarly, if a package version is being held, then the version is
75 printed prefixed with '!'. Held packages and held versions were
76 selected by the user and are not automatically dropped and upgraded,
77 respectively.
78 Below are some examples, assuming the configuration has libfoo 1.0.0
80 configured and held (both package and version) as well as libfoo 1.1.0
81 and 1.1.1 available from source and 1.1.0 from the system.
82 bpkg status libbar
84 libbar unknown
85 bpkg status libbar/1.0.0
87 libbar/1.0.0 unknown
88 bpkg status libfoo/1.0.0
90 !libfoo/1.0.0 configured !1.0.0
91 bpkg status libfoo/1.1.0
93 libfoo/1.1.0 available 1.1.0
94 bpkg status --system libfoo/1.1.0
96 libfoo/1.1.0 available 1.1.0 sys:1.1.0
97 bpkg status libfoo
99 !libfoo configured !1.0.0 available 1.1.0 1.1.1
100 bpkg status libfoo/1.1.1 libbar
102 libfoo/1.1.1 available 1.1.1
103 libbar unknown
104 Assuming now that we dropped libfoo from the configuration:
106 bpkg status libfoo/1.0.0
108 libfoo/1.0.0 unknown
109 bpkg status libfoo
111 libfoo available 1.1.0 1.1.1
112 And assuming now that we built libfoo as a system package with the
114 wildcard version:
115 bpkg status libfoo
117 !libfoo configured,system * available 1.1.0 1.1.1
118
120 --immediate|-i
121 Also print the status of immediate dependencies.
122 --recursive|-r
124 Also print the status of all dependencies, recursively.
125 --old-available|-o
127 Print old available versions.
128 --constraint
130 Print version constraints for dependencies.
131 --system
133 Check the availability of packages from the system.
134 --no-hold
136 Don't print the package or version hold status.
137 --no-hold-package
139 Don't print the package hold status.
140 --no-hold-version
142 Don't print the version hold status.
143 --directory|-d dir
145 Assume configuration is in dir rather than in the current work‐
146 ing directory.
147
149 The common options are summarized below with a more detailed descrip‐
150 tion available in bpkg-common-options(1).
151 -v Print essential underlying commands being executed.
153 -V Print all underlying commands being executed.
155 --quiet|-q
157 Run quietly, only printing error messages.
158 --verbose level
160 Set the diagnostics verbosity to level between 0 and 6.
161 --jobs|-j num
163 Number of jobs to perform in parallel.
164 --no-result
166 Don't print informational messages about the outcome of perform‐
167 ing a command.
168 --no-progress
170 Suppress progress indicators for long-lasting operations, such
171 as network transfers, building, etc.
172 --build path
174 The build program to be used to build packages.
175 --build-option opt
177 Additional option to be passed to the build program.
178 --fetch path
180 The fetch program to be used to download resources.
181 --fetch-option opt
183 Additional option to be passed to the fetch program.
184 --fetch-timeout sec
186 The fetch and fetch-like (for example, git) program timeout.
187 --pkg-proxy url
189 HTTP proxy server to use when fetching package manifests and ar‐
190 chives from remote pkg repositories.
191 --git path
193 The git program to be used to fetch git repositories.
194 --git-option opt
196 Additional common option to be passed to the git program.
197 --sha256 path
199 The sha256 program to be used to calculate SHA256 sums.
200 --sha256-option opt
202 Additional option to be passed to the sha256 program.
203 --tar path
205 The tar program to be used to extract package archives.
206 --tar-option opt
208 Additional option to be passed to the tar program.
209 --openssl path
211 The openssl program to be used for crypto operations.
212 --openssl-option opt
214 Additional option to be passed to the openssl program.
215 --auth type
217 Types of repositories to authenticate.
218 --trust fingerprint
220 Trust repository certificate with a SHA256 fingerprint.
221 --trust-yes
223 Assume the answer to all authentication prompts is yes.
224 --trust-no
226 Assume the answer to all authentication prompts is no.
227 --pager path
229 The pager program to be used to show long text.
230 --pager-option opt
232 Additional option to be passed to the pager program.
233 --options-file file
235 Read additional options from file.
236 --default-options dir
238 The directory to load additional default options files from.
239 --no-default-options
241 Don't load default options files.
242
244 See bpkg-default-options-files(1) for an overview of the default
245 options files. For the pkg-status command the search start directory is
246 the configuration directory. The following options files are searched
247 for in each directory and, if found, loaded in the order listed:
248 bpkg.options
250 bpkg-pkg-status.options
251 The following pkg-status command options cannot be specified in the
253 default options files:
254 --directory|-d
256
258 Send bug reports to the users@build2.org mailing list.
259
261 Copyright (c) 2014-2020 the build2 authors.
262 Permission is granted to copy, distribute and/or modify this document
264 under the terms of the MIT License.
265bpkg 0.13.0 July 2020 bpkg-pkg-status(1)