Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8059
| Path | csiph.com!au2pb.net!feeder.erje.net!1.eu.feeder.erje.net!news.albasani.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | "W. Martin Borgert" <debacle@debian.org> |
| Newsgroups | linux.debian.maint.python |
| Subject | conflicting packages python-pysocks and python-socksipy |
| Date | Mon, 04 Jan 2016 20:20:03 +0100 |
| Message-ID | <qNiPF-7CQ-29@gated-at.bofh.it> (permalink) |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Mon Jan 4 19:18:40 2016 |
| Old-Return-Path | <debacle@debian.org> |
| X-Amavis-Spam-Status | No, score=-7.6 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | using cached result; rate: -5 |
| Old-X-Envelope-From | debacle@debian.org |
| Old-X-Envelope-To | <debian-python@lists.debian.org> |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=utf-8 |
| Content-Disposition | inline |
| User-Agent | Mutt/1.5.24 (2015-08-30) |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/13377 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/20160104191822.GA9605@fama |
| Approved | robomod@news.nic.it |
| Lines | 24 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Mon, 4 Jan 2016 20:18:22 +0100 |
| X-Original-Message-ID | <20160104191822.GA9605@fama> |
| Xref | csiph.com linux.debian.maint.python:8059 |
Show key headers only | View raw
Hi, TLDR: Both are the same, providing the "socks" module. We should remove one of them. Maybe renaming the other to python-socks. Longer story: Recently, I upgraded the outdated python-socksipy package. This involved following a new upstream. Later I was informed, that the new upstream was already packaged under the name python-pysocks. Questions: - shall we remove one of the package? (proposal: yes) - which of the two packages should be removed from Debian? (proposal: remove pysocks, just because socksipy is older) - shall the other package provide dummy transitional packages? (proposal: yes) - shall we rename the binary package to python-socks? (proposal: yes) Any ideas or opinions? TIA & Cheers
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread
conflicting packages python-pysocks and python-socksipy "W. Martin Borgert" <debacle@debian.org> - 2016-01-04 20:20 +0100
Re: conflicting packages python-pysocks and python-socksipy Scott Kitterman <debian@kitterman.com> - 2016-01-05 02:00 +0100
Re: conflicting packages python-pysocks and python-socksipy Scott Kitterman <debian@kitterman.com> - 2016-01-08 08:00 +0100
Re: conflicting packages python-pysocks and python-socksipy "W. Martin Borgert" <debacle@debian.org> - 2016-01-09 17:30 +0100
csiph-web