bpkg-pkg-verify(1)

πŸ“¦
version 0.17.0 Β· 2 versions
, in fedora 43, fedora 44, nixos 26.05

✨ 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 *-build values/files are actually present in the manifest/archive 🧚
  • the files referenced by the *-file manifest 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 *-build values/files are present, and check that files referenced by the *-file manifest values are actually valid.
  • --ignore-unknown β€” ignore unknown manifest entries 🫢 by default bpkg refuses 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 --deep is also on, then in the resulting manifest: the *-file values get replaced with the contents of the referenced files, the *-build values 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 🀐
  • --verbose level β€” set the diagnostics verbosity to level between 0 and 6 🎚️
  • --stdout-format format β€” representation format to use for printing to stdout πŸ’¬
  • --jobs, -j num β€” 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-result fmt β€” 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 🚫🌈
  • --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 πŸ“₯βž•
  • --fetch-timeout sec β€” the fetch and fetch-like (for example, git) program timeout ⏰
  • --pkg-proxy url β€” HTTP proxy server to use when fetching package manifests and archives from remote pkg repositories 🌐
  • --git path β€” the git program to be used to fetch git repositories πŸ™
  • --git-option opt β€” additional common option to be passed to the git 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 ❌
  • --git-capabilities up=pc β€” protocol capabilities (pc) for a git repository URL prefix (up) πŸ™βš™οΈ
  • --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 πŸ“„
  • --default-options dir β€” the directory to load additional default options files from πŸ“
  • --no-default-options β€” don't load default options files πŸš«πŸ“
  • --keep-tmp β€” don't remove the bpkg's temporary directory at the end of the command execution, and print its path at the verbosity level 2 or 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 (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