-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I noticed earlier tonight, after upgrading Fossil and rebuilding, that I couldn't update the fossil-scm.org repository anymore due to having an incompatible schema version. Seemed a bit odd, but I figured that if I recloned the repository and started over that all would be OK...except, not so much.
This is fossil version [5ac4e15182] 2011-02-02 01:09:06 UTC $ fossil clone http://fossil-scm.org fossil.foss il project-id: CE59BB9F186226D80E49D1FA2DB29F935CCA0333 server-id: 5d3d9b32f45ecf2e3790161d679a6e489b7e5089 admin-user: nolan (password is "c83464") $ mkdir trunk $ cd trunk $ fossil open ../fossil.fossil fossil: incorrect repository schema version fossil: you have version "2010-11-24" but you need version "2011-01-28" fossil: run "fossil rebuild" to fix this problem Am I missing something? Does the server need to use the same schema as the client? I figured they'd just exchange artifacts and let each handle the other's payload in whatever schema they had, but either that's not true or I'm missing something. Thanks. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1I/ZYACgkQIaMjFWMehWJ/ZwCfVk16F5Y/EvdlFxVBQDOMUYum gnsAn2aBNa7Fnls5eabsMV5EZLMCh5nw =SibI -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
