Issue #1596 has been updated by gary.

of course :)

/usr/lib/ruby/1.8/puppet/network/xmlrpc/client.rb:55:in `list'
/usr/lib/ruby/1.8/puppet/network/client/proxy.rb:15:in `send'
/usr/lib/ruby/1.8/puppet/network/client/proxy.rb:15:in `list'
/usr/lib/ruby/1.8/puppet/type/file.rb:862:in `sourcerecurse'
/usr/lib/ruby/1.8/puppet/type/file.rb:853:in `each'
/usr/lib/ruby/1.8/puppet/type/file.rb:853:in `sourcerecurse'
/usr/lib/ruby/1.8/puppet/type/file.rb:719:in `recurse'
/usr/lib/ruby/1.8/puppet/type/file.rb:340:in `eval_generate'
/usr/lib/ruby/1.8/puppet/transaction.rb:192:in `eval_generate'
/usr/lib/ruby/1.8/puppet/transaction.rb:227:in `eval_resource'
/usr/lib/ruby/1.8/puppet/transaction.rb:243:in `eval_resource'
/usr/lib/ruby/1.8/puppet/transaction.rb:242:in `each'
/usr/lib/ruby/1.8/puppet/transaction.rb:242:in `eval_resource'
/usr/lib/ruby/1.8/puppet/transaction.rb:243:in `eval_resource'
/usr/lib/ruby/1.8/puppet/transaction.rb:242:in `each'
/usr/lib/ruby/1.8/puppet/transaction.rb:242:in `eval_resource'
/usr/lib/ruby/1.8/puppet/transaction.rb:243:in `eval_resource'
/usr/lib/ruby/1.8/puppet/transaction.rb:242:in `each'
/usr/lib/ruby/1.8/puppet/transaction.rb:242:in `eval_resource'
/usr/lib/ruby/1.8/puppet/transaction.rb:309:in `evaluate'
/usr/lib/ruby/1.8/puppet/util.rb:445:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
/usr/lib/ruby/1.8/puppet/util.rb:444:in `thinmark'
/usr/lib/ruby/1.8/puppet/transaction.rb:308:in `evaluate'
/usr/lib/ruby/1.8/puppet/transaction.rb:302:in `collect'
/usr/lib/ruby/1.8/puppet/transaction.rb:302:in `evaluate'
/usr/lib/ruby/1.8/puppet/node/catalog.rb:118:in `apply'
/usr/lib/ruby/1.8/puppet/network/client/master.rb:264:in `run'
/usr/lib/ruby/1.8/puppet/util.rb:212:in `benchmark'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
/usr/lib/ruby/1.8/puppet/util.rb:211:in `benchmark'
/usr/lib/ruby/1.8/puppet/network/client/master.rb:263:in `run'
/usr/lib/ruby/1.8/sync.rb:230:in `synchronize'
/usr/lib/ruby/1.8/puppet/network/client/master.rb:245:in `run'
/usr/lib/ruby/1.8/puppet/network/client.rb:136:in `runnow'
/usr/lib/ruby/1.8/puppet/network/client.rb:187:in `start'
/usr/lib/ruby/1.8/puppet.rb:336:in `start'
/usr/lib/ruby/1.8/puppet.rb:187:in `newthread'
/usr/lib/ruby/1.8/puppet.rb:186:in `initialize'
/usr/lib/ruby/1.8/puppet.rb:186:in `new'
/usr/lib/ruby/1.8/puppet.rb:186:in `newthread'
/usr/lib/ruby/1.8/puppet.rb:334:in `start'
/usr/lib/ruby/1.8/puppet.rb:333:in `each'
/usr/lib/ruby/1.8/puppet.rb:333:in `start'
/usr/sbin/puppetd:459
err: 
//Node[yutu]/soho::desktopdev/File[/root/test/navicat8_mysql_en/wine/bin/wineg++]:
 Failed to generate additional resources during transaction: nested *?+ in 
regexp: /^\/etc\/puppet-files\/navicat8_mysql_en\/wine\/bin\/wineg++/


----------------------------------------
Bug #1596: Deploying file resources with ++ in name generates error.
http://projects.reductivelabs.com/issues/show/1596

Author: gary
Status: Accepted
Priority: Normal
Assigned to: 
Category: fileserving
Target version: 
Complexity: Unknown
Affected version: 0.24.4
Keywords: 


Using the file resource to deploy a directory, I get this error:

//Node[hostname]/class/File[/usr/local/lib/navicat8_mysql_en/wine/bin/wineg++] 
(err): Failed to generate additional resources during transaction: nested *?+ 
in regexp: /^\/etc\/puppet-files\/navicat8_mysql_en\/wine\/bin\/wineg++/


----------------------------------------
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to