Matthias Saou wrote: > A package related note : With RHEL 5.4, libselinux-ruby is included > at last, so it would be nice to now have the dependency included for > the epel5 package too :-)
This gets a little sticky, since many folks using EPEL are using it with CentOS or another RHEL rebuild. So if we add the dependency too quickly we'll cause them undue trouble. Once CentOS 5.4 is released, then it is something we should probably change. Thanks for the reminder (I've been using Dan Walsh's libselinux packages with the ruby bindings for a good while now, so I'd surely have forgotten about it. :) > And for the next release, I hope this will be fixed (it's trivial), > otherwise you might want to temporarily include a patch : > http://projects.reductivelabs.com/issues/2699 (this problem has been > there for a while, if no one noticed, it must mean that no one is > using a puppetmaster on the non standard port) Hmm. This seems more like a confusion (on the part of the scripts, not you Matthias) about what PUPPET_PORT should be setting. As it was created before my time, perhaps Luke or David L. can chime in with some historical context? The comments in client.sysconfig and the default value of 8140 make it seem like it is now intended to be the port on which to connect to the puppetmaster. But the --port option is still (and has been) perfectly valid for specifying the port that the puppet daemon listens on, which defaults to 8139. It seems to me that we probably want to add a new variable here, say PUPPETMASTER_PORT, which would be passed to puppetd with the --masterport option. Or, we can apply your patch and find out who's happily using PUPPET_PORT to specify the port on which puppetd listens. ;) -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ As long as people will accept crap, it will be financially profitable to dispense it. -- Dick Cavett, in "Playboy", 1971
pgpT2EPRbLgFC.pgp
Description: PGP signature
