Closed rickerc closed 10 years ago
I recall Bode saying we needed to stick to 3.2.3 for the time being. I had run into an issue using 3.3.x with the new data model.
Well if we need to stay 3.2 we need to pin because what we do today blows up as soon as you apt-get dist-upgrade since we add the puppetlabs repo and puppetlabs has gone 3.3
3.3 generated warnings about deprecated syntax but didn't trigger any errors for me
I think that's what I had done on a client node and found the issue. /summons Bode
the problem with latest is that it will get updated to 4 as soon as that is released (there is no concept of major version branches) which will definitely break things.
For COI we'll fix by not using the puppetlabs repo
For upstream, latest or holding the package version are the two reasonable options. Both have problems but either are an improvement from the current. So it's just pick your poison...
Switch from unpinned but versioned puppet install to installing latest upstream puppet always to avoid apt-get dist-upgrade breaking dependencies