Description of problem: The version of Puppet in Fedora 24 and Rawhide is a little old, it should be updated to a current release, e.g. 4.5.0. Version-Release number of selected component (if applicable): 4.2.1-3.fc24
Puppetlabs added support for dnf (as opposed to yum) for f22 in their release 4.3.0 at the end of 2015. Upgrading ought to address a number of the outstanding bugzilla entires.
The LTS support version of Puppet Enterprise uses Puppet 4.8. It would be good if someone can package that release version at a minimum. Looking at the packaging system, the I can see Puppet 4.6 submitted for Fedora 26, which will already be quite out of date. Puppet have just released Puppet 4.9.0 which includes a fix for dnf package provider working on Fedora 25: https://docs.puppet.com/puppet/latest/release_notes.html Puppet 4.9.0 also bring in the updated Hiera 3.3 and Hiera 5 data format as pre-cursor changes for Puppet 5.0 being released. Those packages would be good to have in Fedora 26.
Reassigning this ticket to myself (FAS: hguemar). I've been working towards updating puppet and facter (facter3) but facter is blocked due to leatherman not being packaged in Fedora. (RHBZ#1419271)
I've further updated Rawhide from 4.6.2 to 4.8.2, but to go beyond that requires rubygem-gettext-setup to be packaged (up for review at bug #1455470). Once done, I can update it again to a 4.10 or later release. It would be good to have Facter updated, but it's not a requirement at the moment as the minimum version in Puppet 4.10.1 remains at Facter 2.0.
I am curious, why is this closed as NEXTRELEASE marked for Fedora 27 when Fedora 26 hasn't been officially released yet? Is this puppet 4.10.1 package not going to be available for Fedora 26 either?
(In reply to Dagan McGregor from comment #5) > I am curious, why is this closed as NEXTRELEASE marked for Fedora 27 when > Fedora 26 hasn't been officially released yet? Sorry, should have been RAWHIDE I suppose. > Is this puppet 4.10.1 package not going to be available for Fedora 26 either? Not at the moment, I'll look at submitting an update after release perhaps.