I don't know sometimes it happens when I click on the wrong repository on monticello browser. Then the selected package is not present on this uncorrect repository so it shows all method as deleted. (If it happened to you after a huge amount of time spent on working on Pharo it might be that :) )
What could also happen is if you ran a script to change package informations or classes data / category. Then if your script call the uncorrect class / RPackage method (like a method that does not trigger the proper announcement because internal method), there might be some problem with monticello packages. Lastly it can be a pharo bug ... then we would need a case to reproduce it to fix it... 2013/7/22 Norbert Hartl <[email protected]> > Opps, sorry, I was too shocked to give proper information > > The image is a #20599. And I was using the latest pharo vm. > > Norbert > > Am 22.07.2013 um 17:46 schrieb Camillo Bruni <[email protected]>: > > > that sounds evil... > > which pharo version? > > > > On 2013-07-22, at 17:44, Norbert Hartl <[email protected]> wrote: > >> I've discovered a strange effect. I don't know why it happened but I > want to save a modified package to a repository but looking at the > "changed" in monticello it showed every class and method has been deleted. > That is not true because the code is still there. Saving the package indeed > removed everything for the monticello package. So my image was fine but > loading the new package again removed all the code. > >> > >> Any ideas what might have gone wrong here? Or any ideas for a recheck > of changes? > >> > >> Norbert > > > > > > >
