bpkg-pkg-verify(1)
β¨ bpkg-pkg-verify β verify package archive β¨
okay bestie, so this is the bpkg-pkg-verify(1) page from the General Commands Manual, and I'm gonna walk you through it like we're texting at 2am π
πΈ NAME πΈ
bpkg-pkg-verify β verify package archive, no cap π
π¦ SYNOPSIS π¦
bpkg pkg-verify [options] file
β¨ DESCRIPTION β¨
so the pkg-verify command does exactly what it says on the tin β it verifies that the archive file you pointed at is a valid bpkg package. iconic behavior honestly.
specifically, it checks these things:
- that the file's name and the top-level directory inside the archive both match the canonical name-version form π
- that there's a valid manifest file sitting in that top-level directory π
and then, if you also pass the --deep option, it goes deeper and also checks that:
- the required
*-buildvalues/files are actually present in the manifest/archive π§ - the files referenced by the
*-filemanifest values are present in the archive and are not empty π
π PKG-VERIFY OPTIONS π
--silentβ shhh π€« suppresses the error messages explaining why the package is invalid. it just hands you the error status and nothing else.--deepβ the thorough one β¨ verify that the required*-buildvalues/files are present, and check that files referenced by the*-filemanifest values are actually valid.--ignore-unknownβ ignore unknown manifest entries π«Ά by defaultbpkgrefuses to call a package valid when it sees these, because it literally cannot be sure those unknown entries are valid. note that this option also ignores the version constraints in the special toolchain build-time dependencies.--manifestβ instead of printing the successful verification result in human-readable form, dump the package manifest to stdout π and if--deepis also on, then in the resulting manifest: the*-filevalues get replaced with the contents of the referenced files, the*-buildvalues get automatically added (unless the corresponding files are absent), and the package dependency constraints get completed. chef's kiss π
π COMMON OPTIONS π
here's the rundown of the common options β there's a more detailed description over in bpkg-common-options(1) if you want the extended lore π
-vβ print the essential underlying commands being executed π-Vβ print all the underlying commands being executed ππ--quiet,-qβ run quietly, only printing error messages π€--verboselevel β set the diagnostics verbosity to level between0and6ποΈ--stdout-formatformat β representation format to use for printing to stdout π¬--jobs,-jnum β number of jobs to perform in parallel πβοΈπβοΈ--no-resultβ don't print informational messages about the outcome of performing a command or some of its parts π--structured-resultfmt β write the result of performing a command in a structured form ποΈ--progressβ display progress indicators for long-lasting operations, like network transfers, building, etc. β³--no-progressβ suppress progress indicators for long-lasting operations, like network transfers, building, etc. π«--diag-colorβ use color in diagnostics π--no-diag-colorβ don't use color in diagnostics π«π--buildpath β the build program to be used to build packages π¨--build-optionopt β additional option to be passed to the build program π¨β--fetchpath β the fetch program to be used to download resources π₯--fetch-optionopt β additional option to be passed to the fetch program π₯β--fetch-timeoutsec β the fetch and fetch-like (for example,git) program timeout β°--pkg-proxyurl β HTTP proxy server to use when fetching package manifests and archives from remote pkg repositories π--gitpath β thegitprogram to be used to fetch git repositories π--git-optionopt β additional common option to be passed to thegitprogram πβ--sha256path β thesha256program to be used to calculate SHA256 sums π--sha256-optionopt β additional option to be passed to thesha256program πβ--tarpath β thetarprogram to be used to extract package archives π¦--tar-optionopt β additional option to be passed to thetarprogram π¦β--opensslpath β theopensslprogram to be used for crypto operations π--openssl-optionopt β additional option to be passed to theopensslprogram πβ--authtype β types of repositories to authenticate πͺͺ--trustfingerprint β 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 β--git-capabilitiesup=pc β protocol capabilities (pc) for a git repository URL prefix (up) πβοΈ--pagerpath β the pager program to be used to show long text π--pager-optionopt β additional option to be passed to the pager program πβ--options-filefile β read additional options from file π--default-optionsdir β the directory to load additional default options files from π--no-default-optionsβ don't load default options files π«π--keep-tmpβ don't remove thebpkg's temporary directory at the end of the command execution, and print its path at the verbosity level2or higher ποΈπ«
π DEFAULT OPTIONS FILES π
see bpkg-default-options-files(1) for the whole overview of default options files π
for the pkg-verify command, these options files get searched for in the predefined directories (system, etc) and, if they're found, they're loaded in this exact order:
bpkg.options
bpkg-pkg-verify.options
π BUGS π
found a bug? send those bug reports to the users@build2.org mailing list π§ (be nice to them, they're doing their best π«Ά)
π COPYRIGHT π
Copyright (c) 2014-2024 the build2 authors.
Permission is granted to copy, distribute and/or modify this document under the terms of the MIT License.
and that's the whole page bestie!! π this was bpkg 0.17.0, dated June 2024, brought to you by the build2 girlies β¨ stay verified, stay valid, and remember: an empty file is NOT it. periodt π
πΈ
π¦ where this page comes from
- fedora 43: bpkg 0.17.0-5.fc43 Β· MIT
- fedora 44: bpkg 0.17.0-7.fc44 Β· MIT
- nixos 26.05: bpkg 0.17.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms