Bug#299718: causes data loss

Severity: grave I am having to revert back to svk 0.29 every time I run a dist-upgrade on my workstation. After reading the descriptions of severity levels, I've determined this is actually a "grave" bug since it causes data loss in the remote repository being committed to. -- Matthew R. Scott

Bug#299718: svk: smerge -l ignores commit message, uses "1" instead

Package: svk Version: 0.30-1 Severity: important The smerge operation works correctly, but totally ignores the commit message that you give it, and instead uses "1" as the commit message. To attempt to reproduce this problem, do this: ~$ svk mkdir //test1 (empty commit message) ~$ svk cp