On Mar 26, 2018, at 1:27 PM, Scott Doctor <[email protected]> wrote: > > aborting due to prior errors
I’ve seen that sort of message on “fossil update” when a local file is marked read-only and the file was changed on the remote system. Obviously that is not exactly what is happening here, but the broader point is that if errors occur during a Fossil operation, the SQL-level COMMIT will be rolled back, which Fossil then takes as a cue to roll your local checkout directory back to *its* prior state. It might be simplest to make a clean checkout of the repository into a separate directory, copy all of the changed files over from the broken checkout, then check them in from the clean checkout directory. If that works, then I would look at local file permissions. You’re doing this on Windows, yes? > I tried to do a commit as I have not done so in a while Commit early, commit often! If you’re not yet ready to modify the trunk, do your work on a feature branch, then merge when the feature branch is stable. I’ve had work days with *dozens* of commits. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
