Re: conflicting packages python-pysocks and python-socksipy

2016-01-09 Thread W. Martin Borgert
On 2016-01-08 01:54, Scott Kitterman wrote: ... > This is done (#810306). ... > Bug#810309: torchat > Bug#810308: python-sleekxmpp > Bug#810307: offlineimap Scott, many thanks for filing the bugs and fixing python-socksipy!

Re: conflicting packages python-pysocks and python-socksipy

2016-01-07 Thread Scott Kitterman
On Monday, January 04, 2016 07:58:26 PM Scott Kitterman wrote: > On January 4, 2016 2:18:22 PM EST, "W. Martin Borgert" wrote: > >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: Recen

Re: conflicting packages python-pysocks and python-socksipy

2016-01-04 Thread Scott Kitterman
On January 4, 2016 2:18:22 PM EST, "W. Martin Borgert" wrote: >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 follow

conflicting packages python-pysocks and python-socksipy

2016-01-04 Thread W. Martin Borgert
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 alrea