Your message dated Sat, 03 Oct 2015 17:37:00 +0200 with message-id <[email protected]> and subject line "strict" variable mode available in puppet 3.5.0 has caused the Debian Bug report #563550, regarding puppetmaster - Undefined variable equal to empty to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 563550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563550 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: puppetmaster Version: 0.25.1-3 Severity: normal The puppet manifest language uses empty variables the same way then undefined ones. Many languages, for example perl and sql, have shown in the past that this behaviour produces hard to find errors all over the code. Example: lsb* are undefined if lsb-release is missing. A definition using this needs to explicitely check for the lack of a value. It would be obvious if it bails out on the variable access. This is also different from the behaviour of the templating language, erb bails out on undefined variables. Bastian -- Killing is stupid; useless! -- McCoy, "A Private Little War", stardate 4211.8
--- End Message ---
--- Begin Message ---Version: 3.5.1-1 According to the upstream bug tracker, a "strict" variable mode was introduced in puppet 3.5.0. It is off by default in puppet versions 3 and 4, but will be on by default in puppet version 5.0. Run puppet with "--strict_variables", or an equivalent configuration setting, and empty variables will result in a failed catalog compile. -- Stig Sandbeck Mathisen
--- End Message ---
