Bug#736523: Indeed, python-concurrent.futures is the same

2014-01-25 Thread Dimitri John Ledkov
On 25 January 2014 17:21, Sandro Tosi wrote: >> Huh? Thomas seemed to be doing the right thing per the DPMT standards >> etc; > > if you change the python helper, you HAVE TO contact who's maintaining > the package and have they ack the change, that's the team standard. > No, one does not within

Bug#736523: Indeed, python-concurrent.futures is the same

2014-01-25 Thread Sandro Tosi
> This kind of message saddens me. the same holds for calling my packages as having "lots of problems" (none of them ever being reported as bugs by any of the current users, nor even by you) of accusing me of having done something without thinking. > I'm not expecting this kind of > interaction,

Bug#736523: Indeed, python-concurrent.futures is the same

2014-01-25 Thread Sandro Tosi
> Huh? Thomas seemed to be doing the right thing per the DPMT standards > etc; if you change the python helper, you HAVE TO contact who's maintaining the package and have they ack the change, that's the team standard. > if you don't want the package to be team maintained, perhaps take > it out of

Bug#736523: Indeed, python-concurrent.futures is the same

2014-01-25 Thread Thomas Goirand
On 01/25/2014 06:01 PM, Sandro Tosi wrote: > Sorry, what? and you didn't think to contact me first to almost > rewrite the package? If there's problems, open bugs. Revert your > changes or I'll do at the first occasion. and mainly, why don't you go > away from DPMT once and for all? you're doing mo

Bug#736523: Indeed, python-concurrent.futures is the same

2014-01-25 Thread Robert Collins
On 25 January 2014 23:01, Sandro Tosi wrote: > Sorry, what? and you didn't think to contact me first to almost > rewrite the package? If there's problems, open bugs. Revert your > changes or I'll do at the first occasion. and mainly, why don't you go > away from DPMT once and for all? you're doing

Bug#736523: Indeed, python-concurrent.futures is the same

2014-01-25 Thread Sandro Tosi
Sorry, what? and you didn't think to contact me first to almost rewrite the package? If there's problems, open bugs. Revert your changes or I'll do at the first occasion. and mainly, why don't you go away from DPMT once and for all? you're doing more harm than good here. you're not welcome here. O

Bug#736523: Indeed, python-concurrent.futures is the same

2014-01-24 Thread Thomas Goirand
Hi, Indeed, that's the same source package. Indeed as well, there's lots of problems in the current package in Debian. The current maintainer, Sandro Tosi , completely removes the "futures" API. As a consequence, there's no way for a normal package to use concurrent.futures correctly. I have bee