Issue 301 in glassdb: Upgrade from 1.0-beta.8 or 1.0-beta.8.1 to 1.0-beta.8.7 leaves dirty packages

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-1.0-beta.8

New issue 301 by [hidden email]: Upgrade from 1.0-beta.8 or  
1.0-beta.8.1 to 1.0-beta.8.7 leaves dirty packages
http://code.google.com/p/glassdb/issues/detail?id=301

ConfigurationOfGrease and ConfigurationOfMetacello are dirty but show no  
changes when compared to repository.

Monticello package doesn't show up dirty but many of the timestamps are not  
correct when compared to repository ... a revert of the package cleans  
things up.

The Monticello issue is probably related to the fact that Monticello itself  
is upgraded and the timestamp logic may have changed somewhat and with  
methods partially loaded during the upgrade, the timestamps for some  
methods are lost in the shuffle

Comment #1 on issue 301 by [hidden email]: Upgrade from 1.0-beta.8  
or 1.0-beta.8.1 to 1.0-beta.8.7 leaves dirty packages
http://code.google.com/p/glassdb/issues/detail?id=301

Looks like Core package has same incorrect timestamps as Monticello package

Comment #2 on issue 301 by [hidden email]: Upgrade from 1.0-beta.8  
or 1.0-beta.8.1 to 1.0-beta.8.7 leaves dirty packages
http://code.google.com/p/glassdb/issues/detail?id=301

Looks like you need to logout and login to get the system notification  
working corrrectly ....