On Wed, Feb 22, 2012 at 21:34, Andrea D'Amore wrote:
It seems I sent an empty message to the list by accident.
Anyway the issue is solved as of r90123, cfr. #19247 [1].
--
Andrea
[1] https://trac.macports.org/ticket/19247#comment:18
___
macports-de
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
>>
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
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.
On Feb 21, 2012, at 00:48, Joshua Root wrote:
> 'port sync' now fails for me with
> https://svn.macports.org/repository/macports/trunk/dports in
> sources.conf. Error is "Server certificate verification failed: issuer
> is not trusted".
>
> It seems that the subversion port doesn't know about th
'port sync' now fails for me with
https://svn.macports.org/repository/macports/trunk/dports in
sources.conf. Error is "Server certificate verification failed: issuer
is not trusted".
It seems that the subversion port doesn't know about the Apple-supplied
root certs, and it's really inconvenient to
