The gnupg2 package has been removed as it is just a dummy translation
package. We need to be installing gnupg instead.
This also adds best-effort support for the "Artful Aardvark" (17.10)
version and removes support for "Zesty Zapus" (17.04) and "Yakkety Yak"
(16.10). Both releases are EOL.
Currently Salt 2017.7.2 has a critical bug that has broke disk
formatting for me:
saltstack/salt#44029
That left me looking for a way to pin AWS Linux hosts launched from
salt-cloud to an older release. With this change script args
`stable 2017.7.1` now works with AWS Linux based on the "Pin to Minor
Release" instructions listed at https://repo.saltstack.com/#amzn.
As noted in the comments below this change, we should probably refactor
to use `__install_saltstack_rhel_repository()`... in fact I've copied more
code from that function... but I don't understand all the cases for all
the other RedHat varients, so I'm just putting in the work for AWS
Linux.
Fixes an issue where the bootstrap script bails out if there is a zypper
process running already on the machine to be bootstrapped. This can happen
when a machine has been modified to use zypper in a boot command. We need
to wait for the process to finish before calling the next zypper command.
Otherwise, the following error occurs:
```
System management is locked by the application with pid <pid#> (zypper).
```
The DISTRO_MAJOR_VERSION is not properly set for Debian's like
systems.
The bootstrap script fails with
'ERROR: End of life distributions are not supported.'
when the derivated system have a version number less than 7.
If I understand the logic here the new(ish) aws repo url would only be
used in these two cases - when repo_rev:
* starts with latest or 2016.11
* starts with 0-9 and the year string is greater than 2016
If I'm reading this correct, the second case is wrong so I've removed
the check for "starts with 0-9".
Fixes#1159.
Since we're setting up suse's package repo above, we should rely on
that instead of defining each package explicity in the `stable`
installation functions.
The git installation functions however, still have those packages
defined as is customary in other distributions' git install funcs.
The relevant packages that weren't already installed with the `stable`
function installs have been moved to the `git` install functions.
