[kepler-dev] [Bug 5494] existence of remote 2.2 patches can cause 2.3 to fail to start 2.2 on first attempt

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5494

--- Comment #3 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2011-09-22 18:45:35 PDT ---
Forgot to paste info about fix from r28635 commit msg:

update present.txt and present list variable when downloading modules. Not
knowing modules were present was causing problems. transformName would fall
through to tranformArrowNameForGet, which utilizes the release list, which is
not what you want when a module is present. This caused kepler 2.3.0 to fail to
start on initial try after using it to move back to 2.2.0.
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5494

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.