Re: [Puppet-dev] Re: 'application' is now a reserved word? wtf

2015-08-13 Thread Ryan Coleman
On Thu, Aug 13, 2015 at 3:28 PM, Ryan Coleman wrote: > > On Thu, Aug 13, 2015 at 3:10 PM, Chris Rigby > wrote: > >> My issue in particular is related to a bug introduced into the future >> parser in 3.8.2. >> >> The bug breaks compilation when using a reserved keyword as a classname >> when the

[Puppet-dev] Announce: PuppetDB 2.3.7 is available

2015-08-13 Thread Wyatt Alt
PuppetDB 2.3.7 August 13, 2015 PuppetDB 2.3.7 Downloads Available in native package format in the release repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com For information on how to enable the Puppet Labs repos, see: http://docs.puppetlabs.com/g

Re: [Puppet-dev] Re: 'application' is now a reserved word? wtf

2015-08-13 Thread Ryan Coleman
On Thu, Aug 13, 2015 at 3:10 PM, Chris Rigby wrote: > My issue in particular is related to a bug introduced into the future > parser in 3.8.2. > > The bug breaks compilation when using a reserved keyword as a classname > when the future parser is enabled. > > See https://tickets.puppetlabs.com/br

[Puppet-dev] Re: 'application' is now a reserved word? wtf

2015-08-13 Thread Chris Rigby
My issue in particular is related to a bug introduced into the future parser in 3.8.2. The bug breaks compilation when using a reserved keyword as a classname when the future parser is enabled. See https://tickets.puppetlabs.com/browse/PUP-5036 On Thursday, 13 August 2015 21:24:36 UTC+1, Jo

[Puppet-dev] Re: 'application' is now a reserved word? wtf

2015-08-13 Thread John Bollinger
On Thursday, August 13, 2015 at 9:57:31 AM UTC-5, Chris Rigby wrote: > > Hi, > > So I have a class called `application`, and literally hundreds of > subclasses called `application::something` and now I've just learnt that > 'application' is now a reserved keyword in a point release. (3.8.2). >

Re: [Puppet-dev] Debian Testing and Debian Stable leaving apt.puppetlabs.com

2015-08-13 Thread Daniel Parks
On Thu, Aug 13, 2015 at 9:46 AM, Melissa Stone wrote: > In an effort to reduce duplication and confusion in the packages we > provide, we will no longer be providing packages for Debian Testing or > Debian Stable. We want to ensure we deliver tested and reliable packages, > which includes deliber

[Puppet-dev] Re: Debian Testing and Debian Stable leaving apt.puppetlabs.com

2015-08-13 Thread Melissa Stone
On Thu, Aug 13, 2015 at 9:46 AM, Melissa Stone wrote: > In an effort to reduce duplication and confusion in the packages we > provide, we will no longer be providing packages for Debian Testing or > Debian Stable. We want to ensure we deliver tested and reliable packages, > which includes deliber

[Puppet-dev] Debian Testing and Debian Stable leaving apt.puppetlabs.com

2015-08-13 Thread Melissa Stone
In an effort to reduce duplication and confusion in the packages we provide, we will no longer be providing packages for Debian Testing or Debian Stable. We want to ensure we deliver tested and reliable packages, which includes deliberately adding new platforms that have been vetted. This change is

[Puppet-dev] [announce] beaker 2.19.0 released

2015-08-13 Thread Kevin Imber
Included in this release: - BKR-372 - Support for Ubuntu Vivid (15.04) added - BKR-389 - Fixed upgrade_pe issues for the agent upgrade module - BKR-421 - MSI installation refactored, now includes PUPPET_AGENT_STARTUP_MODE support - BKR-340 - Separated answer file generation into its own library -

[Puppet-dev] 'application' is now a reserved word? wtf

2015-08-13 Thread Chris Rigby
Hi, So I have a class called `application`, and literally hundreds of subclasses called `application::something` and now I've just learnt that 'application' is now a reserved keyword in a point release. (3.8.2). What's going on? Are we all relegated to updating countless manifests that used