[Pkg-puppet-devel] Bug#1028333: puppetserver: find an upgrade path from puppet-master

[Jérôme Charaoui]

The old "puppet-master" and "puppet-master-passenger" were basically 
just configuration files for the systemd/sysvinit and Apache2/Passenger, 
because the main (ruby) code was always in the "puppet" package.

I think the way forward here is that first, we should make the 7.x 
transitional dummy package "puppet" "Breaks: puppet-master, 
puppet-master-passenger", to make clear that the old master packages 
cannot function with the libraries shipping in the latest puppet-agent 
package.

And secondly, we should carefully consider whether a "seamless" 
transition is even possible at all. Puppetserver is completely different 
software which is configured differently than the old master, and as 
such I doubt that one can simple replace one package with the other and 
expect things to "just work". Even if it does, important bits of the 
configuration may likely be lost in translation (eg. auth.conf).

So considering all this I'm currently leaning towards adding a 
transitional "puppet-master" and/or "puppet-master-passenger" package 
for the purpose of shipping a NEWS file recommending that users migrate 
to the puppetserver package manually.

-- Jérôme