Date: Sun, 4 Aug 2013 16:51:08 -0700 From: Peter Wemm <peter@wemm.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: svn error during 'make buildkernel'? Message-ID: <CAGE5yCrJ%2B9tr-Fqw9h_Ox%2Bq1b2g7pdyJ5GEPCoQ8rX-y=o9rQQ@mail.gmail.com> In-Reply-To: <20130804232358.GA6068@troutmask.apl.washington.edu> References: <20130803210348.GA715@troutmask.apl.washington.edu> <20130803210858.GJ78299@glenbarber.us> <20130803213023.GA812@troutmask.apl.washington.edu> <20130803214313.GL78299@glenbarber.us> <20130804232358.GA6068@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 4, 2013 at 4:23 PM, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > On Sat, Aug 03, 2013 at 05:43:13PM -0400, Glen Barber wrote: >> On Sat, Aug 03, 2013 at 02:30:23PM -0700, Steve Kargl wrote: >> > >> > Thanks. >> > >> > Looks like an entry in /usr/src/UPDATING is missing if >> > /usr/bin/svn* is forcing an obsolscence of a functioning >> > installed port. >> > >> >> The port was at 1.8.x before I added the additional lookup of >> svnlite to the script. There really is no need for UPDATING entry, >> since 1.7.9 is deprecated, and the behavior you have seen is not a fatal >> error with the buildkernel process. >> >> BTW, you should upgrade devel/subversion anyway, since there are >> security vulnerabilities. >> > > Here's a perfect example why chasing the bleeding edge ports > is a stupid idea. After upgrading devel/subversion as you > suggested, I see > > cd /usr/ports > % svn upgrade > % svn update > Updating '.': > svn: E170000: Unrecognized URL scheme for 'http://svn.freebsd.org/ports/head' > % svn --version | grep version > svn, version 1.8.1 (r1503906) > % which svn > /usr/local/bin/svn > %which svnlite > /usr/bin/svnlite > % svnlite --version | grep version > svn, version 1.8.1 (r1503906) > Subversion is open source software, see http://subversion.apache.org/ > % svnlite > % svnlite update > Updating '.': > U www/squid33/distinfo > U www/squid33/files/squid.in > U www/squid33/Makefile > U cad/gmsh/Makefile > U cad/gmsh/distinfo > U cad/gmsh/pkg-plist > U lang/gcc47/Makefile > U lang/gcc47/distinfo > U lang/gdc/Makefile > U x11-clocks/xdaliclock/Makefile > U x11-clocks/xdaliclock/distinfo > U net-mgmt/virt-viewer/Makefile > U net-mgmt/virt-viewer/distinfo > U net-mgmt/virt-viewer/pkg-plist > U x11/xfwp/Makefile > U x11/xfwp/distinfo > Updated to revision 324253. > > So, how do I fix svn, now? ports/UPDATING: 20130619: AFFECTS: users of devel/subversion AUTHOR: ohauer@FreeBSD.org devel/subversion has been upgraded from 1.7.10 to 1.8.0 If you want to upgrade, and use http/https access to repositories, please check, that SERF option is enabled, as NEON support ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ is gone. Also, mod_dontdothat and svnauthz_validate are now eanbled with one option TOOLS, among other new tools and SVNMUCC is enabled always. subversion-1.7.x is available as devel/subversion17 -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV UTF-8: So you can \342\200\231 .. for when a ' just won't do <brueffer> ZFS must be the bacon of file systems. "everything's better with ZFS"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGE5yCrJ%2B9tr-Fqw9h_Ox%2Bq1b2g7pdyJ5GEPCoQ8rX-y=o9rQQ>