Re: [OMPI devel] Minor OMPI SVN configuration change
Why did "we" make this change? It was originally this way, and we changed it to the no-auth way for a reason. Brian - Original Message - From: Jeff Squyres [mailto:jsquy...@cisco.com] Sent: Wednesday, February 16, 2011 09:24 AM To: Open Developers Subject: [OMPI devel] Minor OMPI SVN configuration change We have made a minor change in OMPI's SVN configuration: If you access the SVN repo over https, you *must* authenticate. Previously, you could authenticate or not; SVN would serve up what was appropriate in either case (there's one "private" tree in the SVN repo for not-yet-published academic work). Anonymous, read-only access to SVN is still provided over http. I doubt that this change will affect most people, because most people check out via https only if they plan to commit -- meaning that they have a write-enabled SVN account. Let me know if you have any questions / problems with this change. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ ___ devel mailing list de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] Minor OMPI SVN configuration change
Makes sense to me. On Thu, 2011-02-17 at 08:49 -0700, Barrett, Brian W wrote: > Why did "we" make this change? It was originally this way, and we changed it > to the no-auth way for a reason. > > Brian > > > - Original Message - > From: Jeff Squyres [mailto:jsquy...@cisco.com] > Sent: Wednesday, February 16, 2011 09:24 AM > To: Open Developers > Subject: [OMPI devel] Minor OMPI SVN configuration change > > We have made a minor change in OMPI's SVN configuration: > > If you access the SVN repo over https, you *must* authenticate. > > Previously, you could authenticate or not; SVN would serve up what was > appropriate in either case (there's one "private" tree in the SVN repo for > not-yet-published academic work). > > Anonymous, read-only access to SVN is still provided over http. > > I doubt that this change will affect most people, because most people check > out via https only if they plan to commit -- meaning that they have a > write-enabled SVN account. > > Let me know if you have any questions / problems with this change. > -- Kenneth A. Lloyd Director of Systems Science Watt Systems Technologies Inc. Albuquerque, NM USA kenneth.ll...@wattsys.com
Re: [OMPI devel] Minor OMPI SVN configuration change
On Feb 17, 2011, at 10:49 AM, Barrett, Brian W wrote: > Why did "we" make this change? It was originally this way, and we changed it > to the no-auth way for a reason. Are you obliquely saying that there's a reason to have no-auth https access? DongInn and I changed it because we're still having a problem with svnsync on the OMPI repo: - % svnsync init --username jsquyres file://`pwd`/foomirror https://svn.open-mpi.org/svn/ompi % svnsync sync file://`pwd`/foomirror [...MUCH output and about 12 hours...] Transmitting file data svnsync: REPORT of 'https://svn.open-mpi.org/svn/ompi': Could not read chunk size: Secure connection truncated (https://svn.open-mpi.org) % - I did some googling and (re)discovered a bug report that DongInn and I submitted long ago about svnsync: http://subversion.tigris.org/issues/show_bug.cgi?id=3080 The guidance from the SVN developers was to have one method for open+closed (i.e., anon RO access, except for the closed trees) and have a 2nd method for auth-only. I checked with DongInn and we had never followed up on their guidance. I figured we might as well do that as a first step and see if that solved the svnsync problem. Unfortunately, it didn't. DongInn is still investigating. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
