date:20131230

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2205): (main) Remove symlinks from acceptance harness - jpartlow 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1317



  PR (2205): (main) Remove symlinks from acceptance harness - jpartlow 







 h2. (main) Remove symlinks from acceptance harness   * Author: Josh Partlow <>  * Company:   * Github ID: [jpartlow|https://github.com/jpartlow]  * [Pull Request 2205 Discussion|https://github.com/puppetlabs/puppet/pull/2205]  * [Pull Request 2205 File Diff|https://github.com/puppetlabs/puppet/pull/2205/files]  h2. Pull Request Description   Git's cro...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (FACT-170) PR (582): (maint) restrict redcarpet gem to <= 2.3.0 - jhoblitt

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (582): (maint) restrict redcarpet gem to <= 2.3.0 - jhoblitt 










adrienthebo commented:
Merged into stable in de25c2d.












   

 Add Comment











 













 Facter /  FACT-170



  PR (582): (maint) restrict redcarpet gem to <= 2.3.0 - jhoblitt 







 h2. (maint) restrict redcarpet gem to <= 2.3.0   * Author: Joshua Hoblitt   * Company:   * Github ID: [jhoblitt|https://github.com/jhoblitt]  * [Pull Request 582 Discussion|https://github.com/puppetlabs/facter/pull/582]  * [Pull Request 582 File Diff|https://github.com/puppetlabs/facter/pull/582/files]  h2. Pull Request Description ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (FACT-170) PR (582): (maint) restrict redcarpet gem to <= 2.3.0 - jhoblitt

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (582): (maint) restrict redcarpet gem to <= 2.3.0 - jhoblitt 










Pull request (maint) restrict redcarpet gem to <= 2.3.0 has been closed.












   

 Add Comment











 













 Facter /  FACT-170



  PR (582): (maint) restrict redcarpet gem to <= 2.3.0 - jhoblitt 







 h2. (maint) restrict redcarpet gem to <= 2.3.0   * Author: Joshua Hoblitt   * Company:   * Github ID: [jhoblitt|https://github.com/jhoblitt]  * [Pull Request 582 Discussion|https://github.com/puppetlabs/facter/pull/582]  * [Pull Request 582 File Diff|https://github.com/puppetlabs/facter/pull/582/files]  h2. Pull Request Description ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (FACT-158) PR (575): Facter 2 output validation - adrienthebo

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (575): Facter 2 output validation - adrienthebo 










adrienthebo commented:
Updated to normalize and validate in the same operation.












   

 Add Comment











 













 Facter /  FACT-158



  PR (575): Facter 2 output validation - adrienthebo 







 h2. Facter 2 output validation   * Author: Adrien Thebo git...@somethingsinistral.net>  * Company: Puppet Labs  * Github ID: [adrienthebo|https://github.com/adrienthebo]  * [Pull Request 575 Discussion|https://github.com/puppetlabs/facter/pull/575]  * [Pull Request 575 File Diff|https://github.com/puppetlabs/facter/pull/575/files]  h2. Pull Request D...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1255) Default file mode is now 0600 instead of 0644

2013-12-30 Thread Andrew Parker (JIRA)

Title: Message Title










 

 Andrew Parker assigned an issue to Unassigned











 






 Puppet /  PUP-1255



  Default file mode is now 0600 instead of 0644 










Change By:

 Andrew Parker




Assignee:

 Andrew Parker












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1317) PR (2205): (main) Remove symlinks from acceptance harness - jpartlow

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1317



  PR (2205): (main) Remove symlinks from acceptance harness - jpartlow 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 30/Dec/13 4:18 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(main) Remove symlinks from acceptance harness


Author: Josh Partlow <>


Company:


Github ID: jpartlow


Pull Request 2205 Discussion


Pull Request 2205 File Diff


Pull Request Description

Git's cross p

Jira (PUP-1317) PR (2205): (main) Remove symlinks from acceptance harness - jpartlow

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2205): (main) Remove symlinks from acceptance harness - jpartlow 










jpartlow commented:
@hlindberg @ferventcoder Here's relief from the acceptance symlinks.












   

 Add Comment











 













 Puppet /  PUP-1317



  PR (2205): (main) Remove symlinks from acceptance harness - jpartlow 







 h2. (main) Remove symlinks from acceptance harness   * Author: Josh Partlow <>  * Company:   * Github ID: [jpartlow|https://github.com/jpartlow]  * [Pull Request 2205 Discussion|https://github.com/puppetlabs/puppet/pull/2205]  * [Pull Request 2205 File Diff|https://github.com/puppetlabs/puppet/pull/2205/files]  h2. Pull Request Description   Git's cro...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups

Jira (PUP-1312) Packages pushed

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Ryan McKern











 






 Puppet /  PUP-1312



  Packages pushed 










Change By:

 Kylo Ginsberg




Assignee:

 Melissa Stone Ryan McKern












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1314) Updates the downloads page

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Ryan McKern











 






 Puppet /  PUP-1314



  Updates the downloads page 










Change By:

 Kylo Ginsberg




Assignee:

 Melissa Stone Ryan McKern












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1313) Merge 3.4.0 into pe-puppet

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Ryan McKern











 






 Puppet /  PUP-1313



  Merge 3.4.0 into pe-puppet 










Change By:

 Kylo Ginsberg




Assignee:

 Melissa Stone Ryan McKern












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1315) Close "merged pending release" tickets in redmine and "Resolved" ticket jira

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Ryan McKern











 






 Puppet /  PUP-1315



  Close "merged pending release" tickets in redmine and "Resolved" ticket jira 










Change By:

 Kylo Ginsberg




Assignee:

 Melissa Stone Ryan McKern












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1316) PR (2204): (maint) Fix inconsistency when case option is a Type. - hlindberg

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2204): (maint) Fix inconsistency when case option is a Type. - hlindberg 










Pull request (maint) Fix inconsistency when case option is a Type. has been closed.












   

 Add Comment











 













 Puppet /  PUP-1316



  PR (2204): (maint) Fix inconsistency when case option is a Type. - hlindberg 







 h2. (maint) Fix inconsistency when case option is a Type.   * Author: Henrik Lindberg <>  * Company: Cloudsmith Inc.  * Github ID: [hlindberg|https://github.com/hlindberg]  * [Pull Request 2204 Discussion|https://github.com/puppetlabs/puppet/pull/2204]  * [Pull Request 2204 File Diff|https://github.com/puppetlabs/puppet/pull/2204/files]  h2. Pull Request ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1310) Go/no-go meeting

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Ryan McKern











 






 Puppet /  PUP-1310



  Go/no-go meeting 










Change By:

 Kylo Ginsberg




Assignee:

 Melissa Stone Ryan McKern












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1306) Tag the release

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1306



  Tag the release 










