Can this issue please be filed as a bug? There are three recent threads
concerning UTF-8 errors mentioned on the users mailing list that appear
to be the same problem.
Thanks much,
-Steve
-------- Original Message --------
Subject: Re: "Commit failed" / "Invalid UTF-8 sequence" messages when
doing a commit in SVN 1.5.1
Date: Wed, 27 Aug 2008 08:24:31 -0700
From: JP Slavinsky <jpslav_at_gmail.com>
To: Daniel Shahaf <d.s_at_daniel.shahaf.name>
CC: users_at_subversion.tigris.org
References:
<113d67850808211602i6f31d321redb62009acaa1077_at_mail.gmail.com>
<alpine.561.1.10.0808221553040.4608_at_daniel2.local>
On Fri, Aug 22, 2008 at 6:07 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name
<mailto:d.s_at_daniel.shahaf.name>> wrote:
JP Slavinsky wrote on Thu, 21 Aug 2008 at 16:02 -0700:
> Howdy,
>
> My problem: every time I commit to the repository, I get a
"Commit failed"
> message talking about an "invalid UTF-8 sequence". While the
message says
> that the commit failed, the commit is actually always successful
in the
> repository. However, on the client-side (both command line and
Subclipse),
> the working copy isn't up-to-date and calls to update seem to
produce lots
> of issues (conflicts, etc).
>
> My setup: yesterday, I upgraded from from SVN 1.4.4 to SVN 1.5.1.
<http://1.5.1.> I built
> 1.5.1 from source, as I did for 1.4.4. <http://1.4.4.> I access
my repositories over HTTP
> using Apache 2.0.59. <http://2.0.59.> The SVN server is on
RedHat 4. Things in 1.4.4 used to
> work fine, both from a linux command line and from
Eclipse/Subclipse on
> Windows. Now, both the command line and subclipse attempts at
committing
> give the error message described above and in the example below.
>
> My fellow users recently experiencing similar (if not exactly the
same)
> problems
> http://svn.haxx.se/users/archive-2008-08/0444.shtml
> http://svn.haxx.se/users/archive-2008-08/0725.shtml
> (For the life of me I couldn't figure out how to add to their
threads -
> sorry about that).
>
> Any thoughts on why this error is being presented and how to get
rid of it?
>
> Below, I have pasted a log of the steps I take to reproduce the
problem. I
> create a repository, check it out, add a file, do a commit (which
gives the
> nasty error message), show that my client doesn't believe the
commit worked,
> then show that the repository has indeed been updated.
>
Thanks for the transcript, very helpful (and saves a bunch of
questions).
> --------------------------------------------------
> [root_at_cutlass v1.5]$ svnadmin create sandbox
Does the error go away if you create a BDB repository instead?
> [root_at_cutlass v1.5]$ chown -R apache:apache sandbox
> [root_at_cutlass v1.5]$ exit
> [slavinsk_at_cutlass v1.5]$ cd ~/temp/workspace/
> [slavinsk@cutlass workspace]$ svn co http://localhost/svn/sandbox
> Authentication realm: <http://localhost:80> Sandbox SVN
Repository (v1.5)
> Password for 'slavinsk':
> Checked out revision 0.
> [slavinsk_at_cutlass workspace]$ cd sandbox/
> [slavinsk_at_cutlass sandbox]$ touch test.txt
> [slavinsk_at_cutlass sandbox]$ svn add test.txt
> A test.txt
> [slavinsk_at_cutlass sandbox]$ svn commit -m "Committing a dummy file"
> Adding test.txt
> Transmitting file data .svn: Commit failed (details follow):
> svn: Valid UTF-8 data
> (hex: 1c)
> followed by invalid UTF-8 sequence
> (hex: a4 01)
All reports of this error have "a4 01" as the non-UTF-8 sequence.
> [slavinsk_at_cutlass sandbox]$ svn status
> A test.txt
> [slavinsk_at_cutlass sandbox]$ svnlook tree /svn/v1.5/sandbox
> /
> test.txt
> --------------------------------------------------
>
Daniel -- thanks for the response. I don't believe that have the
Berkeley DB option available, so I don't know if there is a problem when
using it. For me, all reports of the invalid UTF-8 sequence do have
"a4 01".
Below I've include a sample of the apache error log. Is anyone else
having problems with SVN 1.5.1 and Apache 2.0.x?
[...] Could not MERGE resource
"/svn/sandbox/!svn/act/026bfc8d-63e8-4f49-91c5-75958fdd7e1b" into
"/svn/sandbox/trunk". [409, #0]
[...] An error occurred while committing the transaction. [409, #22]
[...] Valid UTF-8 data\n(hex: 1c)\nfollowed by invalid UTF-8
sequence\n(hex: a4 01) [409, #22]
[...] Could not DELETE
/svn/sandbox/!svn/act/026bfc8d-63e8-4f49-91c5-75958fdd7e1b. [500, #0]
[...] could not open transaction. [500, #2]
[...] Can't open file '/svn/v1.5/sandbox/db/transactions/1-1.txn/props':
No such file or directory [500, #2]
[...] Could not MERGE resource
"/svn/sandbox/!svn/act/181a52d4-37fe-443d-82f9-2cfb1109c5bf" into
"/svn/sandbox/trunk". [409, #0]
[...] An error occurred while committing the transaction. [409, #22]
[...] Valid UTF-8 data\n(hex: 1c)\nfollowed by invalid UTF-8
sequence\n(hex: a4 01) [409, #22]
[...] Could not DELETE
/svn/sandbox/!svn/act/181a52d4-37fe-443d-82f9-2cfb1109c5bf. [500, #0]
[...] could not open transaction. [500, #2]
[...] Can't open file '/svn/v1.5/sandbox/db/transactions/2-2.txn/props':
No such file or directory [500, #2]
[...] Could not CHECKOUT resource
/svn/sandbox/!svn/ver/2/trunk/test.txt. [409, #0]
[...] resource out of date; try updating [409, #160024]
[...] Could not DELETE
/svn/sandbox/!svn/act/1f07b546-b721-474f-9c82-8c41de1c10e9. [500, #0]
[...] could not abort transaction. [500, #22]
[...] Transaction cleanup failed [500, #22]
[...] Valid UTF-8 data\n(hex: 1c)\nfollowed by invalid UTF-8
sequence\n(hex: a4 01) [500, #22]
[...] Could not MERGE resource
"/svn/sandbox/!svn/act/10990bbe-b92d-41a7-acca-c752915a8dca" into
"/svn/sandbox/trunk". [409, #0]
where "[...]" is "[TimeStamp] [error] [client 127.0.0.1 <http://127.0.0.1>]"
Thanks, JP
Received on 2008-08-28 18:19:40 CEST