You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Florian Schricker <fs...@web.de> on 2005/07/06 09:50:14 UTC
entries file corruption
Hello everybody,
I'm fairly new to this list and Subversion in general so please bear
with me and point me to wherever my question has been answered before;
I searched, but without luck ...
After using our svn-repository for some time I suddenly, out of nowhere
I'd say, get strange file corruptions:
some if not all .svn/entries files all over the repository go haywire!
I've uploaded one of the damaged entries-file of our repository's root
if somebody's interested here:
http://www.uni-koblenz.de/~eyerq/entries
With these damaged enties-files the whole repository is not usable
anymore, svn constantly fails with
svn: XML parser failed in ''
svn: Malformed XML: not well-formed (invalid token) at line 1
(which is not amazing given the above entries-files as input I guess
_any_ XML parser would fail :-/)
Is there anything I can do to fix these entries-files? Is this a known
bug? Any more information I can provide to help sort things out?
puzzled, any help greatly appreciated since this happens frequently!
regards,
Florian Schricker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: entries file corruption
Posted by Florian Schricker <fs...@web.de>.
On Sun, 2005-07-10 at 17:04 -0400, John Szakmeister wrote:
> You could help out a little more by providing some more information.
Well ... I tried to rule out every possible source of these problems and
came to the conclusion that KDevelop-3.2.1's support for subversion
seems to be horribly broken; I activated this feature and re-compiled
and that's when these problems came up. After removing subversion
support from KDevelop-3.2.1 everything seems to be fine now, no
"spoiled" repository anymore since then! :-)
(And before that it goofed up almost three times a week...)
My work-queue's quite full atm but I guess after some weeks I'll try and
dig into it more deeply - maybe KDevelop's bugzilla or whatnot wants to
hear from me... ;-)
> Also, have you tried checking out a new working copy? I'd be very
> surprised if your repository is unusable. More than likely, it's just
> your working copy that's unusable.
Of course you're right - I can always check out a new working copy; it
was just the extra-work of merging in changed files from the broken tree
in the newly checked-out one by hand that made me report this.
> If you can give a few more details, perhaps we can figure out what
> happened.
In case this happens again, although I have KDevelop's subversion
support disabled, I'll report promptly and will try to give more
details. *fingers crossed
Thank you all for commenting on this strange issue,
Florian Schricker
--
A most overlooked advantage to owning a computer is: if they foul up
there's no law against wacking them around a bit.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: entries file corruption
Posted by John Szakmeister <jo...@szakmeister.net>.
On Wednesday 06 July 2005 05:50, Florian Schricker wrote:
> Hello everybody,
>
>
> I'm fairly new to this list and Subversion in general so please bear
> with me and point me to wherever my question has been answered before;
> I searched, but without luck ...
>
> After using our svn-repository for some time I suddenly, out of nowhere
> I'd say, get strange file corruptions:
>
> some if not all .svn/entries files all over the repository go
> haywire!
>
> I've uploaded one of the damaged entries-file of our repository's root
> if somebody's interested here:
>
> http://www.uni-koblenz.de/~eyerq/entries
>
> With these damaged enties-files the whole repository is not usable
> anymore, svn constantly fails with
>
> svn: XML parser failed in ''
> svn: Malformed XML: not well-formed (invalid token) at line 1
>
> (which is not amazing given the above entries-files as input I guess
> _any_ XML parser would fail :-/)
>
> Is there anything I can do to fix these entries-files? Is this a known
> bug? Any more information I can provide to help sort things out?
You could help out a little more by providing some more information.
http://svn.collab.net/repos/svn/trunk/BUGS has the details.
Also, have you tried checking out a new working copy? I'd be very
surprised if your repository is unusable. More than likely, it's just
your working copy that's unusable.
If you can give a few more details, perhaps we can figure out what
happened.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: entries file corruption
Posted by Ryan Schmidt <su...@ryandesign.com>.
On 06.07.2005, at 11:50, Florian Schricker wrote:
> After using our svn-repository for some time I suddenly, out of
> nowhere
> I'd say, get strange file corruptions:
>
> some if not all .svn/entries files all over the repository go
> haywire!
>
> I've uploaded one of the damaged entries-file of our repository's root
> if somebody's interested here:
>
> http://www.uni-koblenz.de/~eyerq/entries
That's certainly very odd. Never seen anything like that before.
Can't imagine how that's happening. Ben, maybe? Or Karl?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org