Databases
StackOverflow2013
Postsdbo
POsvnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POsvnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8
    primarykey
    data
    text
    <p>I'm syncing a bunch of repositories from one machine to another; one repository fails with this error:</p> <pre><code>svnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8 </code></pre> <p>This seems to be a frequently asked question, but I'm struggling with these answers:</p> <ul> <li><a href="https://stackoverflow.com/questions/4702390/syncronize-an-svn-repo-svnsync-with-encoding-errors">Synchronize an SVN repo (svnsync) with encoding errors</a> refers to a patch that seemingly hasn't been applied to my 1.6.17 svnsync. (There's no --source-encoding or similar option.)</li> <li>Many discussions reference an article at <a href="https://help.codesion.com/View.jsp?title=How-to-Deal-with-Svn-Backups-Failing-Due-to-UTF8-Error&amp;procId=fc29d38015b4321e01b645a2e02ae5e9" rel="nofollow noreferrer">https://help.codesion.com/View.jsp?title=How-to-Deal-with-Svn-Backups-Failing-Due-to-UTF8-Error&amp;procId=fc29d38015b4321e01b645a2e02ae5e9</a> but that link is dead.</li> </ul> <p>It seems like svnsync should tell me which revision it's unable to import, but it gives no such clue. Assuming it was struggling with rev 1, I did this:</p> <pre><code>$ svn propget --revprop -r1 --strict svn:log | hexdump -C 00000000 69 6e 69 74 69 61 6c 20 63 68 65 63 6b 69 6e 0d |initial checkin.| 00000010 0a 0d 0a 5b 69 6d 70 6f 72 74 65 64 20 66 72 6f |...[imported fro| 00000020 6d 20 43 56 53 20 62 79 20 63 76 73 32 70 34 20 |m CVS by cvs2p4 | 00000030 61 74 20 32 30 30 35 2f 30 37 2f 30 35 20 31 35 |at 2005/07/05 15| 00000040 3a 34 30 3a 32 36 5d 0d 0a |:40:26]..| 00000049 </code></pre> <p>But that all looks like reasonable 7-bit ASCII, so UTF-8 should accept it.</p> <p>I think all I need to know is which revision has the bad svn:log property; then I can fix it using svn propedit. So how do I find the bad revision(s)?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USChris Jones
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POsvnsync: Cannot accept 'svn:log' property because it is not encoded in UTF-8
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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