Date: Mon, 07 Nov 2011 09:31:09 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: painful binary upgrade from 8.1 to 8.2 Message-ID: <4EB7A55D.3000402@infracaninophile.co.uk> In-Reply-To: <867h3ddped.fsf@red.stonehenge.com> References: <867h3ddped.fsf@red.stonehenge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC3F91B0AEEAC013BBB9C7F73 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 06/11/2011 19:25, Randal L. Schwartz wrote: > When following the instructions at=20 >=20 > http://www.freebsd.org/releases/8.2R/announce.html >=20 > to go from 8.1 to 8.2, I'm presented during the command: >=20 > freebsd-update upgrade -r 8.2-RELEASE >=20 > with no less than *** 322 *** files that differ only by the CVS tag. >=20 The tag presumably being $FreeBSD$? Is it specifically a CVS tag? As opposed to a SVN tag?[*] If the former, then ever since the primary src repo switched to SVN, all of the files under /etc will get a version number bump as a consequence of generating a new release even if the contents didn't change. Before SVN that didn't happen. If the files are taken directly from SVN, then I think the revision number in any file should remain the same in all release branches unless the file contents are changed. Perhaps generating freebsd-update changesets directly out of SVN rather than via CVS would go a long way to avoiding this problem. Cheers, Matthew [*] The pertinent difference being that CVS has version numbers with one or more decimal points in them, whilst SVN uses an integer value. --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enigC3F91B0AEEAC013BBB9C7F73 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk63pWgACgkQ8Mjk52CukIw39QCfSIegOs91jSYgqGl78qD6qosD PioAn3QPxCR18s4RBWzljMkIPDvq0yzW =oY6S -----END PGP SIGNATURE----- --------------enigC3F91B0AEEAC013BBB9C7F73--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EB7A55D.3000402>