Upgrading Ubuntu at work can make you rather unpopular, as the Internet bandwidth is fully utilised downloading all the updates to packages you have long since forgotten that you installed.
It also takes time, time that you should be working rather than upgrading your computer.
For these reasons I like to trickle download the upgrade over a day and only perform the actual upgrade once all the packages are ready, typically the following morning.
This is how I performed my low-bandwidth upgrade…
I finally decided to upgrade my work desktop to Debian Squeeze.
Preparing for the Upgrade
I manually removed all but the official lenny repositories (and removed the Debian Volatile repository which is no longer used), and updated them to “squeeze”: Continue Reading
I have to be careful about the bandwidth I use at work; so I limit the bandwidth of apt-get and wget.
For apt-get you just need to create a new file Continue Reading
I sometimes find myself wondering what a package’s dependencies are. This question is usually quickly satisfied with a
$ sudo apt-get install packagename and then aborting, or perhaps more elegantly
$ sudo apt-get -s install packagename to simulate the installation.
This doesn’t give you the entire picture, as it only lists the dependencies that you don’t already have; which is usually all you care about, but there are occasions when you would like to list all of a package’s dependencies, for example when planning for a system that is not built yet, or not accessible at the current time. Or just for idle curiosity! Perhaps that’s just me.