Ivan Sergio Borgonovo a écrit : > Package: libc6 > Version: 2.3.6.ds1-13etch5 > Severity: grave > > Summary: > > svn was working perfectly. The repository isn't huge (~500 commit). > Now when I commit I get: > Could not get next bucket brigade (server side) > > when I update I get: > client denied by server configuration: /var/www/
This really looks like a problem on the server side. > Could not fetch resource information. > (84)Invalid or incomplete multibyte or wide character: Requests for a > collection must have a trailing slash on the URI. > > On the client side I get: > REPORT di '/svn/main/!svn/vcc/default': 400 Bad Request > > I did a svnadmin verify and svnadmin recover and everything looked > fine on the server. > I did try fsfsverify.py on all revs too. > > Sometimes backing up a file on the local copy, forcing a delete, > adding the file back works... sometimes it doesn't. > I've been able to commit file one by one, some get committed with no > extra hassle, some need this backup/delete/add process, some just > can't be committed. > > I did try to make a commit from other boxes and they worked... > I did a co from other boxes and they worked too. > > the server is a debian sarge (pentium) > Debian sarge (Apache/2.0.54 (Debian GNU/Linux) DAV/2 SVN/1.1.4) > > the client is a debian etch (dual Xeon) > svn, versione 1.4.2 (r22196) > compilato Nov 10 2006, 17:39:50 > > Nothing was changed on the server, most recent update were on the > client (etch) and coincidentally I haven't been able to use svn > starting from the below update on the client. > > linux-image-2.6-686 2.6.18+6etch2 -> 2.6.18+6etch3 > apache2 2.2.3-4+etch3 -> 2.2.3-4+etch4 > apache2-mpm-prefork 2.2.3-4+etch3 -> 2.2.3-4+etch4 > apache2-utils 2.2.3-4+etch3 -> 2.2.3-4+etch4 > apache2.2-common 2.2.3-4+etch3 -> 2.2.3-4+etch4 > cpio 2.6-17 -> 2.6-18 > libc6 2.3.6.ds1-13etch4 -> 2.3.6.ds1-13etch5 > libc6-dev 2.3.6.ds1-13etch4 -> 2.3.6.ds1-13etch5 > libc6-xen 2.3.6.ds1-13etch4 -> 2.3.6.ds1-13etch5 > locales 2.3.6.ds1-13etch4 -> 2.3.6.ds1-13etch5 Have you tried to downgrade libc6 packages to the old version? I really doubt this problem is due to the glibc upgrade. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
