Skip to content

handling package upgrades

Due to the moving nature of wheezy, the current minimal basebox is already 24 packages out of date. When you do a leap init-node it runs an apt-get update and then you see:

** [out :: web1_vagrant] 0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.

we need to determine what to do with this, elijah said that he assumes anything beyond update is the purview of puppet.

we can do unmaintained upgrades, but that typically is done via a cronjob, or we can do the upgrade in the deploy.sh?

speaking of deploy.sh, it does apt-get update, but the init-node does that, so we can probably remove that

(from redmine: created on 2012-11-20, closed on 2013-01-20, relates #1091)