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 sensibl
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 poi
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 "sherl
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.
>
>
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:
#1072
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 i
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
https://salsa.debian.org/pkg-security-team/sherlock/-/commit/00a20c5cc3a9c42a295e886dee
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.
>
> Reopeni
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 H
10 matches
Mail list logo
