Date: Sat, 3 Aug 2013 18:20:47 -0400 From: Glen Barber <gjb@FreeBSD.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: svn error during 'make buildkernel'? Message-ID: <20130803222047.GN78299@glenbarber.us> In-Reply-To: <20130803221702.GA979@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> <20130803221702.GA979@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--uWbmMdDzzl2TXAgx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 03, 2013 at 03:17:02PM -0700, Steve Kargl wrote: > > The port was at 1.8.x before I added the additional lookup of > > svnlite to the script. >=20 > My installed port was at 1.7.9. I can't find anywhere that=20 > states that one must immediately upgrade to a new version > when a port's maintainer updates it. I've banged my head > against the ports collection dependency idiocy too often > to chase after every update. >=20 Fair enough. > > 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. >=20 > Installing a freshly built kernel when an ERROR message appears > within the last 10 lines of 'make buildkernel' seems like a=20 > rather dumb thing do. >=20 But the last 3 lines state that the kernel build completed. > > BTW, you should upgrade devel/subversion anyway, since there are > > security vulnerabilities. >=20 > 1.7.9 works/worked fine for updating my /usr/src and my personal > svn repository. The change to use svnlite in newvers.sh should > have an entry in UPDATING to alert users that have a too old=20 > svn port that they need to upgrade. I go as far to suggest that > that the script should look for svn in the path before it looks > for svnlite. I cannot differentiate what version of svn is used to check out the tree. When in doubt, software in base wins, IMHO. Glen --uWbmMdDzzl2TXAgx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJR/YI/AAoJEFJPDDeguUajUEwIAIoLQRjs9fJf+Ey1sCgkU2DK Yw+By2wP1yR46JffCPl2hGDW2s74gbWUEWWen3dn5xVpnw08rx9h3ofgUY6eHdF3 s3wNtatGx/ayxR0x2qBG4qyiNBGe9dmPZuhzrENRKhKESNuO7bCZsaBA5DYQqpb0 6A38oZFlBNrBJGL7REVXlIIrd/r9bsMOLHwnVL5EjkNc4rybZe8ZK0SKnQZe16Pd /77wEsONmD82ykPDaT+YOOF+k/L2nyNcd1cKVwS7rYN57cl+OWdq2kfrOM4BJh5P AVc0TWAKY/KfevSYW8EIYIw4QpiCR9tGZ7YOYzm7B3LzQLJXVIdaJMmRFeDA1og= =HMN6 -----END PGP SIGNATURE----- --uWbmMdDzzl2TXAgx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130803222047.GN78299>