When upgrading packages on Ubuntu using the apt-get upgrade command you may notice that some packages are not upgraded. Ubuntu will not upgrade packages that could have a major impact to service on the server such as the kernel, kernel headers, MySQL packages, and various others. The packages are held back by aptitude as a safeguard to keep people from upgrading packages that might keep the server from rebooting or that might corrupt something like a database. Below we show the error in more detail and explain the command that can be run to upgrade the packages that are being held back.
While working to verify some packages in Ubuntu 12.04 had backport patches installed properly I needed to list installed package versions. To do this you can install a package called apt-show-versions which will allow you to list all installed packages and their versions with ease. This likely works on most Ubuntu versions but was tested on Ubuntu 12.04 also know as Precise Pangolin and Ubuntu 12.10 also known as Quantal Quetzal. Follow the instructions below to install apt-show-versions and then list all installed packages and their versions.
I needed to use SVN on a new installation of Mountain Lion OSX on my Macbook Pro and initially assumed it would be there because I already had Xcode installed however it was not or was not located in my path. After playing around in the Xcode interface for a moment I located the Command Line Tools package available for download which ended up installing svn on the command line. Below I describe how to verify if SVN is installed on OSX and explain how to install it if it does not already exist.
Recently received a 1U IPSU NetGate ALIX Single to perform some testing with pfSense on this type of platform. I was looking for a way to track the device and hoping to use DMI information so needed to first install dmidecode. Anyhow ran into a couple issues which are noted below along with resolutions for those issues.
If you have used the debconf-set-selections command that I mentioned in a previous article there will likely be more questions that come up over time such as how to view variables that have been set for specific packages or how to flush the debconf database. Below I show a couple example that explain how to view variables in the debconf database and also how to remove those variables from the database.