I mean, the most probable reason for this is that some configuration refers some symbolic version like #stable, #bleedingEdge and that package was updated so that there is a new #stable version whose tests aren't green in Pharo and whose previous-version tests were all green. Cheers El mié, 23-03-2011 a las 13:26 +0100, Marcus Denker escribió:
On Mar 23, 2011, at 12:52 PM, Torsten Bergmann wrote:
Pharo 1.2 is red again!
DuplicatedVariableError: stylingActive is already defined in Workspace
https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/195/
We really need to make sure that the config does not load code if we don't explicitly say so.
So what code was changed? Why was it loaded?
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx