• General
• Repository error messages
• Client specific
  • TortoiseSVN
  • Subversion command line interface

General

If you have problems using Subversion on IgorExchange, please first consult the Using Subversion for Version Control documentation.

If you still cannot find the answer to your question you should submit your question via the IgorExchange Contact Form (choose "Subversion (SVN) related problem" in the Category selection box). Please include the following information whenever you submit a Subversion related question:

• Your operating system (with version) and the Subversion client you are using (eg. TortoiseSVN, Subversion command line interface, etc.) with the version
• What you are trying to do, and the exact steps you tried, including any commands (if applicable)
• Your IgorExchange account name and your Subversion user name
• The name of the project to which you are trying to make changes
• The exact error message (if applicable)

Repository error messages

If you are a developer using Subversion, you may occasionally receive error messages from the repository server when trying to commit files or create branches or tags. Most of those error messages will point you to one of the issues below.

• Properties not defined

  In order for text files that are edited on operating systems that use different line endings to behave properly, the IgorExchange repository requires that certain Subversion properties be set on all files that are added to the repository. In short, text files (this includes Igor Pro procedure files) must have the svn:eol-style=native property set and all other files must have the svn:mime-type property set. Furthermore, if the svn:mime-type property is set to text/plain then the svn:eol-style=native property must also be set for that file. Information on how to set up your Subversion front end to do this automatically and more detailed information on why these properties must be set can be found at Configuring your Subversion client.

• Access denied

  You do not have the proper permission to change files in the directory you are trying to modify. This usually happens because you are trying to commit files to the directory of a project for which you are not the owner or maintainer. If this is the case, you should contact the owner of the project and request SVN access to the project. See Controlling Subversion access for more information.

• File denied

  A file that you tried to commit is not allowed in the repository. Certain file types, including compressed/archived file formats (eg. .zip, .tar, .gz, .tgz), are not allowed in the IgorExchange repository because the packaging scripts will automatically create compressed and archived files for download by users. Try the operation again after removing any files of this format from your commit. For information on how to instruct IgorExchange to package your code into a .zip file that others can download, see Creating a release with Subversion.

• Project not found

  This error message can come up for a few reasons:

  1. The project you are trying to commit files to has not yet been created. You must create the project before you are able to commit files to the repository for that project. See Creating a project for more information.
  2. Your project has already been created, but you are trying to commit files to the wrong directory in the repository (often to the base directory). For links to step-by-step tutorials that include instructions on how to import/add the proper project directory structure and files to the repository, see Using Subversion clients (with tutorials).

• User not found

  The Subversion server accepted your Subversion username and password, however the Subversion username you used could not be matched to a valid account on IgorExchange. The most common reason you would get this message is that the IgorExchange accounts are not properly synchronized with those on the Subversion server. Wait about 10 minutes and then try the operation again. If you still get this error, that means that there could be a bug in our access scripts. Please see the instructions in the General section above regarding how to contact the IgorExchange administrators to report the problem.

• Invalid tag

  You tried to create a tag but the name of the tag is not allowed by the server. Please see Branches and Tags on IgorExchange for detailed information on what format is required for tag naming. If you believe that you are trying to create a valid tag, you may be trying to do it in the wrong way. For links to complete tutorials that include step-by-step instructions for how to create tags, see Using Subversion clients (with tutorials).

• Invalid branch

  You tried to create a branch but the name of the branch is not allowed by the server. Please see Branches and Tags on IgorExchange for detailed information on what format is required for branch naming. If you believe that you are trying to create a valid branch, you may be trying to do it in the wrong way. For links to complete tutorials that include step-by-step instructions for how to create tags, see Using Subversion clients (with tutorials).

• Invalid tag but valid branch

  You tried to create a tag but the name of the tag is not allowed by the server (however the name you are trying would be valid for a branch). Please see Branches and Tags on IgorExchange for detailed information on what format is required for tag naming. If you believe that you are trying to create a valid tag, you may be trying to do it in the wrong way. For links to complete tutorials that include step-by-step instructions for how to create tags, see Using Subversion clients (with tutorials).

• Invalid branch but valid tag

  You tried to create a branch but the name of the branch is not allowed by the server (however the name you are trying would be valid for a tag). Please see Branches and Tags on IgorExchange for detailed information on what format is required for branch naming. If you believe that you are trying to create a valid branch, you may be trying to do it in the wrong way. For links to complete tutorials that include step-by-step instructions for how to create tags, see Using Subversion clients (with tutorials).

• Tag delete denied

  IgorExchange users are allowed to delete tags in directories on the repository to which they have access (that is, if they are an owner or maintainer of the project). If you receive this error message there may be a bug in our tag access control scripts. Please see the instructions in the General section above regarding how to contact the IgorExchange administrators to report the problem.

• Release tag in use

  Though normally users are able to delete tags that they otherwise have permission to change, users are not allowed to delete or move tags that are the target of releases. Instead of trying to delete the tag, it is usually better to just create a new tag and then create a release that points to that new tag.

• Invalid characters and other file name/path issues

  There is no specific error message for this problem, however file names with many special characters can cause errors of various types. The following characters are not allowed in file names:
  
#&;`|*?~<>^()[]{}$\, \x0A \xFF

  Spaces are allowed in file names.

  The Subversion server will treat files in a case sensitive way. In other words, readme.txt is not the same file as README.txt. Some operating systems (eg. Windows) do not treat file paths as case sensitive.

Client specific

• TortoiseSVN

• Subversion Command Line Interface

  Subversion error message 210002

  This message usually means that you are not using the latest version of Subversion. See Using the Subversion Command line interface for information on the version that is currently required and links to download that version.