Date: Sun, 4 Aug 2013 17:44:33 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Peter Wemm <peter@wemm.org> Cc: freebsd-current@freebsd.org Subject: Re: svn error during 'make buildkernel'? Message-ID: <20130805004433.GA6355@troutmask.apl.washington.edu> In-Reply-To: <CAGE5yCrJ%2B9tr-Fqw9h_Ox%2Bq1b2g7pdyJ5GEPCoQ8rX-y=o9rQQ@mail.gmail.com> 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> <CAGE5yCrJ%2B9tr-Fqw9h_Ox%2Bq1b2g7pdyJ5GEPCoQ8rX-y=o9rQQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 04, 2013 at 04:51:08PM -0700, Peter Wemm wrote: > 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 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I did not want to upgrade. It was suggested/forced on me by revisio 252505 of newvers.sh that looks for svnliteversion instead of the installed svnversion. 1.7.9 was working fine. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130805004433.GA6355>