Change By:

 Kylo Ginsberg




Assignee:

 Melissa Stone Ryan McKern












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1308) Create packages

Title: Message Title










 

 Kylo Ginsberg assigned an issue to Ryan McKern











 






 Puppet /  PUP-1308



  Create packages 










Change By:

 Kylo Ginsberg




Assignee:

 Melissa Stone Ryan McKern












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1314) Updates the downloads page

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1314



  Updates the downloads page 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Updates the downloads page












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1315) Close "merged pending release" tickets in redmine and "Resolved" ticket jira

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1315



  Close "merged pending release" tickets in redmine and "Resolved" ticket jira 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Close "merged pending release" tickets in redmine and "Resolved" ticket jira












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1312) Packages pushed

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1312



  Packages pushed 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Packages pushed












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1313) Merge 3.4.0 into pe-puppet

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1313



  Merge 3.4.0 into pe-puppet 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Merge 3.4.0 into pe-puppet












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1311) Docs pushed

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1311



  Docs pushed 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Docs pushed












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1309) Smoke test packages

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1309



  Smoke test packages 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Smoke test packages












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1310) Go/no-go meeting

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1310



  Go/no-go meeting 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Go/no-go meeting












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1308) Create packages

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1308



  Create packages 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Create packages












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1307) Change the SHA1 for Puppet_For_The_Win to include 3.4.0 items

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1307



  Change the SHA1 for Puppet_For_The_Win to include 3.4.0 items 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Change the SHA1 for Puppet_For_The_Win to include 3.4.0 items












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1306) Tag the release

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1306



  Tag the release 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Tag the release












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1305) Prepare puppet-announcement

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1305



  Prepare puppet-announcement 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Prepare puppet-announcement












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1304) Is a redmine "affected version" created for the new version

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1304



  Is a redmine "affected version" created for the new version 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Is a redmine "affected version" created for the new version












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1303) Is there a commit for every bug targeted at the release

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1303



  Is there a commit for every bug targeted at the release 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Is there a commit for every bug targeted at the release












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1302) Is there a bug targeting at the release for every commit

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1302



  Is there a bug targeting at the release for every commit 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Is there a bug targeting at the release for every commit












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1300) Start 3.4.2 Final - Dec 31, 2013

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1300



  Start 3.4.2 Final - Dec 31, 2013 










Change By:

 Kylo Ginsberg




Summary:

 CLONE -  Start 3.4.2 Final - Dec 31, 2013












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1301) Are tests passing (spec, acceptance, all platforms)

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1301



  Are tests passing (spec, acceptance, all platforms) 










Change By:

 Kylo Ginsberg




Summary:

 CLONE - CLONE -  Are tests passing (spec, acceptance, all platforms)












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1300) CLONE - Start 3.4.2 Final - Dec 31, 2013

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1300



  CLONE - Start 3.4.2 Final - Dec 31, 2013 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.4.0




Fix Version/s:

 3.4.2












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1316) PR (2204): (maint) Fix inconsistency when case option is a Type. - hlindberg

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1316



  PR (2204): (maint) Fix inconsistency when case option is a Type. - hlindberg 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 30/Dec/13 3:52 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










(maint) Fix inconsistency when case option is a Type.


Author: Henrik Lindberg <>


Company: Cloudsmith Inc.


Github ID: hlindberg


Pull Request 2204 Discussion


Pull Request 2204 File Diff


Pull Request Description

Jira (PUP-1306) CLONE - CLONE - Tag the release

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1306



  CLONE - CLONE - Tag the release 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Components:


 RE




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1309) CLONE - CLONE - Smoke test packages

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1309



  CLONE - CLONE - Smoke test packages 










Issue Type:

  Sub-task




Assignee:

 Joshua Partlow




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper










Platforms


RHEL6


Debian (squeeze & wheezy)


Centos (5 & 6)


Ubuntu (lucid & precise)


Fedora (18)


Windows 2003 & 2008R2 & 2012


Packages


puppet


puppetmaster

Jira (PUP-1313) CLONE - CLONE - Merge 3.4.0 into pe-puppet

Title: Message Title










 

 Andrew Parker created an issue











 






 Puppet /  PUP-1313



  CLONE - CLONE - Merge 3.4.0 into pe-puppet 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Components:


 PE, RE




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Normal




Reporter:

 Andrew Parker










It should be merged into pe-puppet/master












   

 Add Comment

Jira (PUP-1308) CLONE - CLONE - Create packages

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1308



  CLONE - CLONE - Create packages 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Components:


 RE




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1315) CLONE - CLONE - Close "merged pending release" tickets in redmine and "Resolved" ticket jira

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1315



  CLONE - CLONE - Close "merged pending release" tickets in redmine and "Resolved" ticket jira 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Normal




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails fro

Jira (PUP-1305) CLONE - CLONE - Prepare puppet-announcement

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1305



  CLONE - CLONE - Prepare puppet-announcement 










Issue Type:

  Sub-task




Assignee:

 Ryan McKern




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googl

Jira (PUP-1307) CLONE - CLONE - Change the SHA1 for Puppet_For_The_Win to include 3.4.0 items

Title: Message Title










 

 Rob Reynolds created an issue











 






 Puppet /  PUP-1307



  CLONE - CLONE - Change the SHA1 for Puppet_For_The_Win to include 3.4.0 items 










Issue Type:

  Sub-task




Assignee:

 Matthaus Owens




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Normal




Reporter:

 Rob Reynolds










This should be done in Jenkins












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1310) CLONE - CLONE - Go/no-go meeting

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1310



  CLONE - CLONE - Go/no-go meeting 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.c

Jira (PUP-1312) CLONE - CLONE - Packages pushed

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1312



  CLONE - CLONE - Packages pushed 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Components:


 RE




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1311) CLONE - CLONE - Docs pushed

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1311



  CLONE - CLONE - Docs pushed 










Issue Type:

  Sub-task




Assignee:

 Nicholas Fagerlund




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.c

Jira (PUP-1314) CLONE - CLONE - Updates the downloads page

