Carlo Cabrera

> I'd rather spend my limited time at the moment fixing up whatever issues there are with bootstrapping without `git` because that does work but seems to need polishing. We...

> Should we blanket fail for `HOMEBREW_INSTALL_FROM_API` when the linux version is not Ubuntu 22.04 or is there a way to detect which formulae would cause this? We may be...

I'd like to avoid creating these at all, but, yes, these should be unversioned `gcc` if we have to. If/when enough bottles are rebuilt with #13659, we could even probably...

> A future nice-to-have would be to use the tag `x86_64_linux` for bottles that depend on neither Glibc nor GCC. I think we've got some of those already; they're tagged...

No objections, though given recent revelations about Ubuntu 22.04 runtime libraries, most (but not all) rebuilding is no longer needed.

Looks like we have 89 formulae that have licenses that are neither `isOsiApproved` nor `isFsfLibre`. We can do one (or possibly multiple) of the following: 1. Make this check `--strict`,...

> Looks like we have 89 formulae that have licenses that are neither `isOsiApproved` nor `isFsfLibre`. Additionally, some of these formulae have multiple licenses, and may have an `any_of:` that...

This seems like a bug report and not a feature request. What is the output of `brew config` and `brew doctor`?

> Failed upgrades of packages should not trigger removal of old version making the system useless. `node` seemed to install just fine, despite the noisy error messages, though. Which formulae...

The `[email protected]` dependency is recorded in the tab, because it had that dependency when the bottle was poured. It doesn't have that anymore, but `brew` currently doesn't know how to...