libttf.so.2 for package: nagios

This was the ominous error I got every time I tried to upgrade nagios from what CentOS 5 provides in its base repository (2.12) to the more recent 3.0.6 provided in RPMForge's repository. I couldn't figure out what was going on and the Internet was full of accounts of the error that magically vanished the next day.

I don't know what they all had done wrong but I finally figured out what I'd done wrong to deserve this error :). I'd made the mistake of installing the rpmforge-release package meant for CentOS 4 instead of CentOS 5. This meant I was trying to install the el4 version of the nagios-3.0.6 package which apparently had this dependency. Before encountering this problem, however, I'd switched to the CentOS 5 repository so I didn't make the connection until I decided to read every letter of a yum install report:

[root@services ~]# yum install nagios
Loading "priorities" plugin
Loading "fastestmirror" plugin
Loading mirror speeds from cached hostfile
* epel: mirror.hiwaay.net
* rpmforge: apt.sw.be
* base: mirror.trouble-free.net
* updates: centos.mirror.nac.net
* centosplus: centos.mirror.nac.net
* addons: mirror.nyi.net
* extras: centos.mirror.nac.net
0 packages excluded due to repository priority protections
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package nagios.i386 0:3.0.6-1.el4.rf set to be updated
--> Processing Dependency: libttf.so.2 for package: nagios
--> Finished Dependency Resolution
Error: Missing Dependency: libttf.so.2 is needed by package nagios

I then realized why this problem might've fixed itself the next day - the yum cache might've become stale enough to be rebuilt. At that time yum would realize the el4 repository no longer existed and would remove it from the cache and replace it with the information about the el5 repository. When running a yum install nagios against the el5 repository, we get much more pleasant output:

[root@services ~]# yum install nagios
Loading "priorities" plugin
Loading "fastestmirror" plugin
Loading mirror speeds from cached hostfile
* epel: mirror.hiwaay.net
* rpmforge: apt.sw.be
* base: mirror.trouble-free.net
* updates: centos.mirror.nac.net
* centosplus: centos.mirror.nac.net
* addons: mirror.nyi.net
* extras: centos.mirror.nac.net
0 packages excluded due to repository priority protections
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package nagios.i386 0:3.0.6-1.el5.rf set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
nagios i386 3.0.6-1.el5.rf rpmforge 3.6 M

Transaction Summary
=============================================================================
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)

Total download size: 3.6 M
Is this ok [y/N]: y

The moral of the story? After changing anything in your yum repositories, make sure to run:

yum clean all
yum makecache

Upgrading Ubuntu 8.10 (Intrepid Ibex) to KDE 4.2

With KDE 4.2 officially released and in possession of quite a few positive reviews (unless I'm looking in the wrong places), I wanted to give it a shot but it hadn't been back-ported to Ubuntu 8.10 yet. I searched around and found that one can enable an experimental Ubuntu repository where one can install KDE 4.2 from.

Long story short, I ended up following this site on upgrading to 4.2. I ran the apt-get while I was away from my computer and when I returned, lo and behold, instead of finding a nice KDE 4.2 package install log I found an error with installing some packages. I did what anyone else would do - I didn't believe my eyes and re-ran the command hoping to brute force my way through this :) Here's what I saw:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
krita-data kword-data koshell kthesaurus kpresenter krita kugar kword ksysguardd kchart karbon compizconfig-backend-kconfig
kspread libpoppler-qt2 kplato libwv2-1c2 kexi libpqxx-2.6.9ldbl kpresenter-data
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
kde-window-manager kdebase-workspace-data libplasma3
The following packages will be REMOVED:
libplasma2
The following NEW packages will be installed:
libplasma3
The following packages will be upgraded:
kde-window-manager kdebase-workspace-data
2 upgraded, 1 newly installed, 1 to remove and 73 not upgraded.
6 not fully installed or removed.
Need to get 0B/10.0MB of archives.
After this operation, 12.3kB of additional disk space will be used.
Do you want to continue [Y/n]?
(Reading database ... 252512 files and directories currently installed.)
Preparing to replace kde-window-manager 4:4.1.3-0ubuntu1~intrepid1 (using .../kde-window-manager_4%3a4.2.0-0ubuntu1~intrepid1~ppa7_i386.deb) ...
Unpacking replacement kde-window-manager ...
dpkg: error processing /var/cache/apt/archives/kde-window-manager_4%3a4.2.0-0ubuntu1~intrepid1~ppa7_i386.deb (--unpack):
trying to overwrite `/usr/share/kde4/apps/kconf_update/plasma-add-shortcut-to-menu.upd', which is also in package kdebase-workspace-data
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/kde-window-manager_4%3a4.2.0-0ubuntu1~intrepid1~ppa7_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

After much searching and trying tools like synaptic and aptitude I went for the sniper rifle: dpkg. I removed the offending packages kde-window-manager and kdebase-workspace-data. Now my apt-get is running smoothly in the background. Let's hope it finished upgrading me to KDE 4.2 :)

KMail Integration with Microsoft Exchange

I found this interesting post on the kde-pim mailing list which is very to-the-point and informative on how to connect KMail to Exchange. You do need IMAP enabled on the Exchange server but once you get over that hurdle - and believe me, in a pure Microsoft shop it's a big hurdle - you're good to go.

I haven't gotten Calendar integration working just yet but I haven't put a lot of time into it yet. This page on the KDE Wiki explains how to use webdav to perform one-way syncs against an Exchange server using a plugin for KOrganizer.

Edit: Even brought it to my attention that the KDE Wiki link is no longer working.  It seems the KDE wiki has changed structure since I was last on it.  I found Jason Kasper's blog, however, where he's talking about a ruby-based solution to the 1-way sync between an Exchange OWA server and KOrganizer.