Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get wrong reference to load a package version such as '.1', '.11' developed by the same guy #187

Open
GoogleCodeExporter opened this issue Mar 24, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

I attached a document that explains the steps to reproduce the problem, the 
expected output and what I see instead.

The version of products we are using are:

GLASS version 3.0.1.

Pharo 1.0

ConfigurationOfGsMonticello-dkh.143
ConfigurationOfMetacello-dkh.675
ConfigurationOfGoferProjectLoader-DaleHenrichs.21
ConfigurationOfGsMonticello-dkh.143

Original issue reported on code.google.com by [email protected] on 6 Jan 2015 at 9:26

Attachments:

@GoogleCodeExporter
Copy link
Author

From what I can tell by looking at the cod, you are correct that Metacello 
should not be loading the .1 version of that package ...

This bug actually rings a bell and is likely to have been fixed in a newer 
version of Metacello ... since you are using GemStone, I would recommend that 
you make a backup of your system, and then load the latest version of Metacello 
using the following expression:

Gofer new
  package: 'GsUpgrader-Core';
  url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
  load.
(Smalltalk at: #GsUpgrader) upgradeMetacello.

I'm also tempted to ask you to upgrade to the latest version of GLASS using the 
following (this includes a Metacello upgrade):

Gofer new
  package: 'GsUpgrader-Core';
  url: 'http://ss3.gemtalksystems.com/ss/gsUpgrader';
  load.
(Smalltalk at: #GsUpgrader) upgradeGLASS.

Just to make sure that you are running with the latest version of GLASS as 
well, but I don't think that upgrading GLASS is required.

Once you've upgraded try the load again and let me know if it works. Make sure 
that you've got your Transcript open when you give this a try and if it doesn't 
work, attach the contents of the Transacript to this report ...

Original comment by [email protected] on 6 Jan 2015 at 10:06

  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant