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)). The
16 latter mode can be modified to print the status of all the packages by
17 specifying the --all|-a option. Additionally, the status of immediate
18 or all dependencies of the above packages can be printed by specifying
19 the --immediate|-i or --recursive|-r options, respectively. Note that
20 the status is written to stdout, not stderr.
21 The status output format is regular with components separated with spa‐
23 ces. Each line starts with the package name and version (if specified)
24 followed by one of the status words listed below. Some of them can be
25 optionally followed by ',' (no spaces) and a sub-status word. Lines
26 corresponding to dependencies from linked configurations will addition‐
27 ally mention the configuration directory in square brackets after the
28 package name and version.
29 unknown
31 Package is not part of the configuration nor available from any
32 of the repositories.
33 available
35 Package is not part of the configuration but is available from
36 one of the repositories.
37 fetched
39 Package is part of the configuration and is fetched.
40 unpacked
42 Package is part of the configuration and is unpacked.
43 configured
45 Package is part of the configuration and is configured. May be
46 followed by the system sub-status indicating a package coming
47 from the system. The version of such a system package (described
48 below) may be the special '*' value indicating a wildcard ver‐
49 sion.
50 broken
52 Package is part of the configuration and is broken (broken pack‐
53 ages can only be purged; see bpkg-pkg-purge(1)).
54 If only the package name was specified without the package version,
56 then the available status word is followed by the list of available
57 versions. Versions that are only available for up/down-grading are
58 printed in '[]' (such version are only available as dependencies from
59 prerequisite repositories of other repositories). If the --system op‐
60 tion is specified, then the last version in this list may have the sys:
61 prefix indicating an available system version. Such a system version
62 may be the special '?' value indicating that a package may or may not
63 be available from the system and that its version is unknown.
64 Similarly, if only the package name was specified, then the fetched,
66 unpacked, configured, and broken status words are followed by the ver‐
67 sion of the package. If newer versions are available, then the package
68 version is followed by the available status word and the list of newer
69 versions. To instead see a list of all versions, including the older
70 ones, specify the --old-available|-o option. In this case the currently
71 selected version is printed in '()'.
72 If the package name was specified with the version, then only the sta‐
74 tus (such as, configured, available, etc.) of this version is consid‐
75 ered.
76 If a package is being held, then its name is printed prefixed with '!'.
78 Similarly, if a package version is being held, then the version is
79 printed prefixed with '!'. Held packages and held versions were se‐
80 lected by the user and are not automatically dropped and upgraded, re‐
81 spectively.
82 Below are some examples, assuming the configuration has libfoo 1.0.0
84 configured and held (both package and version) as well as libfoo 1.1.0
85 and 1.1.1 available from source and 1.1.0 from the system.
86 bpkg status libbar
88 libbar unknown
89 bpkg status libbar/1.0.0
91 libbar/1.0.0 unknown
92 bpkg status libfoo/1.0.0
94 !libfoo/1.0.0 configured !1.0.0
95 bpkg status libfoo/1.1.0
97 libfoo/1.1.0 available 1.1.0
98 bpkg status --system libfoo/1.1.0
100 libfoo/1.1.0 available 1.1.0 sys:1.1.0
101 bpkg status libfoo
103 !libfoo configured !1.0.0 available 1.1.0 1.1.1
104 bpkg status libfoo/1.1.1 libbar
106 libfoo/1.1.1 available 1.1.1
107 libbar unknown
108 Assuming now that we dropped libfoo from the configuration:
110 bpkg status libfoo/1.0.0
112 libfoo/1.0.0 unknown
113 bpkg status libfoo
115 libfoo available 1.1.0 1.1.1
116 And assuming now that we built libfoo as a system package with the
118 wildcard version:
119 bpkg status libfoo
121 !libfoo configured,system * available 1.1.0 1.1.1
122 Another example of the status output this time including dependencies:
124 bpkg status -r libbaz
126 !libbaz configured 1.0.0
127 libfoo configured 1.0.0
128 bison [.bpkg/host/] configured 1.0.0
129 libbar configured 2.0.0
130
132 --all|-a
133 Print the status of all the packages, not just held.
134 --link Also print the status of held/all packages from linked configu‐
136 rations.
137 --immediate|-i
139 Also print the status of immediate dependencies.
140 --recursive|-r
142 Also print the status of all dependencies, recursively.
143 --old-available|-o
145 Print old available versions.
146 --constraint
148 Print version constraints for dependencies.
149 --system
151 Check the availability of packages from the system.
152 --no-hold
154 Don't print the package or version hold status.
155 --no-hold-package
157 Don't print the package hold status.
158 --no-hold-version
160 Don't print the version hold status.
161 --directory|-d dir
163 Assume configuration is in dir rather than in the current work‐
164 ing directory.
165
167 The common options are summarized below with a more detailed descrip‐
168 tion available in bpkg-common-options(1).
169 -v Print essential underlying commands being executed.
171 -V Print all underlying commands being executed.
173 --quiet|-q
175 Run quietly, only printing error messages.
176 --verbose level
178 Set the diagnostics verbosity to level between 0 and 6.
179 --jobs|-j num
181 Number of jobs to perform in parallel.
182 --no-result
184 Don't print informational messages about the outcome of perform‐
185 ing a command or some of its parts.
186 --no-progress
188 Suppress progress indicators for long-lasting operations, such
189 as network transfers, building, etc.
190 --build path
192 The build program to be used to build packages.
193 --build-option opt
195 Additional option to be passed to the build program.
196 --fetch path
198 The fetch program to be used to download resources.
199 --fetch-option opt
201 Additional option to be passed to the fetch program.
202 --fetch-timeout sec
204 The fetch and fetch-like (for example, git) program timeout.
205 --pkg-proxy url
207 HTTP proxy server to use when fetching package manifests and ar‐
208 chives from remote pkg repositories.
209 --git path
211 The git program to be used to fetch git repositories.
212 --git-option opt
214 Additional common option to be passed to the git program.
215 --sha256 path
217 The sha256 program to be used to calculate SHA256 sums.
218 --sha256-option opt
220 Additional option to be passed to the sha256 program.
221 --tar path
223 The tar program to be used to extract package archives.
224 --tar-option opt
226 Additional option to be passed to the tar program.
227 --openssl path
229 The openssl program to be used for crypto operations.
230 --openssl-option opt
232 Additional option to be passed to the openssl program.
233 --auth type
235 Types of repositories to authenticate.
236 --trust fingerprint
238 Trust repository certificate with a SHA256 fingerprint.
239 --trust-yes
241 Assume the answer to all authentication prompts is yes.
242 --trust-no
244 Assume the answer to all authentication prompts is no.
245 --pager path
247 The pager program to be used to show long text.
248 --pager-option opt
250 Additional option to be passed to the pager program.
251 --options-file file
253 Read additional options from file.
254 --default-options dir
256 The directory to load additional default options files from.
257 --no-default-options
259 Don't load default options files.
260
262 See bpkg-default-options-files(1) for an overview of the default op‐
263 tions files. For the pkg-status command the search start directory is
264 the configuration directory. The following options files are searched
265 for in each directory and, if found, loaded in the order listed:
266 bpkg.options
268 bpkg-pkg-status.options
269 The following pkg-status command options cannot be specified in the de‐
271 fault options files:
272 --directory|-d
274
276 Send bug reports to the users@build2.org mailing list.
277
279 Copyright (c) 2014-2021 the build2 authors.
280 Permission is granted to copy, distribute and/or modify this document
282 under the terms of the MIT License.
283bpkg 0.14.0 October 2021 bpkg-pkg-status(1)