On 6/9/24 18:47, Samuel Henrique wrote:
Zigo,
I just saw that sherlock (the social networks package) moved its python
files to /usr/share, instead of /usr/lib/python3/dist-packages
. This was
the sensible thing to do, as it doesn't really need to expose itself as
Python module.
Not really, that was done by accident when Nilson was trying to remove the
system-wide init file (#1071007) and was reverted already.
Upstream has mentioned (to me) that their intention is to provide a library for
sherlock, as we've had since the package was introduced.
Well, sherlock is an app, and therefore, it's the sensible thing to do
to push it's Python code in /usr/share. IMO, it shouldn't have been
reverted.
Normally, the one that owns the PyPi name such as:
https://pypi.org/project/sherlock/
also get to have the python module name. Clearly, sherlock (the social
media package) didn't do that.
Now, if you know upstream, then probably you can convince them to rename
their lib to something that doesn't clash? And also, maybe, add its
software on PyPi?
Therefore, this bug can be closed, and there's IMO nothing more to do in
the python-sherlock (the cluster lock package), as the conflict is now
solved.
I'll reopen 1072733 since the clash still exists.
:(
Cheers,
Thomas Goirand (zigo)
