On Wed, Jun 22, 2016 at 1:58 AM, Stig Sandbeck Mathisen <[email protected]> wrote: > Ryan Whitehurst <[email protected]> writes: > >> The package "puppet-agent" was recently added to Debian Testing >> ("Stretch"). All it does is add an init script and systemd unit file >> for running puppet as a service, something which would normally be >> included in the main package, not require a separate package. There >> isn't really any benefit to having a separate package for this. > > Hi, and thanks for reporting a bug. > > There has been separate packages in Debian just for running the puppet > agent and master services since puppet 0.25.3. I've considered dropping > them[0], but left them in, mostly due to "that's the way it's been for a > long time". > > Previously, the "puppet" and "puppetmaster" packages would contain only > the init script, upstart job and systemd service. These were renamed to > "puppet-agent" and "puppet-master". The puppet software itself was > contained in the "puppet-common" and "puppetmaster-common" > packages. These was merged into the "puppet" package. > > Since this renaming clearly creates problems for Puppet (the software) > provided by Puppet (the company), I'll move the puppet agent and master > services into puppet (the Debian package), but I think I'll have to > disable them by default. > > There is also a puppet-master-passenger package, which should be > separate due to its dependencies on apache httpd and passenger. > > [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798636#20
Thanks, that makes sense. I got really confused at first when I had a manually installed (particular version) upstream puppet-agent package, ran updates on my stretch laptop, and then some of my auxiliary tooling had total failures because it couldn't find the ruby environment it expected. :)
