During the recent update, I ran into a conflict between these two packages. At the time I just removed one of them, but now I’m striking it again as I upgrade a less used machine and wondering whether this should be fixed.
This library converts Japanese text to romanized Japanese. The binary kakasi is an optional dependency of QuodLibet (I removed this) and python-pykakasi is a dependency of Calibre. When Calibre is updated it creates a conflict:
conflicting files:
- python-pykakasi: /usr/bin/kakasi already exists in filesystem (owned by kakasi)
So, I’m wondering is this a mistake in the python-pykakasi package? Shouldn’t it accept that kakasi could already be separately installed?
More like the two should correctly conflict … instead of simply running into the existing file.
And if the ‘parent’ packages depends can be fulfilled by either package then their depends should properly reflect that.
And/or some other combination of changes … I am not familiar with any of these packages … but normally an ‘exists in filesystem’ is not an error that should occur through normal interactions with regular repository packages but only created when someone manually works outside of the package manager with third party software sources.
Really, it’s probably not worth my time trying to sort it out, but it seems that the kakasi package (the original project) installs a C binary to /usr/bin/kakasi and the python-pykakasi package installs a python program to /usr/bin/kakasi, so they definitely should conflict.