Pharo Issue Tracker - FogBugz (Fall [Issue]20447) Crosscutting and Misc - SystemVersion>>highestUpdate not initialized and nil

FogBugz Notification

	Torsten Bergmann opened Case 20447: SystemVersion>>highestUpdate not initialized and nil and assigned it to Everyone: Bug in Crosscutting and Misc: 1. Pharo Image • You are subscribed to this case

The code

SystemVersion current highestUpdate

unfortunately returns nil in Pharo 7.0.

In Pharo 6.0 this gives the latest full build number (for instance 60510).

Reason is simple: during the boostrap process the #highestUpdate: setter is not called/initialized
with the correct value and therefore the instance variable highestUpdate is nil then.

But this leads to several problems as highestUpdate number is used on several places in the
image and externally. Also some projects do not load anymore (for instance try to load Artefact
from catalog in Pharo 7 - the config of artefact is checking if the image is above a certain update
and loading crashes because of the nil value).

	Priority: 5 – Fix If Time		Status: Work Needed
	Assigned to: Everyone		Milestone: Pharo7.0

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want FogBugz notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker