Upgrading 5.3 > 6.0 buildworld failure now in libmagic

[Doug Barton]

On Tue, 6 Dec 2005, secmgr wrote:

> Not to belabour this, but the 6.0 release notes do specificly say 5.3 RELEASE 
> and newer.

5.4-STABLE is newer. :)

> "Source upgrades to FreeBSD 6.0-RELEASE are only supported from FreeBSD 
> 5.3-RELEASE or later. Users of older systems wanting to upgrade 6.0-RELEASE 
> will need to update to FreeBSD 5.3 or newer first, then to FreeBSD 
> 6.0-RELEASE."

How does this change to UPDATING in RELENG_6 look to you:

Index: UPDATING
===================================================================
RCS file: /home/ncvs/src/UPDATING,v
retrieving revision 1.416.2.7
diff -u -r1.416.2.7 UPDATING
--- UPDATING    1 Nov 2005 23:44:40 -0000       1.416.2.7
+++ UPDATING    7 Dec 2005 00:42:04 -0000
@@ -229,7 +229,13 @@
         page for more details.

         Due to several updates to the build infrastructure, source
-       upgrades from versions prior to 5.3 no longer supported.
+       upgrades from versions prior to 5.4-STABLE are not likely
+       to succeed.
+
+       When upgrading from one major version to another, it is
+       generally best to upgrade to the latest code in the branch
+       currently installed first, then do another upgrade to the
+       new branch.


> This is one of my pet peeves with FreeBSD.  You can read the Release Notes, 
> the UPDATING, the ERRATA, the HARDWARE, thinking you've prepped yourself for 
> the upgrade, and still be screwed.

This is an open source project. The only way that things improve is if 
people help make it better. It's also worth pointing out that this issue of 
upgrading to the latest version of the branch you're in has been "common 
knowledge" for, basically, always; so if the folks that wrote the release 
notes neglected to include it, it's understandable. (Although, as you point 
out, potentially frustrating for new(er) users.)

> If RE wants to change the requirements for upgrading, then how bleeping 
> hard would it be to update either release notes or errata.  It's not so 
> much that I now need to do multiple upgrades (ok, that IS pretty 
> annoying), it's that I'd never of known unless I followed this thread.

Ok, so, after you calm down a bit, why don't you write a message to 
re at freebsd.org and mention this issue.

hth,

Doug

-- 

     This .signature sanitized for your protection