Puppet version bump

Robie Basak robie.basak at canonical.com
Tue Feb 5 12:52:35 UTC 2013

On Sun, Jan 27, 2013 at 11:23:37AM -0500, John Moser wrote:
> OK further research yields that Debian is not updating Sid due to
> feature freeze for Testing.  However, Mathisain notes this:
> On the other hand, the master packaging branch at
> http://anonscm.debian.org/gitweb/?p=pkg-puppet/puppet.git;a=summary
> yields a working set of puppet 3.0.2 debs, they're just not tagged with
> a debian release. Feel free to use that until we can upload to sid.
> Can we see this imported to 13.04?

What would the implications be of an update to puppet 3 in the archive
for installations using older LTS releases running older versions of
puppet? Can an agent continue to run 2.7 and be served by a 3

There is some documentation for this.
http://docs.puppetlabs.com/guides/upgrading.html says "Older agent nodes
can get catalogs from a newer puppet master. The inverse is not always
true.". So it sounds like it should be fine. If we provide puppet 3 in
13.04, then providing that users upgrade their puppetmaster to 13.04,
then everything will work smoothly, right?

I'm just trying to identify if there are any cases where it could be
painful for users to find that puppet has been updated, for any
reasonable upgrade path. Are there any complications that I haven't
thought of, or would everything be fine?


More information about the Ubuntu-devel-discuss mailing list