Control: found -1 python3-django-solo/2.1.0-1
Control: affects -1 = solo1-cli

Philip Rinn wrote:
> thanks for the bug report, but I guess you missed that solo1-cli.ships this 
> file for years (in stable, testing, unstable) while  python-django-solo was 
> just uploaded yesterday. So I think the bug is in python-django-solo actually.

I concur. I am not sure how this got misdetected. Presumably, the
heuristic concluded that since solo1-cli from experimental was
conflicting with a package from unstable that it must be the cause.
I'll have to see how I can avoid future misdetections of the same kind.
Sorry for the noise.

Helmut

Reply via email to