[Pkg-puppet-devel] Bug#950182: Bug#950182: Bug#950182: Puppet 5.5 EOL in November 2020

Stig Sandbeck Mathisen ssm at debian.org
Sat Feb 1 09:51:42 GMT 2020

Thomas Goirand <zigo at debian.org> writes:

> Could you list them? I'd be ok to do that work within the team, if
> someone else is working on Puppet itself.

>From the "puppet-agent" repository, at

puppetlabs-augeas_core https://forge.puppet.com/puppetlabs/augeas_core
puppetlabs-cron_core https://forge.puppet.com/puppetlabs/cron_core
puppetlabs-host_core https://forge.puppet.com/puppetlabs/host_core
puppetlabs-mount_core https://forge.puppet.com/puppetlabs/mount_core
puppetlabs-sshkeys_core https://forge.puppet.com/puppetlabs/sshkeys_core
puppetlabs-selinux_core https://forge.puppet.com/puppetlabs/selinux_core
puppetlabs-yumrepo_core https://forge.puppet.com/puppetlabs/yumrepo_core
puppetlabs-zfs_core https://forge.puppet.com/puppetlabs/zfs_core
puppetlabs-zone_core https://forge.puppet.com/puppetlabs/zone_core
puppetlabs-scheduled_task https://forge.puppet.com/puppetlabs/scheduled_task

>> From a user point of view, the missing modules mainly shows up when
>> doing rspec module testing.
> So, we're talking about Ruby stuff?

The resource types and provides are written in ruby, but distributed as
puppet modules.

When testing puppet modules, and your code use the "cron", "host",
"mount" (from the list above) resource types, they need to be present.

The resource types are present in the puppet 5 source repository, while
in puppet 6, they are maintained as separate puppet modules in their own
repositories, and we would need to add them as packaged dependencies.

Stig Sandbeck Mathisen
Debian Developer

More information about the Pkg-puppet-devel mailing list