#39894 closed defect (invalid)
subversion @1.8.1+mod_dav_svn+tools: mod_dav_svn.so is missing
Reported by: | thomas.demel@… | Owned by: | danielluke (Daniel J. Luke) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | blair (Blair Zajac) | |
Port: | subversion |
Description (last modified by larryv (Lawrence Velázquez))
After upgrading subversion mod_dav_svn.so is missing Trying to fix it with
sudo port clean subversion; sudo port -f uninstall subversion; sudo port install subversion +mod_dav_svn +tools
didn't change.
There is no mod_dav_svn.so in modules, so apache crashes. removing the configuration for the repositories and removing the "LoadModule dav_svn_module modules/mod_dav_svn.so" helps but now the dav access to the repositories doesn't work! with subversion 1.7.x all was fine, the configuration of the repositories did work, but now ... What can I do? Is this a general bug or did I something wrong and how can I fix it.
Attachments (1)
Change History (10)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
Cc: | blair@… added |
---|---|
Description: | modified (diff) |
Keywords: | subversion svn dav mod_dav_svn removed |
Owner: | changed from macports-tickets@… to dluke@… |
Summary: | subversion - mod_dav_svn.so is missing → subversion @1.8.1+mod_dav_svn+tools: mod_dav_svn.so is missing |
Version: | 2.2.0 |
comment:2 Changed 11 years ago by danielluke (Daniel J. Luke)
Owner: | changed from dluke@… to dluke@… |
---|---|
Status: | new → assigned |
You haven't provided a full log, so it's impossible to determine what went wrong for you.
It's possible that there's a bug with the port (maybe some interaction with +mod_dav_svn and +tools?). I know +mod_dav_svn works, and I know +tools works, but I don't think I tested them together.
You can always install an older version of the port if you need to get things working right away (and you haven't saved your previously installed version as 'inactive'). See InstallingOlderPort.
I always recommend doing upgrades on a staging/test system before your production system(s).
comment:3 follow-up: 4 Changed 11 years ago by danielluke (Daniel J. Luke)
I just did a test build of +mod_dav_svn and +tools at the same time and mod_dav_svn.so gets installed as expected.
please run:
sudo port clean subversion sudo port -dv install subversion +mod_dav_svn +tools
and attach the output to this ticket.
comment:4 Changed 11 years ago by thomas.demel@…
It doesn't make difference if I install with +tools or without. So it doesn't belong to installing them together.
comment:5 Changed 11 years ago by danielluke (Daniel J. Luke)
um, that logfile looks like it's for sudo port clean subversion (and not for the build/install - which is what I need to see to be able to help).
comment:6 Changed 11 years ago by danielluke (Daniel J. Luke)
oh, and that's my bad - you need to uninstall subversion too in order to get it to actually try to build it.
Changed 11 years ago by thomas.demel@…
Attachment: | output_ sudo port -dv install subversion +mod_dav_svn.txt added |
---|
output after uninstall, cleaning subversion and install sudo port -dv install subversion +mod_dav_svn
comment:7 Changed 11 years ago by kobayos
It seems that the cause of this problem is the location of mod_dav_svn. mod_authz_svn.so mod_dav_svn_.so mod_dontdothat.so are installed at "/opt/local/libexec" now. However, these files must be installed under "/opt/local/apache2" to access from httpd since ServerRoot is set to "/opt/local/apache2" in "/opt/local/apache2/conf/httpd.conf" Because the other mods are installed on /opt/local/apache2/modules, I am wondering that this problem can be solved by changing the location of the files to "/opt/local/apache2/modules". Anyway, I could avoid this problem by making symbolic link of these files at "/opt/local/apache2/modules" and adding "LoadModule dav_svn_module modules/mod_dav_svn.so" in httpd.conf.
comment:8 Changed 11 years ago by danielluke (Daniel J. Luke)
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
comment:9 Changed 11 years ago by danielluke (Daniel J. Luke)
FYI - you can use an absolute path in your apache conf to load modules outside of ServerRoot.
Thanks for the ticket. In the future, please Cc relevant port maintainers.