David Bremner <[email protected]> writes: > IMHO the right place to deal with this is upstream. And presumably upstream > already knows?
I am not sure of the best contact for upstream. Presumable the package maintainer has good contacts with upstream (Matt Palmer is listed as the package maintainer?). Talking to upstream, like it or not, is part of the job of maintaining Debian packages. It makes it easier on upstream only having to deal with one voice, the maintainer, who knows what direction they want to take the package. Also should point out there is a strong push at the moment to move Debian to Python 3.x, as Python 2.7 is no longer being developed anymore. After the release of stretch I believe the plan is not to accept any new Python 2 packages. Eventually this is going to become an RC bug as a result of phasing out Python 2.7. -- Brian May <[email protected]>
