Bug#1028333: puppetserver: find an upgrade path from puppet-master
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
Bug#1028333: puppetserver: find an upgrade path from puppet-master
Package: puppetserver Severity: grave At the moment, this package doesn't acknowledge the existence of the puppet-master package at all. As such, if the two packages are installed on the same machines, important breakage is likely. A proper upgrade path should be found, to make the transition from puppet-master to puppetserver seamless. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_0xE1E5457C8BAD4113.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1028333: [Pkg-puppet-devel] Bug#1028333: puppetserver: find an upgrade path from puppet-master
On 2023-01-19 11:30:31, Jérôme Charaoui wrote: > 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. Agreed. We should also probably make an entry in the release notes. According to the RT, this should be done in a MR here: https://salsa.debian.org/ddp-team/release-notes/ -- Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway. - Andrew S. Tanenbaum, "Computer Networks"
