On Sun, 3 Oct 2021 12:29:41 +0100 Simon McVittie wrote:
> > Either way, the documentation changes will probably be reverted when
> > the ':any' is dropped from the Python prerequisites.
>
> I don't think removing the :any from the package names in e.g.
>
On Sat, 02 Oct 2021 at 22:48:23 -0700, Felix Lechner wrote:
> I am still researching my recent commit [8] in the context of the
> rationale presented in 2013. [9] My position is that "python:any"
> implies the ability to satisfy "python".
It depends exactly what you mean by that.
Being able to
Hi,
On Sat, Oct 2, 2021 at 1:45 AM Julien Puydt wrote:
>
> so I think it's a false positive.
Actually, Lintian has required the ':any' for Python prerequisites
since 2013 [1] but the implementation was defective. [2] You are now
seeing an accurate picture of Lintian's settings [3][4][5][6][7]
On Sat, 02 Oct 2021 10:40:14 +0200 Julien Puydt wrote:
> E: python-anyio source: missing-build-dependency-for-dh-addon python3
> => python3:any | python3-all:any | python3-dev:any | python3-all-
> dev:any | dh-sequence-python3
>
> but in d/control:
> Build-Depends: debhelper-compat (= 13),
>
Package: lintian
Version: 2.107.0
Severity: normal
Updating the python-anyio package, lintian complained quite vehemently
(an error):
E: python-anyio source: missing-build-dependency-for-dh-addon python3
=> python3:any | python3-all:any | python3-dev:any | python3-all-
dev:any |
5 matches
Mail list logo
