graphicsmagick 1.3.20
graphicsmagick: add 1.3.20 bottle.

Closes #32004.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
imagemagick 6.8.9-7
imagemagick: update 6.8.9-7 bottle.

Closes #32002.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
sqlitebrowser 3.3.1

database browser 3.3.1 for sqlite

New version to reflect the project being renamed upstream. ;)
sqlitebrowser: update 3.3.1 bottle.

Closes #32005.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
node: npm bump, devel killed, npm update change.

Okay, this is part 1 of what will likely become a host of wider changes
I propose on Node to tackle the issues discussed in
[#31777](https://github.com/Homebrew/homebrew/issues/31777).

Part 1: I’ve killed the devel build. It hasn’t been updated since May,
and Node haven’t expressed any sort of haste in issuing even a new
minor bump to the devel build that fixes the rather large [OpenSSL
vulnerabilities](https://github.com/joyent/node/tree/v0.11.13-release/de
ps/openssl/openssl) in 0.11.13. At this point, my feeling is that it’s
dangerously irresponsible to leave the devel build present given those
vulnerabilities, and I’d like to see us scrap it until we see some
movement on patching those issues. This issue is open with Node
[here](https://github.com/joyent/node/issues/8000) but remains largely
ignored and dormant.

Second change: Bumps the npm version that we ship back to the latest
stable release. A minor thing, but an early step towards fixing some of
the bigger npm problems.

Third change: Changes the way we handle npm updates post-install to
specifically target the latest stable release. Our current ``` npm
update npm -g ``` has been habitually dumping people onto the alpha &
beta builds for npm, and this solution (according to the npm team)
should solve that problem permanently. Having done local testing with
this, It does indeed seem to do the job.

These are largely minor fixes to patch things over in a stable, solid
fashion till I can work out ways to avoid the Node issues we’ve been
encountering so rampantly lately.
node: update 0.10.31 bottle.

Closes #31914.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
node: don't use user npmrc.
Lua: Lua => Lua51

See [this](https://github.com/Homebrew/homebrew/pull/29236) PR for more
details. This is step 1 described in
[this](https://github.com/Homebrew/homebrew/pull/29236#issuecomment-5397
1789) comment.
Lua => Lua51

Fixes the test calling Lua without the version stopper.
Lua => Lua51

Cleans it up a bit.
Lua => Lua51

This is pretty much a test. I’m hoping by bumping the pkg-config I can
get the bot to automatically find the new lua library location. If that
doesn’t work might have to look at manually specifying where the new
lua libraries are for each affected formula, eek.
Lua => Lua51

Expecting this build to very probably fail still, but this update
allows Lua51 to be compiled alongside Lua52 and for both of them to be
linked without conflict. I’ve also reverted cardpeek because that’s
been massively changed and now needs its own PR, which I’ll do in a
second.
Lua => Lua51

I say this very nervously, but this one might, might, might just pass
the build bot.
Lua => Lua51

It is *super* annoying that software varies wildly between looking for
lua5.1 and lua-5.1. This commit includes an extra dose of symlinking to
get around different software looking for the same package both with
and sans hyphen.
Lua => Lua51

Yet another symlink to fix one of the formulas looking for
liblua5.1.dylib instead of liblua.5.1.dylib.
Lua => Lua51

This should finally be the one that passes. I’m mildly confident.
Lua => Lua51

Whitespacing. Darn whitespacing.
Lua => Lua51

These two lines were completely screwing up the placement of the lib
directory. I think given the dylib renaming, this might not be
necessary any more.