puppet-agent (8.4.0-1) unstable; urgency=medium Puppet 8 is a major new release that introduces some breaking changes from the previous version. Legacy facts, such as 'hostname', 'ipaddress', 'osfamily' and others, are now disabled by default. If your manifests refer to such facts, you're likely to encounter issues compiling or applying catalogs. The recommended action is to migrate to structured facts, eg. "$facts['os']['family']". Alternatively, setting 'include_legacy_facts=true' in puppet.conf may be used to re-enable legacy facts. In addition, strict mode catalog compilation is now enabled by default. This may be reverted by using the 'strict_variables=false' and 'strict=warning' settings in puppet.conf. More information about upgrading from Puppet 7 to 8 can be found at: https://www.puppet.com/docs/puppet/8/upgrading-from-puppet7-to-puppet8.html Finally, for improved compatibility with the larger Puppet ecosystem, the package also now ships the same set of core modules as upstream, in the $vendormoduledir directory. The modules are: augeas_core, cron_core, host_core, mount_core, scheduled_task, selinux_core, sshkeys_core, yumrepo_core, zfs_core and zone_core. -- Jérôme Charaoui Mon, 19 Feb 2024 19:26:40 -0500 puppet-agent (7.22.0-3) unstable; urgency=medium The behavior of purging this package has changed between 7.22.0-2 and earlier versions. Prior to 7.22.0-2, purging puppet-agent would remove configuration files and the /var/lib/puppet directory. Beginning with 7.22.0-2, when purging this package, debconf will prompt the user with a warning that all Puppet configuration and data will be removed. This includes the /etc/puppet, /var/cache/puppet, /var/lib/puppet and /var/log/puppet directories. The user will be able to opt out, and in this case only unmodified configuration files will be removed, as usual. If the package is being purged in non-interactive mode, these directories will be removed automatically. -- Jérôme Charaoui Sun, 29 Jan 2023 10:47:29 -0500