[MacPorts] #39894: subversion @1.8.1+mod_dav_svn+tools: mod_dav_svn.so is missing (was: subversion - mod_dav_svn.so is missing)

MacPorts noreply at macports.org
Mon Jul 29 12:05:48 PDT 2013


#39894: subversion @1.8.1+mod_dav_svn+tools: mod_dav_svn.so is missing
-----------------------------+---------------------
  Reporter:  thomas.demel@…  |      Owner:  dluke@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  subversion      |
-----------------------------+---------------------
Changes (by larryv@…):

 * cc: blair@… (added)
 * owner:  macports-tickets@… => dluke@…
 * version:  2.2.0 =>
 * keywords:  subversion, svn, dav, mod_dav_svn =>


Old description:

> 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.

New description:

 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.

--

Comment:

 Thanks for the ticket. In the future, please Cc relevant port maintainers.

-- 
Ticket URL: <https://trac.macports.org/ticket/39894#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list