I talked to David about this behavior, and the problem comes down to a clash between the patch checker, which is aware of remote sources, and the local build system that works with locally downloaded modules. The references to -2.2.^ modules, when you do the change suite, resolves to your local modules 2.2.0. The patch checker only kicks in on next run and immediately finds the -2.2.1 versions of the modules.
We're going to look into this behavior, file a bug, and see if we can't streamline it a bit. In the meantime, after the module manager reboots and the patch checker installs the new modules, you should indeed be in a good state. - Sean On Mon, Sep 5, 2011 at 6:16 AM, Tomasz Żok <[email protected]> wrote: > Hi, > > I just wanted to bump this thread, because the version resolution problem > is > still there as I checked now (with the HEAD revision updated a moment ago). > Can > you confirm that the 2.2.^ version is incorrectly resolved to 2.2.0 instead > of > 2.2.1? Or maybe it is a desired and correct behaviour? > > Best regards, > Tomek > > > On 08/29/11 at 09:25am, Tomasz Żok wrote: > > I have made the required changes and the suites listing is now fine. I > can see > > only serpens-2.2, and if I check "Show suites patches" there are also > > serpens-2.2.0 and serpens-2.2.1 so everything is fine with the listing. > > > > However I noticed that the module installation mechanism is not fully > correct > > if I understand it right. > > > > The content of > .../releases/released/serpens-2.2.1/module-info/modules.txt is: > > vine-toolkit-2.2.^ > > unicore-2.2.^ > > glite-2.2.^ > > *kepler-2.2.^ > > > > But if I choose serpens-2.2 or serpens-2.2.1 suite, it installs the three > > modules in 2.2.0 versions (2.2.1 are available). During the next run, it > > informs me correctly that there are patches available, but I think it > should > > install them already in the first place. > > -- > Tomasz Zok > Poznan Supercomputing and Networking Center > ul. Noskowskiego 10, 61-704 Poznan, POLAND > http://www.man.poznan.pl >
_______________________________________________ Kepler-dev mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
