On 2011-11-22, at 18:49, "Philip Martin" wrote:
> Aleksandr Sidorenko writes:
>
>> Since upgrading the svn client to 1.7.1 (following the server's
>> upgrade to the same version), we are getting the following error when
>> doing a commit:
>>
>
On 2011-11-22, at 16:09 , Aleksandr Sidorenko wrote:
> Hi everyone,
>
> Since upgrading the svn client to 1.7.1 (following the server's upgrade to
> the same version), we are getting the following error when doing a commit:
>
>svn: E175002: Commit failed (details fol
t) in
response to POST request for '/xxx/!svn/me'
This happens on a freshly-checked out working copy. We are using Apache as a
front-end (mod_dav_svn). A commit done via the file system is successful.
Any ideas on what's going on?
Aleksandr Sidorenko
Administrateur systèmes/rése
On 2011-11-16, at 11:37 , Aleksandr Sidorenko wrote:
> On 2011-11-16, at 11:15 , Philip Martin wrote:
>
>> Aleksandr Sidorenko writes:
>>
>>> The sqlite command worked (I see the expected output), but I suspect that's
>>> because the rep-cache.db fi
On 2011-11-16, at 11:15 , Philip Martin wrote:
> Aleksandr Sidorenko writes:
>
>> The sqlite command worked (I see the expected output), but I suspect that's
>> because the rep-cache.db file was already there (since 1.6.12). If I move
>> it, though, the file is
On 2011-11-16, at 11:15 , Philip Martin wrote:
>> ...
>
> Try this patch:
>
> Index: subversion/libsvn_fs_fs/fs_fs.c
> ===
> --- subversion/libsvn_fs_fs/fs_fs.c (revision 1202738)
> +++ subversion/libsvn_fs_fs/fs_fs.c (worki
> "Bert Huijben" writes:
>
>> You get in this branch if a previous atomic initialization call failed: the
>> callback function failed and returned an error. This result is then ignored
>> in some code paths.
>>
>> It is most likely not caused by the atomic operations failing itself, but
>> more
On 2011-11-16, at 10:41 , Bert Huijben wrote:
>>
>> -Original Message-
>> From: Philip Martin [mailto:philip.mar...@wandisco.com]
>> Sent: woensdag 16 november 2011 16:37
>> To: Aleksandr Sidorenko
>> Cc:
>> Subject: Re: "Couldn't op
On 2011-11-16, at 10:36 , Philip Martin wrote:
> Aleksandr Sidorenko writes:
>
>> But it seems it's not this error that is triggered; it's the one a few lines
>> down (I changed the error message to detect it):
>>
>> #if APR_HAS_THREADS
>&g
On 2011-11-16, at 10:21 , Philip Martin wrote:
> Aleksandr Sidorenko writes:
>
>> Rebuilt, now I get this message on post-commit:
>>
>> Warning: post commit FS processing had error:
>> Couldn't perform atomic initialization
>
> It could be the atomi
On 2011-11-16, at 10:04 , Philip Martin wrote:
> Aleksandr Sidorenko writes:
>
>> I tried changed the permissions on the repository to be more permissive, and
>> changing the user/group of the Apache server: no help.
>>
>> I also tried recompiling from source
SVN server to 1.7.1:
Warning: post commit FS processing had error:
Couldn't open rep-cache database
On 2011-11-14, at 21:35 , Aleksandr Sidorenko wrote:
>>> Since posting the question, I tried using "svnserve" instead of
>>> Apache (the mod_dav_svn module)
>> Since posting the question, I tried using "svnserve" instead of
>> Apache (the mod_dav_svn module), and the error does NOT occur in
>> this case (we would still prefer to stick with mod_dav_svn).
>
> How did you manage permissions using svnserver? You mentioned a group
> which you gave read/wri
On 2011-11-14, at 11:38 , Daniel Shahaf wrote:
> Aleksandr Sidorenko wrote on Mon, Nov 14, 2011 at 11:06:49 -0500:
>> Hi everyone,
>>
>> I've searched the mailing list archive for this error, but results were
>> pretty limited. I also haven't found a fix e
right after we updated the server from 1.6.12 to
1.7.1.
Any help would be greatly appreciated!
Aleksandr Sidorenko
Administrateur systèmes/réseaux • System/Network Administrator
Espeo Inc.
2000, ave McGill College, bureau 230
Montréal, Québec (H3A 3H3)
www.espeo.com
asidore...@espeo.com
514-905-1268 #234
15 matches
Mail list logo
