On Feb 21, 2012, at 4:59 AM, Joshua Root wrote: > On 2012-2-21 20:46 , Dan Ports wrote: >> On Tue, Feb 21, 2012 at 05:48:44PM +1100, Joshua Root wrote: >>> It seems that the subversion port doesn't know about the Apple-supplied >>> root certs, and it's really inconvenient to put a config file in >>> /opt/local/var/macports/home. /usr/bin/svn might do better. >> >> /usr/bin/svn is going to be svn 1.6 (or earlier), which has a working >> copy format that's incompatible with the one svn 1.7 (in ports) uses, >> so that doesn't sound like a great option. > > Right, I meant it might know about Apple's root certs. >
svn was probably using your $HOME/.subversion/auth/svn.ssl.server directory before, where you had permanently accepted the macosforge certificate in the past (ssh model). Fixing macports to svn (and openssl) to use a real CA bundle would be good, but pre-populating /opt/local/var/macport/home with the macports server cert would work for most people, and documenting /opt/local/var/macport/home would point users with private repositories in the right direction… Thanks, Eric _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
