I wonder if the core issue at hand here is simply that the python VCSs are on a resource writable by only one person (meaning no one else can contribute)? See: https://code.launchpad.net/~doko/python/pkg2.7-debian https://code.launchpad.net/~doko/python/pkg3.2-debian
If that's the case, then perhaps a simple voteable option would be a request to re-home the VCS somewhere that can support multiple contributors (possibly stating preferably on a Debian resource like alioth)? Perhaps, the alternative team could start the alioth VCS on their own anyway, and use that to sort of NMU maintain the package (while it appears to be somewhat ignored now). Sort of like we're doing for wine: http://lists.alioth.debian.org/pipermail/pkg-wine-party/2012-May/thread.html Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
