As the upstream and Debian maintainer for it, I am ok with it. It could be easily made to build for python 3 but tests would show that it is not entirely kosher. I better reupload it when it i an sure it is functioning correctly again
On June 13, 2020 1:16:58 PM EDT, "Moritz Mühlenhoff" <j...@inutil.org> wrote: >On Mon, Feb 03, 2020 at 08:36:43AM +1100, Stuart Prescott wrote: >> Dear maintainers, >> >> In the last update on pymvpa2, it sounded like upstream would soon >have sorted >> Python 3 compatibility and the FTBFS bugs for the package would soon >be fixed. >> However, there has been no upstream activity in the referenced PR >> https://github.com/PyMVPA/PyMVPA/pull/525 for many months. >> >> What are the prospects for a fixed package in the buster release >cycle? Given >> that it will have to go through NEW to gain the Python 3 module >package in any >> case, are we at the stage where it should just be removed from >Debian, perhaps >> to be reintroduced later when upstream work is completed? >> >> (There's a cost to keeping buggy packages in Debian in that they >occupy >> people's time when dealing with transitions or bug squashing. Even >finding the >> packaging Vcs to see if there has been yet-to-be uploaded progress on >these >> bugs is excessively difficult right now) > >Indeed, let's remove it from unstable for now? > >Cheers, > Moritz
