Keep vm's and ve's up to date

[Joachim Langenbach]

Actually keeping the vm's (and ve's) up to date is very time consuming. It may be more easy, if a target exists, which starts all vm's after each other and installs all available updates.

[Bruno Cornec]

Do you mean something like:

pb updatevm

or

pb -m distro-ver-arch updatevm

?

[Joachim Langenbach]

I ment the first, so that all vm's in vmlist default are updated. But also the second version may be usefull. It's also behaves like the other targets (like cms2vm) than too (in this case also pb -p PROJECT updatevm is missing).

[Bruno Cornec]

Fixed in rev [1111]

[Joachim Langenbach]

Thanks for the work on this suggestion.

I've patched my pb with the mentioned changeset and I've found some possible problems and solutions:

• Gentoo should do a (I do that normally on my gentoo boxes):

    sudo emerge --update --deep world; sudo revdep-rebuild
  

  To update all possible packages and take care of all changed libraries afterwards. (note: As far as I know, revdep-rebuild will be replaced with emerge @preserved-rebuild in Portage 2.2)
• Debian distros should use a

    sudo apt-get update; sudo apt-get upgrade
  

  Last part does the upgrade after updating the repos. But it is not really non-interactive (see: ​1).

    sudo apt-get update; export DEBIAN_FRONTEND="noninteractive"; apt-get --quiet -y --force-yes dist-upgrade
  

  is one of the two suggested solution in ​1. I've tested it and it is not noninteractive (here grub update has asked a question).

[Bruno Cornec]

In fact, if I make mistakes here (as I don't use all distros myself on a regular basis), it's possible for the user to adapt himself these commands. this is in the /etc/pb/pb.conf file with the entries osupd.

Now, I've taken in account your feedback, as it's important of course to have them as valid as possible.

For the non-interactive debian update, i keep what is given. May be updated later on if a better solution is found.

All in rev [1123]