On Fri, Oct 4, 2013 at 8:52 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> On Fri, Oct 4, 2013 at 6:27 AM, Ron Aaron <r...@ronware.org> wrote: > >> I have a large-ish repo, and after cloning it and updating some files, I >> try to commit ... and get this message. I did already try "fossil >> rebuild" to no effect. >> > > > eeek! It should never be possible that that happens _after_ a commit (if > it's going to happen it should fail during the before-commit checking). > Spoke too soon: it DID happen while committing, which means nothing is permanently broken :-D But that also means that the command i sent you won't work because rid 12892 gets rolled back. Hmmm... we might need you to add some printfs() to fossil to debug this one, unless there's a switch i'm unaware of to dump the manifest out before committing. What platform are you on? Is there any weird filename encoding in play (Windows/Mac)? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
