[Radosław Antoniuk] > That's not true. The subversion format changes. > If you try to access the older repository with a new 1.6 tortoisesvn > client, it will succeed. > Afterwards though, if you try to do anything with an older client on > the same repository, it will behave similarly to this you can see > described here: > http://subversion.tigris.org/faq.html#broken-subclipse
Oh... that is different. That is not client/server compatibility, but repository and working copy compatibility. It only matters if you share your repositories or working copies between different instances of Subversion. We do not ship multiple Subversion versions in Debian at the same time, so this really only matters if you share a single disk between two or more computers that run different versions. It is much more common to have a separate working copy on each workstation, and to only have your repository directly accessible from a single server. Anyway... I think I will target unstable and testing when Subversion 1.6.3 is released, if by then I can solve two bugs I know about. (Or you could use Ubuntu's unstable - Steve L. followed my recommendation and uploaded 1.6.1 to karmic the other day. (: ) -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
