Open dalehenrich opened 4 years ago
a reload of the project seems to clear up the package corruption ...
this does not work ...
because of the way that Monticello is defined, there is no practical way to patch this particular bug ... it has been introduced during the bootstrapping process and the package Monticello.v3 in $GEMSTONE/seaside/monticello/repository/Monticello.v3-dkh.457.mcz in 3.5.3 ... which is part of the 3.5.x release ... so the best bet is to delete the packages. Here's an example using tODE:
mc delete Metacello
mc delete Tonel
Then using the project list, revert
the Metacello project to reload ...
This bug will be fixed in 3.5.4 and 3.6.0 ... (above patch will have to be used for 3.5.0, 3.5.1. and 3.5.2)
In Tode, when I look at the packages associated with Metacello project, I get some bogus entries (
Metacello ()
):while the list of packages extracted from the baseline is correct:
Things look correct in 3.4.5 and will need to track back to see where things have broken down ...