OPAM-REINSTALL(1)

📦
version 2.6.1 · 8 versions
, in arch rolling, fedora 44

✨ opam-reinstall ✨

the one and only — straight out of the Opam Manual, bestie 🫶

🌸 NAME 🌸

opam-reinstall — reinstall a whole lil list of packages, no biggie 💅

🦋 SYNOPSIS 🦋

opam reinstall [OPTION]… [PACKAGES]…

🌈 DESCRIPTION 🌈

okay so picture this: this command removes the packages you named plus every package that depends on them, and then reinstalls the exact same versions. like a glow-up that ends up looking identical. iconic honestly ✨

If you give it no arguments at all? It just assumes --pending and reinstalls any package that has upstream changes. surprise reinstall, no warning, main character energy 👑

And if you pass a directory as an argument, then literally anything pinned to that directory gets selected for reinstall. directory = the vibe check 🎀

🍓 ARGUMENTS 🍓

  • PACKAGES — a list of package names, and you may tack on a version or a constraint, like pkg, pkg.1.0 or pkg>=0.5 💖 Orrrr they can be directory names containing a package description, as long as you name the directory explicitly (think ./srcdir or just .)

💅 OPTIONS 💅

  • --assume-built — for locally-pinned packages only: assume they're already built correctly and just run their installation instructions straight from their source directory. It skips the build instructions entirely, which is super handy when you're installing packages you're actively working on. Implies --inplace-build. And nope, no locally-pinned package gets skipped. not one 🫶
  • --forget-pending — forget about pending reinstallations of the packages you listed. Real talk though: this implies making opam assume your packages were installed with a newer version of their metadata, so only touch this if you genuinely know what you're doing and you know the actual changes you're overriding. hotter take: it may be safer to run opam pin --current on the packages with pending reinstalls and explicitly lock them into their current state 🔒
  • --list-pending — just lists the packages that have changed since they were installed and are marked for reinstallation. window shopping, but for reinstalls 🛍️
  • --pending — actually performs the pending reinstallations, i.e. reinstalls packages that changed since they were installed
  • --recursive — allows recursive lookups of *.opam files. Cf. --subpath too 👀
  • --subpath=PATH — *.opam files get retrieved from the given sub directory instead of the top directory. Sources then come from that targeted sub directory, and internally only this subdirectory is copied/fetched. You can team it up with --recursive to get a recursive lookup on the subpath 🧚

🔥 PACKAGE BUILD OPTIONS 🔥

  • --assume-depexts — skip the installation step for any missing system packages and try to push through with compiling the opam packages anyway. If the install succeeds, opam won't nag you about those system packages again. Only meaningful if external dependency handling is enabled ⚠️
  • -b, --keep-build-dir — keep the build directories around after compiling packages. Equivalent to setting $OPAMKEEPBUILDDIR to "true" 📦
  • --build-doc — Removed in 2.1, use --with-doc instead. gone bestie, rip 💀
  • --build-test — Removed in 2.1, use --with-test instead. also gone 😭
  • -d, --with-doc — build the package documentation. This only affects packages listed on the command-line. Equivalent to setting $OPAMWITHDOC (or the deprecated $OPAMBUILDDOC) to "true" 📚
  • --dry-run — simulate the command without actually performing any changes. Can also be set with the environment variable $OPAMDEBUG. delulu edition, nothing really happens 🫧
  • --fake — registers the actions into the opam database without actually performing them. ⚠️ WARNING: this option is dangerous and likely to break your opam environment. You probably want --dry-run. You've been warned. not me telling you twice 💀
  • --ignore-available-on[=PACKAGES] (default=) — forces opam to mark the listed packages as available. You can use this to test compatibility, but expect builds to break when you do. Note that version constraints of the packages' dependencies are unaffected 🔧
  • --ignore-constraints-on[=PACKAGES] (default=) — forces opam to ignore version constraints on all dependencies of the listed packages. Good for compatibility testing, but again: expect builds to break. Note that the availability of the packages, as well as version constraints on optional dependencies and conflicts, are unaffected. Equivalent to setting $OPAMIGNORECONSTRAINTS
  • --inplace-build — when compiling a package whose source is bound to a local directory, process the build and install actions directly in that directory instead of in a clean copy handled by opam. Only affects packages explicitly listed on the command-line. Equivalent to setting $OPAMINPLACEBUILD to "true" 🏠
  • -j JOBS, --jobs=JOBS — set the max number of concurrent jobs to use. The default is calculated from the number of cores. You can also set it with the $OPAMJOBS environment variable ⚡
  • --lock-suffix=SUFFIX (absent=locked) — set the locked files suffix to SUFFIX
  • --locked — in commands that use opam files found from pinned sources, if a variant of the file with an added .locked extension exists (e.g. foo.opam.locked alongside foo.opam), that one gets used instead. Typically useful for offering a more specific set of dependencies and reproducing similar build contexts — hence the name. The lock option can generate such files based on the versions of the dependencies currently installed on the host. Equivalent to setting the $OPAMLOCKED environment variable. Note that this option doesn't generally affect already pinned packages 🔐
  • -m MAKE, --make=MAKE — Removed in 2.1, use opam config set[-global] make MAKE instead 😭
  • --no-checksums — do not verify the checksum of downloaded archives. Equivalent to setting $OPAMNOCHECKSUMS to "true" 🙈
  • --no-depexts — temporarily disables handling of external dependencies. Use this if a package isn't available on your system package manager but you installed the required dependency by hand. Implies --assume-depexts, and stores the exceptions upon success as well ✂️
  • --require-checksums — reject installation of packages that don't provide a checksum for the upstream archives. Equivalent to setting $OPAMREQUIRECHECKSUMS to "true" ✅
  • --reuse-build-dir — reuse existing build directories (the ones you kept with --keep-build-dir) instead of compiling from a fresh clone of the source. Faster, sure, but it can also lead to failures if the build systems of the packages don't handle upgrades of dependencies well. Equivalent to setting $OPAMREUSEBUILDDIR to "true" ♻️
  • --show-actions — call the solver and display the actions. Perform no changes whatsoever. Equivalent to setting $OPAMSHOW 👀
  • --skip-updates — when running an install, upgrade or reinstall on source-pinned packages, they're normally updated from their origin first. This flag disables that behaviour and keeps them at their cached version. Equivalent to setting $OPAMSKIPUPDATE ⏭️
  • -t, --with-test — build and run the package unit-tests. Only affects packages listed on the command-line. Equivalent to setting $OPAMWITHTEST (or the deprecated $OPAMBUILDTEST) to "true" 🧪
  • --unlock-base — Removed in 2.1, use --update-invariant instead 💀
  • --update-invariant — allow changes to the set of packages set as switch base (typically, the main compiler). Use with caution ⚠️ Equivalent to setting the $OPAMUNLOCKBASE environment variable
  • --verbose-on=PACKAGES — be more verbose on specific packages. Equivalent to setting $OPAMVERBOSE 🗣️
  • --with-dev-setup — include development tools only dependencies 🛠️

✨ COMMON OPTIONS ✨

