Issue 3016 - Improve Nginx source => PPA migration steps

Issue 3016 - Improve Nginx source => PPA migration steps

[Felix Dahlke, 2015-09-10 05:34:58]

Assuming that this is something that will disappear once nginx from the new PPA
has been rolled out everywhere - LGTM.

(If this was intended to stay in place longer, I'd vote for investigating why
Puppet's purge doesn't do the trick, and also for a comment that explains why
this is necessary.)

[mathias, 2015-09-10 07:31:01]

On 2015/09/10 05:34:58, Felix Dahlke wrote:
> (If this was intended to stay in place longer, I'd vote for investigating why
> Puppet's purge doesn't do the trick, and also for a comment that explains why
> this is necessary.)

Yes it's supposed to vanish in the near future, as I wrote in the ticket
already.

Note that I of course investigated this in the process already. Otherwise it
would be marked as a quick-fix that requires further measures, but in fact I
doubt that there is any other way. Fact's first:

- The Nginx Package is a meta-package depending on nginx-full, which depends on
nginx-common
- All three need to be the same version
- Replacing them  with another version using apt-get requires that all packages
are given to the same command, e.g. apt-get -y install nginx=$version
nginx-common=$version nginx-full=$version
- Puppet does not provide any native facility to install multiple packages at
once, not even in version 3.x+
- Puppet instead converts each package resource into a single command, which
will always result in unmet dependencies being reported by APT

Purging nginx-common like done before is part of the actual problem. That
package is required, but would be purged during subsequent Puppet runs. It
worked before because the apt::source version of nginx-full did not enforce that
one to be the exact same version, but was fine with the native one - in which
case the package is marked as a regular dependency (not manually installed) and
purging has no effect.