Safe to update/upgrade node with apt-get?

[hambleto]

I am wondering, is is safe to update the proxmox node? When I run apt-get -u update it says that there are not packages set. However when I run apt-get -u upgrade I get :

The following packages have been kept back:
  openssh-client openssh-server
The following packages will be upgraded:
  cpio libgnutls13 libkrb53 libnet-dns-perl libpcre3 libperl5.8 libsmbclient
  libssl0.9.8 libxslt1.1 mtr-tiny openssl perl perl-base perl-modules
  perl-suid python2.4 python2.4-minimal rsync ssh
19 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 15.9MB of archives.
After unpacking 201kB disk space will be freed.
Do you want to continue [Y/n]?

Is it safe to do so on the nodes or does it break things?
Thank you,
Ben

 

[dietmar]

We are not aware of any problems - upgrade should work.

- Dietmar

 

[hambleto]

I ran the update this morning on a test node and so far no problems. I will test it some more and if nothing is wrong I will upgrade the rest of the nodes.
Thank you,
Ben

 

[tog]

Thanks for testing that for me, I'm always afraid when I update perl it's going to blow up and lose all my existing installed modules. At least that's what happens if you ever update from, say, perl 5.8.7 --> 5.8.8.

 

[reinier]

now with dist-upgrade

Hi,

same question, but now when upgrading from Hardy to Ibex?

I am using the Hardy Minimal template for all my VM's. Can I upgrade one of the VM's to ibex, without trashing all the others?

Or should i first create a new template, and then upgrade that one?

rgds,
reinier

PS, thanks for all this work, this saves me so much time every day.

 

[dietmar]

same question, but now when upgrading from Hardy to Ibex? I am using the Hardy Minimal template for all my VM's. Can I upgrade one of the VM's to ibex, without trashing all the others?

Should work in theory. Although those 'minimal' templates are not well suited to do upgrades. But you can simply test that yourself.

- Dietmar