bzr-svn badly horks svn repository if pushing a changeset which includes a new symlink

[GiuseppeVerde]

Binary package hint: bzr-svn

bzr-svn badly horks a svn repository when pushing a changeset which contains a new symlink. "Badly horks" here means that nobody can check out any subsequent changes until the symlink is removed. If you're using bzr-svn, not even that will help you; you cannot pull or branch from the repo until you get an updated version of bzr-svn.

This is likely also a bug in svn, as svn shouldn't allow DoS like that. :)

Steps to reproduce:
  1) Get a svn repo
  2) Branch the svn repo with bzr (using bzr-svn)
  3) Add a symlink to the repo
  4) Commit the symlink
  5) Push the updates back to the svn repo
  6) Check out the project from svn or try to pull updates from it via bzr (not the bzr repo you made the symlink changes from, as it'll just report that there are no changes)
  7) Watch the fireworks

A fix was comitted yesterday in the bzr-svn maintainer's 0.4 branch. However, bzr-svn 0.4 apparently requires bzr 1 (says the maintainer). The fix is in revno 816 at http://people.samba.org/bzr/jelmer/bzr-svn/0.4/

Additionally, the maintainer says that a great many bugfixes are present from Gutsy's current version (0.4.1) going to the latest version (0.4.5).

This bug is a grave bug, as it effectively prevents further access to the SVN repo!! At least backport it, if you don't want to bring bzr-svn 0.4 up to the latest version.

[GiuseppeVerde (launchpad-digitasaru)]

I added svn to this, as they may need to be on the lookout for this particular type of horkage.

[Jelmer Vernooij (jelmer)]

This has been fixed, change will hopefully be in 0.4.6 (hardy).

[Jelmer Vernooij (jelmer)]

I wouldn't consider this a subversion bug, since it can only get into this state if you have a broken caller (such as broken versions of bzr-svn).

[Jelmer Vernooij (jelmer)]

0.4.6 was released