Bug#883053: dependency-on-python-version-marked-for-end-of-life doesn't match python:any dependency

[Niels Thykier <niels@thykier.net>]

On Wed, 29 Nov 2017 20:43:05 +0900 Chris Lamb <lamby@debian.org> wrote:
> Hi Matthias,
> 
> > As seen with the dput-ng binary, the
> > dependency-on-python-version-marked-for-end-of-life doesn't match the python:any
> > dependency.
> 
> As I understand the code, the following should work:
> 
>   --- a/checks/python.pm
>   +++ b/checks/python.pm
>   @@ -83,7 +83,7 @@ sub _run_binary {
>                for my $dep (@PYTHON2) {
>                    tag 'dependency-on-python-version-marked-for-end-of-life',
>                      "($field: $dep)"
>   -                  if $info->relation($field)->implies($dep);
>   +                  if $info->relation($field)->restriction_less->implies($dep);
>                }
>            }
>        }
> 
> However, it still does not match. (NB. there is no relation_noarch for
> Binary.pm, which might be a symptom of the root cause..)
> 
> My testcase is:
> 
> [...]
> 
> 
> Any pointers, Niels et al.? :)
> 
> 
> [...]

I think it would just be a question of using "python2:any" instead of
"python2" in the @PYTHON2 list.  As I recall, Lintian knows that "X:any"
implies "X" (but "X" does not imply "X:any" as X:any is a superset of X).

Thanks,
~Niels