Issue #2671 wontfix

Problem committing via svn client to bitbucket repo (BB-1585)

created an issue

I saw somewhere on the bitbucket site where this can be caused by the repo being located on an older shard without svn commit support. Is this a per-account thing or a per-repo thing? I don't really care about the existing repo (it's just a test), but if it's per-account, please move me to a svn-capable shard.


Command output:



rks@atom:~/tmp/trunk$ svn status M README

rks@atom:~/tmp/trunk$ svn commit svn: Commit failed (details follow): svn: At least one property change failed; repository is unchanged svn: Server sent unexpected return value (500 Internal Server Error) in response to PROPPATCH request for '/rks1222/test/%21svn/wrk/f8ca4615-b0a5-4e49-a8ed-99bd97cb51a7/' svn: Your commit message was left in a temporary file: svn: '/home/rks/tmp/trunk/svn-commit.tmp'


Comments (5)

  1. Dylan Etkin


    The SVN support is no longer dependent on shards, in fact we have removed sharding.

    However, the svn support is still "beta" meaning that we have a bunch of bugs around it such that it does not always work. I believe that you are encountering one of those bugs, sorry.

    Can you re-run the command with a verbose flag and paste the output here? It will help us investigate the issue.

    I am afraid that we are not really spending any time on the SVN bridge at the moment but hopefully we will try to dedicate some in the medium term future.



  2. rks1222 reporter

    Hi Dylan,

    I tried setting --verbose, but svn didn't like it. None of the other options looked useful to me:

    rks@atom:~/tmp/trunk$ svn commit --cl test --message "test" --verbose
    Subcommand 'commit' doesn't accept option '-v [--verbose]'
    Type 'svn help commit' for usage.
    rks@atom:~/tmp/trunk$ svn help commit
    commit (ci): Send changes from your working copy to the repository.
    usage: commit [PATH...]
      A log message must be provided, but it can be empty.  If it is not
      given by a --message or --file option, an editor will be started.
      If any targets are (or contain) locked items, those will be
      unlocked after a successful commit.
    Valid options:
      -q [--quiet]             : print nothing, or only summary information
      -N [--non-recursive]     : obsolete; try --depth=files or --depth=immediates
      --depth ARG              : limit operation by depth ARG ('empty', 'files',
                                'immediates', or 'infinity')
      --targets ARG            : pass contents of file ARG as additional args
      --no-unlock              : don't unlock the targets
      -m [--message] ARG       : specify log message ARG
      -F [--file] ARG          : read log message from file ARG
      --force-log              : force validity of log message source
      --editor-cmd ARG         : use ARG as external editor
      --encoding ARG           : treat value as being in charset encoding ARG
      --with-revprop ARG       : set revision property ARG in new revision
                                 using the name[=value] format
      --changelist ARG         : operate only on members of changelist ARG
                                 [aliases: --cl]
      --keep-changelists       : don't delete changelists after commit
    Global options:
      --username ARG           : specify a username ARG
      --password ARG           : specify a password ARG
      --no-auth-cache          : do not cache authentication tokens
      --non-interactive        : do no interactive prompting
      --trust-server-cert      : accept unknown SSL server certificates without
                                 prompting (but only with '--non-interactive')
      --config-dir ARG         : read user configuration files from directory ARG
      --config-option ARG      : set user configuration option in the format:
                                 For example:

    Version information, if it's useful:

    rks@atom:~/tmp/trunk$ svn --version
    svn, version 1.6.12 (r955767)
       compiled Mar 22 2011, 19:47:54
    Copyright (C) 2000-2009 CollabNet.
    Subversion is open source software, see
    This product includes software developed by CollabNet (http://www.Collab.Net/).
    The following repository access (RA) modules are available:
    * ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
      - handles 'http' scheme
      - handles 'https' scheme
    * ra_svn : Module for accessing a repository using the svn network protocol.
      - with Cyrus SASL authentication
      - handles 'svn' scheme
    * ra_local : Module for accessing a repository on local disk.
      - handles 'file' scheme

    I'll try searching the other bugs to see if anything looks relevant. This was on a beta Ubuntu (11.04) server. I'll also try running the command on a different system.

  3. Log in to comment