okay bestie, these ones? literally every single opam command has them 💅 they're the universal group-chat members. let's go 🫶

  • --best-effort — don't just give up when some of the packages you asked for won't install 😭 try to install as many as you possibly can. heads up tho: not all external solvers support this (recent versions of aspcud or mccs should, no cap). it's the same as setting the $OPAMBESTEFFORT environment variable ✨
  • --cli=MAJOR.MINOR (absent=2.6) — use the command-line interface syntax and semantics of MAJOR.MINOR. this one's for anything persistent you do with opam (scripts, blog posts, etc. — yes bestie, blog posts), because any version of opam in the same MAJOR series will behave like the MINOR release you specified 💖. fun fact: this flag didn't exist in opam 2.0, so if you want the 2.0 CLI you gotta set the OPAMCLI environment variable to 2.0 instead of using this param 🙈
  • --color=WHEN — colorize the output 🌈 WHEN has to be one of always, never or auto.
  • --confirm-level=LEVEL — the confirmation level, where LEVEL must be one of ask, no, yes or unsafe-yes. you can pass it more than once 🔁 if --yes or --no are also given, then the value of the last --confirm-level wins. this is equivalent to setting $OPAMCONFIRMLEVEL 💜
  • --criteria=CRITERIA — set your user preferences for dependency solving, just for this run 👑 overrides $OPAMCRITERIA, $OPAMFIXUPCRITERIA and $OPAMUPGRADECRITERIA. for the deets on the supported language and the external solvers available, go peek at http://opam.ocaml.org/doc/External_solvers.html 📚 and there's a whole general guide to using solver preferences at http://www.dicosmo.org/Articles/usercriteria.pdf 🧚
  • --cudf=FILENAME — debug option 🐛 saves the CUDF requests sent to the solver into FILENAME-<n>.cudf, where <n> is the n-th call to the solver during the opam run.
  • --debug — print debug messages to stderr. equivalent to setting $OPAMDEBUG to "true" 💀
  • --debug-level=LEVEL — like --debug, but you get to pick the debug level (--debug just sets it to 1). equivalent to setting $OPAMDEBUG to a positive integer ✨
  • --git-version — print the git version of opam, if it's set (i.e. you're running a development version), then exit 🏃‍♀️
  • --help[=FMT] (default=auto) — show this help in format FMT 💖 where FMT must be one of auto, pager, groff or plain. with auto, the format is pager or plain whenever the TERM env var is dumb or undefined 🫶
  • --ignore-pin-depends — ignore the extra pins required by packages that get pinned, whether you did it manually through opam pin or through opam install DIR 📌 equivalent to setting IGNOREPINDEPENDS=true.
  • --json=FILENAME — save the results of the opam run into a computer-readable file 🤖 if the filename contains the character `%', it gets replaced by an index that won't overwrite an existing file. similar to setting the $OPAMJSON variable ✨
  • --no — answer no to every opam yes/no question, no prompting needed 🙅‍♀️ see also --confirm-level. this is equivalent to setting $OPAMNO to "true".
  • --no-aspcud — removed in 2.1 💀 she's gone bestie, don't come looking.
  • --no-auto-upgrade — when configuring or updating a repository that was written for an earlier opam version (1.2), opam internally converts it to the current format 🌀 this disables that behaviour. note: repositories should define their format version in a 'repo' file at their root, or they'll be assumed to be in the older format 👀 it's, in any case, preferable to upgrade the repositories manually using opam admin upgrade [--mirror URL] when possible 💅
  • --no-self-upgrade — opam will replace itself with a newer binary found at OPAMROOT/opam if present 🔄 this disables that behaviour.
  • -q, --quiet — disables --verbose 🤫
  • --root=ROOT — use ROOT as the current root path. equivalent to setting $OPAMROOT to ROOT 🌳
  • --safe, --readonly — make sure nothing gets automatically updated or rewritten 🛑 super useful for calling from completion scripts, for example. will fail whenever such an operation is needed; also avoids waiting for locks, skips interactive questions and overrides the $OPAMDEBUG variable. this is equivalent to setting the environment variable $OPAMSAFE 🫶
  • --solver=CMD — specify the CUDF solver to use for resolving package installation problems 🧩 this is either a predefined solver (this version of opam supports builtin-mccs+lp(), builtin-mccs+glpk, builtin-dummy-z3-solver, builtin-0install, aspcud, mccs, aspcud-old, packup), or a custom command that should contain the variables %{input}%, %{output}%, %{criteria}%, and optionally %{timeout}%. equivalent to setting $OPAMEXTERNALSOLVER ✨
  • --strict — fail whenever an error is found in a package definition or a configuration file 😤 the default is to just continue silently if possible 🤐
  • --switch=SWITCH — use SWITCH as the current compiler switch. equivalent to setting $OPAMSWITCH to SWITCH 🎚️
  • --use-internal-solver — disable any external solver and use the built-in one instead (this requires that opam has been compiled with a built-in solver 👀). equivalent to setting $OPAMNOASPCUD or $OPAMUSEINTERNALSOLVER 💜
  • -v, --verbose — be more verbose 🗣️ one -v shows all package commands, and repeating it also displays commands called internally (e.g. tar, curl, patch etc.). repeating it n times is equivalent to setting $OPAMVERBOSE to "n" 🌸
  • --version — show version information 🏷️
  • -w, --working-dir — whenever updating packages that are bound to a local, version-controlled directory, update to the current working state of their source instead of the last committed state, or the ref they're pointing to 🌿 since the source directory gets copied as-is, if it isn't clean it may result in an opam build failure 💀 this only affects packages explicitly listed on the command-line. can also be set with $OPAMWORKINGDIR ✨
  • -y, --yes — answer yes to all opam yes/no questions, no prompting 🥳 see also --confirm-level. equivalent to setting $OPAMYES to "true" 💖

🌈 ENVIRONMENT 🌈

okay so opam lowkey reads a whole bunch of environment variables and you're gonna want to know them all. here's the tea:

Booleans, bestie — set them to 0, no, false or the empty string to turn them off, and 1, yes or true to turn them on. periodt.

  • OPAMALLPARENS — surround all filters with parenthesis.
  • OPAMASSUMEDEPEXTS — see option --assume-depexts.
  • OPAMAUTOANSWER — internal use only 🙈 (not for you, not for me).
  • OPAMAUTOREMOVE — see remove option --auto-remove.
  • OPAMBESTEFFORT — see option --best-effort.
  • OPAMBESTEFFORTPREFIXCRITERIA — sets the string that must be prepended to the criteria when the --best-effort option is set, and is expected to maximise the opam-query property in the solution.
  • OPAMBUILDDOC — removed in 2.1 💀.
  • OPAMBUILDTEST — removed in 2.1 💀.
  • OPAMCLI — see option --cli.
  • OPAMCOLOR — when set to always or never, sets a default value for the --color option.
  • OPAMCONFIRMLEVEL — see option --confirm-level. OPAMCONFIRMLEVEL has priority over OPAMYES and OPAMNO. 👑
  • OPAMCRITERIA — specifies user preferences for dependency solving. The default value depends on the solver version, so use config report to know the current setting. See also option --criteria.
  • OPAMCUDFFILE — save the cudf graph to file-actions-explicit.dot.
  • OPAMCUDFTRIM — controls the filtering of unrelated packages during CUDF preprocessing.
  • OPAMCURL — can be used to select a given 'curl' program. See OPAMFETCH for more options.
  • OPAMDEBUG — see options --debug and --debug-level.
  • OPAMDEBUGSECTIONS — if set, limits debug messages to the space-separated list of sections. Sections can optionally have a specific debug level (for example, CLIENT:2 or CLIENT CUDF:2), but otherwise use --debug-level.
  • OPAMDIGDEPTH — defines how aggressive the lookup for conflicts during CUDF preprocessing is.
  • OPAMDOWNLOADJOBS — sets the maximum number of simultaneous downloads.
  • OPAMDROPWORKINGDIR — overrides packages previously updated with --working-dir on update. Without this variable set, opam would keep them unchanged unless explicitly named on the command-line.
  • OPAMDRYRUN — see option --dry-run.
  • OPAMEDITOR — sets the editor to use for opam file editing, overrides $EDITOR and $VISUAL. 💅
  • OPAMERRLOGLEN — sets the number of log lines printed when a sub-process fails. 0 to print all.
  • OPAMEXTERNALSOLVER — see option --solver.
  • OPAMFAKE — see option --fake.
  • OPAMFETCH — specifies how to download files: either wget, curl or a custom command where variables %{url}%, %{out}%, %{retry}%, %{compress}% and %{checksum}% will be replaced. Overrides the 'download-command' value from the main config file.
  • OPAMFIXUPCRITERIA — same as OPAMUPGRADECRITERIA, but specific to fixup and reinstall.
  • OPAMIGNOREAVAILABLE — see install option --ignore-available-on.
  • OPAMIGNORECONSTRAINTS — see install option --ignore-constraints-on.
  • OPAMIGNOREPINDEPENDS — see option --ignore-pin-depends.
  • OPAMINPLACEBUILD — see option --inplace-build.
  • OPAMJOBS — sets the maximum number of parallel workers to run.
  • OPAMJSON — log json output to the given file (use character % to index the files).
  • OPAMKEEPBUILDDIR — see install option --keep-build-dir.
  • OPAMKEEPLOGS — tells opam to not remove some temporary command logs and some backups. This skips some finalisers and may also help to get more reliable backtraces.
  • OPAMLOCKED — combination of --locked and --lock-suffix options.
  • OPAMLOGS — logdir sets log directory, default is a temporary directory in /tmp.
  • OPAMMAKECMD — set the system make command to use.
  • OPAMMERGEOUT — merge process outputs, stderr on stdout.
  • OPAMNO — answer no to any question asked, see options --no and --confirm-level. OPAMNO is ignored if either OPAMCONFIRMLEVEL or OPAMYES is set.
  • OPAMNOAGGREGATE — with opam admin check, don't aggregate packages.
  • OPAMNOASPCUD — deprecated 🚫.
  • OPAMNOAUTOUPGRADE — disables automatic internal upgrade of repositories in an earlier format to the current one, on update or init.
  • OPAMNOCHECKSUMS — enables option --no-checksums when available.
  • OPAMNODEPEXTS — disables system dependencies handling, see option --no-depexts.
  • OPAMNOENVNOTICE — internal 🔒.
  • OPAMNOSELFUPGRADE — see option --no-self-upgrade.
  • OPAMPINKINDAUTO — sets whether version control systems should be detected when pinning to a local path. Enabled by default since 1.3.0.
  • OPAMPRECISETRACKING — fine grain tracking of directories.
  • OPAMPREPRO — set this to false to disable CUDF preprocessing. Less efficient, but might help debugging solver issue.
  • OPAMREPOSITORYTARRING — internally store all non-vcs repositories as tar.gz files (by default, http repositories are stored as archive). This can be much faster on filesystems that don't cope well with scanning large trees. All operation are done in-memory, no I/O for scanning the repository.
  • OPAMREQUIRECHECKSUMS — enables option --require-checksums when available (e.g. for opam install).
  • OPAMRETRIES — sets the number of tries before failing downloads.
  • OPAMREUSEBUILDDIR — see option --reuse-build-dir.
  • OPAMROOT — see option --root. This is automatically set by opam env --root=DIR --set-root.
  • OPAMROOTISOK — don't complain when running as root.
  • OPAMSAFE — see option --safe.
  • OPAMSHOW — see option --show.
  • OPAMSKIPUPDATE — see option --skip-updates.
  • OPAMSKIPVERSIONCHECKS — bypasses some version checks. Unsafe, for compatibility testing only. ⚠️
  • OPAMSOLVERALLOWSUBOPTIMAL — (default true) allows some solvers to still return a solution when they reach timeout; while the solution remains assured to be consistent, there is no guarantee in this case that it fits the expected optimisation criteria. If true, opam will continue with a warning, if false a timeout is an error. Currently only the builtin-z3 backend handles this degraded case.
  • OPAMSOLVERTIMEOUT — change the time allowance of the solver. Default is 60.0, set to 0 for unlimited. Note that all solvers may not support this option.
  • OPAMSOLVERTOLERANCE — changes the tolerance towards the solver choosing an unoptimized solution (i.e. might pull outdated packages). Typical values range from 0.0 (best solution known to the solver) to 1.0 (unoptimized solution). Default is 0.0. This option is useful in case the solver can't find a solution in a reasonable time (see $OPAMSOLVERTIMEOUT). Note that all solvers may not support this option.
  • OPAMSTATS — removed in 2.4 💀.
  • OPAMSTATUSLINE — display a dynamic status line showing what's currently going on on the terminal. (one of one of always, never or auto)
  • OPAMSTRICT — fail on inconsistencies (file reading, switch import, etc.).
  • OPAMSWITCH — see option --switch. Automatically set by opam env --switch=SWITCH --set-switch.
  • OPAMUNLOCKBASE — see install option --unlock-base.
  • OPAMUPGRADECRITERIA — specifies user preferences for dependency solving when performing an upgrade. Overrides OPAMCRITERIA in upgrades if both are set. See also option --criteria.
  • OPAMUSEINTERNALSOLVER — see option --use-internal-solver.
  • OPAMUSEOPENSSL — removed in 2.2 💀.
  • OPAMUTF8 — use UTF8 characters in output (one of one of always, never or auto). By default auto, which is determined from the locale.
  • OPAMUTF8MSGS — use extended UTF8 characters (camels 🐪) in opam messages. Implies OPAMUTF8. This is set by default on macOS only.
  • OPAMVALIDATIONHOOK — if set, uses the %{hook}% command to validate an opam repository update.
  • OPAMVERBOSE — see option --verbose.
  • OPAMVERBOSEON — see option --verbose-on.
  • OPAMVERSIONLAGPOWER — do not use. 🙅
  • OPAMWITHDEVSETUP — see install option --with-dev-setup.
  • OPAMWITHDOC — see install option --with-doc.
  • OPAMWITHTEST — see install option --with-test.
  • OPAMWORKINGDIR — see option --working-dir.
  • OPAMYES — see options --yes and --confirm-level. OPAMYES has priority over OPAMNO and is ignored if OPAMCONFIRMLEVEL is set.
  • OPAMVAR_var — overrides the contents of the variable var when substituting %{var}% strings in opam files.
  • OPAMVAR_package_var — overrides the contents of the variable package:var when substituting %{package:var}% strings in opam files.

🦋 CLI VERSION 🦋

okay this part matters, bestie, listen up 📢

All scripts and programmatic invocations of opam should use --cli in order to ensure that they work seamlessly with future versions of the opam client. Additionally, blog posts or other documentation can benefit, as it prevents information from becoming stale. no cap, it's giving future-proof 💅

Although opam only supports roots (~/.opam/) for the current version, it does provide backwards compatibility for its command-line interface.

Since CLI version support was only added in opam 2.1, use OPAMCLI to select 2.0 support (as opam 2.0 will just ignore it), and --cli=2.1 for 2.1 (or later) versions, since an environment variable controlling the parsing of syntax is brittle. To this end, opam displays a warning if OPAMCLI specifies a valid version other than 2.0, and also if --cli=2.0 is specified. 🫶

The command-line version is selected by using the --cli option or the OPAMCLI environment variable. --cli may be specified more than once, where the last instance takes precedence. OPAMCLI is only inspected if --cli is not given. ✨

💀 EXIT STATUS 💀

okay bestie this is the part where we talk about the numbers. the little codes that tell you what just happened. they're giving "the universe texting you in integers" and honestly? iconic.

⚠️ one exception before we start, pay attention: the exec command does NOT play by these rules. it returns 127 if the command wasn't found or couldn't be executed, and otherwise it returns the command's own exit value. that's it. that's the whole exception. don't get got. 🫶
  • 0 — Success 💖 or, for boolean queries, "true".
  • 1 — False. this one shows up when a boolean return value is expected, like when you run with --check, or for queries like opam lint.
  • 2 — Bad command-line arguments, OR command-line arguments that point at an invalid context (think: a file that doesn't follow the expected format). rude.
  • 5 — Not found. you asked for something — a package, a version, a repository, etc. — and it simply could not be found. 🕳️
  • 10 — Aborted. the operation needed confirmation and you didn't give it.
  • 15 — Could not acquire the locks required for the operation. 🔒 the locks said no.
  • 20 — There is no solution to the user request. this can happen if you ask to install two incompatible packages, for example. the math said no.
  • 30 — Error in package definition, or other metadata files. using --strict makes this error raise more often.
  • 31 — Package script error. some package operations were unsuccessful. this may be an error in the packages, or an incompatibility with your system. heads up: this can be a partial error.
  • 40 — Sync error. couldn't fetch some remotes from the network. also possibly a partial error.
  • 50 — Configuration error. opam or your system configuration doesn't allow the operation and needs fixing. 🛠️
  • 60 — Solver failure. the solver failed to return a sound answer. this can be because of a broken external solver, or an error in solver configuration.
  • 99 — Internal error. something went wrong, and it's likely a bug in opam itself. 🐛 (not your fault bestie, file it)
  • 130 — User interrupt. SIGINT was received, generally because the user pressed Ctrl+C. you did this. it's fine. ✨

and also, on top of all of that, there's this little extra set of codes:

  • 0 — on success.
  • 123 — on indiscriminate errors reported on standard error.
  • 124 — on command line parsing errors.
  • 125 — on unexpected internal errors (bugs).

📚 FURTHER DOCUMENTATION 📚

more reading, more lore: see <https://opam.ocaml.org/doc>. 💅

👑 AUTHORS 👑

the legends. the main characters. the people who built the thing you're complaining about in the group chat. show some respect bestie:

  • David Allsopp <david@tarides.com>
  • Vincent Bernardoff <vb@luminar.eu.org>
  • Raja Boujbel <raja.boujbel@ocamlpro.com>
  • Kate Deplaix <kit-ty-kate@exn.st>
  • Roberto Di Cosmo <roberto@dicosmo.org>
  • Thomas Gazagnaire <thomas@gazagnaire.org>
  • Louis Gesbert <louis.gesbert@ocamlpro.com>
  • Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
  • Anil Madhavapeddy <anil@recoil.org>
  • Guillem Rieu <guillem.rieu@ocamlpro.com>
  • Ralf Treinen <ralf.treinen@pps.jussieu.fr>
  • Frederic Tuong <tuong@users.gforge.inria.fr>

🦋 SEE ALSO 🦋

💀 BUGS 💀

found a bug? check the bug reports at <https://github.com/ocaml/opam/issues>. go forth and file, bestie, that's how the ecosystem heals. 🫶

that's a wrap on this whole page fr fr. you made it to the end, and honestly? that's main character energy. this was Opam 2.6.1, page OPAM-REINSTALL(1). go forth, reinstall, slay. periodt. 🌈✨💖

📦 where this page comes from