Bug#404207: more information
severity 404207 normal
I've been pondering why this might have happened for me, and I think I
realise what's gone on. I've probably done the rmdir and ls stuff myself
to fix bug #402716 prior to package upgrade (as per the workaround
posted in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402716;msg=10).
Then 4:3.5.5a.dfsg.1-2 assumed that it was still a dir and hence broke.
Since the breakage was relying on an assumption that would normally be
true, this is probably not RC. So I'll downgrade.
However, if this transition has to happen from sarge -> etch, then it
would be nice if it could cope with scenarios like this, as people are
likely to implement such a quick workaround for an annoying bug when