HI
Hey guys!
I just finished updating Sherlock, fixing the conflicts that led to this bug
being opened.
> Packager can also get rid of the only- run-one-test solution for unit
> testing, as there is built in support for offline-only unit tests via
> either `tox -e offline` (preferred for
Hey all
Upstream has been bumped to 0.15.0, and with this, the importable
module has been renamed from `sherlock` to `sherlock_project`.
Repackaging should allow both Serious bugs to be closed.
As indicated in the prior...
With this, upstream has also moved to adopt properly tagged releases,
We are planning to bump to 0.15.0 to coordinate merges for all our
planned breaking changes at once
With this, the importable module's name will be changed, avoiding
conflict. I've proposed sherlock_project to match pypi and the egg, as
Thomas recommended.
We also plan to adopt proper tagged
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
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 this discussion now being had on the deb
Hello Thomas,
On Mon, 10 Jun 2024 at 12:03, Thomas Goirand wrote:
>
> 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
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,
Control: reopen 1072733 =
Hello all,
Chris,
> > I see your point now, it seems like it should be just "Conflicts", do you
> > agree? None of those 2 packages can/should be renamed.
>
> Please see https://www.debian.org/doc/debian-policy/ch-files.html#binaries
>
> Conflicts is not appropriate for
* Samuel Henrique [240608 20:37]:
> > If they share a name but none of the API / features, then it is not
> > a correct solution.
>
> They do not share the same API.
>
> > These descriptions do not sound related at all. In this case,
> > Conflicts/Replaces is not appropriate.
>
> I see your
Hey all
Thanks for your patience. Life gets a bit busy sometimes.
I've just merged #2127 [1] upstream, switching Sherlock from
setup-tools to Poetry, from unittest to pytest, and adding tox. With
this, the site-/dist-packages dir is no longer dirtied. This bug
**should** be resolved with the new
Hello Chris,
> > > Per Debian policy this is not the correct solution for naming conflicts.
> > > Both
> > > maintainer (teams), please find a policy compliant solution together.
> >
> > The solution for this one seems correct, it's a Conflict + Replaces because
> > both packages provide a
Hi Samuel,
only replying to your question below, with new questions.
* Samuel Henrique [240608 14:04]:
> For #1072733:
>
> Chris
> > Per Debian policy this is not the correct solution for naming conflicts.
> > Both
> > maintainer (teams), please find a policy compliant solution together.
>
>
Hi everybody!
Firstly, we have to make it clear that we have two distinct bugs:
They seem to be the same because you are bumping into the only files they have
in common:
__init__.py
The first bug was due to Sherlock installing his modules in the root of the
package directories.
This has so
Control: tags 1072733 moreinfo
Control: reopen 1071007 =
Hello all,
I wasn't subscribed to both bugs so I missed some of the replies, I'm
subscribed now.
I'm sending this reply to both #1072733 and #1071007 because they are related
and I'm trying to clarify the situation on both.
Summary:
In accordance with the other Package Uploaders,
Debian Developer, Francisco Vilmar.
I will be closing the bug.
Since the problem itself, with Sherlock installing its
modules in the root of the packages, has been fixed.
Nilson F. Silva
Hi Paul!
Just clarifying!
My goal with this patch was to just solve a conflict problem by trying, not
changing your code through a patch.
But unfortunately, both attempts were not accepted by Samuel, as they did not
solve the problem itself.
This led to the bug being reopened twice as RC,
Hi Samuel!
I hope you are well!
I'm sorry for responding so late.
I had a problem with my laptop keyboard.
I just pushed a new version of shelock with a fix for the problem in the
"master" branch.
If that's ok, I'll do a merge.
Control: reopen -1 =
> I have read the other replies to the bug, which I missed previously.
> It's not upstream's intention to ship the modules in dist-packages.
Nevermind this, I misread upstream's response. Upstream contacted me to ask
about it and it's clear to me now.
Nilson:
> As Sherlock
Control: reopen -1 =
The latest upload broke the package, this time by mis-placing the files in
/usr/share/:
https://salsa.debian.org/pkg-security-team/sherlock/-/commit/58dacca3117b66341a4371431d6f38a1d35b08c9
Hi!
As Sherlock is a private module, I moved it to usr/share according to this
policy here:
https://www.debian.org/doc/packaging-manuals/python-policy/#programs-shipping-private-modules
It is not necessary to __init__py of the package as suggested by Samuel.
Thank you everyone for your help!
All --
::: Re: 1071007, ALL CONCERNED :::
I am associated with the upstream project.
This is a real bug. Discovered it some time last week. This seems to have
been introduced when we added the new pyproject file with a setuptools
backend.
For some unknown reason, the installed package would
Em sáb., 18 de mai. de 2024 às 21:08, Samuel Henrique
escreveu:
>
> Control: reopen -1 =
>
> I see on git that the bug was closed with a Conflicts+Replaces stanza, but
> that's not the correct solution for this issue.
>
> As discussed on this bugreport, the fix is to not ship the file.
>
>
Control: reopen -1 =
I see on git that the bug was closed with a Conflicts+Replaces stanza, but
that's not the correct solution for this issue.
As discussed on this bugreport, the fix is to not ship the file.
Reopening to block the problematic package to migrate to testing.
Cheers,
--
Samuel
Control: affects -1 - pycrc
Control: clone -1 -2 -3
Control: reassign -2 pycrc 0.10.0-2
Control: retitle -1 sherlock: Must not ship
/usr/lib/python3/dist-packages/__init__.py
Control: retitle -2 pycrc: Must not ship
/usr/lib/python3/dist-packages/__init__.py
Control: reassign -3 lintian 2.117.0
Package: sherlock
Version: 0.14.3+git20240511.b83f5be-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + pycrc
sherlock has an undeclared file conflict. This may result in an unpack
error from dpkg.
The file
25 matches
Mail list logo
