Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #13188
| From | Sandro Tosi <morph@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python, linux.debian.bugs.dist |
| Subject | Re: Python louvain packages naming confusion. |
| Date | 2021-02-11 00:40 +0100 |
| Message-ID | <BH7fr-4uJ-5@gated-at.bofh.it> (permalink) |
| References | <BGJG9-6Wa-1@gated-at.bofh.it> <BGU8y-4Y9-3@gated-at.bofh.it> <BH4hA-2Je-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
+Steffen explicitly, given the team is not in Maintainer nor Uploaders > How about renaming the current python3-louvain package to > python3-community-louvain using a normal transition package. that's incorrect: src:python-louvain builds a module called `community` (that includes also a cli tool), so the resulting binary package should either be `python3-community` or `community` where the cli is the main product and the module is installed in /usr/share/ to support it. > Then I can submit the other louvain package using a binary package name > of python3-louvain-igraph. this is incorrect too: (perspective) src:louvain (or src:louvain-igraph, as the upstream called their repo) builds a module called `louvain` so the resulting binary package should be `python3-louvain` eventually conflicting with the existing package (<< current-version-in-sid) src:python-louvain is in a pretty bad shape: it received a single upload in late 2018, it has an RC bug since a *day* after that upload, and it has never been in testing: tbh i dont consider this package to be maintained/targeting any stable release, so i believe you can "take over" the namespace given you seem to show interest in maintaining https://github.com/vtraag/louvain-igraph Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-09 23:30 +0100
Re: Python louvain packages naming confusion. Paul Wise <pabs@debian.org> - 2021-02-10 02:50 +0100
Re: Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-10 05:30 +0100
Re: Python louvain packages naming confusion. "Michael R. Crusoe" <crusoe@debian.org> - 2021-02-10 10:50 +0100
Bug#982417: Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-10 19:40 +0100
Re: Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-10 21:30 +0100
Re: Python louvain packages naming confusion. Sandro Tosi <morph@debian.org> - 2021-02-11 00:40 +0100
Bug#982417: Python louvain packages naming confusion. Diane Trout <diane@ghic.org> - 2021-02-11 02:00 +0100
csiph-web