Hi,
I have a fresh extent in which I loaded gsDevKit and tODE. If I do 'project list' in tODE one of the projects I get is XMLSupport. If I click on "browse project entry" I shows me this: ^ TDProjectSpecEntryDefinition new configuration: 'XMLSupport' version: #'1.2.2.1' repository: 'http://seaside.gemtalksystems.com/ss/MetacelloRepository' loads: #('Core'); status: #(#'inactive'); locked: true; yourself I think the version specification is incorrect since the fact of using a symbol for the version (#'1.2.2.1') rather than a plain string, confuses Metacello and thinks that such a version is a symbolic version, rather than a normal one. And then you have strange error messages for example. What I had to do is to edit the project entry, so that to set '1.2.2.1' but then I kept having same problems. So then I did a "unregister" and that SEEMS to have worked. Does it make sense? _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On 10/14/2015 08:23 AM, Mariano Martinez Peck via Glass wrote: > Hi, > > I have a fresh extent in which I loaded gsDevKit and tODE. If I do > 'project list' in tODE one of the projects I get is XMLSupport. If I > click on "browse project entry" I shows me this: > > ^ TDProjectSpecEntryDefinition new > configuration: 'XMLSupport' > version: #'1.2.2.1' > repository: > 'http://seaside.gemtalksystems.com/ss/MetacelloRepository' > loads: #('Core'); > status: #(#'inactive'); > locked: true; > yourself > > I think the version specification is incorrect since the fact of using > a symbol for the version (#'1.2.2.1') rather than a plain string, > confuses Metacello and thinks that such a version is a symbolic > version, rather than a normal one. And then you have strange error > messages for example. [1] https://github.com/GsDevKit/gsDevKitHome/commit/181fd8b3d536d355ed96d4aafb167783feab91ef > > What I had to do is to edit the project entry, so that to set > '1.2.2.1' but then I kept having same problems. So then I did a > "unregister" and that SEEMS to have worked. > > Does it make sense? Yeah, right now if you have a lock project entry and changed the disk copy, the locked, in-image registration is used ... this is the same bug that I referred to the other day ... I plan to address this one shortly ... Dale _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On Wed, Oct 14, 2015 at 1:57 PM, Dale Henrichs via Glass <[hidden email]> wrote:
Great, thanks. What I had to do is to edit the project entry, so that to set '1.2.2.1' but then I kept having same problems. So then I did a "unregister" and that SEEMS to have worked.Yeah, right now if you have a lock project entry and changed the disk copy, the locked, in-image registration is used ... this is the same bug that I referred to the other day ... OK, do we have an issue open for this one?
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On 10/14/2015 10:29 AM, Mariano
Martinez Peck wrote:
I don't think so ... Dale _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On Wed, Oct 14, 2015 at 2:31 PM, Dale Henrichs <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Free forum by Nabble | Edit this page |