Date: Fri, 28 May 1999 19:19:08 -0700 (PDT) From: delaroca@ucla.edu To: freebsd-gnats-submit@freebsd.org Subject: i386/11920: FBSD 3.2 upgrade claims not to upgrade /usr/src Message-ID: <19990529021908.2CE6515AC3@hub.freebsd.org>
index | next in thread | raw e-mail
>Number: 11920 >Category: i386 >Synopsis: FBSD 3.2 upgrade claims not to upgrade /usr/src >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 28 19:20:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Denis DeLaRoca >Release: 3.1 and 3.2 >Organization: >Environment: FreeBSD acacia.cts.ucla.edu 3.1-RELEASE FreeBSD 3.1-RELEASE #10: Tue Apr 27 17:31:04 PDT 1999 root@acacia.cts.ucla.edu:/usr/src/sys/compile/ROSEBUD i386 >Description: The upgrade option in the FBSD 3.2 floppies warns that /usr/src won't be upgraded -- suggesting instead to use CVSup or CTM. This is unlike previous releases where the upgrade option always upgraded /usr/src as well... The warning suggests that the upgrade would be done for the binary components and that /usr/src would be left undisturbed... but carrying the upgrade *does* upgrade /usr/src. This need fixing and I hope you keep the ability to upgrade /usr/src when doing a release upgrade. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the messagehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990529021908.2CE6515AC3>