Your message dated Tue, 19 Feb 2008 22:23:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#466519: close: it seems not related
has caused the Debian Bug report #466519,
regarding svn client doesn't work: Could not get next bucket brigade + Invalid
or incomplete multibyte or wid...: random no commit, no update
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
466519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466519
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
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/
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
and nothing has changed on the server.
I haven't been able to do much tests from other clients but till now
all commit, updates and checkout from different clients worked. So it
seems the problem was introduced by the updates above on the client.
Could be related to this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465583
but the client has ipv6 loaded...
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
--- End Message ---
--- Begin Message ---
Ivan Sergio Borgonovo a écrit :
> I started to experience the same problem on other boxes too...
>
> Update of libc6 and this problem now just seem an unlucky coincidence.
>
Ok, closing the bug with this mail.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
