Hi Diego,
Thanks for the update. I hadn't noticed that popcon reports only two
installations of the existing python3-jellyfish, so I guess that it really
isn't a problem to eventually take over that name.
The name src:jellyfish is surely off-limits anyway so this package will need a
different source package name in any case. Since the only consideration is the
binary package name which is fairy painless to rename later, then my suggestion
would be:
* upload this package as src:jellyfish-strings (or src:jellyfish-python or
whatever) now with binary package names like python{,3}-jellyfish-strings (it
seems better with a dash separating the disambiguation part so as to appear
less like a different module name).
* if and when the DNA package is renamed, whether or not this has cleared the
NEW queue, upload a new version of the same source package with the binary
package names python{,3}-jellyfish. As I understand it there would be no need
to keep transitional packages around for long barring a Debian stable release
in the meantime, so it wouldn't be messy or difficult.
Since you already did all the work to package it, it seems a waste to let it
hang in purgatory over choosing a nice name :P
Cheers,
Carl
