How do you mean? Fail in what way - destroy in what way?

I thought that this should be read only for everything in /path/to/original/maus (unless you are building in /path/to/original/maus, in which case I don't know what will happen)

When the install failed on the alternate tracker branch
I tried to run simulate_mice.py on the trunk installation and got the following

failed to import Go
failed to import InputPyJSON
failed to import InputPyEmptyDocument
failed to import InputPySpillGenerator
failed to import InputCppDAQData
failed to import MapPyRemoveTracks
failed to import MapCppSimulation
failed to import MapPyValidateSpill
failed to import MapCppTOFSlabHits
failed to import MapCppTrackerRecon
failed to import MapCppTOFDigits
failed to import MapCppTOFSpacePoints
failed to import MapPyGroup
failed to import MapCppPrint
failed to import MapPyScalersDump
failed to import MapPyTOFPlot
failed to import MapPyBeamMaker
failed to import MapPyPrint
failed to import MapPyDoNothing
failed to import MapCppTrackerDigitization
failed to import MapCppTrackerMCDigitization
failed to import MapPyFakeTestSimulation
failed to import ReducePyHistogramTDCADCCounts
failed to import ReducePyROOTHistogram
failed to import ReducePyDoNothing
failed to import ReducePyMatplotlibHistogram
failed to import ReducePyTOFPlot
failed to import OutputPyDoNothing
failed to import OutputPyImage
failed to import OutputPyJSON
Traceback (most recent call last):
File "./simulate_mice.py", line 43, in <module>
run()
File "./simulate_mice.py", line 24, in run
my_input = MAUS.InputPySpillGenerator()
AttributeError: 'module' object has no attribute 'InputPySpillGenerator'

some of these correspond to a message from the install script that they
had been removed - and is identical (or almost) to the error message from
the install script

the command I used was
./install_test_build.bash /home/Paul/research/maus-v0.1.1

running from /home/Paul/research/tracker/tracker_devel