As I wrote earlier, I spent a fair chunk of this weekend upgrading Debian from Wheezy to Jessie.
Well, as part of that upgrade, some packages were removed unexpectedly. While some packages had replacements, there was no replacement for “gedit” or “seahorse”. While I don’t rely on either on a day to day basis, they’re nice to have when you want a convenient graphic text editor or graphical manager for assorted encryption keys.
I also noticed that while the packages for PostgreSQL 9.4 had been installed, they’d actually been installed alongside PostgreSQL 9.1. So no actual upgrade had occurred there per se. It was up to me.
Well, I don’t use PostgreSQL very often. In my day to day work, I use MySQL/MariaDB with Koha. While I sometimes use PostgreSQL with DSpace and other projects, I’m more familiar with MySQL. So I did some Googling and found this link: http://nixmash.com/postgresql/upgrading-postgresql-9-1-to-9-3-in-ubuntu/.
In essence, I ran the following:
“service postgresql stop”
“pg_dropcluster –stop 9.4 main”
“pg_upgradecluster 9.1 main”
“service postgresql start 9.4”
Then I tried “psql” which reported that both the client and server were 9.4, rather than before when it said that the client was 9.4 but the server was 9.1.
I also poked around in my “dspace” database to make sure I could still access all the data stored therein.
“service postgresql stop”
“pg_dropcluster –stop 9.1 main”
“service postgresql start”
“apt-get remove postgresql-9.1”
“apt-get remove postgresql-client-9.1”
There were still some remnants of 9.1 around so I had to do the following:
“apt-get purge postgresql-9.1”
“dpkg -l | grep postgres”
That last command just shows me what packages are installed with “postgres” in there name. I can now see that 9.1 is totally gone and only 9.4 remains. I can also verify that by doing:
And noting that the 9.1 directory is gone and only 9.4 remains. Same with “/etc/postgresql”.
Actually, it’s interesting if I run the following to list all packages that have “rc”, that is packages that have been “removed” but which still have “configuration” files present:
“dpkg -l | egrep ‘^rc'”
I see several hundred packages that have been removed but still have configuration files present.
It’s actually interesting reading through these, as I see another package that Debian removed which I actually wanted to keep. It was “swat” which is a web-based tool for managing Samba shares.
Interestingly enough… while it was easy to re-install “seahorse” and “gedit”, it looks like “swat” doesn’t have a package in Jessie. The latest package I see for it is in Wheezy.
After a quick Google, I can see that’s because “swat” had too many security vulnerabilities and there was no one willing to maintain it. Honestly, I rarely used it in the past, and it actually created problems in the long-run because it would overwrite the configuration file which you may have edited using Ansible or edited by hand.
In fact, during the upgrade, I noticed that /etc/samba/smb.conf had an update. At the time, I’d backed up the existing file (for the millionth time), and let the package version replace it. I just spent a few minutes comparing the differences between the files with “vimdiff”, and added what few differences that were still required (ie a couple of shares and some global options).
Anyway, most of these “rc” entries don’t really bother me, so I won’t bother with them for now.
After a “service smbd restart” and a check over that the Samba shares are working as expected across the network, I think it’s time to take a well deserved break.