https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362012-07-27T17:10:20ZEcoinformatics RedmineKepler - Bug #5398: Re-install of Kepler-x.y doesn't overwrite modules.txthttps://projects.ecoinformatics.org/ecoinfo/issues/5398?journal_id=186192012-07-27T17:10:20Zjianwu jianwujianwu@sdsc.edu
<ul></ul><p>After discussing with Derik, the information about the bug is clearer.</p>
<p>I can reproduce the first scenario for kepler-2.2. The reason is because Kepler-2.2 reinstall will not overwrite ~/KeplerData/kepler.modules/build-area/modules.txt. So if the modules.txt is changed by other kepler versions or suites, Kepler 2.2 won't start.</p>
<p>The phenomenon is different for Kepler 2.3. After uninstallation and re-installation, Kepler 2.3 can start correctly (even ~/KeplerData/kepler.modules/build-area/modules.txt might be set by other versions). But if a user install kepler-2.3.0, download and switch to reporting-2.3.0, uninstall and reinstall kepler-2.3, and it start into reporting-2.3. This means it didn't overwrite modules.txt</p>
<p>Before we do any changes, I think we can agree on what the correct behavior it should be. In my opinion, re-installation should replace both existing version and existing suite, no matter this re-installation is newer or older than other Kepler versions on the machine.</p> Kepler - Bug #5398: Re-install of Kepler-x.y doesn't overwrite modules.txthttps://projects.ecoinformatics.org/ecoinfo/issues/5398?journal_id=186202012-07-30T21:17:55Zjianwu jianwujianwu@sdsc.edu
<ul></ul><p>After discussion with Dan, we think it is correct to keep its suite configuration even a Kepler version is uninstalled and re-installed. Many software uninstallation and re-installation keep user settings.</p>
<p>It means the following behavior is correct: if a user install kepler-2.3.0, download and switch to reporting-2.3.0, uninstall and reinstall kepler-2.3, and it start into reporting-2.3.</p>
<p>~/KeplerData/kepler.modules/build-area/install-id.txt records the Kepler version number. Since kepler 2.3, if the install-id.txt in ~/KeplerData/ and the install-id.txt in installation path do not match (no matter which is newer), Kepler will first copy modules.txt and install-id.txt from installation path to ~/KeplerData/kepler.modules/build-area/ and overwrite the old texts in the directory. It means Kepler can always start correctly after Kepler 2.3.</p>
<p>So this bug is only in Kepler 2.2, not in later Kepler versions.</p>
<p>We can discuss it during the next 2.4 release call. My current opinion is that we need to do nothing about this bug for 2.4 release.</p> Kepler - Bug #5398: Re-install of Kepler-x.y doesn't overwrite modules.txthttps://projects.ecoinformatics.org/ecoinfo/issues/5398?journal_id=186212012-08-06T19:24:11ZIlkay Altintasaltintas@sdsc.edu
<ul></ul><p>This was a 2.2 bug. It has been solved for 2.3. The behavior right now seems to be ok for 2.4, but the user needs to go through the process manually. This creates a usability problem for the user.</p>
<p>Add a new bug on the usability perspective of module upgrade management. Some of the process can be automated.</p> Kepler - Bug #5398: Re-install of Kepler-x.y doesn't overwrite modules.txthttps://projects.ecoinformatics.org/ecoinfo/issues/5398?journal_id=186222012-08-24T17:19:23Zjianwu jianwujianwu@sdsc.edu
<ul></ul><p>As discussed, new bug is create at bug 5695. close this one.</p> Kepler - Bug #5398: Re-install of Kepler-x.y doesn't overwrite modules.txthttps://projects.ecoinformatics.org/ecoinfo/issues/5398?journal_id=186232013-03-27T21:30:17ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 5398</p>