Comment 2 for bug 68764

My workaround was simply to remove python-clearsilver, as I suspect the python2.4-clearsilver package (which has the same version number) will do the trick for whatever is depending on it. I guess I'll find out if that's the case soon.

Is this maybe an old package that should be removed? It seems that usually packages named like this are empty packages that depend on the latest more-specific version of the package, to make upgrading easier. Does this one actually contain all the same files as the python2.4-clearsilver package?