Hello,Debian has the following package:Package: python-captchaSource: pycaptchaVersion: 0.4-1Installed-Size: 788Maintainer: Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>Architecture: allDepends: python2.6 | python2.7, python (>= 2.6.6-7~), python (<< 2.8), python-imaging (>= 1.1.5), ttf-bitstream-veraDescription-en: collection of Python modules implementing CAPTCHAsThis package contains Python modules to add some captchain an application to recognize a human versus a robot.The package generates an image based on a dictionary.Description-md5: 2d19869b66fbe12deefdf153202fb4b5Tag: devel::lang:python, implemented-in::python, role::shared-libSection: pythonPriority: optionalFilename: pool/main/p/pycaptcha/python-captcha_0.4-1_all.debSize: 385570MD5sum: 4b080c1bb24da0ab0dff77fb2158fae0SHA1: 06eca771b4049072dadd97fbdd6f443b0be6c405SHA256: b85cb47d172a1070ec24e73b063933e134373c1dfcb6c61fe6f5da4d22cf65ccAccording to that homepage, the last release was 2006, so it appears to have been abandoned upstream. I can't find documentation for it. It provides the python module name "Captcha"I have a project that requires django-simple-captcha, from:It provides the python module name "captcha", comes with documentation, and has recent commits.Technically speaking, the module names don't conflict, this is only because of the case of the first character is different, which IMHO isn't sufficient. Also policy would require me to package django-simple-captcha as python-captcha, which would clash.I filed an ITP for django-simple-captcha before I realized the clash:
I considered porting my application to use python-captcha, however as that appears to be the inferior library, don't think I want to do that.What is the solution? I can think of:* Get upstream to rename django-simple-captcha. Very hard to justify when development of the conflicting package is dead.* Remove python-captcha from Debian. Nothing appears to depend on it in the Debian archive.Any thoughts?Thanks--
Brian May <brian@microcomaustralia.com.au>