Closed Bug 301653 Opened 20 years ago Closed 20 years ago

Upgrades from 2.18 with a new localconfig file may lose old Field Value choices

Categories

(Bugzilla :: Installation & Upgrading, defect)

2.20
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 311047

People

(Reporter: mkanat, Unassigned)

Details

Steps to Reproduce ------------------ 1) Take a 2.18 database, install a brand-new tarball of Bugzilla 2.20. 2) Run checksetup, it creates localconfig with no choices for OS/Version/etc. 3) Run checksetup again, it upgrades the database, and fills the Field Value choices with the defaults, instead of whatever was in the 2.18 database. So you can "lose" all of your old choices if you don't have the same localconfig file. This is easy to work-around (just copy over your old localconfig and re-upgrade), but could be a possible issue for some people. (I just ran into it myself, upgrading a test installation where I didn't have the old localconfig available.)
*** This bug has been marked as a duplicate of 311047 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.