On Tue, Mar 1, 2016 at 12:25 PM, Matthew Gaspar wrote:
> A config file for facter is intriguing to me.
>
> Would this solely be used to change behaviors when running facter, or do
> you see some potential for defining some facts within the config itself?
>
I'd rather not mix config with content.
On Fri, Feb 5, 2016 at 12:06 AM, Alex Harvey wrote:
>
>
> On Friday, February 5, 2016 at 9:58:41 AM UTC+11, Michael Stanhke wrote:
>>
>>
>> Why would I ship a ruby when Red Hat does? The packages we ship for
>> Puppet 3 are designed to ship with System Ruby. System ruby is 1.8.7. I
>> realize tha
On Fri, Jan 29, 2016 at 8:16 AM, Alex Harvey wrote:
> Yep, it's solved in Puppet 4 - the all-in-one package is fantastic, as is
> so much in Puppet 4. However PE hasn't release Puppet 4 yet; my assessment
> of the Puppet Forge is that not many modules out there are ready; and I am
> not super co
tlabs.com/browse/PA/
[4] https://tickets.puppetlabs.com/browse/CPR/
Michael Stahnke
Release Engineering
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an e
On Mon, Oct 19, 2015 at 12:41 PM, Michael Stahnke
wrote:
>
>
> On Tue, Oct 13, 2015 at 6:04 AM, Trevor Vaughan
> wrote:
>
>> Hi Michael,
>>
>> Thanks for getting these released to the public, it's always good to have
>> new workflow tools!
>>
minimal VM and then destroy
it, (which is roughly what mock does, just on the same system).
> Thanks,
>
> Trevor
>
> On Mon, Oct 12, 2015 at 2:31 PM, Michael Stahnke
> wrote:
>
>> A couple of tooling announcements (or maybe just things that happened)
>> during the week o
A couple of tooling announcements (or maybe just things that happened)
during the week of PuppetConf.
1. Our tool to build our clojure services and packages was open sourced.
It's called ezbake[1] (like the oven). It uses our packaging[2] repo as
well. The way our services are managed in terms of
On Thu, Mar 5, 2015 at 1:25 PM, Roy Nielsen wrote:
> Curious - will this be able to be compiled and used on Arm or other
> architectures (cross platform compatibility)?
>
>
> I have been toying with ARM chips at home to get this working. (Not
official from Puppet Labs). Thus far I haven't got it
On Tue, Feb 24, 2015 at 10:31 AM, Wil Cooley wrote:
> On Mon, Feb 23, 2015 at 2:17 PM, Jeff McCune wrote:
>
>> On Sun, Feb 22, 2015 at 12:08 PM, Trevor Vaughan
>> wrote:
>>
>>> Yes please. Moving this out of $vardir/ssl will be quite irritating to
>>> teach existing users about the new product
On Tue, Nov 18, 2014 at 11:23 AM, Joshua Hoblitt wrote:
> On 11/18/2014 12:04 PM, Eric Sorenson wrote:
> > 2. To enable #1 but still support OSes that ship with 1.8.7, we're
> > going to be packaging and delivering Puppet 4 an an 'all-in-one' (AIO)
> > package bundled together with
> > - openssl
>
>> That's only semantic BS. The primary consumer of facter is puppet code
>> writers. If the meaning of return values of something like sprintf would
>> change, all hell would break loose. Why should it be different for the
>> return value of $operatingsystem ?
>>
>>
>
> Preach it, Brother!
>
>
Additionally, from a performance perspective, we couldn't even run the test
suites we run with PuppetDB against the ActiveRecord based system. It falls
over, we run out of memory and the slowness is unreal. If you want to see
this in action, Look for "PuppetConf Deepak" on youtube and you'll see
ta
On Tue, Jan 14, 2014 at 7:07 AM, Jason Antman wrote:
> I thought I'd throw in my 2 cents, as a long-time puppet user, current
> PE customer, and community member trying to make more code contributions...
>
> First off, this thread has been great. I was going to quote a few replies,
> but there h
There is always http://elruby.websages.com.
I am the guy behind that. I needed different rubies for lots of
projects I was working on and just decided to make them public.
Disclaimers:
1. I am not always super fast if there are updates (or CVEs). My job
is to keep Puppet Labs stuff updated, not
The FHS says conf files don't live in /usr, especially your data dir. (Keep
in mind the FHS follows some old-school ideas, like /usr should be able to
be mounted Read-Only.).
Anyway, a conf file, if needed should be in /etc. If it's for a specific
provider, ideally it would be something like /etc/
On Tue, Oct 30, 2012 at 2:57 PM, Andy Parker wrote:
> On Tue, Oct 30, 2012 at 1:41 PM, David Schmitt wrote:
>> On 2012-10-30 16:25, Jeff McCune wrote:
>>>
>>> Are there any "nightly" rpms or some-such around?
There's a sore lack of documentation at the moment, but the packaging
repo is here
In Puppet 2.7 you get deterministic ordering of resources.
Also, 2.6.x is currently only getting security fixes, so no bug fixes
will go into it. Is there a reason you can't use a newer puppet?
On Wed, Sep 19, 2012 at 4:34 AM, Lukáš Zapletal wrote:
> Hello,
>
> we are using Puppet 2.6 and need
On Fri, Aug 24, 2012 at 1:53 PM, Kent Shultz wrote:
> I'd rather have the monitoring solution collect incoming facts that are
> already coming to a central location rather than reaching out to the nodes.
> I suppose a cronjob on the nodes could run facter, but still it seems
> redundant since Fact
On Thu, Aug 23, 2012 at 10:49 AM, Roland Gruber wrote:
> Hi all,
>
> I would like to add support for Puppet to my OpenSource project LDAP Account
> Manager (LAM): http://www.ldap-account-manager.org/
> This will provide you a free web GUI to manage your Puppet entries in your
> LDAP directory (inc
On Mon, Aug 6, 2012 at 10:16 AM, Ken Barber wrote:
> Hi puppet-dev,
>
> TL;DR - I'm thinking about shipping minitar with puppet to make module
> install/build work consistently (and to ease development) (see:
> http://projects.puppetlabs.com/issues/15841) and wanted some feedback
>
> --
>
> So
As many of you have doubtless noticed, Puppet 3 and Facter 2 have been sitting
in RC (Release Candidate process) for a long time. That's about to change, but
they won't be getting released as they currently stand. Puppet 3 and Facter 2
have been pulled out of the RC process after we recognized that
On Wed, Jun 6, 2012 at 5:06 PM, Trevor Vaughan wrote:
> All,
>
> Very awesome work on this release and I'm looking forward to trying it out.
>
> Is there any chance that DNS SRV records are going to make it into 2.7?
Short answer, no.
It required some configuration parsing changes that were quit
On Thu, May 24, 2012 at 5:44 AM, Ashley Penney wrote:
> My only question is: Does this really need Ruby 1.9? As a Redhat user I
> firmly live years in the past, lumbered with ancient versions of everything
> we use in our toolchain. The module appears to only support Ubuntu in the
> first place
On Wed, May 23, 2012 at 9:53 PM, Russell Jackson wrote:
> On 05/23/2012 05:10 PM, James Turnbull wrote:
>>
>> Puppet Labs is really thrilled to announce, in conjunction with EMC, our
>> new open source bare metal provisioning tool: Razor.
>>
>> Razor is next generation provisioning software that h
://projects.puppetlabs.com/projects/puppetdb/issues
Michael Stahnke
Community Manager
Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this g
2.7.14 released today. We will continue maintaing 2.7.x for a while now.
On Wed, May 2, 2012 at 5:09 PM, Jo Rhett wrote:
> On May 2, 2012, at 7:35 AM, Peter Meier wrote:
>
> Unlikely, as up to now usually two major releases were supported for quite a
> while. Why do you assume it died?
>
>
> I
There was some discussion and concern about moving the Nagios
types/providers out of the core area of Puppet for Telly. We made a
mistake of talking about a point solution to a problem rather than the
vision on where we’d like it to go, and why. We’ve attempted to
outline this a bit more so you c
So, after a week of contemplation, I don't feel like we landed anywhere.
We have people that want the github noise off of the list.
We have people that want to be able to comment on patches on the list,
but not using the current workflow.
What should we do here? I'm still inclined to promote di
On Thu, Apr 19, 2012 at 1:39 PM, Ken Barber wrote:
>> An interactive puppet shell:
>> https://github.com/lak/puppet/tree/prototype/master/puppet_shell
>>
>> The best tool I ever had for managing ldap directories was a simple, stupid
>> tool I wrote called ldapsh: http://search.cpan.org/dist/lda
On Mon, Apr 16, 2012 at 11:36 AM, Todd Zullinger wrote:
> Michael Stahnke wrote:
>>
>> For the next major Puppet version, code-named Telly, we have some changes
>> coming. This is the first in a series of emails around these changes and
>> may require some input fr
Puppet Labs is happy to announce full support for Ruby 1.9.3 will be part of
the next major release of Puppet, codenamed Telly. Ruby 1.8.7 and 1.9.3 are
considered the primary supported Ruby versions, on all platforms including
Unix, Linux, Windows, and MacOS-X. Ruby 1.8.5 is also supported, on t
For the next major Puppet version, code-named Telly, we have some
changes coming. This is the first in a series of emails around these
changes and may require some input from the community.
For Telly, the nagios types will be moved into a module. This allows
them to be iterated on in isolation f
On Mon, Apr 9, 2012 at 2:11 PM, Jeff McCune wrote:
> On Mon, Apr 9, 2012 at 5:09 PM, Michael Stahnke
> wrote:
>>
>>
>> We have a goal to foster development discussion from the community.
>> Because of that, I am proposing we move the github notifications to a
&
feed for the puppet projects you have
the most interest in.
This decision isn't final, but I would like to get opinions on the
idea. I welcome feedback until Friday, April 13.
Michael Stahnke
Community Manager
--
You received this message because you are subscribed to the Google Groups
&q
This is a maintenance release candidate of Puppet Dashboard.
It includes contributions from Carl Caum, Josh Lifton, and Matt Robinson.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball.
See the Veri
, Konrad Scherer, Luke Kanies, Matt Robinson, Matthaus
Litteken, Michael Stahnke, Moses Mendoza, Nan Liu, Nick Fagerlund,
Nick Lewis, Ossi Herrala, Patrick Carlisle, Peter Meier, Pieter van de
Bruggen, R.I.Pienaar, Sean Millichamp, Stefan Schulte, Tim Bishop
---
Ben Hughes (1):
4911faf (
or see our security page[6].
Thanks,
Michael Stahnke
Community Manager
[1]https://github.com/blog/1068-public-key-security-vulnerability-and-mitigation
[2]http://guides.rubyonrails.org/security.html#mass-assignment
[3]http://blog.mhartl.com/2008/09/21/mass-assignment-in-rails-applications
Puppet Labs will apply to be a mentoring organization for Google
Summer of Code[1] this year. The first part of this process is to
come up with some great ideas for improvements and features in our
open source projects. While internally we have many ideas for
projects for GSOC, I wanted to take t
We are continuing to see several issues introduced Puppet 2.7.10. We
are recommending that users discontinue its usage. This could mean
using 2.7.9 or waiting patiently until we can get 2.7.11 out the door.
These are the most significant tickets around the 2.7.10 regressions.
http://projects.p
Facter 1.6.6rc2 was cut today. This addresses the following issue:
Make ec2 facts work on CentOS again (#12666)
Refactoring the ec2 facts lost the support for CentOS where the
hardware address in arp -an is uppercased. Fix and add a unit
test now that there are those
Thanks
On Wed, Feb 8, 2012 at 1:33 PM, Michael Stahnke wrote:
> We have 1 week until we cut RCs for Puppet, Dashboard and Facter. If
> you have tickets you've been working on, please try to get pull
> requests in and merged as soon as reasonably possible for this
> release.
We'r
We have 1 week until we cut RCs for Puppet, Dashboard and Facter. If
you have tickets you've been working on, please try to get pull
requests in and merged as soon as reasonably possible for this
release.
Mike
--
You received this message because you are subscribed to the Google Groups
"Puppe
On Tue, Jan 31, 2012 at 11:06 AM, Chris Price wrote:
> https://projects.puppetlabs.com/issues/12336
>
> Hello,
>
> As a result of a recent change to how we handle user-related environment
> variables when we launch processes from puppet
> (see: https://projects.puppetlabs.com/issues/5224 ), a bug
Welcome to the first Puppet Dashboard maintenance release of the new year.
This release includes a security update to address CVE-2012-0891, a
XSS vulnerability discovered by David Dasz . We have
classified the risk from this exposure as moderate. All Puppet Dashboard
users are encouraged to upgra
al, Dominic Maraglia, Eli
Klein, Gary Larizza, Ilya Sher, Jacob Helwig, James Turnbull, Jeff
McCune, Josh Cooper, Joshua Harlan Lifton, Jude Nagurney, Kelsey
Hightower, Matt Robinson, Matthaus Litteken, Matthias Pigulla, Max
Martin, Michael Stahnke, Nan Liu, Nick Lewis, Patrick, Patrick
Carlisle,
Welcome to the first maintenance release for Facter in the new year.
It includes contributions from the following people: Adrien Thebo,
Barrie Bremner, Gary Larizza, Jonathan Boyett, Josh Cooper, Ken
Barber, Marcus Vinicius Ferreira, Matt Dainty, Michael Kincaid, Moses
Mendoza, Pieter Lexis
This
um, Cody Herriges, Daniel
Pittman, Deepak Giridharagopal, Dominic Cleal, Dominic Maraglia, Eli
Klein, Gary Larizza, Ilya Sher, Jacob Helwig, James Turnbull, Jeff
McCune, Josh Cooper, Joshua Harlan Lifton, Jude Nagurney, Kelsey
Hightower, Matt Robinson, Matthaus Litteken, Matthias Pigulla, Max
Martin, Micha
We're about a week away from the January release candidates. If any
developers have code they'd like in
* Puppet 2.7.10
* Dashboard 1.2.5
* Facter 1.6.5
Please get it reviewd/merged.
Mike
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group
On Tue, Jan 10, 2012 at 11:56 AM, Matt Robinson wrote:
> I've wanted command line completion for some time, so I've whipped
> something up that gets it going:
>
> https://github.com/mmrobins/puppet-completion
>
> I've been meaning to get it to a state to merge into Puppet core, but
> haven't had t
This is a maintenance release candidate of Puppet Dashboard. This release
resolves issues #6717, #7554, #9529, #10017, #10076, #11058, and
#11063. More details below.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages a
Puppet 2.7.8rc1 is available. 2.7.8rc1 contains everything that was
being previewed in the 2.7.7rc series as well as some new content.
Key highlight in this release (beyond items from 2.7.7rc series) are:
* Allow providers to be selected in the run they become suitable
* Showdiff is now not
Per our timed-release cycle process[1], we've entered the THUNDERDOME
for 2.7.7rc series (Nov) vs 2.7.8 series (Dec).
Two releases enter; one leaves.
It was determined today that 2.7.8 has won the Thunderdome. (It was a
gory battle where 2.7.8 kicked 2.7.7 in the face, 2.7.7 fought back
with a w
Puppet 2.7.7rc2 is available.
This RC addresses a few significant issues found in 2.7.7rc1.
File serving performance issue with large numbers of files:
https://projects.puppetlabs.com/issues/9671
Agent may crash when attempting to manage permissions on non-NTFS
filesystems (on Windows)
https://p
This is a maintenance release of Puppet Dashboard release candidate.
This rc address one issue: (#10024) Update Puppet Dashboard Workers init script
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarbal
We have found 3 bugs we want tracked down before cutting the next
Puppet RC. (2.7.7rc2)
File serving performance issue with large numbers of files:
https://projects.puppetlabs.com/issues/9671
Agent may crash when attempting to manage permissions on non-NTFS
filesystems (on Windows)
https://proje
Puppet 2.7.7rc1 is available.
This release fixes several issues with Mongrel and Puppet 2.7.x,
Windows fixes and updates, test fixes, documentation updates and more.
Release Notes for 2.7.7 series --
https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
This release is available fo
November welcomes us to another round of Release Candidates for our software.
Facter 1.6.3rc1 is a maintenance release containing fixes, updates and
refactoring.
This release is available for download at:
http://puppetlabs.com/downloads/facter/facter-1.6.3rc1.tar.gz
See the Verifying Puppet Dow
Puppet 2.7.6 is a feature and security update release in the 2.7.x branch.
The security changes in 2.7.6 addres CVE-2011-3872
* CVE-2011-3872, Altnames Vulnerability
For more details on this vulnerability, follow the link on our
blog post:
http://puppetlabs.com/blog/important-security-announceme
Puppet 2.6.12 is a security update release in the 2.6.x branch.
The only changes since 2.6.11 are security fixes for the following
vulnerability:
* CVE-2011-3872, Altnames Vulnerability
For more details on this vulnerability, follow the link on our
blog post:
http://puppetlabs.com/blog/importan
/
* Remediation module:
http://links.puppetlabs.com/cve20113872_remediation
As a result of this vulnerability (CVE-2011-3872) we have released new
version of Puppet.
* 2.6.12
* 2.7.6
We will be sending separate announcements about each of those releases.
Michael Stahnke
Release Manager - Puppet Labs
On Fri, Oct 14, 2011 at 6:39 AM, Trevor Vaughan wrote:
> Has this been tagged in Git? I'm not seeing it when pulling from
> git://github.com/puppetlabs/puppet.git.
It's been pushed. Sorry about that.
>
> Thanks,
>
> Trevor
>
> On Thu, Oct 13, 2011 at
Puppet 2.7.6rc3 is available.
This release candidate fixes a regression in the Exec resource that
prevented multi-line execs from working properly.
Release Notes for 2.7.6 series --
https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
This release is available for download at:
ht
This is a maintenance release of Puppet Dashboard 1.2.2.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball.
RPMs are also available on yum.puppetlabs.com.
See the Verifying Puppet Download sectio
Facter 1.6.2 is a maintenance release containing fixes, updates and
refactoring. Primary new features include updated facts for DragonFly
BSD, Amazon Linux and Windows.
A few other facts have been added and updated. Full release notes below.
This release is available for download at:
http://pu
Puppet 2.7.6rc2 is available. This release candidate fixes issues
undercovered with using storedconfigs.
Release Notes for 2.7.6 series --
https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes
This release is available for download at:
http://downloads.puppetlabs.com/puppet/
See
Greetings,
I'd like to remove the cruft (no longer maintained) areas of
yum.puppetlabs.com. I fear they only cause confusion and offer
less-than-desirable experience for our users.
I'd like to remove
/base
/prosvc
/porsvc.unsigned
/SRMS
/sources
I'd like to do this some time next week. The stu
This is a maintenance release candidate of Puppet Dashboard 1.2.2rc2.
New in this RC is a bug-fix to no longer allow you edit node names.
In the past you were able to
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages a
It was a busy week last week, but we're back to our monthly release candidates
for our projects.
This is an enhancement/fix release candidate of Puppet. A major focus on this
release was Windows support. Puppet now works on Windows as agent. Another focus
was on the RAL around using it with toolin
After a very busy week on the security front last week, we are back to
monthly release/RC cycles.
Facter 1.6.2rc1 is a maintenance release containing fixes, updates and
refactoring.
This release is available for download at:
http://puppetlabs.com/downloads/facter/facter-1.6.2rc1.tar.gz
See the
Puppet 2.7.5 is a security update release in the 2.7.x branch.
The only changes since 2.7.4 are security fixes for the following
vulnerabilities:
* CVE-2011-3870, a symlink attack via a user's SSH authorized_keys file
* CVE-2011-3869, a symlink attack via a user's .k5login file
* CVE-2011-3871, a
Puppet 2.6.11 is a security update release in the 2.6.x branch.
The only changes since 2.6.10 are security fixes for the following
vulnerabilities:
* CVE-2011-3870, a symlink attack via a user's SSH authorized_keys file
* CVE-2011-3869, a symlink attack via a user's .k5login file
* CVE-2011-3871,
If you have any questions or need additional clarification on
anything, please respond to secur...@puppetlabs.com.
Thanks,
Michael Stahnke
Release Manager - Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this gr
Facter 1.6.1 is a maintenance release containing fixes, updates and
refactoring. Significant effort has been put into getting to Facter to
run on Windows for this release, as noted below.
This release is available for download at:
http://puppetlabs.com/downloads/facter/facter-1.6.1.tar.gz
See th
Puppet 2.7.4 is available. This release of Puppet and includes a
security fix for CVE-2011-3848.
Puppet 2.7.4 is an enhancement + security release of Puppet on the
2.7.x branch. Due to the security patches included, it is recommended
anybody using the 2.7.x series update to 2.7.4.
The significa
Puppet 2.6.10 is a maintenance release in the 2.6.x branch.
This release is 2.6.9 + a security fix for CVE-2011-3848.
Note: Features/fixes that were targeted at 2.6.10 have been moved to 2.6.11.
Puppet 2.6.10 is available. Changelog entries are available below.
More detailed information is a
asing any
upstream source of it.
If you have any questions or need additional clarification on
anything, please respond to secur...@puppetlabs.com.
Thanks, Michael Stahnke
Release Manager -- Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet
On Tue, Sep 20, 2011 at 4:55 AM, Ken Barber wrote:
> Interesting approach. I'll be in portland for a week after puppetconf.
> Happy to lend a hand.
>
> On Tue, Sep 20, 2011 at 2:48 AM, Luke Kanies wrote:
>> I agree. Maybe it's worth a merge-a-thon to get as many merged as possible
>> in a fixed a
On Mon, Sep 12, 2011 at 3:39 PM, Vlad wrote:
> Are there any plans to get the latest puppet and facter into
> apt.puppetlabs.com?
>
Of course. I started with yum simply because it was asked for more
loudly, and I know rpm a bit better than the debian packaging. I
welcome any help, reviews, ideas
I've had a vision of having packages for Puppet, Dashboard,
mcollective, facter, et al, available in native packaging formats for
as many distributions as possible.
I've updated http://yum.puppetlabs.com quite a bit today.
We have most of what I laid out in ticket
http://projects.puppetlabs.com/
On Wed, Sep 7, 2011 at 9:04 PM, Matt Robinson wrote:
> On Wed, Sep 7, 2011 at 6:15 PM, Michael Stahnke
> wrote:
>> 3. Dashboard has had no commits since 1.2.0, so no RC this month.
>
> Dashboard does have commits since 1.2.0
>
> $ git log --oneline --no-merges 1.2.0
On Wed, Sep 7, 2011 at 6:27 PM, Eric Sorenson wrote:
> Hi Mike -- is there a 2.6.10 on the horizon? I see a few bugs slated for it
> and many more on '2.6.x'.
Short answer, yes. I don't know when yet though. I'll find out more
and let you know.
Mike
--
You received this message because yo
Greetings,
This month we're having a couple changes in our release cycle.
1. Facter 1.6.1 will rc shortly. We actually cut rc1 internally and
caught some test failures that appear to be order dependent. We are
hoping to have this out 08-Sep-2011
2. Puppet 2.7.4rc1 will be cut ASAP, likely 08
Telly must support RHEL4, as PE supports RHEL4.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscr...@googlegr
It's here. Puppet Labs Announces Puppet Dashboard version 1.2.0.
This is a significant upgrade over the 1.1.x series, with new
features, prettier views and some all-in-all awesomeness. Thanks to
those who filed bugs, submitted patches and helped with the RC
process.
Major Highlights:
--
*
My thoughts on having three branches are the following. I'm happy to
revisit though.
Mostly from semver.org
Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards
compatible bug fixes are introduced. A bug fix is defined as an
internal change that fixes incorrect behavior.
Thi
ant changes
to facter, and would require some puppet modification to handle
structured data.
Mike
>
> --
> Luke Kanies | +1-615-594-8199 | http:/about.me/lak
>
> On Aug 23, 2011, at 5:58 PM, Michael Stahnke wrote:
>
>> All,
>>
>> I've added some new bra
All,
I've added some new branches to Facter in order to get some
much-needed love into it.
We have
1.6.x --> feature set for 1.6 (no API breakage please, mostly bug fixes)
1.7.x --> new features go here
master --> newer, possibly experimental things here (this might be
2.0 eventually, or w
Once more, with feeling,
Welcome to another Release Candidate for Puppet Dashboard (number 9).
This RC addresses security concerns announced/discovered in Rails over
the last couple days.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debi
Greetings,
Welcome to another Release Candidate for Puppet Dashboard (number 8).
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball.
See the Verifying Puppet Download section at:
http://projects.pu
Greetings,
Welcome to another Release Candidate for Puppet Dashboard (number 7).
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball.
See the Verifying Puppet Download section at:
http://projects.pu
As stated a few days ago [1], the 2.7.2 series died in the
Thunderdome[2], as per our release process. August has brought about
2.7.3. This includes all fixes from the 2.7.2, series as well as
several new fixes and enhancements. This is also the first
release of the 2.7 (Statler) series, that in
Greetings,
Welcome to another Release Candidate for Puppet Dashboard (number 6).
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball.
See the Verifying Puppet Download section at:
http://projects.pu
As stated a few days ago [1], the 2.7.2 series died in the
Thunderdome[2], as per our release process. August has brought about
2.7.3rc1. This includes all fixes from the 2.7.2 series as well as
several new fixes and enhancements. This will also be the first
release of the 2.7 (Statler) series,
Per our timed-release cycle process[1], we've entered the THUNDERDOME
for 2.7.2rc series (July) vs 2.7.3rc series (August).
Two releases enter; one leaves.
It was determined today that 2.7.3 has won the Thunderdome. (It was a
gory battle where 2.7.3 kicked 2.7.2 in the face)
So, look for 2.7.3
Greetings,
Welcome to another Release Candidate for Puppet Dashboard (number 5).
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball.
See the Verifying Puppet Download section at:
http://projects.pu
On Wed, Aug 3, 2011 at 6:54 AM, Dominic Cleal wrote:
> On 03/08/11 01:57, Jacob Helwig wrote:
>> The tl;dr:
>>
>> Our new preferred method of contributing changes is via GitHub pull
>> requests, and all Puppet Labs developers will be submitting their
>> changes for inclusion into the reposit
This a feature release candidate (number 4) of Puppet Dashboard.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages as well as a tarball.
See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/proj
Puppet 2.7.2rc3 is available. RC2 was accidentally packaged from the
wrong branch; thus causing some odd regressions and behavior. I
apologize for that. This rc corrects that mistake.
New since RC2
===
* Fix an issue where some commits in 2.7.x made their way into
2.7.2rc2 due to a branch conf
>
> PS: Everyone who ever again says Debian has outdated Software should
> take a redhat floppy and ...
>
The CentOS guys back-ported 187 to EL 5. Maybe that will help?
http://centos.karan.org/el5/ruby187/
--
You received this message because you are subscribed to the Google Groups
"Puppet D
On Tue, Jul 26, 2011 at 3:40 PM, Roy Nielsen wrote:
> Hello,
>
> I was wondering if tickets 6487/8375 was fixed for 2.7.2? They were for
> 2.6.9, but I don't think they got into the 2.7 branch yet - any idea when
> 2.7 branch will be ready for OS 10.7 (Lion)? (I didn't see anything in the
> rele
1 - 100 of 138 matches
Mail list logo
