From: Dan Aloni <da-x@mo...> - 2005-10-04 18:35:43
On Tue, Oct 04, 2005 at 08:26:20PM +0200, Henry Nestler wrote:
> the monotone server is down.
> Please Dan, restart the server ;-)
Oh it seems someone has reseted the box and the daemon went off,
got it back again anyway.
da-x@..., da-x@..., da-x@...
From: Nuno Lucas <ntlucas@gm...> - 2005-10-05 07:26:43
On another note, with monotone 0.23 we're back to the problems we had
with 0.22. A user can't do the initial pull with 0.23, so we have to
make a colinux.db available for download for monotone.0.23 users.
The reason is that, due to bugs in earlier monotone versions, we ended
with a corrupted db, more exactly we have manifests with
"non-normalized" file paths (mixed relative and "absolute" paths that
point to the same file, like "README" and "./README").
As those problems started to be checked only with 0.22, we could get
away with a "db rebuild" on the server, which solved half the
problems. With 0.23 they do more checks on the database consistency,
and the only solution is a not yet implemented "db migrate" (or a
better/clever "db rebuild").
The solution of downloading the db and only then do update "pulls"
work because the corrupted manifests are from a long time ago and most
users will not try to do a "checkout" on those, only recent ones.
I've talked with njs from #monotone (one of the lead monotone
developers) and the solution may take some time. The fact is we are
the only project with that problem and a fix would imply a "db
migrate" for all other users, which they are trying to avoid until
they really need to (like when they will change the database internal
On 10/4/05, Dan Aloni <da-x@...> wrote:
> On Tue, Oct 04, 2005 at 08:26:20PM +0200, Henry Nestler wrote:
> > the monotone server is down.
> > Please Dan, restart the server ;-)
> Oh it seems someone has reseted the box and the daemon went off,
> got it back again anyway.