Comment 9 for bug 703230

My guess is that it happened in the past when the package switched from directory to that symlink (between dapper and hardy somewhen) that it didn't get handled properly ("A directory will never be replaced by a symbolic link to a directory or vice versa" (Debian policy §6.6.4)). But as this didn't cause any problems till now it went unnoticed. So only system which got installed a couple releases ago and got upgraded constantly should be affected.