(cc'ing fladi as Uploader of django-fsm and django-fsm-admin) Hi,
I would like to package django-fsm-2[1] which is a fork/continuation of django-fsm[2] which is already in Debian. However I'm a bit unsure what's the best way forward. Both call themselves "django_fsm" internally, so they can't be co-installed. The only rdep of django-fsm in Debian is python3-django-fsm-admin which seems to be very inactive upstream. AIUI, there are two options: 1. Update src:django-fsm to use django-fsm-2 as new upstream. This might/will make python3-django-fsm-admin uninstallable or broken, I would need to test it. If so, python3-django-fsm-admin will have to be RM'd. 2. Package django-fsm-2 as src:django-fsm-2 and add Conflicts: python3-django-fsm to it, so they won't be co-installed. I think option 2 would be friendlier to possible users out there and also maybe more correct as it will match the name on PyPI. I'm looking for feedback what's the best way forward as I have no experience so far handling PyPI vs. module vs. package name discrepancies. Cheers, sur5r P.S.: Please cc me as I'm not currently subscribed to the list. [1] https://github.com/django-commons/django-fsm-2 [2] https://github.com/viewflow/django-fsm -- ceterum censeo microsoftem esse delendam.
pgpsRRTGPv3gL.pgp
Description: OpenPGP digital signature
