Re: conflict python-captcha vs django-captcha
This isn't necessarily fatal. See python-dnspython (provides the dns module)
and python-dns (provides the DNS module). Sine python-captcha is already
used, I'd recommend picking an alternate name for your package. Since python
module names are case sensitive, this thing can happen and we shouldn't
preclude the two different modules being in Debian.
Scott K
On Friday, June 20, 2014 09:23:31 Brian May wrote:
> Hello,
>
> Just noticed that Olivier Sallou did a new upload of python-captcha
> recently, so presumably this means there is some interest in keeping
> python-captcha in Debian. Have CCed him in case he can offer any opinions.
>
> Thanks.
>
> On 5 May 2014 09:58, Brian May <brian@microcomaustralia.com.au> wrote:
> > Hello,
> >
> > Debian has the following package:
> >
> > Package: python-captcha
> > Source: pycaptcha
> > Version: 0.4-1
> > Installed-Size: 788
> > Maintainer: Debian Python Modules Team <
> > python-modules-team@lists.alioth.debian.org>
> > Architecture: all
> > Depends: python2.6 | python2.7, python (>= 2.6.6-7~), python (<< 2.8),
> > python-imaging (>= 1.1.5), ttf-bitstream-vera
> > Description-en: collection of Python modules implementing CAPTCHAs
> >
> > This package contains Python modules to add some captcha
> > in an application to recognize a human versus a robot.
> > The package generates an image based on a dictionary.
> >
> > Homepage: http://pypi.python.org/pypi/PyCAPTCHA/0.4
> > Description-md5: 2d19869b66fbe12deefdf153202fb4b5
> > Tag: devel::lang:python, implemented-in::python, role::shared-lib
> > Section: python
> > Priority: optional
> > Filename: pool/main/p/pycaptcha/python-captcha_0.4-1_all.deb
> > Size: 385570
> > MD5sum: 4b080c1bb24da0ab0dff77fb2158fae0
> > SHA1: 06eca771b4049072dadd97fbdd6f443b0be6c405
> > SHA256: b85cb47d172a1070ec24e73b063933e134373c1dfcb6c61fe6f5da4d22cf65cc
> >
> >
> > According 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:
> >
> > https://github.com/mbi/django-simple-captcha
> > http://readthedocs.org/docs/django-simple-captcha
> > https://pypi.python.org/pypi/django-simple-captcha/0.4.2
> >
> > 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:
> >
> > http://bugs.debian.org/746632
> >
> > 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>
Reply to: