1 |
Paul de Vrieze wrote: |
2 |
> Quite likely you changed db versions along the run. While this |
3 |
> theoretically should work. The best course of action is to dump the |
4 |
> repository. Make sure you have a consistent use of db, and load the |
5 |
> repository. Alternatively you could try to use fs_fs |
6 |
|
7 |
Eventually I was able to get a dump by compiling 1.1.4 myself using |
8 |
all the dependencies included in the source with the exception of |
9 |
db-4.1.25_p1-r4. |
10 |
|
11 |
> In principle the 1.0 apr's and later should work for subversion. The main |
12 |
> versions are still the 0.9.x versions though. These are the ones I use. |
13 |
> These database errors are normally not related to the apache version. |
14 |
> (apr/apr-util can be related though). |
15 |
|
16 |
I was able to get the 1.1.4 ebuild to work but only with |
17 |
apache-2.0.52-r3, apr-0.9.5-r3, and apr-util-0.9.5. All my attempts |
18 |
to merge 1.1.4 or 1.1.3 and apache-2.0.53/54 (which use apr 0.9.6) |
19 |
resulted in the same failing svn binaries. |
20 |
|
21 |
With the working apache-2.0.52 and subversion-1.1.4 combination I |
22 |
dropped the repository, recreated as fsfs, and successfully loaded the |
23 |
dump I made with my own compile of 1.1.4. It's been running fine since. |
24 |
|
25 |
> Also for very safe subversion, try to first unmerge it and only after that |
26 |
> compile. |
27 |
|
28 |
That I did. |
29 |
|
30 |
Regards, |
31 |
|
32 |
Ian |
33 |
-- |
34 |
gentoo-dev@g.o mailing list |