Re: svn error during 'make buildkernel'?
--QTprm0S8XgL7H0Dt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Aug 06, 2013 at 01:11:07PM -0500, Matthew D. Fuller wrote:
> On Sun, Aug 04, 2013 at 08:55:30PM -0400 I heard the voice of
> Glen Barber, and lo! it spake thus:
> >=20
> > The error generated is non-fatal, and once I receive response on a
> > proposed patch, will be suppressed if the svn version used to check
> > out the tree is not compatible with that used to check the version
> > of the tree with the kernel build.
>=20
> But not try the ports svn as well? I mean, as breakage goes, it's not
> even in the top 100; I'd _much_ rather have a kernel that I have to
> guess the revision of but boots, than one properly recorded that
> doesn't. But it's still unpleasant, and is one of those things you
> probably won't notice missing until suddenly you need it.
>=20
> And this isn't just a presentism. Sure, right _now_ devel/subversion
> and base svnlite get along, but what happens when ports moves to 1.9
> which changes the WT format? Even if -CURRENT src gets upgraded
> simultaneously[0], the same surely can't be said of every back branch.
>=20
> I realize this is all still a WIP, and please don't read any anger
> into my words. But this _has_ been something I've found a little
> worrisome since the original import/newvers change. Heck, newvers can
> show me version info if I'm getting my source tree from git or p4, but
> can't handle ports svn? By the time this works its way into a stable
> branch, I really think it should either handle svnversion from ports
> as well, or come with a big bright flashing warning that using svn
> from anything but base svnlite for /usr/src is a degraded experience.
>=20
>=20
> [0] Which still wouldn't really fix things, since
> /usr/bin/svnliteversion is arbitrarily old, not up to date with
> the source tree.
>=20
I have this on my todo list, but right now I have bigger things to deal
with. As soon as I can, I will fix the logic. Right now, it is not "as
easy as checking which svn works", because the more I look at the logic
for newvers.sh, the more I dislike how it all works.
Glen
--QTprm0S8XgL7H0Dt
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (FreeBSD)
iQEcBAEBCAAGBQJSAUDeAAoJEFJPDDeguUaj2xIH/11KAffErE4gjYwBxuPe43h+
CNCtuQjxMm6iqowJNap6MnShYHKiTmllqHdIgo+qk9MIKJjw6EDq3ox+7kAaht69
eMEaYGkVQkKBK7i0+gyR/xApLHWx2WSlpUt4xhWKL67ScISOToYv2MWMO7IahRV7
GtzHfiP+DxEfYZ7xYp4h68T/M2TNnOQdDclP6n82ii3tJbPKX6jYJzxP52fWPFpK
Zu/9kRbKdAzfuOkk2z068Vrp8KCSvE25+/d/BjziTPNIs9MTZW1HVSBtjuUn1moq
JgBfeEVJrO1Dhs7+FgBtDh0AZmcUtzL0HV2wfyCBWdwm1NABXJ8jMHIOn6uS6tc=
=suAp
-----END PGP SIGNATURE-----
--QTprm0S8XgL7H0Dt--
討論串 (同標題文章)
完整討論串 (本文為第 35 之 39 篇)：