Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It will be the next revision after the one you've seen the Committed message for. For example I took and manually edited a repository to have invalid data in svn:log for revision 3. Then I did a sync to another repo and got this output:</p> <pre><code>$ svnsync sync file://`pwd`/dest Transmitting file data . Committed revision 1. Copied properties for revision 1. Transmitting file data . Committed revision 2. Copied properties for revision 2. svnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8 </code></pre> <p>The patch you referenced had the option renamed to <a href="http://subversion.tigris.org/issues/show_bug.cgi?id=3817" rel="nofollow"><code>--source-prop-encoding</code> and was added with 1.7.0</a>. If you expect your svn:log properties to be UTF-8 then you probably just want to keep fixing them as you dump though I'd guess that this may be a sign that something is corrupted in the source repository.</p> <p>If you know that your svn:log properties are not in UTF-8 then I'd suggest that you use a newer version of Subversion with the <code>--source-prop-encoding</code> option.</p> <p>You can use Subversion 1.7.x binaries to do the sync even if you want to maintain compatibility with a 1.6.x server/client. For one thing old format repositories can always be read/written by newer versions. But also the <a href="https://subversion.apache.org/docs/release-notes/1.7.html#compatibility" rel="nofollow">format for the repository didn't change between 1.6.x and 1.7.x</a>.</p> <p>You can of course build your own copy of 1.7.x and then run the svnsync out of the build tree <code>$BUILDDIR/subversion/svnsync/svnsync</code> or you can <a href="https://subversion.apache.org/packages.html" rel="nofollow">download and use a pre-built binary</a>.</p> <p>My suggestion would be just to go to 1.8.x, 1.6.x is no longer supported by the Apache Subversion project. Like I mentioned above you can maintain compatibility with a 1.6.x server, in fact you can even create a 1.6.x repository with a 1.8.x svnadmin command by doing <code>svnadmin create --compatible-version=1.6</code>.</p> <p>One last thought. Are you sure you have Subversion 1.6.17? The svn:log you reference has CRLF line endings which isn't considered to be valid for svn:* properties. Starting with Subversion 1.6.3 we started normalizing line endings to LF in svn:* properties. Using 1.6.24 that log message transfers though I get a note that it normalized properties to LF line endings.</p>
    singulars
    1. This table or related slice is empty.
    1. POsvnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBen Reser
    1. USBen Reser
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POsvnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COGreat answer; thanks. The server is using 1.6, but the repo itself is pretty old, back from probably 1.4 or earlier. My conversion job errored out the first time, and I restarted it after losing the original output. So I couldn't tell what revision was actually giving the errors. In the end, I compiled 1.7 and used the latin-1 encoding.
      singulars
      1. PO
      1. USChris Jones
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload