| Age | Commit message (Collapse) | Author |
|
|
|
Fail if the start or end commit are missing and retry finding the
previous tag by fetching all tags if they are missing.
This should fix CI on the current Homebrew/brew `master` branch.
Closes #2404.
|
|
|
|
|
|
The structure should be consistent, so there are always pinned and
pinned_version fields even if there are no pinned versions for a given formula.
|
|
|
|
Split the tests up into quiet and verbose output with contexts.
|
|
Call an explicit method on Installer to reinstall rather than using a
flag to indicate when we're reinstalling a cask
|
|
|
|
If we're adding a versioned formulae we want to ensure that there's also
an unversioned one too.
|
|
Check the remote for homebrew/core as well as homebrew/brew as we've
seen a few cases (e.g. #2387) where it was misconfigured.
While we're here, tweak the messaging to tell people what to do and how
to do so with a single command.
|
|
updating the exception for "kibana" for the "@" naming scheme. File changed: audit.rb
|
|
- Remove taps that are (or will shortly be) deprecated.
- Remove commands that are only relevant to the boneyard (which will
shortly be removed).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
pull: warn (not die) on bottle publish failure.
|
|
Rather than just checking if a requirement's dependency is installed or
not check if the requirement was actually satisfied by a particular
formula rather than e.g. just having a `default_formula` defined.
|
|
ilovezfs/migrator-allow-new-cellar-to-exist-already
migrator: allow new cellar to exist already
|
|
gpg: add GnuPG series 2.1.x to supported versions
|
|
Lets us migrate a formula to a name that may have previously been used.
If gnupg 1.x is installed as "gnupg" and gnupg 2.x is installed as
"gnupg2," it's currently not possible to rename gnupg2 -> gnupg, since
the 1.4 keg will already be installed in the "gnupg" Cellar, so in order
to reclaim the name "gnupg" to be used for 2.1, either 1.x must be
manually uninstalled, or the new cellar needs to be allowed to exist
already.
|
|
link: tell users of `brew link --force` about opt.
|
|
This is useful when you're pulling PRs where individual bottles can't be
uploaded/built but you still want to pull the PR as a whole anyway.
|
|
If people are force-linking keg-only things they should probably be told
that they can add the opt prefix to their PATH instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
man: generate Markdown man page.
|
|
The existing `brew.1.html` wasn't particularly pleasant to read and
given everything else in `docs/` is a Markdown file it makes sense to
generate a post-processed Markdown file that can in turn be used by
Jekyll to generate a nicely themed HTML file.
|
|
Ensure the full HOMEBREW_TAP_DIR path is created before deleting and
creating the symlink for it. This ensures that non-`homebrew` taps will
have the necessary username/organisation folder created.
Fixes #2378.
|
|
Check if `HOMEBREW_CELLAR/old_name` is a symlink. If so, it's already
been migrated so can be skipped.
|
|
tests: unset HOMEBREW_TEMP
|
|
Hint at new location of migrated formulae
|
|
Setting `HOMEBREW_TEMP` env. var [currently] breaks tests (`brew
tests`). Although this behavior looks like a bug, the solution is
straightforward: unset `HOMEBREW_TEMP`.
|
|
formula_installer: need up to date requirement formulae.
|
|
audit: check system dupe deps on new formulae.
|
|
audit: deprecate depends_on :tex.
|
|
update-report: migrate all formulae every time.
|
|
These methods belong together so combine them in a single class to
provide a simpler API.
|
|
This will allow extending this class so it can be used by more than
just blacklisting.
|
|
This wasn’t adapted to the new, multiple repository world.
|
|
|
|
This makes it easier to turn an arbitrary path into a tap path.
|