On Oct 24, 6:36 am, "Stephen Moretti" <[EMAIL PROTECTED]> wrote: > 2008/10/24 garu <[EMAIL PROTECTED]> > > > > > > > Since i broke my head to understand what was going on, i wish to share > > this info in the hope that it may help someone to avoid the loss of > > time i had. > > > If you install any version of svn and related python bindings after > > version 1.5.0 with apache 2.0 on Windows (up to the latest released > > 2.0.63) you won't be able to access any longer svn repositories from > > trac and you'll get the infamous "Unsupported version control system > > "svn": DLL load failed with error code 182" message. > > > The problem is that apache 2.0 is shipping an old version of > > ssleay32.dll and libeay32.dll that are no longer compatible with > > latest svn dlls (the same released with python bindings). > > No matter how do you fiddle with PATH env or PythonPath declaration, > > Apache2 /bin dll's will always be loaded first, so the only options > > you have is to remove them from the Apache2 /bin so that those in > > Subversion/bin are loaded instead (Subversion/bin must be on the path) > > or substituting those in Apache2 /bin with those copied from > > Subversion/bin. > > > I don't know exactly when this happened, i migrated from svn 1.4.6 to > > 1.5.3, then i tested also 1.5.1 that i downloaded some time ago with > > same results, so i can assure that the problem exist at least after > > 1.5.0 and with Apache 2.0.61 and 2.0.63, but it could exist also in > > any intermediate version after 1.4.6. > > What about upgrading Apache to 2.2? Does this have the correct dlls in it? > > BTW - Thanks for the info - I was about to embark on this route myself. > > Regards > > Stephen
the subversion 1.5X release states that the apache 2.2.9+ is required for the bindings if using apache 2.2 if sticking with 2.0 then 2.0.63 or higher is required within the 2.0.x series - I would check this first. also: "Windows binaries - ATTENTION!: The mod_dav_svn binaries available here are NOT compatible with Apache 2.2 -- see the Windows Apache 2.2.x folder." if you are using that. That said, when I "uninstalled" the python subversion 1.4 bindings when I did upgrade, I ended up having a copy of the dll's you mentioned laying around. I ended up finding this out by using the python commandline and importing svn, which worked fined. I then started from svn import core commands, eventually getting an error pop-up dialog on what dll was not working. I then searched my system for all instances of that dll, removing those dll's, I then took the zip version of the bindings and copied those dll's into the site-lib directory. since it happened that when I did my upgrade, the .exe windows installer had the wrong version of those particular dll's. They sound like the ones you are mentioning. There were 2 others, 4 in total I think. For some reason, when I upgraded, I HAD to go to apache 2.2 for some reason, i forget what it was, maybe it was the dav component, I forget exactly why, but I went to subversion 1.5 and apache 2.2 at the same time, and had your pain with the bindings. I thought I detailed it somewhere in the forum here. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
