Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Hello Carl and Andreas, On Sun, Jun 26, 2016 at 07:27:58AM +0200, Andreas Tille wrote: > > While renaming _this_ package was the proposed solution during most of > > the ITP discussions, please be aware that the most recent (~2 months) > > recommendation from #debian-python [1][2] would be to rename _the Python > > DNA package_ instead. I'm still trying to find out Andrea's point of > > view on this recommendation [3], though. > > My point is that I agree. If somebody would commit patches for DNA > Jellyfish this could speed up the action. > > Sorry for not setting the proper priority on this issue Thanks for stating your point of view, Andreas, and no worries in regards to the priority - I fully understand time is a scarce resource! I'll try to retake the work on the existing DNA Jellyfish patches at #819016 (for renaming the module) and append the relevant patches for renaming the binary package in the next days. On Sun, Jun 26, 2016 at 13:02:47 +1000, Carl Suster wrote: > 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: > ... Thanks for the reasonable suggestion! However, taking into account Andreas' answer, would it be reasonable to wait a sensible amount of time and see if we manage to fully rename DNA's python-jellyfish before going through with your suggestion, basically for avoiding the renaming "dance" for this package and focusing my efforts in the hopefully final solution? I'm not familiar enough with the full process, though, and cannot estimate how long it would take nor if that would be sensible in regards to the beets' package needs, so I'd basically trust your criteria if you feel the DNA renaming seems to far in the future. Best regards, -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 signature.asc Description: Digital signature
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
On Sat, Jun 25, 2016 at 06:43:09PM +0200, Diego M. Rodriguez wrote: > Hello Carl, > > > Has there been any progress on this? > > As far as I know, unfortunately this issue is still stalled due to > waiting on a decision (and action) about the naming conflicts. I think the decision is clear - but there is no real action due to more urgent things to do. > > Since python3-jellyfish from the DNA package has been in the archive for a > > little while, it seems like it would be a bad idea to use that name and > > hence > > the only real option is to differ from upstream here. Maybe > > python*-jellyfish-strings (or -matching)? > > While renaming _this_ package was the proposed solution during most of > the ITP discussions, please be aware that the most recent (~2 months) > recommendation from #debian-python [1][2] would be to rename _the Python > DNA package_ instead. I'm still trying to find out Andrea's point of > view on this recommendation [3], though. My point is that I agree. If somebody would commit patches for DNA Jellyfish this could speed up the action. Sorry for not setting the proper priority on this issue Andreas. > The details are a bit scattered among the RFS, ITP, etc., but a short > recap would be that, for this bug to move forward it would be needed to: > 1) rename the existing python3-jellyfish Python bindings *module* name > (in progress at [4]) > 2) make a decision on which package is to be renamed (this one vs DNA) > 3) proceed with the actually renaming of the package > > I'll be a bit short on time during next week, but I intend to update the > package to the newest upstream version (released this week) early next > month, and also do my best to try to give another push to getting this > ITP forward - any suggestions, comments and help would be much > appreciated. > > Best regards, > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807432#80 > [2] http://paste.debian.net/432489 > [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819016#30 > [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819016 > -- > Diego M. Rodriguez > 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 > -- http://fam-tille.de
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
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
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Hello Carl, > Has there been any progress on this? As far as I know, unfortunately this issue is still stalled due to waiting on a decision (and action) about the naming conflicts. > Since python3-jellyfish from the DNA package has been in the archive for a > little while, it seems like it would be a bad idea to use that name and hence > the only real option is to differ from upstream here. Maybe > python*-jellyfish-strings (or -matching)? While renaming _this_ package was the proposed solution during most of the ITP discussions, please be aware that the most recent (~2 months) recommendation from #debian-python [1][2] would be to rename _the Python DNA package_ instead. I'm still trying to find out Andrea's point of view on this recommendation [3], though. The details are a bit scattered among the RFS, ITP, etc., but a short recap would be that, for this bug to move forward it would be needed to: 1) rename the existing python3-jellyfish Python bindings *module* name (in progress at [4]) 2) make a decision on which package is to be renamed (this one vs DNA) 3) proceed with the actually renaming of the package I'll be a bit short on time during next week, but I intend to update the package to the newest upstream version (released this week) early next month, and also do my best to try to give another push to getting this ITP forward - any suggestions, comments and help would be much appreciated. Best regards, [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807432#80 [2] http://paste.debian.net/432489 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819016#30 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819016 -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 signature.asc Description: Digital signature
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Has there been any progress on this? Getting this package into the archive is blocking the upgrade of beets (#775719) which is by now lagging far behind upstream, so it would be nice to have this obstacle out of the way. Since python3-jellyfish from the DNA package has been in the archive for a little while, it seems like it would be a bad idea to use that name and hence the only real option is to differ from upstream here. Maybe python*-jellyfish-strings (or -matching)? Cheers, Carl
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Just a note to reflect that I have just uploaded a new package to mentors (0.5.4-1) [1] as a result of a new upstream release, which fixes a minor problem on the README examples [2], among other changes. [1] https://mentors.debian.net/package/python-jellyfish [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807432#70 -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 signature.asc Description: Digital signature
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
An update in regards to the Debian package name conflict (ie. not the Python module name conflict discussed on [1]): the upstream author has confirmed that it has "no real preference" over the chosen Debian package name, and we temptatively agreed on using something similar to "python-jellyfishstr" (or a similar variation that hints that the package is string-matching related) if needed. [1] https://lists.debian.org/debian-python/2015/12/msg00107.html -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 signature.asc Description: Digital signature
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Hello Andreas, > Thanks for your understanding and as said above - some name different > from python-jellyfish would be helpful. Sure thing, and thanks for the clarification on the intent of enabling the bindings on the original package. I fully understand and agree that coming up with a new name seems like the sensible thing to do, and one that would be better handled at this stage before the package is released indeed. I will contact upstream in the hopes of picking a reasonable name for this package, and update the bug and files accordingly. Again, thanks for raising awereness to this issue! Best regards, -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 signature.asc Description: Digital signature
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Hi Diego, On Mon, Dec 28, 2015 at 06:42:15PM +0100, Diego M. Rodriguez wrote: > > My only minor doubt comes from the fact that the upstream DNA jellyfish > package seems to provide binding to several languages [1], Python being among > them. It seems the bindings are currently not being included in Debian as an > individual package, but I'm wondering if it would be advisable to preemptively > reserve the "python-jellyfish" name for them, just in case they are included > in the future. Thanks a lot for checking and by doing so teking responsibility for work that is on my (or the Debian Med teams) table. Since I took over the jellyfish package from a maintainer who left the team I trusted on his initial work without doing these checks. Under this circumstances I wonder whether you could choose a different name than python-jellyfish since I'm just checking the opportunity to provide Perl and Python bindings which might be really interesting for DNA jellyfish users. > Again, thanks for your comments, and I'd be happy to make any further changes > if needed! Thanks for your understanding and as said above - some name different from python-jellyfish would be helpful. Kind regards Andreas. -- http://fam-tille.de
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Hello Andreas, > I'd leave it to your opinion whether you think there is a chance for > really confusing the packages or whether an additional hint might add > confusion. May be README.Debian would be a less noisy place to mention > this. Thanks again for your feedback and tips, they are most welcome. After taking another look at the situation, I am fairly confident that the risk of conflicts should indeed be minimal, and opted for the README.Debian route. The latest version of the package on mentors and the preliminary VCS has been updated. My only minor doubt comes from the fact that the upstream DNA jellyfish package seems to provide binding to several languages [1], Python being among them. It seems the bindings are currently not being included in Debian as an individual package, but I'm wondering if it would be advisable to preemptively reserve the "python-jellyfish" name for them, just in case they are included in the future. Again, thanks for your comments, and I'd be happy to make any further changes if needed! [1] https://github.com/gmarcais/Jellyfish/tree/develop#binding-to-script-languages -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 signature.asc Description: Digital signature
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Hi Diego, On Wed, Dec 23, 2015 at 02:35:10PM +0100, Diego M. Rodriguez wrote: > Hello Andreas, > > and thanks for the heads up! I did notice the potential naming conflict and > the existence of the DNA-related package you mention on your reply, and opted > for simply prepending the "python-" prefix to this package (as upstream also > chose just "jellyfish" as the official name of the software). I noticed this and think that is fine. > I'd be happy to make the differentiation more obvious, although I could not > find the official Debian guidelines for solving these cases. As long there is no file name conflict there is nothing to solve. > Would it be > desirable to rename the package to something less prone to confusion, or would > it be enough to include some clarification string on the package description? I'd leave it to your opinion whether you think there is a chance for really confusing the packages or whether an additional hint might add confusion. May be README.Debian would be a less noisy place to mention this. Kind regards Andreas. -- http://fam-tille.de
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Hello Andreas, and thanks for the heads up! I did notice the potential naming conflict and the existence of the DNA-related package you mention on your reply, and opted for simply prepending the "python-" prefix to this package (as upstream also chose just "jellyfish" as the official name of the software). I'd be happy to make the differentiation more obvious, although I could not find the official Debian guidelines for solving these cases. Would it be desirable to rename the package to something less prone to confusion, or would it be enough to include some clarification string on the package description? Best regards, On Wed, Dec 23, 2015 at 09:19:47AM +0100, Andreas Tille wrote: > Hi, > > sorry for the late response. I just want to note that we have a > (non-Python) jellyfish inside Debian which is developed at > https://github.com/gmarcais/Jellyfish. > > I do not see a name conflict but I wonder whether some hint might > be sensible. > > Kind regards > > Andreas. -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 signature.asc Description: Digital signature
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Hi, sorry for the late response. I just want to note that we have a (non-Python) jellyfish inside Debian which is developed at https://github.com/gmarcais/Jellyfish. I do not see a name conflict but I wonder whether some hint might be sensible. Kind regards Andreas. On Mon, Nov 30, 2015 at 01:21:27PM +0100, Diego M. Rodriguez wrote: > Package: wnpp > Severity: wishlist > Owner: "Diego M. Rodriguez" > > * Package name: python-jellyfish > Version : 0.5.1 > Upstream Author : James Turk > * URL : https://github.com/jamesturk/jellyfish > * License : BSD-2-clause > Programming Lang: Python > Description : Python library for doing approximate and phonetic > matching of strings > > Jellyfish is a python library for doing approximate and phonetic > matching of strings. Includes algorithms for string comparison > (Levenshtein Distance, Damerau-Levenshtein Distance, Jaro Distance, > Jaro-Winkler Distance, Match Rating Approach Comparison, Hamming > Distance) and phonetic encoding (American Soundex, Metaphone, NYSIIS, > Match Rating Codex). > > > This package is a dependency on the latest versions of the "beets" > package, as noted in a recent bug report [1]. Jellyfish itself has no > external dependencies, and includes an optional C implementation of its > algorithms compiled using the distutils build_ext command [2]. > > Ideally I'd love to maintain this package under the umbrella and > hopefully guidance of the Debian Python Modules Team. > > Please note that this package is unrelated to the existing "jellyfish" > debian package [3]. > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775719#10 > [2] https://github.com/jamesturk/cjellyfish > [3] https://packages.debian.org/jessie/jellyfish > > -- > Diego M. Rodriguez > 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 > -- http://fam-tille.de
Bug#806716: ITP: python-jellyfish -- Python library for doing approximate and phonetic matching of strings
Package: wnpp Severity: wishlist Owner: "Diego M. Rodriguez" * Package name: python-jellyfish Version : 0.5.1 Upstream Author : James Turk * URL : https://github.com/jamesturk/jellyfish * License : BSD-2-clause Programming Lang: Python Description : Python library for doing approximate and phonetic matching of strings Jellyfish is a python library for doing approximate and phonetic matching of strings. Includes algorithms for string comparison (Levenshtein Distance, Damerau-Levenshtein Distance, Jaro Distance, Jaro-Winkler Distance, Match Rating Approach Comparison, Hamming Distance) and phonetic encoding (American Soundex, Metaphone, NYSIIS, Match Rating Codex). This package is a dependency on the latest versions of the "beets" package, as noted in a recent bug report [1]. Jellyfish itself has no external dependencies, and includes an optional C implementation of its algorithms compiled using the distutils build_ext command [2]. Ideally I'd love to maintain this package under the umbrella and hopefully guidance of the Debian Python Modules Team. Please note that this package is unrelated to the existing "jellyfish" debian package [3]. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775719#10 [2] https://github.com/jamesturk/cjellyfish [3] https://packages.debian.org/jessie/jellyfish -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232 signature.asc Description: Digital signature
