Your message dated Tue, 19 Jan 2010 11:16:50 +0100 (CET)
with message-id <20100119101650.19ff932...@fsck>
and subject line Re: Bug#563555: puppetmaster - Class redefinition is allowed
has caused the Debian Bug report #563555,
regarding puppetmaster - Class redefinition is allowed
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.)
--
563555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563555
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: puppetmaster
Version: 0.25.1-3
Severity: important
I found nothing in the documentation about this, so it maybe just a
documentation bug, but for me the behaviour is surprising:
| class test {
| @@sshkey { $fqdn: type => rsa, key => $sshrsakey, alias => ["test"] }
| }
| class test {
| Sshkey[$fqdn] { alias => ["test"] }
| }
| include test
This example bails out because of the redefinition on the alias
parameter, not because of the redefinition of the class.
The second class definition is merged with the first, something no other
language allows. As the complete namespace is flat, this can produce
hard to find problems.
Bastian
--
There is a multi-legged creature crawling on your shoulder.
-- Spock, "A Taste of Armageddon", stardate 3193.9
--- End Message ---
--- Begin Message ---
tag 563555 + wontfix
thanks
Hello, and thanks for the bug report.
This seems to be by design. Think of it as setting a class context
around your manifest, instead of defining a single class. The
behaviour is similar to that of VCL (the Varnish Command Language).
I'll close this bug.
--- End Message ---
