similar to: I think 0.23.3 is ready

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all There is some discussion of doing a 0.23.3 release to backport a number of bugs fixes from 0.24.0. What do people think of this idea? Would you prefer a dot upgrade to 0.23.3 or are most planning to upgrade cleanly to 0.24.x? I understand from Luke that 0.24.1 will be released shortly and that 0.23.2 clients should cleanly connect and

Hi everyone, I''m using a svn pre-commit hook to check manifests for syntax errors. I''ve recently upgraded puppet from 0.22.4 to 0.23.2 and the hook stopped working. I use the following command to parse .pp files: /usr/local/bin/puppet --confdir=/tmp --vardir=/tmp --parseonly --ignoreimport /tmp/$$.pp Now, I make a decision based on the exit code. If 0 then commit, else exit

Hi all, I''m considering moving --parseonly to just puppet, rather than it and puppetmasterd. Considering that it''s really only useful for parsing a specific file, puppet has the benefit of requiring that you specify that file directly. Since Puppet now supports multiple environments, --parseonly becomes both more difficult and more ambiguous when used with

Hello, I was wondering if there is a way to parse individual manifest files as part of a pre-commit hook in subversion. I am looking for something like puppetmasterd --parseonly, but that will work on individual files. This way I can reject a commit if it does not pass. Any ideas? TIA

Hi all, It was brought to my attention that the front page lists 0.23.3 as the stable release, but that no such release exists. I could have sworn I released this a few weeks ago, but now I can find no evidence of that. I''m going to publish it from the latest commit in the 0.23.x branch as soon as possible (probably in about 12 hours), so if anyone wants to get that last-minute

Hi all, Hobbeswalsh on IRC has discovered a backward compatibility issue in 0.24.0, preventing 0.23.x clients working well with 0.24.0 servers. Specifically, you can''t specify relationships to builtin resources when the client is 0.23.x, although specifying relationships to defined resources still works. The problem is that prior to 0.24.0 there was no central class

This has been a much-requested feature, and is now a reality (in svn trunk): There is a new option, --ignoreimport, that will (surprisingly) ignore import statements. This is really only useful when using -- parseonly in a commit hook, and note that you''ll have to add the option to --parseonly, none of the puppet executables will add it for you. You should be able to

We have started having developers make changes to our manifests file. We have a couple of changes with errors that have broken updating for all clients. We even ran into a bug where a broken configuration on puppetmaster start would cause it to return 500 server errors to all clients. I would like to have a way for developers to check their changes before committing them to version control and

Hello! I''m trying to use pre-commit SVN hook for checking puppet syntax. For it I try to use some scripts from this thread: http://groups.google.com/group/puppet-users/browse_thread/thread/50ff2eb268f982da?pli=1 But when I try some of the scripts I see the common problem, expression like this: # puppet --parseonly --ignoreimport file.pp produces no output, but "file.pp" has a

Hi is anybody using the svn pre-commit hook from http://www.reductivelabs.com/trac/puppet/wiki/VersionControlPuppet with 0.24.1 . It was working fine with 0.23.1 and I like it to test stupid typos before checking in. However after updating to 0.24.1 I get the following error for the site.pp: Could not parse for environment development: No file(s) found for import of

I don''t manage any macosx machines but I do run puppet standalone to check syntax etc. I''ve been getting the following error: Could not autoload "/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceoverride.rb": superclass mismatch for class ResourceOverride specifically small test pp files still work, though I''ve found when I use parseonly it

Hi i am creating a template.pp for different OS.. Following is my template.pp file node basenode { case $operatingsystem { fedora: { include fedora } default: { include debian } } include baseapps, sshd, admin, default } <=== line 7 node default inherits basenode {} I receive an error. err: Could not parse for environment production: Syntax error

Hi all, I''ve done as much bug-fixing as I''m going to be able to do in 0.24.2, I think, so please test the current code if you can. I made some unfortunately significant changes today, in order to try to remove any shared objects in the file server, which will hopefully solve the file corruption issues, plus some very strange issues resulting from renaming

This is the latest stable release of CTDB. CTDB 2.5.5 can be used with Samba releases prior to Samba 4.2.x (i.e. Samba releases 3.6.x, 4.0.x and 4.1.x). Changes in CTDB 2.5.5 ===================== User-visible changes -------------------- * Dump stack traces for hung RPC processes (mountd, rquotad, statd) * Add vaccuming latency to database statistics * Add -X option to ctdb tool that uses

Hi all I''ve watched all the discussion about svn commit hooks, as I really want to integrate that into my system - the only thing is, that I use Mercurial as my SCM system. So I was wondering if someone out there knows mercurial well enough to write a commit hook? I''ve tried myself, and came up with this: pretxncommit.parsecheck_puppet = hg log -v -r $HG_NODE | sed -n

Hi all, I'm about to change my Debian mailserver setup from Postfix/dovecot1/procmail to Postfix/dovecot2/sieve with lmtp enabled. After enabling lmtp the virtual users can receive e-mails but not the local users: Mar 21 14:21:40 orange postfix/lmtp[4119]: DE62226216: to=<user at orange.domain.de>, relay=orange.domain.de[private/dovecot-lmtp], delay=7627, delays=7627/0/0/0.02,

Hi all, I'm setting a mailserver using dovecot version: 2.1.7. On the server I have a couple of system users using PAM authentication and a lot of virtual users using SQL authentication. When a virtual user (e.g. david at virtdomain.de) logs in dovecot tries to authenticate the user via PAM and after failing it uses SQL: Mar 19 11:39:42 orange dovecot: auth-worker(7815): pam(david at

For anyone that has experienced the odd End of file or Cannot describe errors, we''ve found that switching to Mongrel has fixed this problem for us. We''re currently running 5 instance of puppetmaster under mongrel (with the apache proxy in front) and things are going great. For more information on setting up Mongrel, visit:

Could someone please post a concise explanation of what's required to get directX working in wine? Here's what I've tried, and vaguely what happened (I'm running RedHat 7.1, new install): installed most recent rpm version of wine can't find direct X (shouldn't be surprising) uninstalled got most recent tarball of wine compiled it can't find direct X

Dear all, I would like to use shared folders but I'm not quite sure whether Dovecot supports it the way I want it: -user A should be able to share a folder with users B, C, D -B, C and D should have read-access to this folder Did anyone implement shared folders like this? Regards, David -- The day microsoft makes something that doesn't suck is the day they start making vacuum