Hi,
On 08/04/13 19:23, Steve Kargl 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?
You need to enable the SERF option for the port and rebuild, it is now
required to be able to access http/https-type repositories.
Hope this helps
Johannes
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"