Your message dated Sun, 9 Jun 2024 14:00:56 +0200
with message-id <f035c704-17c7-49e3-8092-d62e3332f...@debian.org>
and subject line Re: python-Sherlock conflict sherlock
has caused the Debian Bug report #1072733,
regarding sherlock has an undeclared file conflict on
/usr/lib/python3/dist-packages/sherlock/__init__.py
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1072733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sherlock
Version: 0.14.4+git20240531.e5ad3c4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + python3-sherlock
sherlock has an undeclared file conflict. This may result in an unpack
error from dpkg.
The file /usr/lib/python3/dist-packages/sherlock/__init__.py is
contained in the packages
* python3-sherlock/0.4.1-2 as present in trixie|unstable
* sherlock/0.14.4+git20240531.e5ad3c4-1 as present in unstable
These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.
Kind regards
The Debian Usr Merge Analysis Tool
This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
On 6/7/24 14:05, Nilson Silva wrote:
Hello Thomas Goirand!
I am a maintainer of sherlock and you are the maintainer of python-sherlock.
Our packages conflict when installed in the same environment.
[...]
Hi,
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.
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.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
