The limitation was added in 3c6e6607 because Debian at the time didn't
had the required minimum version of the Connector/C. Now it has.

For programmatically managing Transmissions using Python. Exciting.

There's no repository so I download the package from the GitHub release.
It maybe a little better from the worked around build process, less
code, less fragile and probably a little faster to build.

I wasn't too happy with having another package manager (APT and the
language specific managers seemed enough) and there security issues when
running as a regular user. Before running it for the first time as root
worked and I didn't it need afterwards. Now however, it refuses to even
run once.

Build the go binary from source. It's more complex than just go get or
go install, see https://github.com/kubernetes/kompose/issues/1472 from
more information. This the last Homebrew package. Now to remove
Homebrew.

Buid the go binary. Leaving just one last package from Homebrew. It's
days are numbered!

go get is being deprecated in favor of go install and modules. Run go
get commands before setting GO111MODULE.

Build the Go binary. And another Homebrew package is removed.

Requires their package from kubectl. Another Homebrew item removed.

Build the Go binary. One less thing using Homebrew.

The fix is installing the ca-certificates package before adding the
source files. Doing that would make the 2 build stages close enough that
it doesn't make sense anymore to have 2 build stages.

Try to disable GitLab runner's umask fiddling and see if that works (it
might, you don't know).

- Don't use the builddeps image since it no longer tracks Debian
  testing. Use the same image in all stages of the build (save some
space).
- Install gnupg and curl in the stage that fetches the repos keys.
- Merge the APT installs in the final build stage. There's no need to
  install anything before running apt-get update (once the files are in
place).
- A little nicer handling of GPG keyrings (stole from the Datadog agent
  installation instructions).

I only added to mimic the kbfs mount in MacOS because smile-cli
depended on it but I've since removed Keybase from that utility
completely so it's no longer needed.

When I added the `|| true` to different Keybase utilities builds, it
applied to all of the previous commands which is not what I wanted. Wrap
them in curly brackets to get the behavior I wanted.

Package was removed from Debian and its suggested replacement is tnftp.

I have a plan to run a remote atd and add some aliases for remote
wrappers to at, atq and atrm. This image will be the image for atd
(along with the regular workbench) so running commands remotely will
have all of the tools ready.

- Replace go get with go install since that's the new blessed way of
  doing things (IIUC go get is going to be deprecated eventually). Don't
change for reg since that fails to build with go install.
- Ignore failure to build keybase and kbfs. It's some Golang dependency
  issue and right now it seems like we're moving away from Keybase
altogether in work so I'm not going to invest time trying to fix this.

Replace it from buildpack-deps to Debian. I don't know why, but there's
no image for Debian testing (currently Bookworm). With
buildpack-deps:testing you get Debian Bullseye (currently stable). I'm
guessing that Docker no longer builds the Debian testing variant for
that image (I missed that memo) and I'm getting the last build for that
image.

With https://github.com/cloudposse/packages/issues/1622 fixed for over 6
weeks now, I think it's safe to remove the workaround.

Add the AWS RDS instances certificate authority so that secure access is
verified with all of the tools.