Agreed.  I'll leave it to the maintainer/ITP owner to sort things out.

Scott K

On Tuesday, December 29, 2015 12:59:17 PM Paul Tagliamonte wrote:
> In the meantime, I suggest we both avoid uploading any python*-jellyfish
> packages
> 
>   Paul
> 
> On Tue, Dec 29, 2015 at 12:56 PM, Scott Kitterman <deb...@kitterman.com>
> 
> wrote:
> > I think the respective maintainers should talk and then discuss with their
> > upstreams as the collision potential isn't just in Debian.
> > 
> > Scott K
> > 
> > On Tuesday, December 29, 2015 12:27:37 PM Paul Tagliamonte wrote:
> > > Just FYI - there's a Python module called Jellyfish about to be
> > > uploaded;
> > > can we resolve the name collision early?
> > > 
> > > https://pypi.python.org/pypi/jellyfish
> > > 
> > > Paul
> > > 
> > > On Tue, Dec 29, 2015 at 12:06 PM, Scott Kitterman <deb...@kitterman.com>
> > > 
> > > wrote:
> > > > On Tuesday, December 29, 2015 11:52:07 AM Scott Kitterman wrote:
> > > > > On Tuesday, December 29, 2015 12:30:14 AM Andreas Tille wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > I realised that for jellyfish[1] Python bindings can be
> > 
> > activated.  I
> > 
> > > > > > tried to do so and configuring and building works fine - but I
> > 
> > have no
> > 
> > > > > > idea how to sensibly install the files into the python-jellyfish
> > > > > > package.  Any idea how to call swig/python/setup.py or do
> > > > > > something
> > > > 
> > > > else
> > > > 
> > > > > > to install the files into the right location.
> > > > > > 
> > > > > > Any help?
> > > > > > 
> > > > > > Kind regards
> > > > > > 
> > > > > >         Andreas.
> > > > > > 
> > > > > > [1] git://anonscm.debian.org/debian-med/jellyfish.git
> > > > > 
> > > > > I haven't been able to actually test this since when I try to build
> > 
> > it,
> > 
> > > > > I
> > > > > get this error:
> > > > > 
> > > > > jellyfish_wrap.cxx:3104:33: fatal error: jellyfish/mer_dna.hpp: No
> > 
> > such
> > 
> > > > file
> > > > 
> > > > > or directory
> > > > > 
> > > > > I think it should ~work.  Note that these bindings are for python3,
> > 
> > not
> > 
> > > > > python.  I've adjusted things accordingly.  The configure changes I
> > 
> > made
> > 
> > > > (so
> > > > 
> > > > > that configure wouldn't fail) mean perl bindings don't get built
> > > > 
> > > > either.  I
> > > > 
> > > > > didn't check if that was working before.
> > > > > 
> > > > > Scott K
> > > > 
> > > > Correction: It's not in the diff, but I had to remove the
> > 
> > auto-configure
> > 
> > > > override to get through configure.
> > > > 
> > > > Scott K

Reply via email to