Comment 5 for bug 68764

John,

As far as I can tell, nothing has changed. I did an update and try to install python-clearsilver again and got the same error.

Having never packaged anything, I'm not sure about this, but it seems from other packages are organized that the python-clearsilver package should be an empty archive with a dependency on python2.4-clearsilver (or whatever is the current version).

Instead, it contains the same set of files as the python2.4-clearsilver archive, but appears to contain a newer version of the package (0.10.3-2 vs. 0.9.13-3.2). I know nothing about this package itself (it was installed as a dependcy of something else), so I don't know if there's a reason to keep the old version, but if not, I'd suggest repackaging the current version as python2.4-clearsilver and making the package with no version number strictly a dependent on that real package. Please correct me if I've got this stuff wrong, as I'd like to get more involved once I understand the system a little better.