Summary: | svn upgrade errors not handled | ||
---|---|---|---|
Product: | [Developer tools] kdesrc-build | Reporter: | Will Stephenson <wstephenson> |
Component: | general | Assignee: | Michael Pyne <mpyne> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.15.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kdesrc-build/9a7a4d6330fa247e5cd57ea8e196b26229f34222 | Version Fixed In: | |
Sentry Crash Report: |
Description
Will Stephenson
2012-08-02 03:55:12 UTC
I take it this is Subversion 1.7 or something? My current svn (1.6.17) doesn't even have an upgrade command... :-/ Git commit 9a7a4d6330fa247e5cd57ea8e196b26229f34222 by Michael Pyne. Committed on 04/08/2012 at 01:52. Pushed by mpyne into branch 'master'. Upgrade svn 1.7 repositories automatically. Subversion 1.7 requires a manual upgrade of the working copy in order to do anything (even to run svn status). Luckily there's an error message ID for this case so it's not too hard to grep for situations where this is necessary. One problematic element is that since even 'svn info' doesn't work in this situation, --pretend mode doesn't work either for svn modules. For now I just throw an exception (after the check) when in pretend mode so avoid follow-on useless error messages. It was interesting how I still had the old 1.6.17 for so long -- turns out I had forgot to rename my subversion selector asking for unstable versions in Gentoo (at some point their package name changed from dev-util/subversion to dev-vcs/subversion, which I didn't keep up with). Thanks Will Stephenson for the bug report. M +66 -3 kdesrc-build http://commits.kde.org/kdesrc-build/9a7a4d6330fa247e5cd57ea8e196b26229f34222 |