Create repositories for distributing .rpm and .deb packages of earthly for linux users

[alexcb]

We have .rpm and .deb packages distributed by our own yum and apt repos.

See https://docs.earthly.dev/docs/misc/alt-installation#installing-from-earthly-repositories for instructions on setting up our repos.

If you run into any issues, please leave feedback in this ticket.

[alexcb]

autocompletion fails when switching from curl-based install to deb-based install

To work around this, run:

sudo rm /usr/local/share/zsh/site-functions/_earthly
sudo rm /usr/share/bash-completion/completions/earthly
sudo earthly bootstrap

We will fix the deb packages to address this post-install issue.

[rrjjvv]

A peer attempted an earthly install via yum, and I noticed a couple minor issues. This is not our standard installation mechanism, so this is probably the first time and last time we'll ever encounter this, but figured you may still want the feedback.

1. An initial install results in a (non-fatal) error:

<snip>
Running transaction
  Installing : earthly-0.6.28-1.x86_64                                                                                                                                                                                                        1/1 
/var/tmp/rpm-tmp.ck9Gwu: line 23: syntax error: unexpected end of file
warning: %post(earthly-0.6.28-1.x86_64) scriptlet failed, exit status 2
Non-fatal POSTIN scriptlet failure in rpm package earthly-0.6.28-1.x86_64
<snip>

The root cause is fairly straightforward; the block isn't terminated:

earthly/release/yum-repo/earthly.spec

Lines 44 to 46 in 1700511

	if ! docker info 2>/dev/null >/dev/null
	%postun

I have no clue whether that was a useful check that accidentally got truncated, or non-useful code that didn't get fully erased.

2. When looking into that, I noticed the metadata references your old license, which is probably oversight:

   earthly/release/yum-repo/earthly.spec

   Line 5 in 1700511

   License: Business Source License

3. When doing a removal (without ever having actually running earthly, thus something of an edge case), I also get a (non-fatal) error:

<snip>
Running transaction
  Erasing    : earthly-0.6.28-1.x86_64                                                                                                                                                                                                        1/1 
removing earthly-buildkitd docker container
Error: No such container: earthly-buildkitd
warning: %postun(earthly-0.6.28-1.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package earthly-0.6.28-1.x86_64
  Verifying  : earthly-0.6.28-1.x86_64
<snip>

The guilty line

earthly/release/yum-repo/earthly.spec

Line 69 in 1700511

docker rm --force earthly-buildkitd

exits non-zero if the container doesn't exist (even with --force). Oddly enough, the volume removal will actually exit 0 if the volume doesn't exist (with --force).

[rrjjvv]

I debated whether to bring this up, but figured I'd let you guys decide what skill-set/experience you expect your users to have.

Even though this came up during a yum install (atypical for us), it's not specific to this. There is some minimum docker version required to run earthly, but the RPM doesn't declare any docker dependency, let alone version. And minimum version isn't actually documented anywhere.

Our user came to me with this (after the yum install):

Though I had never encountered this before, I had a strong suspicion it was due to using the distro's own docker package (and it was; it's ancient). Documenting (and/or enforcing) these minimum requirements might help some of your less technical user-base.