From root@generations.stdio.com  Thu Jul  4 17:24:44 1996
Received: from generations.stdio.com (generations.stdio.com [204.152.114.70])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA22796
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 4 Jul 1996 17:24:43 -0700 (PDT)
Received: (from root@localhost) by generations.stdio.com (8.7.5/8.7.3) id IAA00701; Fri, 5 Jul 1996 08:24:04 GMT
Message-Id: <199607050824.IAA00701@generations.stdio.com>
Date: Fri, 5 Jul 1996 08:24:04 GMT
From: root@generations.stdio.com
Reply-To: risner@stdio.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: sysinstall bug 0627 SNAP changing release names not passed
X-Send-Pr-Version: 3.2

>Number:         1368
>Category:       misc
>Synopsis:       change a release name in "options" does not work
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul  4 17:30:03 PDT 1996
>Closed-Date:    Thu Jul 4 18:05:10 PDT 1996
>Last-Modified:  Thu Jul  4 18:06:45 PDT 1996
>Originator:     Charlie &
>Release:        FreeBSD 2.1-STABLE 062796 SNAP i386
>Organization:
Open World
>Environment:

	none

>Description:

	I often install BIN and MAN dist on a local server and use
	ftp.freebsd.org for anything else I need like packages and such.
	Thus I am changing the release a lot in the middle of running.
	It does not seem to accept the change.

	For this to work you need to enter sysinstall and select the
	correct release name BEFORE trying to switch.

>How-To-Repeat:

	select a media in "Media"
	select a release name in "Options"
	Select packages, get an INDEX ok.
	Switch release name in "Options" to another release.
	Delete the INDEX from the new release.
	Select packages, get an INDEX and you still get the OLD index
	from the old release before you changed.

>Fix:

	I am not sure.
	I think it boils down to once it gathered data it remembers it.
	And if the release changed it will not attempt to go out and see
	if things haved changed.  I did a ktrace of the events and noticed
	that it DID NOT try to cd and open packages the second time.
	It apparently remembered it and used the in memory cache of
	packages/INDEX.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Thu Jul 4 18:05:10 PDT 1996 
State-Changed-Why:  
This is a feature - the package cache is supposed to stick around 
since it takes a long time to build (and it's not designed to have 
its contents free'd, either :-).  For the latter reason, I'm probably 
not even going to try to add a cache-invalidation on release change 
feature - that will have to wait for the Son of Sysinstall. :-) 
>Unformatted:
