I realized after sending the bit about there being a bug filed that I
should have checked myself.
As for the RPM, perhaps I'm a little spoiled from the Debian world
(though not all packages are of equal upgrade automation) and this is
not the paradigm used by most RPM authors, but I'm used to the upgrading
of a package taking various steps to smooth the upgrade for me.
R.I.Pienaar wrote:
> hello,
>
>
> ----- "Neil Prockter" <n.prock...@lse.ac.uk> wrote:
>
>
>> I have always had /etc/puppet/puppetd.conf managed by puppet so I let
>> puppet delete it.
>>
>> I agree the RPM has /etc/puppet/puppetd.conf in it and it should not
>> (I've only check the 0.24.8 from EPEL that I use)
>>
>
>
> Take another look, it does not create this file if you're just adding a new
> package on a clean machine:
>
> %ghost %config(noreplace,missingok) %{_sysconfdir}/puppet/puppetd.conf
>
> From the RPM docs:
>
> " As we mentioned in the Section called The %files List, if a file is
> specified in the %files list, that file will automatically be included in the
> package. There are times when a file should be owned by the package but not
> installed - log files and state files are good examples of cases you might
> desire this to happen.
>
> The way to achieve this, is to use the %ghost directive. By adding this
> directive to the line containing a file, RPM will know about the ghosted
> file, but will not add it to the package. However it still needs to be in the
> buildroot."
>
> but if you had a package prior to this behavior and you upgrade it wont
> delete your old {puppetd,puppetmasterd}.conf files, however the bug - that's
> fixed already in 0.25 - caused that to be a problem, its a common FAQ one
> that would have been solved in about a minute on the IRC channel.
>
> Problem some kind of release not on the RPM should mention this, but as this
> is a known bug and a very simple search for "puppetd.conf" on
> projects.reductivelabs.com would have found the issue I dont know why this is
> such a big issue.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
