[users] Puppet 2.7.3 updates available

[Nico Kadel-Garcia]

The puppet-2.7.3 release is available. I've grabbed the 2.6.6 version
from Fedora 16 development, grabbed the updated tarball from the
Puppet website,. It seems to behave well on RHEL 5, although I've only
*just* started working with it and would welcome attention. Should I
attach the 20K .spec file, or or publish the changes against the 2.6.6
file from Fedora 16?

Note that that the authors have apparently decided to re-index their
numbering, and went from 0.25.5 to 2.6.0, so the version increase from
the older 0.25.x release in RPMforge is not as large as one might
think.....

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
The puppet-2.7.3 release is available. I've grabbed the 2.6.6 version
from Fedora 16 development, grabbed the updated tarball from the
Puppet website,. It seems to behave well on RHEL 5, although I've only
*just* started working with it and would welcome attention. Should I
attach the 20K .spec file, or or publish the changes against the 2.6.6
file from Fedora 16?

Just check our git repo out, I bet you will be pleasantly surprised.

N.B. Puppet 2.6.9+ is not working properly with SELinux in enforcing
mode, the selinux-policy that would tentatively fix this issue is
available from Dan Walsh's repo and we're waiting for it to be pushed
out in the next RHEL 6 update cycle.

[Nico Kadel-Garcia]

Post by Yury V. Zaytsev

Post by Nico Kadel-Garcia
The puppet-2.7.3 release is available. I've grabbed the 2.6.6 version
from Fedora 16 development, grabbed the updated tarball from the
Puppet website,. It seems to behave well on RHEL 5, although I've only
*just* started working with it and would welcome attention. Should I
attach the 20K .spec file, or or publish the changes against the 2.6.6
file from Fedora 16?

Just check our git repo out, I bet you will be pleasantly surprised.
N.B. Puppet 2.6.9+ is not working properly with SELinux in enforcing
mode, the selinux-policy that would tentatively fix this issue is
available from Dan Walsh's repo and we're waiting for it to be pushed
out in the next RHEL 6 update cycle.

I see it. Cool.

Why are the "vim-puppet" and "emacs-puppet" packages split off, and
why are they not "puppet-emacs" and "puppet-vim"?

[Steve Huff]

Post by Nico Kadel-Garcia
Why are the "vim-puppet" and "emacs-puppet" packages split off, and
why are they not "puppet-emacs" and "puppet-vim"?

they're split off because i didn't want to make any text editor a dependency for installing puppet, and they're named differently for consistency with other text-editor-related packages (cf. vim-enhanced, vim-X11, emacs-git etc.).

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 243 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20110826/5562f26f/attachment.bin

[Steve Huff]

Post by Nico Kadel-Garcia
Why are the "vim-puppet" and "emacs-puppet" packages split off, and
why are they not "puppet-emacs" and "puppet-vim"?

they're split off because i didn't want to make any text editor a dependency for installing puppet, and they're named differently for consistency with other text-editor-related packages (cf. vim-enhanced, vim-X11, emacs-git etc.).

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 243 bytes
Desc: This is a digitally signed message part
URL: <http://lists.repoforge.org/pipermail/users/attachments/20110826/5562f26f/attachment.sig>

[Nico Kadel-Garcia]

Post by Yury V. Zaytsev

Post by Nico Kadel-Garcia
The puppet-2.7.3 release is available. I've grabbed the 2.6.6 version
from Fedora 16 development, grabbed the updated tarball from the
Puppet website,. It seems to behave well on RHEL 5, although I've only
*just* started working with it and would welcome attention. Should I
attach the 20K .spec file, or or publish the changes against the 2.6.6
file from Fedora 16?

Just check our git repo out, I bet you will be pleasantly surprised.
N.B. Puppet 2.6.9+ is not working properly with SELinux in enforcing
mode, the selinux-policy that would tentatively fix this issue is
available from Dan Walsh's repo and we're waiting for it to be pushed
out in the next RHEL 6 update cycle.

I see it. Cool.

Why are the "vim-puppet" and "emacs-puppet" packages split off, and
why are they not "puppet-emacs" and "puppet-vim"?

[Nico Kadel-Garcia]

The puppet-2.7.3 release is available. I've grabbed the 2.6.6 version
from Fedora 16 development, grabbed the updated tarball from the
Puppet website,. It seems to behave well on RHEL 5, although I've only
*just* started working with it and would welcome attention. Should I
attach the 20K .spec file, or or publish the changes against the 2.6.6
file from Fedora 16?

Note that that the authors have apparently decided to re-index their
numbering, and went from 0.25.5 to 2.6.0, so the version increase from
the older 0.25.x release in RPMforge is not as large as one might
think.....

[Yury V. Zaytsev]

Post by Nico Kadel-Garcia
The puppet-2.7.3 release is available. I've grabbed the 2.6.6 version
from Fedora 16 development, grabbed the updated tarball from the
Puppet website,. It seems to behave well on RHEL 5, although I've only
*just* started working with it and would welcome attention. Should I
attach the 20K .spec file, or or publish the changes against the 2.6.6
file from Fedora 16?

Just check our git repo out, I bet you will be pleasantly surprised.

N.B. Puppet 2.6.9+ is not working properly with SELinux in enforcing
mode, the selinux-policy that would tentatively fix this issue is
available from Dan Walsh's repo and we're waiting for it to be pushed
out in the next RHEL 6 update cycle.