Updating the VM

[jsanz]

There are lots of packages to update at the VM, including some "geo" stuff. If I run a "sudo aptitude safe-upgrade" I get the following output:

Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
Resolving dependencies...
Resolving dependencies...
Resolving dependencies...
Resolving dependencies...
The following NEW packages will be installed:
  libgdal1-1.6.0{a} libgeos-3.1.0{a} libproj-dev{a} libproj0{a} 
  linux-headers-2.6.28-15{a} linux-headers-2.6.28-15-generic{a} 
  linux-image-2.6.28-15-generic{a} 
  linux-restricted-modules-2.6.28-15-generic{a} proj-bin{a} proj-data{a} 
The following packages will be REMOVED:
  linux-headers-2.6.28-11{u} linux-headers-2.6.28-11-generic{u} 
The following packages will be upgraded:
  acpid app-install-data app-install-data-commercial apport apport-gtk 
  apturl bind9-host bluetooth bluez bluez-alsa bluez-cups bluez-gstreamer 
  bluez-utils brasero cgi-mapserver consolekit cron cups cups-bsd 
  cups-client cups-common dbus dbus-x11 dhcp3-client dhcp3-common 
  dnsmasq-base dnsutils evince file firefox firefox-3.0 
  firefox-3.0-branding firefox-3.0-gnome-support foomatic-db-engine 
  gnome-app-install gnome-desktop-data gnome-system-tools 
  gstreamer0.10-plugins-good gvfs gvfs-backends gvfs-bin hal imagemagick 
  imagemagick-doc language-selector language-selector-common libbind9-40 
  libbluetooth3 libbrasero-media0 libcamel1.2-14 libck-connector0 
  libcompress-raw-zlib-perl libcups2 libcupsimage2 libcurl3-gnutls 
  libdbus-1-3 libdns45 libebook1.2-9 libecal1.2-7 libedataserver1.2-11 
  libevdocument1 libevview1 libfreetype6 libgeos-c1 libgl1-mesa-dri 
  libgl1-mesa-glx libglu1-mesa libgnome-desktop-2-11 libgnutls26 
  libgoffice-0-6 libgoffice-0-6-common libgoffice-gtk-0-6 libgvfscommon0 
  libgweather-common libgweather1 libhal-storage1 libhal1 libical0 libisc45 
  libisccc40 libisccfg40 liblwres40 libmagic1 libmagickcore1 libmagickwand1 
  libmetacity0 libmpfr1ldbl libnautilus-extension1 libnspr4-0d libnss3-1d 
  libpam-ck-connector libpam-modules libpam-runtime libpam0g 
  libpoppler-glib4 libpoppler4 libpurple-bin libpurple0 libsasl2-2 
  libsasl2-modules libsmbclient libsoup-gnome2.4-1 libsoup2.4-1 
  libsqlite3-0 libssl0.9.8 libtiff4 libtrackerclient0 libudev0 
  libvolume-id1 libvorbis0a libvorbisenc2 libvorbisfile3 libwbclient0 
  libwmf0.2-7 libxcb-render0 libxcb1 libxi6 libxklavier12 libxml2 
  libxml2-utils linux-generic linux-headers-generic linux-image-generic 
  linux-libc-dev linux-restricted-modules-common 
  linux-restricted-modules-generic lsb-base lsb-release metacity-common 
  mozilla-thunderbird notification-daemon ntpdate openssl pidgin 
  pidgin-data poppler-utils proj python-apport python-cupshelpers 
  python-gobject python-libxml2 python-problem-report samba-common 
  screen-profiles smbclient splix synaptic system-config-printer-common 
  system-config-printer-gnome thunderbird udev update-manager 
  update-manager-core xfce4-terminal xfce4-weather-plugin 
  xserver-xorg-video-intel xulrunner-1.9 xulrunner-1.9-gnome-support 
158 packages upgraded, 10 newly installed, 2 to remove and 0 not upgraded.
Need to get 132MB of archives. After unpacking 113MB will be used.
Do you want to continue? [Y/n/?]

[camerons]

Nice catch Jorge, Feel free to update main.sh to include "aptitude safe-upgrade" as you suggest. Can you please run the script after the update to confirm it works without crashing.

[wildintellect]

A word of caution, we need to be careful if we mix apt and aptitude commands. Reading up aptitude seems overall better for the standard user, but if we go with that we should move all scripts to using it. We'll need to check with some Debian/Ubuntu package pros to make sure this would work for everyone.

Also, thinking about the Ubuntu script we installed a specific version, however a new one may pop-up an be installed even if we meant to install the old one. So we'll have to watch out for those problems. Shouldn't be an issue if this is run on a fresh vm before anything else is installed.

[wildintellect]

Replying to wildintellect:

I meant the QGIS script in my last post.

"> Also, thinking about the Ubuntu script we installed a specific version,"

[hamish]

Replying to wildintellect:

A word of caution, we need to be careful if we mix apt and aptitude commands. Reading up aptitude seems overall better for the standard user, but if we go with that we should move all scripts to using it. We'll need to check with some Debian/Ubuntu package pros to make sure this would work for everyone.

for automated builds apt-get should be used. somewhere in the wiki.debian.org LiveHelper pages it explains why, IIRC it has to do with aptitude sometimes being too interactive and smart for its own good, and the fact that it has a bad habit of trying to install all Recommends packages as well.

 echo 'APT::Install-Recommends "false"' >> /etc/apt/apt.conf

Also, thinking about the [QGIS] Ubuntu script we installed a specific version, however a new one may pop-up an be installed even if we meant to install the old one. So we'll have to watch out for those problems. Shouldn't be an issue if this is run on a fresh vm before anything else is installed.

yeah, and qgis is broken in the alpha5 RC because of it. A newer version was posted to the UbuntuGIS repo and the old version was removed. I've now updated install_qgis.sh to the new version number, but now that ubuntuGIS is the only extra repo can we now remove the versioning so this doesn't happen again?

Hamish

[wildintellect]

yeah, and qgis is broken in the alpha5 RC because of it. A newer version was posted to the UbuntuGIS repo and the old version was removed. I've now updated install_qgis.sh to the new version number, but now that ubuntuGIS is the only extra repo can we now remove the versioning so this doesn't happen again?

Yes, we should be able to use just qgis now instead of a specific version now that there's no repo conflict.

[hamish]

Replying to wildintellect:

Yes, we should be able to use just qgis now instead of a specific version now that there's no repo conflict.

done in r2008.

H

[jsanz]

I used aptitude on this line to see the changes just because it's my normal tool for updating my system.

I've searched for aptitude usage at bin folder and no results were found.

Sorry for the noise

[wildintellect]

Seems safe if we do this before running any other install scripts, as to make sure we don't screw up anyone's specific versions.

[wildintellect]

Opps, meant to say if we use apt-get update, apt-get upgrade Not aptitude, only so we don't mix and match package managers.

[hamish]

apt-get update && apt-get --yes upgrade added to setup.sh