same here, we got a method accidentally registered twice with monticello: - once in the package extension - once in the real category the only solution to get it back to normal, was an intermediate commit with said method being renamed |-( => can you open an issue? On 2012-11-28, at 06:22, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:

Hi,

we have got some problems with package extensions and merging of them during updates. This problems became evident in this issues: - http://code.google.com/p/pharo/issues/detail?id=6956 - http://code.google.com/p/pharo/issues/detail?id=7036

In the first one we several times tired to move the methods to the correct package. At the end we tried to remove them in a fixing slice but how can you see in the latest image, this methods are still there. This methods cause 5 of 6 test failures in the Pharo Kernel (the last one is the Undeclared test with 5 undeclared classes)

In the second issue the Form class methods are in the correct method category but as you may see in the Monticello browser, they are not in the Graphics-Files package. The Pharo Kernel shrinking removes packages with respect to method category and doesn't take an opinion of Monticello into account. So this methods are (correctly) removed during shrinking. But because they are not part of the Graphics-Files package by Monticello, they are not correctly loaded with the rest of the Morphic and thus the Jenkins job "Pharo Kernel 2.0 Reload by Monticello" is failing.

Cheers, -- Pavel