NAME

bpkg-pkg-status – print package status

SYNOPSIS

bpkg pkg-status|status [options] pkg[/ver]...

DESCRIPTION

The pkg-status command prints the status of the specified packages or, if ver is specified, package versions. Note that the status is written to STDOUT, not STDERR.

The status output format is regular. If several packages were specified, then each line starts with the package name (and version, if specified) followed by ':'. Then comes one of the status words listed below. Some of them can be optionally followed by ',' (no spaces) and a sub-status word.

unknown
Package is not part of the configuration nor available from any of the repositories.
available
Package is not part of the configuration but is available from one of the repositories.
fetched
Package is part of the configuration and is fetched.
unpacked
Package is part of the configuration and is unpacked.
configured
Package is part of the configuration and is configured. May be followed by the system sub-status indicating a package coming from the system. The version of such a system package (described below) may be the special '*' value indicating a wildcard version.
broken
Package is part of the configuration and is broken (broken packages can only be purged; see bpkg-pkg-purge(1)).

If only the package name was specified without the package version, then the available status word is followed by the list of available versions. The last version on this list may have the sys: prefix indicating an available system version. Such a system version may be the special '?' value indicating that a package may or may not be available from the system and its version is unknown.

Similarly, if only the package name was specified, then the fetched, unpacked, configured, and broken status words are followed by the version of the package. After the package version, these status words may be followed by one or more sub-status words. Currently, these can be hold_package (package should not be automatically dropped) and hold_version (package should not be automatically upgraded). Finally, if only the package name was specified and newer versions are available from some of the repositories, then the sub-status word is followed by ';', the available status word, and the list of newer versions.

Below are some examples, assuming the configuration has libfoo 1.0.0 configured and held as well as libfoo 1.1.0 and 1.1.1 available from source and 1.1.0 from the system.

bpkg status libbar
unknown

bpkg status libbar/1.0.0
unknown

bpkg status libfoo/1.0.0
configured hold_package

bpkg status libfoo/1.1.0
available 1.1.0 sys:1.1.0

bpkg status libfoo/1.1.1
available

bpkg status libfoo
configured 1.0.0 hold_package; available 1.1.0 1.1.1 sys:1.1.0

bpkg status libfoo/1.0.0 libbar
libfoo/1.0.0: configured hold_package
libbar: unknown

Assuming now that we dropped libfoo from the configuration:

bpkg status libfoo/1.0.0
unknown

bpkg status libfoo
available 1.1.0 1.1.1 sys:1.1.0

And assuming now that we built libfoo as a system package with the wildcard version:

bpkg status libfoo
configured,system * hold_package; available 1.1.0 1.1.1 sys:1.1.0
unknown

PKG-STATUS OPTIONS

--directory|-d dir
Assume configuration is in dir rather than in the current working directory.

COMMON OPTIONS

The common options are summarized below with a more detailed description available in bpkg-common-options(1).

-v
Print essential underlying commands being executed.
-V
Print all underlying commands being executed.
--quiet|-q
Run quietly, only printing error messages.
--verbose level
Set the diagnostics verbosity to level between 0 and 6.
--build path
The build program to be used to build packages.
--build-option opt
Additional option to be passed to the build program.
--fetch path
The fetch program to be used to download resources.
--fetch-option opt
Additional option to be passed to the fetch program.
--sha256 path
The sha256 program to be used to calculate SHA256 sums.
--sha256-option opt
Additional option to be passed to the sha256 program.
--tar path
The tar program to be used to extract package archives.
--tar-option opt
Additional option to be passed to the tar program.
--openssl path
The openssl program to be used for crypto operations.
--openssl-option opt
Additional option to be passed to the openssl program.
--auth type
Types of repositories to authenticate.
--trust fingerprint
Trust repository certificate with a SHA256 fingerprint.
--trust-yes
Assume the answer to all authentication prompts is yes.
--trust-no
Assume the answer to all authentication prompts is no.
--pager path
The pager program to be used to show long text.
--pager-option opt
Additional option to be passed to the pager program.
--options-file file
Read additional options from file.

BUGS

Send bug reports to the users@build2.org mailing list.