Title: Message Title










 

 Michelle Johansen created an issue











 






 Puppet /  PUP-1314



  CLONE - CLONE - Updates the downloads page 










Issue Type:

  Sub-task




Assignee:

 Melissa Stone




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Normal




Reporter:

 Michelle Johansen












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubsc

Jira (PUP-1303) CLONE - CLONE - Is there a commit for every bug targeted at the release

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1303



  CLONE - CLONE - Is there a commit for every bug targeted at the release 










Issue Type:

  Sub-task




Assignee:

 Andrew Parker




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to

Jira (PUP-1304) CLONE - CLONE - Is a redmine "affected version" created for the new version

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1304



  CLONE - CLONE - Is a redmine "affected version" created for the new version 










Issue Type:

  Sub-task




Assignee:


 Unassigned




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and s

Jira (PUP-1302) CLONE - CLONE - Is there a bug targeting at the release for every commit

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1302



  CLONE - CLONE - Is there a bug targeting at the release for every commit 










Issue Type:

  Sub-task




Assignee:

 Andrew Parker




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email t

Jira (PUP-1301) CLONE - CLONE - Are tests passing (spec, acceptance, all platforms)

Title: Message Title










 

 Joshua Cooper created an issue











 






 Puppet /  PUP-1301



  CLONE - CLONE - Are tests passing (spec, acceptance, all platforms) 










Issue Type:

  Sub-task




Assignee:

 Andrew Parker




Created:


 30/Dec/13 3:52 PM




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pup

Jira (PUP-1300) CLONE - Start 3.4.2 Final - Dec 31, 2013

Title: Message Title










 

 Andrew Parker created an issue











 






 Puppet /  PUP-1300



  CLONE - Start 3.4.2 Final - Dec 31, 2013 










Issue Type:

  Task




Assignee:

 Andrew Parker




Created:


 30/Dec/13 3:52 PM




Due Date:


28/Jun/13




Fix Versions:


 3.4.0




Priority:

  Major




Reporter:

 Andrew Parker












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-797) PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez 










Verified that parameters can be set in the registry:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\puppet\ImagePath
  "C:\Program Files (x86)\Puppet Labs\Puppet\service\daemon.bat" --debug



When the service is started, e.g. net start puppet, debug statements are written to the log in $vardir/log/windows.log


2013-12-30 15:22:48 -0800 Puppet (notice): Starting service: --debug
2013-12-30 15:22:48 -0800 Puppet (notice): Service running
2013-12-30 15:22:48 -0800 Puppet (debug): Using 'C:/Program Files (x86)/Puppet Labs/Puppet/bin/puppet.bat'



Also specifying arguments via the Service Control Manager also works.
Note that most configuration settings should be set in puppet.conf, but --debug is one of those settings that can't be specified in the configuration file.












   

 Add Comment











 













 Puppet /  PUP-797



  PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez 







 h2. (#23219) - Fix support of extra arguments in windows service   * Author: Luis Fernández Álvarez <>  * Company: CERN  * Github ID: [luisfdez|https://github.com/luisfdez]  * [Pull Request 2094 Discussion|https://github.com/puppetlabs/puppet/pull/2094]  * [Pull Request 2094 File Diff|https://github.com/puppetlabs/puppet/pull/2094/files]  h2. Pull Request...

Jira (PUP-1299) Deprecate and eliminate magic parameter array handling

2013-12-30 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1299



  Deprecate and eliminate magic parameter array handling 










Change By:

 Charlie Sharpsteen









 Puppet's parser will automatically de-arrayify single element arrays for parameters (and properties). See `lib/puppet/parser/resource.rb`{code}result[p] = if v.is_a?(Array) and v.length == 1v[0]  elsev  end{code}As a result when writing a custom type, the parameter's validate and munge methods may receive an array or string depending on what values were specified in the manifest. This leads to idioms such as:{code}munge do |value|  # I don't really know how this is happening.  value = value.shift if value.is_a?(Array){code}and{code}munge do |value|  value = [value] unless value.is_a?(Array){code}However, the magic only happens when parsing a manifest, not when writing tests that create resources. For example:{code}$ puppet apply -e "exec { '/bin/true': environment => [ 'foo=bar']}"values = [values] unless values.is_a? Array(rdb:1) values"foo=bar"{code}But:{code}$ irb>> require 'puppet'>> Puppet::Type.type(:exec).new(:command => '/bin/true', :environment => ['foo=bar'])values = [values] unless values.is_a? Array(rdb:1) values["foo=bar"]{code}If a parameter only accepts a single argument, then the DSL should support this easily, e.g. `newparam(:timeout, :array => false)`See also [#6746| http://projects.puppetlabs.com/issues/6746 ] and  < https://github.com/puppetlabs/puppet/commit/46252b5bb858a1f2b87cc8646f3a59f935c58061 >












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscr

Jira (PUP-1299) Deprecate and eliminate magic parameter array handling

2013-12-30 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1299



  Deprecate and eliminate magic parameter array handling 










Change By:

 Charlie Sharpsteen









 Puppet's parser will automatically de-arrayify single element arrays for parameters (and properties). See `lib/puppet/parser/resource.rb`{code}result[p] = if v.is_a?(Array) and v.length == 1v[0]  elsev  end{code}As a result when writing a custom type, the parameter's validate and munge methods may receive an array or string depending on what values were specified in the manifest. This leads to idioms such as:{code}munge do |value|  # I don't really know how this is happening.  value = value.shift if value.is_a?(Array){code}and{code}munge do |value|  value = [value] unless value.is_a?(Array){code}However, the magic only happens when parsing a manifest, not when writing tests that create resources. For example:{code}$ puppet apply -e "exec { '/bin/true': environment => [ 'foo=bar']}"values = [values] unless values.is_a? Array(rdb:1) values"foo=bar"{code}But:{code}$ irb>> require 'puppet'>> Puppet::Type.type(:exec).new(:command => '/bin/true', :environment => ['foo=bar'])values = [values] unless values.is_a? Array(rdb:1) values["foo=bar"]{code}If a parameter only accepts a single argument, then the DSL should support this easily, e.g. `newparam(:timeout, :array => false)`See also  [  #6746 |]  and 












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email t

Jira (PUP-1299) Deprecate and eliminate magic parameter array handling

2013-12-30 Thread Charlie Sharpsteen (JIRA)

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1299



  Deprecate and eliminate magic parameter array handling 










Change By:

 Charlie Sharpsteen









 Puppet's parser will automatically de-arrayify single element arrays for parameters (and properties). See `lib/puppet/parser/resource.rb`  {code} result[p] = if v.is_a?(Array) and v.length == 1v[0]  elsev  end  {code} As a result when writing a custom type, the parameter's validate and munge methods may receive an array or string depending on what values were specified in the manifest. This leads to idioms such as:  {code} munge do |value|  # I don't really know how this is happening.  value = value.shift if value.is_a?(Array)  {code} and   {code} munge do |value|  value = [value] unless value.is_a?(Array)  {code} However, the magic only happens when parsing a manifest, not when writing tests that create resources. For example:  {code} $ puppet apply -e "exec { '/bin/true': environment => [ 'foo=bar']}"values = [values] unless values.is_a? Array(rdb:1) values"foo=bar"  {code} But:  {code} $ irb>> require 'puppet'>> Puppet::Type.type(:exec).new(:command => '/bin/true', :environment => ['foo=bar'])values = [values] unless values.is_a? Array(rdb:1) values["foo=bar"]  {code} If a parameter only accepts a single argument, then the DSL should support this easily, e.g. `newparam(:timeout, :array => false)`See also #6746 and 












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails f

Jira (PUP-312) Get MSI packages so that we can test windows against packages.

2013-12-30 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-312



  Get MSI packages so that we can test windows against packages. 










Change By:

 Michelle Johansen




Assignee:

 Joshua Partlow Matthaus Owens












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PDB-246) One item array are casted to String when stored in puppetdb

