Boneyarding Metalua

Proposing that we toss Metalua into the boneyard. Reasons:

1) It is hard-coded to look for Lua & Luac binaries, which are
obviously now pointing at Lua (5.2). I tried tweaking those hard-coded
lines with inreplace and had some success, but it still broke on
finding Luac. It complies ‘successfully’, but it won’t do very much.

2) There’s been no stable Metalua release for 5 years.

3) The HEAD build hasn’t worked in at least 8 months because the github
has moved away from compile scripts in favour of becoming Luarocks.

4) Honestly, interest in Metalua seems to be pretty low. If nobody has
noticed the HEAD build has been dead for 8 months…?

I feel like we’d be better scrapping this and pointing people at the
new Luarocks available for Metalua, which are on versions 0.7.2-1
compared to our shipped 0.5-rc2.
hevea 2.18

Also: add test, fix prefix.
hevea: add 2.18 bottle.

Closes #32434.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
hevea: reported inreplace upstream.
libpst: deparallelize install
libpst: update 0.6.55 bottle.

Closes #32469.

Signed-off-by: Tim D. Smith <git@tim-smith.us>
Stop recording the fails_with cause internally

The string passed as the cause is currently unused, so we don't need to
actually store it.
wine: fix build on 10.7 under superenv
syncthing 0.9.17
syncthing: update 0.9.17 bottle.

Closes #32458.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
libsodium 0.7.1
libsodium: update 0.7.1 bottle.

Closes #32477.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
keybase 0.6.2
keybase: add 0.6.2 bottle.

Closes #32476.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
Revert "keybase: add 0.6.2 bottle."

This reverts commit 454930c4d8d24729692e6ef3d12e5406d49b2ed0.
PyPy 2.4.0 with setuptools 5.8

Closes #32479.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
libuv 1.0.0-rc1 (devel)

Closes #32478.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>