[Debian-med-packaging] Bug#806716: Jellyfish name conflicts

[Andreas Tille]

Hi Diego,

On Tue, Mar 15, 2016 at 07:34:39PM +0100, Diego M. Rodriguez wrote:
> > This was not really intended but now it happened.  We now need to
> > decide about the two options:
> > 
> >   1. Cancel the upload to new and drop the python3-jellyfish package
> >   2. Just leave this as is and follow the advise of the jellyfish
> >      author quoted on top of this mail to the python list[4] to
> >      rename just the Python module.
> > 
> > I think option 2. is better for all parts and if you agree I'd
> > immediately cancel the upload to new.
> 
> thanks for the detailed clarification on the events surrounding the
> package and the prompt response!
> 
> I would be happy to go with either option (personally leaning towards
> option 2 as well), and basically rely on your expertise - the upstream
> string-jellyfish author has explicitely mentioned that he has no strong
> opinion on the Debian package name and I don't have either.

Hmmmm, ftpmaster was fast - now python-jellyfish is accepted.  This only
leaves us option 2 without fiddling around to much.
 
> With this in mind, I'm wondering if this would be a good time to rename
> this ITP and the RFS (and the mentors package, etc) to the hopefully
> final Debian package name ("python-jellyfishstr"?)?

The latter sounds sensible.  Sorry for all the confusion and leaving you
alone a bit with this issue.

Kind regards

      Andreas.



-- 
http://fam-tille.de