2013-12-30 Thread Deepak Giridharagopal (JIRA)

Title: Message Title










 

 Deepak Giridharagopal commented on an issue











 






  Re: One item array are casted to String when stored in puppetdb 










After some investigation, it looks like this happens inside of Puppet for all resources. There isn't a way we can handle this inside of puppetdb's terminus, because by the time Puppet hands us the catalog the transformation has already happened.
There is already a ticket for this against Puppet itself:
https://tickets.puppetlabs.com/browse/PUP-1299
Please add commentary to that ticket; I'll link this to PUP-1299 and close this one out.












   

 Add Comment











 













 PuppetDB /  PDB-246



  One item array are casted to String when stored in puppetdb 







 When I try to create an exported resource (in my exemple a nginx::resource::vhost) with some parameters containing a one-item array, it is casted to String in puppetdb :   {quote}    @@nginx::resource::vhost { 'my resource':  ensure => present,  server_name => ['first item'],  listen_port => 9200,  proxy => "http://${::fqdn}"  ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1299) Deprecate and eliminate magic parameter array handling

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1299



  Deprecate and eliminate magic parameter array handling 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 30/Dec/13 3:09 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Puppet's parser will automatically de-arrayify single element arrays for parameters (and properties). See `lib/puppet/parser/resource.rb`
 result[p] = if v.is_a?(Array) and v.length == 1 v[0] else v end 
As a result when writing a custom type, the parameter's validate and munge methods may receive an array or string depending on what values were specified in the manifest. This leads to idioms such as:
 munge do |value|


I don't really know how this is happening. value = value.shift if value.is_a?(Array) 


and 
 munge do |value| value = [value] unless value.is_a?(Array) 
However, the magic only happens when parsing a manifest, not when writing tests that create resources. For example:
 $ puppet apply -e "exec  { '/bin/true': environment => [ 'foo=bar']}
" values = [values] unless values.is_a? Array (rdb:1) values "foo=bar" 
But:
 $

Jira (PUP-1211) Puppet Resource Package fails

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Puppet Resource Package fails 










In other words, this is a puppet bug












   

 Add Comment











 













 Puppet /  PUP-1211



  Puppet Resource Package fails 







 Trying to get all windows package resources i get the following error   {code}  ruby 1.9.3p448 (2013-06-27) [i386-mingw32]   C:\Windows\system32>puppet resource package  Error: Could not run: invalid byte sequence in US-ASCII  {code}















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1211) Puppet Resource Package fails

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Puppet Resource Package fails 










I was able to reproduce by adding ® to Notepad++ DisplayName:


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Notepad++]
"DisplayName"="Notepad++®"
"UninstallString"="C:\\Program Files (x86)\\Notepad++\\uninstall.exe"
"DisplayIcon"="C:\\Program Files (x86)\\Notepad++\\notepad++.exe"
"DisplayVersion"="6.1.5"
"URLInfoAbout"="http://notepad-plus-plus.org/"
"Publisher"="Notepad++ Team"
"VersionMajor"="6"
"VersionMinor"="45"
"MajorVersion"="6"
"MinorVersion"="45"



And then trying to run puppet resource package, and it blows up:


C:\Windows\system32>puppet resource package
Error: Could not run: invalid byte sequence in US-ASCII















   

 Add Comment











 













 Puppet /  PUP-1211



  Puppet Resource Package fails 







 Trying to get all windows package resources i get the following error   {code}  ruby 1.9.3p448 (2013-06-27) [i386-mingw32]   C:\Windows\system32>puppet resource package  Error: Could not run: invalid byte sequence in US-ASCII  {code}

Jira (PUP-312) Get MSI packages so that we can test windows against packages.

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Get MSI packages so that we can test windows against packages. 










Michelle Johansen no movement.
Matthaus Owens Currently we are polling puppet_for_the_win every hour, and only building puppet stable with its assorted dependencies. http://jenkins-legacy.delivery.puppetlabs.net/job/Windows%203.x%20Polling%20Build/. This has a few problems.


We're not generating MSIs when changes are pushed to the master branch only


We're polling the puppet_for_the_win repo for changes, which causes us to rebuild and overwrite an MSI even when `puppet` hasn't changed.


I would like to see the build process modified so that when a commit is pushed to puppet stable or master, we build a puppet MSI. An acceptance job should be able to retrieve and install the MSI given the puppet SHA, e.g.


start /w cmd.exe /c msiexec /qn /i http://builds.puppetlabs.lan/puppet/SHA/artifacts/windows/puppet-VERSION.msi















   

 Add Comment











 













 Puppet /  PUP-312



  Get MSI packages so that we can test windows against packages. 







 Need to check with delivery and see if the pipeline can produce msi packages.   * need to move to using re's packaging system (generate MSI on commit)  * be able to build stable vs master puppet with appropriately versioned MSIs so that they don't collide on builds.puppetlab

