bpkg-rep-fetch(1)

📦
version 0.17.0 · 2 versions
, in fedora 43, fedora 44, nixos 26.05

💖 bpkg-rep-fetch(1) — the "gimme the whole package list bestie" era 💖

okay so this is a page from the General Commands Manual (bpkg section, she's that girl) and we're talking about bpkg-rep-fetch, aka the command that goes and gets you the tea on what packages exist. sit down, hydrate, let's go 🫶

✨ NAME ✨

bpkg-rep-fetch — fetch list of available packages 🌸

✨ SYNOPSIS ✨

bpkg rep-fetch|fetch [options] [(rep-name | rep-loc)...]

yes bestie, rep-fetch and fetch are the same command, it just has a nickname, iconic behavior honestly 💅

✨ DESCRIPTION ✨

so the rep-fetch command fetches the list of available packages for the repositories you named — plus all their complement and prerequisite repositories, recursively. like, it's not gonna leave the prerequisites behind, that's rude. if you don't specify any repositories at all, then it fetches all the repositories you previously added (via bpkg-rep-add(1)) to the configuration. no repo left behind, periodt ✨

the repository you wanna fetch can be given either as a repository name or as a repository location (a URL or a directory path; peek at bpkg-rep-add(1) for the deets). if you give a location, that location gets added/replaced just like you'd run the rep-add command first. sneak attack, but make it helpful 🦋

⚠️ okay lowkey important: if you fetch only one specific repository and it happens to be a prerequisite or complement of another repository that you're not fetching, you can end up with an inconsistent repository state. so like, be mindful. no cap, this is the real warning. 💀

✨ REP-FETCH OPTIONS ✨

these are the options that are just for this command, she's special like that 🎀

  • --shallow — don't re-fetch the complement and prerequisite repositories of the specified repositories unless the set of complements and/or prerequisites has actually changed. lazy in the smart way, we love efficiency 💅
  • --directory|-d _dir_ — assume the configuration lives in _dir_ instead of in the current working directory. basically "bestie she's over there, not here" 📁

✨ COMMON OPTIONS ✨

here's the whole common options situation, summarized below — and there's a fuller breakdown over in bpkg-common-options(1) if you want the extended cut 🌈

  • -v — print essential underlying commands being executed. the receipts, but only the important ones.
  • -V — print all underlying commands being executed. the full receipts, every single one, no filter 👀
  • --quiet|-q — run quietly, only printing error messages. shhh era 🤫
  • --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. multitasking queen 👑
  • --no-result — don't print informational messages about the outcome of performing a command or some of its parts. no play-by-play, just vibes.
  • --structured-result _fmt_ — write the result of performing a command in a structured form.
  • --progress — display progress indicators for long-lasting operations, such as network transfers, building, etc. loading bar ASMR ✨
  • --no-progress — suppress progress indicators for long-lasting operations, such as 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. automatic yes girl 💅
  • --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. leaving the temp folder there like a little souvenir 🎀

✨ DEFAULT OPTIONS FILES ✨

head to bpkg-default-options-files(1) for the whole overview of default options files, bestie. for the rep-fetch command specifically, the search start directory is the configuration directory. the following options files get searched for in each directory and, if found, loaded in the order listed:

bpkg.options
bpkg-rep-fetch.options

and these rep-fetch command options cannot be specified in the default options files:

  • --directory|-d

soz, that one's not allowed in there 🙈

✨ BUGS ✨

send bug reports to the users@build2.org mailing list. they're nice, they wanna hear from you 🐛💌

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!! you now know everything bpkg-rep-fetch knows 💜

okay final cute sign-off moment: this whole thing is bpkg 0.17.0, dated June 2024, and yes it's bpkg-rep-fetch(1) — go forth and fetch those package lists, you absolute legend 👑✨🎀

📦 where this page comes from