We'll start by looking at a Subversion 1.3.2 backport to Dapper. So far , I +1 it, but we still need to test the server-side aspect of it, and whether or not an upgrade to 1.3.2 requires any manual work on the server side.
As far as a repository of risky backports, that's one of the reasons that motivated me to write prevu -- so that those with more aggressive backporting needs can easily do it themselves. I don't see a compelling reason to organize prevu'ed packages into a repository. -- Please backport subversion 1.4.0 to Breezy, Dapper and Edgy https://launchpad.net/bugs/71058 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
