On 6/12/24 22:25, Paul Pfeister wrote:
Any opposition to naming the importable package `sherlocklib`?
The installable package (via apt) would presumably remain `sherlock`
The importable module (via python) would become `sherlocklib`
The binary exec would remain `sherlock`
Fine for me, as long
On 6/10/24 23:43, Paul Pfeister wrote:
When building the rpm, I named the (rpm) package sherlock-project to
have parity with PyPI, due to the same conflicting package. The
importable module is still simply sherlock, however, which is _less than
ideal_, and should probably be addressed.
With t
Any opposition to naming the importable package `sherlocklib`?
The installable package (via apt) would presumably remain `sherlock`
The importable module (via python) would become `sherlocklib`
The binary exec would remain `sherlock`
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, tha
Hi Thomas!
Correct me if I'm wrong. But I believe that our packages
conflict because they assume the same name at compile time.
Sherlock
#!/usr/bin/make -f
#export DH_VERBOSE = 1
export PYBUILD_NAME=sherlock
export PYBUILD_TEST_CUSTOM=1
pyhon-sherlock
https://tracker.debian.org/media/packages/
Control: reopen -1
Control: reassign -1 sherlock,python3-sherlock
On Fri, Jun 07, 2024 at 12:09:08PM +, Debian Bug Tracking System wrote:
> sherlock (0.14.4+git20240531.e5ad3c4-2) unstable; urgency=medium
> .
>* Add Conflicts and Replaces fields in the sherlock binary. (Closes:
> #10727
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/
7 matches
Mail list logo
