Description of Problem:
Traceback occurs when attempting a specific partitioning setup

How Reproducible:
Totally

Steps to Reproduce:
1.  Devote a drive to a working Windows install
2.  Install Roswell on another drive, use another drive for swap
3.  Attempt another Roswell install on the Swap drive - should get a
traceback in DiskDruid upon trying to modify that last drive

Actual Results:
Traceback at the DiskDruid screen

Expected Results:
Successful install

Additional Information:
Here's the traceback:
	Traceback (innermost last):
  File "/usr/bin/anaconda", line 610, in ?
    intf.run(id, dispatch, configFileData)
  File "/tmp/28762-i386/install//usr/lib/anaconda/text.py", line 371, in
run
  File "/tmp/28762-i386/install//usr/lib/anaconda/textw/partition_text.py",
line
 975, in __call__
  File "/tmp/28762-i386/install//usr/lib/anaconda/textw/partition_text.py",
line
 921, in editCb
  File "/tmp/28762-i386/install//usr/lib/anaconda/textw/partition_text.py",
line
 605, in editPartitionRequest
NameError: newfstype