[BUG] Monticello remote repository

Avi Bryant avi at beta4.com
Mon May 5 21:01:27 UTC 2003


On Mon, 5 May 2003, Derek Brans wrote:

> Although Monticello versioning isn't being worked on (or used by many)
> right now, I've run into a bug that prevents me from using this
> otherwise very useful package.  Any advice would appreciated.

Let me just clarify here.  What you're describing below is a bug in a very
old version of Monticello.  Monticello as a project is definitely being
actively worked on.  The experimental feature that you're using
(Squeak-based remote repositories) has been dropped temporarily in an
effort to limit the scope and increase the usability of the package.
That feature (in fact, that entire version) was only ever intended as a
proof of concept, and I wasn't aware until this message that *anybody*
actually used it (I certainly never did).

My recommendation would be that you move to the newer versions of
Monticello, and use CVS as your remote repository for now.  If we get a
critical mass of people doing this, work on the core model should proceed
fairly quickly, and we can then look at bringing the fun stuff like
Squeak-based repositories back online.

If you would really prefer to keep using the old, pre-alpha version of
Monticello, go ahead, but I have no cycles available to support it...

Cheers,
Avi

> I get this error while commiting changes to a remote repository 75% of the time.
> It happens a minute or so after "accepting" the differences in the commit.
> It happens on the client side.





More information about the Squeak-dev mailing list