Hi,
svn 1.8.8 (r1568071)
I've found an interesting scenario where merged revisions are not appearing
in the output of an 'svn log -g' command.
The revision is included in the svn:mergeinfo changes for the merged
revision, but does not appear in the log output. The file changes are in
that commit
On 06/07/14 21:58, Branko Čibej wrote:
> On 06.07.2014 13:35, Andreas Stieger wrote:
>> Your repository is of type bdb, (berkeley db backend), not fsfs. As such
>> is it not suitable for a direct upgrade.
>
> That's nonsense.
See DB_VERSION_MISMATCH and others. Building the bdb backend might just
On 06.07.2014 13:35, Andreas Stieger wrote:
> Hi,
>
> On 06/07/14 12:11, Mohsin Abbas wrote:
>> [upgraded server from 1.4.2 to 1.8.9]
>> [Fri Jul 04 15:07:43 2014] [error] [client 192.168.x.x] (20014)Internal
>> error: Failed to load module for FS type 'bdb'
I replied to this same question yesterd
Hi,
> On 6 Jul 2014, at 13:24, David Gerler wrote:
>
> [...]existing SVN 1.3.1 repository[...]
>
> Does anyone have a suggestion on how to migrate svn 1.3.1 to
> 1.8.9 without console access?
Builtin tools will show the behaviour you described. This one is older and
might co
Good Morning,
I'm trying to figure out how to migrate our existing SVN 1.3.1
repository to another server. It's on a Jumpbox with TRAC. We paid for it, but
have lost the license key and I'm not getting a response from Jumpbox so far.
I followed the instructions and
Hi,
On 06/07/14 12:11, Mohsin Abbas wrote:
> [upgraded server from 1.4.2 to 1.8.9]
> [Fri Jul 04 15:07:43 2014] [error] [client 192.168.x.x] (20014)Internal
> error: Failed to load module for FS type 'bdb'
Your repository is of type bdb, (berkeley db backend), not fsfs. As such
is it not suitable
Hello All,
Hope you are doing well . I have recently upgraded my SVN from V1.4.2 to
V1.8.9 on Linux environment all repositories which were created in SVN
V1.4.2 are working fine with V1.8.9 except one which gives error while
accessing via Tortoise SVN client or Browser . I have shared Apache erro
