On Sat, Jan 3, 2009 at 14:17, "Martin v. Löwis" email@example.com wrote:
I have been using bzr for all of my importlib work. It's worked out well sans the problem that SOMEONE <cough>Barry</cough> has not upgraded the bzr installation to support the newest wire protocol.
I'm probably to blame for this. Debian doesn't come with the latest bzr revision (bzr evolves way too fast for Debian, so that even their backports infrastructure doesn't provide recent binaries). I'm fairly opposed to installing non-vendor packages on www.python.org, as those typically don't see any maintenance, and often break as the regular packages get upgraded.
As a consequence, I would always request that whatever VCS Python uses: the version that is in the current Debian's "stable" distribution must be sufficient to use the VCS, and must in particular be sufficient on the server side.
Even if someone like me or Barry volunteers to maintain the installation of the DVCS software? I would be willing to do this if/when the replacement for svn is chosen.
Unfortunately, the current Debian release is stuck in political debates, so that we still can't use subversion 1.5 on the server.
This is why depending wholly on Debian for everything can be annoying. I understand the policy and support it overall, but in the case of something like a DVCS that doesn't have ridiculous dependencies like svn and someone explicitly taking the lead on the specific installation it would seem like an exception could potentially be made.