Jira (PUP-1211) Puppet Resource Package fails

2013-12-30 Thread Michelle Johansen (JIRA)

Title: Message Title










 

 Michelle Johansen updated an issue











 






 Puppet /  PUP-1211



  Puppet Resource Package fails 










Change By:

 Michelle Johansen




Labels:

 Support windows












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (FACT-168) Changed domain and fqdn facts

2013-12-30 Thread Justin Honold (JIRA)

Title: Message Title










 

 Justin Honold commented on an issue











 






  Re: Changed domain and fqdn facts 










http://serverfault.com/questions/562842/name-resolution-difference-between-centos-and-debian could be in play too, on resolv.conf stuff?
I ran into that ticket (as well as the Redmine base for this ticket) when I updated Facter on my own CentOS boxes, and started getting different results.












   

 Add Comment











 













 Facter /  FACT-168



  Changed domain and fqdn facts 







 I just updated a bunch of RHEL6 systems from facter 1.6.18 to 1.7.2, and for some reason the domain and fqdn facts have changed. I think it's related to the fix in issue #20938, since all of the servers affected have non-resolvable hostnames.   Before : [root@d01 ~]# facter domain fqdn hostname  domain => evo.example.com  fqdn => d01.evo.exampl...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@g

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

2013-12-30 Thread Kurt Wall (JIRA)

Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall











 






 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Change By:

 Kurt Wall




Assignee:

 Kurt Wall












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PDB-247) Fix Schema warning, replacing String and Number

2013-12-30 Thread Ryan Senior (JIRA)

Title: Message Title










 

 Ryan Senior created an issue











 






 PuppetDB /  PDB-247



  Fix Schema warning, replacing String and Number 










Issue Type:

  Bug




Affects Versions:


 1.6.0




Assignee:


 Unassigned




Created:


 30/Dec/13 1:41 PM




Fix Versions:


 2.0




Priority:

  Normal




Reporter:

 Ryan Senior










Due to this issue: https://github.com/Prismatic/schema/issues/21 we're seeing warnings like:
WARNING: String already refers to: class java.lang.String in namespace: schema.core, being replaced by: #'schema.core/String WARNING: Number already refers to: class java.lang.Number in namespace: schema.core, being replaced by: #'schema.core/Number
to stderr. We should be able to fork it and fix it, or if someone beats us to it, just upgrade.












   

 Add Comment

Jira (PUP-1298) manage_membership for unix groups provider

2013-12-30 Thread Antoine (JIRA)

Title: Message Title










 

 Antoine commented on an issue











 






  Re: manage_membership for unix groups provider 










There seems to be a working provider here:
https://github.com/pdxcat/puppet-module-group/blob/master/lib/puppet/provider/group/ggroupadd.rb
Looks simple enough/












   

 Add Comment











 













 Puppet /  PUP-1298



  manage_membership for unix groups provider 







 I searched and didn't see this feature request so if is/was at some point forgive me.   I'd like to be able to define the users that belong to a group in the group's resource. My compelling reason is that a specific unix group is used to determine ssh access via AllowGroups in sshd_config, and I'd like to make sure that at all times only specific users a...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.co

Jira (PUP-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek 










fhrbek commented:
I'll at the travis failure and the PUP ticket tomorrow.












   

 Add Comment











 













 Puppet /  PUP-1274



  PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek 







 h2. PE-2123 Do not fail hard on unparseable files   * Author: Filip Hrbek   * Company:   * Github ID: [fhrbek|https://github.com/fhrbek]  * [Pull Request 2201 Discussion|https://github.com/puppetlabs/puppet/pull/2201]  * [Pull Request 2201 File Diff|https://github.com/puppetlabs/puppet/pull/2201/files]  h2. Pull Request Description ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/op

Jira (PUP-1298) manage_membership for unix groups provider

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1298



  manage_membership for unix groups provider 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 30/Dec/13 1:03 PM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










I searched and didn't see this feature request so if is/was at some point forgive me.
I'd like to be able to define the users that belong to a group in the group's resource. My compelling reason is that a specific unix group is used to determine ssh access via AllowGroups in sshd_config, and I'd like to make sure that at all times only specific users are in that group. My workaround is to manage /etc/group as a file resource, which isn't very puppet-like.












   

 Add Comment

Jira (PUP-1255) Default file mode is now 0600 instead of 0644

2013-12-30 Thread Andrew Parker (JIRA)

Title: Message Title










 

 Andrew Parker commented on an issue











 






  Re: Default file mode is now 0600 instead of 0644 










Merged into stable in 6cabaa












   

 Add Comment











 













 Puppet /  PUP-1255



  Default file mode is now 0600 instead of 0644 







 As of Puppet 3.4.1 and 2.7.24, the default file mode when no mode is explicitly specified on a file resource has changed from 0644 to 0600. It appears from the commits (https://github.com/puppetlabs/puppet/commit/65909fbe and 691fbbeaa) that this was not the intention.   {noformat}  # rpm -q puppet  puppet-3.4.0-1.el6.noarch  # puppet apply -e 'file { "...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1297) PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog 










Pull request Issue/master/pup 1255 incorrect default permissions has been closed.












   

 Add Comment











 













 Puppet /  PUP-1297



  PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog 







 h2. Issue/master/pup 1255 incorrect default permissions   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2203 Discussion|https://github.com/puppetlabs/puppet/pull/2203]  * [Pull Request 2203 File Diff|https://github.com/puppetlabs/puppet/pull/2203/files]  h2. Pull Request Description  (w...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1297) PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1297



  PR (2203): Issue/master/pup 1255 incorrect default permissions - kylog 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 30/Dec/13 12:37 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Issue/master/pup 1255 incorrect default permissions


Author: Kylo Ginsberg <>


Company:


Github ID: kylog


Pull Request 2203 Discussion


Pull Request 2203 File Diff


Pull Request Description

Jira (PDB-246) One item array are casted to String when stored in puppetdb

2013-12-30 Thread Maxence Dunnewind (JIRA)

Title: Message Title










 

 Maxence Dunnewind created an issue











 






 PuppetDB /  PDB-246



  One item array are casted to String when stored in puppetdb 










Issue Type:

  Bug




Affects Versions:


 2.x




Assignee:


 Unassigned




Created:


 30/Dec/13 12:36 PM




Environment:


Debian 7. Puppet vm : facter 1.7.4-1puppetlabs1 hiera 1.3.0-1puppetlabs1 puppet 3.4.1-1puppetlabs1 puppet-common 3.4.1-1puppetlabs1 puppet-dashboard 1.2.23-1puppetlabs1 puppetdb-terminus 1.5.2-1puppetlabs1 puppetlabs-release 1.0-7 puppetmaster 3.4.1-1puppetlabs1 puppetmaster-common 3.4.1-1puppetlabs1 puppetmaster-passenger 3.4.1-1puppetlabs1 ruby-rgen 0.6.5-1puppetlabs1
puppetdb vm: puppetdb 1.5.2-1puppetlabs1




Priority:

  Normal




Reporter:

 Maxence Dunnewind










When I try to create an exported resource (in my exemple a nginx::resource::vhost) with some parameters containing a one-item array, it is casted to String in puppetdb :

 @@nginx::resource::vhost { 'my resource': ensure => present, server_name => ['first item'], listen_port => 9200, proxy => "http://${::fqdn}" }

In puppetdb I get :

puppetdb=# select * from resource_params where resource = '0e27f67d04b10bf659967bc8ecc704fa767bf278'

Jira (PUP-1296) PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog 










Pull request Issue/master/pup 1255 incorrect default permissions has been closed.












   

 Add Comment











 













 Puppet /  PUP-1296



  PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog 







 h2. Issue/master/pup 1255 incorrect default permissions   * Author: Kylo Ginsberg <>  * Company:   * Github ID: [kylog|https://github.com/kylog]  * [Pull Request 2202 Discussion|https://github.com/puppetlabs/puppet/pull/2202]  * [Pull Request 2202 File Diff|https://github.com/puppetlabs/puppet/pull/2202/files]  h2. Pull Request Description  (w...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-797) PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez

Title: Message Title










 

 Joshua Cooper assigned an issue to Joshua Cooper











 






 Puppet /  PUP-797



  PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez 










Change By:

 Joshua Cooper




Assignee:

 Rob Reynolds Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1192) PR (2176): (maint) Windows file provider :links => :follow - Iristyle

Title: Message Title










 

 Joshua Cooper assigned an issue to Unassigned











 






 Puppet /  PUP-1192



  PR (2176): (maint) Windows file provider :links => :follow - Iristyle 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek 










kylog commented:
Can you enter a PUP ticket for this and reference it in the commit message? Also, travis is faling, though I didn't look at what the failure was.












   

 Add Comment











 













 Puppet /  PUP-1274



  PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek 







 h2. PE-2123 Do not fail hard on unparseable files   * Author: Filip Hrbek   * Company:   * Github ID: [fhrbek|https://github.com/fhrbek]  * [Pull Request 2201 Discussion|https://github.com/puppetlabs/puppet/pull/2201]  * [Pull Request 2201 File Diff|https://github.com/puppetlabs/puppet/pull/2201/files]  h2. Pull Request Description ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.

Jira (PUP-1296) PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1296



  PR (2202): Issue/master/pup 1255 incorrect default permissions - kylog 










Issue Type:

  Task




Assignee:


 Unassigned




Components:


 Community




Created:


 30/Dec/13 12:10 PM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Issue/master/pup 1255 incorrect default permissions


Author: Kylo Ginsberg <>


Company:


Github ID: kylog


Pull Request 2202 Discussion


Pull Request 2202 File Diff


Pull Request Description

Jira (PUP-1274) PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek 










fhrbek commented:
@hlindberg Thanks for your comments. I fixed the "erros" typo and answered your question, however as I force pushed the comments are now hidden 
So, whoever is interested in what Henrik asked about, please disclose the second outdated diff. The question was about where to find the parse errors, it's probably a problem that needs to be solved. I appreciate any help in this area (as I am not the puppet core developer I don't know where it fits the best).












   

 Add Comment











 













 Puppet /  PUP-1274



  PR (2201): PE-2123 Do not fail hard on unparseable files - fhrbek 







 h2. PE-2123 Do not fail hard on unparseable files   * Author: Filip Hrbek   * Company:   * Github ID: [fhrbek|https://github.com/fhrbek]  * [Pull Request 2201 Discussion|https://github.com/puppetlabs/puppet/pull/2201]  * [Pull Request 2201 File Diff|https://github.com/puppetlabs/puppet/pull/2201/files]  h2. Pull Request Description ...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-797) PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez 










Merged in 9ea2f7f to be released in 3.5.0.












   

 Add Comment











 













 Puppet /  PUP-797



  PR (2094): (#23219) - Fix support of extra arguments in windows service - luisfdez 







 h2. (#23219) - Fix support of extra arguments in windows service   * Author: Luis Fernández Álvarez <>  * Company: CERN  * Github ID: [luisfdez|https://github.com/luisfdez]  * [Pull Request 2094 Discussion|https://github.com/puppetlabs/puppet/pull/2094]  * [Pull Request 2094 File Diff|https://github.com/puppetlabs/puppet/pull/2094/files]  h2. Pull Request...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1133) Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1133



  Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (FACT-168) Changed domain and fqdn facts

2013-12-30 Thread Brandon Ooi (JIRA)

Title: Message Title










 

 Brandon Ooi commented on an issue











 






  Re: Changed domain and fqdn facts 










Hi guys, is there any final word on what the correct behavior is? We use virtual machines heavily and reverse dns isn't set up when we run puppet for the first time (in fact, we use puppet to do it). 
In my opinion, it's incorrect behavior to basically "guess" the hostname by what's in /etc/resolv.conf. It should fall back to whatever hostname reports. Also, how would this work if the machine is being run independently at a remote location (no dns changes...)












   

 Add Comment











 













 Facter /  FACT-168



  Changed domain and fqdn facts 







 I just updated a bunch of RHEL6 systems from facter 1.6.18 to 1.7.2, and for some reason the domain and fqdn facts have changed. I think it's related to the fix in issue #20938, since all of the servers affected have non-resolvable hostnames.   Before : [root@d01 ~]# facter domain fqdn hostname  domain => evo.example.com  fqdn => d01.evo.exampl...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To u

Jira (PUP-1211) Puppet Resource Package fails

2013-12-30 Thread Louis Mayorga (JIRA)

Title: Message Title










 

 Louis Mayorga commented on an issue











 






  Re: Puppet Resource Package fails 










Yeah, 
I guess so but i did rebuilt my desktop machine with puppet and now is working fine. I don't use the PowerGUI (Just a Powershell experiment a while ago.)












   

 Add Comment











 













 Puppet /  PUP-1211



  Puppet Resource Package fails 







 Trying to get all windows package resources i get the following error   {code}  ruby 1.9.3p448 (2013-06-27) [i386-mingw32]   C:\Windows\system32>puppet resource package  Error: Could not run: invalid byte sequence in US-ASCII  {code}















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1133) Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist 










Merged in bc89aec to be released in 3.5.0












   

 Add Comment











 













 Puppet /  PUP-1133



  Windows generates test failures when %ALLUSERSPROFILE%\PuppetLabs\puppet doesn't exist 







 If %ALLUSERSPROFILE%\PuppetLabs\puppet (C:\ProgramData\PuppetLabs\puppet on Win2008 R2) does not exist, a number of failures are generated.   On cursory examination, manually creating `C:\ProgramData\PuppetLabs` is not sufficient to remove the errors.   One work-around that *does* work is to run the Windows MSI package, allow it to create `C:\ProgramDat...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1211) Puppet Resource Package fails

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Puppet Resource Package fails 










Thanks Louis, I suspect these products are causing the problem due to the non US-ASCII character in the name:


"DisplayName"="Quest PowerGUI® 3.6"
"DisplayName"="Quest PowerGUI® 3.6"















   

 Add Comment











 













 Puppet /  PUP-1211



  Puppet Resource Package fails 







 Trying to get all windows package resources i get the following error   {code}  ruby 1.9.3p448 (2013-06-27) [i386-mingw32]   C:\Windows\system32>puppet resource package  Error: Could not run: invalid byte sequence in US-ASCII  {code}















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this grou

Jira (PUP-1295) Yum provider "purge" target runs irrespective of package installation status

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1295



  Yum provider "purge" target runs irrespective of package installation status 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 30/Dec/13 11:00 AM




Labels:


 redmine customer




Priority:

  Normal




Reporter:

 redmine.exporter










It seems the yum provider will try to purge an absent package:  [root@test ~]# cat test.pp  package  { logwatch: ensure => purged; }
[root@test ~]# /bin/rpm -q logwatch --nosignature --nodigest --qf '% {NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' package logwatch is not installed  [root@test ~]# puppet -d -v test.pp  debug: Puppet::Type::Package::ProviderRpm: Executing '/bin/rpm --version' debug: Puppet::Type::Package::ProviderUrpmi: Executing '/bin/rpm -ql rpm' debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm --version' debug: Puppet::Type::Package::ProviderAptrpm: Executing '/bin/rpm -ql rpm' debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/portupgrade does not exist debug: Puppet::Type::Package::ProviderAptitude: file /usr/bin/aptitude does not exist debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox does not exist debug: Puppet::Type::Package::ProviderApt: file /usr/bin/apt-get does not exist debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not exist debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist debug: Puppet::Type::Package::ProviderDpkg: file /usr/bin/dpkg does not exist debug: Puppet::Type::Package::ProviderSun: file /usr/sbin/pkgrm does not exist debug: Puppet::Type::Package::ProviderAptrpm: file apt-get does not e

Jira (PUP-1294) The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys

Title: Message Title

redmine.exporter created an issue

Puppet / PUP-1294

The 'forcelocal' parameter for the 'user' resource still performs NSS lookups for certain subkeys

Issue Type:

Bug

Assignee:

Unassigned

Created:

30/Dec/13 10:58 AM

Labels:

redmine

Priority:

Normal

Reporter:

redmine.exporter

I have a particular configuration where a custom NSS plugin intercepts getent passwd calls and replaces the login shell with a new shell. In this situation, using the standard 'user' resource causes a false-positive for Puppet where it thinks the shell is configured as this new value, but it should be set to the value specified in the manifest. Unfortunately, setting 'forcelocal' to 'true' does not appear to solve the issue. I did a little looking through the code, and as far as I can tell, only certain specific subkeys (uid, gid, etc.) utilize the 'forcelocal' parameter (and the login shell is unfortunately not one of them).
If 'forcelocal' does not support certain keys than (IMO) either:
1. The documentation should be updated to explicitly list the supported keys 2. The behavior should change so that all of the keys are supported. 3. The login shell key is made compatible with 'forcelocal', and #1 is done to boot for the remaining keys to avoid future confusion about this issue
Right now this is not a huge blocker, but it's requiring me to avoid validating the local settings for login shells wherever this custom NSS module is being used.
As a side note, my 'libuser' Puppet feature appears to be loading correctly (which is a prereq for 'forcelocal')

Jira (HI-9) Hiera stable acceptance testing for Solaris with Vcloud

Title: Message Title










 

 Justin Stoller updated an issue











 






 Hiera /  HI-9



  Hiera stable acceptance testing for Solaris with Vcloud 










Change By:

 Justin Stoller




Assignee:

 Joshua Partlow Kurt Wall












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (HI-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.

Title: Message Title










 

 Justin Stoller updated an issue











 






 Hiera /  HI-7



  Hiera stable acceptance tests use dynamically provisioned vcloud templates. 










Change By:

 Justin Stoller




Assignee:

 Justin Stoller Kurt Wall












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (HI-8) Hiera stable acceptance testing for Windows using VCloud

Title: Message Title










 

 Justin Stoller updated an issue











 






 Hiera /  HI-8



  Hiera stable acceptance testing for Windows using VCloud 










Change By:

 Justin Stoller




Assignee:

 Joshua Partlow Kurt Wall












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1293) service status is ignored ( puppet 3.2 + upstart provider )

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1293



  service status is ignored ( puppet 3.2 + upstart provider ) 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 30/Dec/13 10:50 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










 cat > test.pp < notice("os = $::operatingsystem, puppetversion = $::puppetversion") exec  { 'run': command => "/sbin/status network-interface INTERFACE=eth0", logoutput => true, }
-> service  { 'network-interface': ensure => running, status => '/sbin/status network-interface INTERFACE=eth0', }
EOF puppet apply test.pp  will output the following  Notice: Scope(Class[main]): os = Ubuntu, puppetversion = 3.2.4 Notice: /Stage[main]//Exec[run]/returns: network-interface (eth0) start/running Notice: /Stage[main]//Exec[run]/returns: executed successfully Error: /Stage[main]//Service[network-interface]: Could not evaluate: Execution of '/sbin/status network-interface' returned 1: status: Unknown parameter: INTERFACE Notice: Finished catalog run in 0.27 seconds 












   

 Add Comment

Jira (HI-124) Write tests to test hiera on agent platforms

Title: Message Title










 

 Justin Stoller updated an issue











 






 Hiera /  HI-124



  Write tests to test hiera on agent platforms 










Change By:

 Justin Stoller









 Currently the hiera functional tests don't do anything on agent platforms. We need to write new tests or refactor existing tests to ensure that happens. See HI-8 &  Hi  HI -9.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (HI-124) Write tests to test hiera on agent platforms

Title: Message Title










 

 Justin Stoller created an issue











 






 Hiera /  HI-124



  Write tests to test hiera on agent platforms 










Issue Type:

  Bug




Assignee:

 Kurt Wall




Components:


 QA




Created:


 30/Dec/13 10:50 AM




Priority:

  Normal




Reporter:

 Justin Stoller










Currently the hiera functional tests don't do anything on agent platforms. We need to write new tests or refactor existing tests to ensure that happens. See HI-8 & Hi-9.












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1258) Puppet should be filesystem ACL aware

2013-12-30 Thread Patrick Hemmer (JIRA)

Title: Message Title










 

 Patrick Hemmer commented on an issue











 






  Re: Puppet should be filesystem ACL aware 










Here is a provider I wrote which subclasses the POSIX provider, and uses getfacl/setfacl to manage permissions. It properly solves all the issues listed.



Unable to find source-code formatter for language: ruby. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


Puppet::Type.type(:file).provide :posix_facl, :parent => :posix do
  desc "Uses POSIX & file ACL functionality to manage file ownership and permissions."

  initvars
  commands :getfacl => 'getfacl', :setfacl => 'setfacl'

  def mode
mode = super
return mode unless mode.is_a?(String)
mode = mode.to_i(8)

output = getfacl('--', resource[:path])
mode_parts = {}
output.split("\n").each do |line|
  next if line[0] == '#'
  if line.match(/^(user|group|other)::(\S+)/) then
mode_parts[$1] = $2
  end
end
mode_str = "u=#{mode_parts['user'].gsub('-','')},g=#{mode_parts['group'].gsub('-','')},o=#{mode_parts['other'].gsub('-','')}"

# we take the original mode from the POSIX provider, strip off the last 3 octal digits, and replace them with what we got from `getfacl`
mode = (mode & 07000) | (resource.symbolic_mode_to_int(mode_str) & 0777)

mode.to_s(8)
  end

  def mode=(value)
setfacl('-m', "user::#{value[-3]},group::#{value[-2]},other::#{value[-1]}", '--', resource[:path])
if value.length >= 4 then
  # we also need to set flags (which can't be done with setfacl (without a `--restore`)). Pull the current mode, strip off the flags, then add our flags on to it, and then use the normal chmod
  File.chmod((File.stat(resource[:path]).mode & 00777) | (value.to_i(8) & 07000), resource[:path])
end
  end
end















   

 Add Comment











 













 Puppet /  PUP-1258



  Puppet should be filesystem ACL aware

Jira (PUP-1292) Chocolatey package provider on Windows

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1292



  Chocolatey package provider on Windows 










Change By:

 Joshua Cooper




Labels:

 redmine  windows












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1290) Puppet should support *.msp upgrade packages on Windows

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1290



  Puppet should support *.msp upgrade packages on Windows 










Change By:

 Joshua Cooper




Labels:

 customer redmine  windows












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1292) Chocolatey package provider on Windows

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1292



  Chocolatey package provider on Windows 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 30/Dec/13 10:39 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










Investigate chocolatey package provider:
 












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

Jira (PUP-1290) Puppet should support *.msp upgrade packages on Windows

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1290



  Puppet should support *.msp upgrade packages on Windows 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 30/Dec/13 10:38 AM




Labels:


 redmine customer




Priority:

  Normal




Reporter:

 redmine.exporter










Puppet client on Windows should make enable installing *.msp upgrade packages.  For example when I'm trying to install update file to previously installed msi package client responds with error message like below:  "change from absent to present failed: Don't know how to install 'c:\AdbeRdrUpd1013.msp'" 
*.msp packages are installed in the same way as *.msi files. The only difference is /p switch instead if /i 












   

 Add Comment

Jira (PUP-1291) scheduled_task : add support for "every X minutes or hours" mode

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1291



  scheduled_task : add support for "every X minutes or hours" mode 










Change By:

 Joshua Cooper




Labels:

 redmine  windows












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1291) scheduled_task : add support for "every X minutes or hours" mode

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1291



  scheduled_task : add support for "every X minutes or hours" mode 










Issue Type:

  New Feature




Assignee:


 Unassigned




Created:


 30/Dec/13 10:38 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










As stated in the Puppet documentation (http://docs.puppetlabs.com/windows/writing.html#scheduledtaskscheduledtask), the "scheduled_task" resource type does not support repetition modes such as "every X minutes". 
It is a pity, because such tasks are very commonly used in Windows servers (and maybe less on Windows clients), making "scheduled_task" not so useful.
It is true that the configuration of Windows scheduled task is complicated (as opposed to crontab...); we may not need all the features available in the Windows GUI (like "Until", "Duration" or "If the task is still running, stop it at this time"), I guess it would be enough to support "every X minutes" and "every Y hours".












   

 Add Comment

Jira (PUP-1286) Automatically backslashify windows MSI package sources

Title: Message Title










 

 redmine.exporter created an issue











 






 Puppet /  PUP-1286



  Automatically backslashify windows MSI package sources 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 30/Dec/13 10:35 AM




Labels:


 redmine




Priority:

  Normal




Reporter:

 redmine.exporter










When installing an MSI, the windows package provider passes the package source parameter to msiexec.exe. Unfortunately, it must use backslashes, otherwise, msiexec thinks it's a command line argument and will fail with a cryptic error: Failed to install: Fail on INT 24.
The windows package provider should automatically convert the source to backslashes so that it just works.












   

 Add Comment

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

Title: Message Title










 

 Joshua Cooper updated an issue











 






 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Joshua Cooper




Labels:

 customer redmine  windows












   

 Add Comment











 










 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Jira (PUP-1289) Ability to manage a windows service's user account and password