Problems after upgrape to svn 0.27

[ma...@gmx.net]

hi @ll

i have a problem, after i updated to svn 0.27.

when i try to look at the repository w/ a browser i get Error 500 internal
server error.

when i look @ the error_log of apache i get this entries:

[Mon Aug 18 13:51:33 2003] [error] [client xx.xx.xx.xx] Could not fetch
resource information.  [500, #0], referer: https://yy.yy.yy.yy/
[Mon Aug 18 13:51:33 2003] [error] [client xx.xx.xx.xx] Could not open the
root of the repository  [500, #160027], referer: https://yy.yy.yy.yy/
[Mon Aug 18 13:51:33 2003] [error] [client xx.xx.xx.xx] (17)File exists:
Malformed node-revision skeleton  [500, #160027], referer: https://yy.yy.yy.yy/

any ideas whats going wrong here?

greetz
achim

-- 
COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test
--------------------------------------------------
1. GMX TopMail - Platz 1 und Testsieger!
2. GMX ProMail - Platz 2 und Preis-Qualitätssieger!
3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Problems after upgrape to svn 0.27

[cm...@collab.net]

mailing.lists@gmx.net writes:

> hi @ll
> 
> i have a problem, after i updated to svn 0.27.

Did you update to 0.27, or to HEAD?  I asked, because...

> [Mon Aug 18 13:51:33 2003] [error] [client xx.xx.xx.xx] (17)File
> exists: Malformed node-revision skeleton [500, #160027], referer:
> https://yy.yy.yy.yy/

... after 0.27 was rolled out, we changed the filesystem schema in an
incompatible way that would yeild *exactly* this error if you didn't
put your repository through an svnadmin dump/load cycle.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org