From owner-freebsd-ports@freebsd.org Fri Aug 7 03:51:55 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7FC49B322F for ; Fri, 7 Aug 2015 03:51:55 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 856ACD42 for ; Fri, 7 Aug 2015 03:51:55 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oio137 with SMTP id 137so47152221oio.0 for ; Thu, 06 Aug 2015 20:51:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=s0MvwxBhg3BWk2Mtw9VwSRQS8Gh3M7AHHNvXBAJGb78=; b=rjCAjSR/Lq+/tJdibVxR+M4pPihmu8au14W7E9yeOQmyC0CppEvHFRT47XtOB6Uh53 aKWdcvJXJnucSAmnft/lMSMmuhmm7uLcxogaBIu4cKArjacuXotL7qV5pqoaNKRJZxtD Uq1wl2x1gM8LFdgvyQ6fh9HvO5p5crYrpiMjV4hbGDDUqYg/cZD6KyLLAyyNQ5KH5JD7 Cmb1P8ggLri+Ug3bzJWr/nUPQ6WrkykFqDtDP3e7NH7mY+IeC/8KliLPxxtRZ00ybib1 Vkj1GQXdbKUbfRQdPzNVo2NfobMq6GT6jkUF70YthgtqnTbr8UzNc/jTJfaFyR0JE4sd qRBw== MIME-Version: 1.0 X-Received: by 10.202.188.2 with SMTP id m2mr4572334oif.59.1438919514523; Thu, 06 Aug 2015 20:51:54 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Thu, 6 Aug 2015 20:51:54 -0700 (PDT) In-Reply-To: <55C3CA26.60806@gmx.de> References: <20150805221752.GF1056@albert.catwhisker.org> <55C2CEA8.8050200@FreeBSD.org> <55C3CA26.60806@gmx.de> Date: Thu, 6 Aug 2015 20:51:54 -0700 X-Google-Sender-Auth: edfQ6t3nzj8cvB9j1CFwvdWu1_o Message-ID: Subject: Re: Unable to relocate to new svn URL From: Kevin Oberman To: olli hauer Cc: FreeBSD Ports ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2015 03:51:55 -0000 On Thu, Aug 6, 2015 at 1:57 PM, olli hauer wrote: > On 2015-08-06 05:44, Kevin Oberman wrote: > > > ... > > > > This still leaves the issue of requiring SASL support in subversion. A > note > > in the handbook section on ports would help, though I'll admit that I > > probably would not have found it in this case. Perhaps a note in > > ports/UPDATING might be in order. At least that one was fairly easy to > find > > once I started looking. > > Hi Kevin, > > SASL support is not required to checkout/update src/ports/docs > > To see a list of client features fire the command > > $ svn --version > svn, version 1.8.14 (r1692801) > ... > The following repository access (RA) modules are available: > > * ra_svn : Module for accessing a repository using the svn network > protocol. > - handles 'svn' scheme > * ra_local : Module for accessing a repository on local disk. > - handles 'file' scheme > * ra_serf : Module for accessing a repository via WebDAV protocol using > serf. > - using serf 1.3.8 > - handles 'http' scheme > - handles 'https' scheme > > > or on FreeBSD >= 10.x > > $ svnlite --version > svn, version 1.8.10 (r1615264) > ... > The following repository access (RA) modules are available: > > * ra_svn : Module for accessing a repository using the svn network > protocol. > - handles 'svn' scheme > * ra_local : Module for accessing a repository on local disk. > - handles 'file' scheme > * ra_serf : Module for accessing a repository via WebDAV protocol using > serf. > - using serf 1.3.7 > - handles 'http' scheme > - handles 'https' scheme > > > -- > olli > I have been running subversion for years without SASL using svn scheme with no issues, but when I issued the command "svn relocate svn://svn0.us-west https://svn", I got an error that the format of the new location was unsupported. I changed the config for subversion to add SASL support and reinstalled it. Then it worked except for failing to authenticate the cert. (I don't have the exact message any longer.) Since the only thing that changed between the failure and success was the change of adding SASL support, it sure looked like it was needed. Now that I have certs installed into /etc/ssl, the version without SASL is working. I wonder if the lack of certs caused serf to throw the error, but adding SASL allowed https to be accepted and got it to almost work. In any case, I just moved my /usr/src to https://svn with no SASL module installed but the certs in place and it worked fine. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683