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

Diego M. Rodriguez diego.plan9 at gmail.com
Tue Mar 15 18:34:39 UTC 2016


Hello Andreas,

> 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.

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"?)?

Best regards,
-- 
Diego M. Rodriguez
36B3 42A9 9F2F 2CFB F79B  FF9B B6C4 B901 06BC E232

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20160315/d3f59b99/attachment.sig>


More information about the Debian-med-packaging mailing list