[Pkg-puppet-devel] Bug#947105: Bug#947105: puppet: Default install uses outdated configuration file and directory locations

Thomas Goirand zigo at debian.org
Sun Dec 22 22:22:37 GMT 2019


On 12/21/19 3:46 AM, Todd H. Poole wrote:
> Package: puppet
> Version: 5.5.10-4
> Severity: important
> 
> Hi Maintainers,
> 
> In early 2015, upstream Puppet changed the location of several core config files and directories with the release of Puppet 4.0. Today, almost 5 years later, a default install of Puppet 5.5 on Debian 10 still uses those old config file and directory locations.
> 
> For example, per Debian's Puppet man page[1], the upstream Puppet docs[2], and innumerable web search results, the default config directory ("confdir") for Puppet should be /etc/puppetlabs/puppet/, but in Puppet 5.5.10-4 on Debian 10, it's still /etc/puppet/.

I don't see this as an issue. Why would the package include the vendor
name? Why Debian can't choose, if we feel /etc/puppet is better?

> Similar issues exist for all other config file and directory locations changed in Puppet 4.0[3].

Are you suggesting that Debian should use /opt? Hopefully, you are not.

> Although not package-breaking, inconsistencies like these present usability problems for those coming from other distributions or for those who were previously using Puppet's official open source packages.

Though for those who come from Debian and discovered puppet there, it
looks like the upstream decision to move to /etc/puppetlabs is a bad
decision that does abnormal vendor advertising.

> Could a Maintainer update the Debian Puppet package so that Puppet's behavior on Debian matches the documented behavior in the man pages, upstream docs, and upstream packages?

I'd vote for leaving things the way they are now. I wont close the bug,
as I have only uploaded puppet once to Debian, but I suggest the other
uploaders to do so.

Cheers,

Thomas Goirand (zigo)



More information about the Pkg-puppet-devel mailing list