I've reassigned it to solo1-cli,
because I thought it wasn't a library (and the start of the docs lead me to
it), but actually it is a library.
My mistake, re-reassigning to django_solo, the newcomer has to go elsewhere.
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
Control: reassign -1 python-django-solo
Hi Helmut,
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.
Best,
Package: solo1-cli
Version: 0.1.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + python3-django-solo
solo1-cli has an undeclared file conflict. This may result in an unpack
error from dpkg.
The file
4 matches
Mail list logo
